Preparation of Files Containing Data Sets Sample Clauses

Preparation of Files Containing Data Sets. Each full data set consists of an XML document meeting the content and format requirements of Parts B and C of this document. Once the XML document is generated, the following preparation steps will be performed: a. The XML document will be placed in a file named according to the following convention: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day; in all cases a single-digit number should be left-padded with a zero). b. The Registry Operator may optionally specify to split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1GB each (except the final file). If files are split, an .MD5 file (produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors. The Registry Operator may optionally compress the document using the Unix GZIP command (or equivalent) to reduce the file size. c. The file(s) will then be encrypted and signed using PGP, version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the escrow file in addition to encrypting it.) An ICANN public key will be used for the encryption and the Registry Operator's private key will be used for the signature. Public keys will be exchanged between the Registry Operator and ICANN by e-mail, physical delivery of floppy diskettes or other agreed means.
Sample 1Sample 2Sample 3See All (17)
AutoNDA by SimpleDocs
Preparation of Files Containing Data Sets. Each full and incremental data set consists of an XML document meeting the content and format requirements of Parts B and C of this document. Once the XML document is generated, the following preparation steps will be performed: a. The XML document will be placed in a file named according to the following convention: For full data sets: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day; in all cases a single digit number should be left-padded with a zero). For incremental data sets: "wiYYMMDD" where "YYMMDD" follows the same format. b. The Registry Operator may optionally specify to split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1GB each (except the final file). If files are split, an MD5 file (produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors in case of transfer fault. The Registry Operator may optionally specify to compress the document using the Unix GZIP command (or equivalent) to reduce the file size. c. The file(s) will then be encrypted and signed using PGP, version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the escrow file in addition to encrypting it.) The Data Recipient's public key will be used for the encryption and the Registry Operator's private key will be used for the signature. Public keys will be exchanged between the Registry Operator and the Designated Recipient by e-mail, physical delivery of floppy diskettes, or other agreed means.
Sample 1Sample 2Sample 3See All (11)
Preparation of Files Containing Data Sets. Each full and incremental data set consists of an XML document meeting the content and format requirements of Parts B and C of this document. Once the XML document is generated, the following preparation steps will be performed: a. The XML document will be placed in a file named according to the following convention: For full data sets: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day; in all cases a single-digit number should be leftpadded with a zero). For incremental data sets: "wiYYMMDD" where "YYMMDD" follows the same format. b. The Registry Operator may optionally split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1GB each (except the final file). If files are split, an MD5 file (produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors in case of transfer fault. The Registry Operator may optionally compress the document using the Unix GZIP command (or equivalent) to reduce the file size. c. The file(s) will then be encrypted and signed using PGP, version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the escrow file in addition to encrypting it.) The Data Recipient's public key will be used for the encryption and the Registry Operator's private key will be used for the signature. Public keys will be exchanged between the Registry Operator and the Designated Recipient by e-mail, physical delivery of floppy diskettes, or other agreed means.
Sample 1Sample 2See All (10)
Preparation of Files Containing Data Sets. Each full data set consists of an XML document meeting the content and format requirements of Parts B and C of this document. Once the XML document is generated, the following preparation steps will be performed:
Sample 1Sample 2
Preparation of Files Containing Data Sets. Each full data set consists of an XML document meeting the content and format requirements of Parts B and C of this document. Once the XML document is generated, the following preparation steps will be performed: a. The XML document will be placed in a file named according to the following convention: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day; in all cases a single-digit number should be left-padded with a zero). b. The Sponsor may optionally specify to split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1GB each (except the final file). If files are split, an .MD5 file (produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors. The Sponsor may optionally compress the document using the Unix GZIP command (or equivalent) to reduce the file size. c. The file(s) will then be encrypted and signed using PGP, version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the escrow file in addition to encrypting it.) An ICANN public key will be used for the encryption and the Sponsor's private key will be used for the signature. Public keys will be exchanged between the Sponsor and ICANN by e-mail, physical delivery of floppy diskettes or other agreed means.
Sample 1
Preparation of Files Containing Data Sets. Each full data set consists of an XML document meeting the content and format requirements of Parts B and C of this document. Once the XML document is generated, the following preparation steps will be performed: a. The XML document will be placed in a file named according to the following convention: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day; in all cases a single-digit number should be left-padded with a zero). b. The Registry Operator, or its technical operator on its behalf, may optionally specify to split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1GB each (except the final file). If files are split, an .MD5 file (produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors. The Registry Operator may optionally compress the document using the Unix GZIP command (or equivalent) to reduce the file size. c. The file(s) will then be encrypted and signed using PGP, version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the escrow file in addition to encrypting it.) An ICANN public key will be used for the encryption and the Registry Operator's private key will be used for the signature. Public keys will be exchanged between the Registry Operator and ICANN by e-mail, physical delivery of floppy diskettes or other agreed means.
Sample 1

Related to Preparation of Files Containing Data Sets

  • Books, Records and Regulatory Filings (a) The Sub-Adviser agrees to maintain and to preserve for the applicable periods any such records as are required to be maintained by the Sub-Adviser with respect to the Fund by the 1940 Act and rules adopted thereunder, and by any other applicable laws, rules and regulations. The Sub-Adviser further agrees that all records that it maintains for the Fund are the property of the Fund and it will promptly surrender any of such records upon request; provided, however, that the Sub-Adviser may retain copies of such records for the applicable periods they are required by law to be retained, and thereafter shall destroy such records. (b) The Sub-Adviser agrees that it shall furnish to regulatory authorities having the requisite authority any information or reports in connection with its services hereunder that may be requested in order to determine whether the operations of the Fund are being conducted in accordance with applicable laws, rules and regulations. (c) The Sub-Adviser shall make all filings with the SEC required of it pursuant to Section 13 of the 1934 Act with respect to its duties as are set forth herein. The Sub-Adviser also shall make all required filings on Schedule 13D or 13G and Form 13F (as well as other filings triggered by ownership in securities under other applicable laws, rules and regulations) in respect of the Portfolio as may be required of the Fund due to the activities of the Sub-Adviser. The Sub-Adviser shall be the sole filer of Form 13F with respect to the Portfolio of the Fund.

  • Information Packages As soon as available and in any event not later than two (2) Business Days prior to each Settlement Date, an Information Package as of the most recently completed Fiscal Month.

  • Preparation of Reports The Servicer shall prepare and deliver such additional reports as required under this Servicing Agreement, including a copy of each Semi-Annual Servicer’s Certificate described in Section 4.01(c)(ii), the annual statements of compliance, attestation reports and other certificates described in Section 3.03 and the Annual Accountant’s Report described in Section 3.04. In addition, the Servicer shall prepare, procure, deliver and/or file, or cause to be prepared, procured, delivered or filed, any reports, attestations, exhibits, certificates or other documents required to be delivered or filed with the SEC (and/or any other Governmental Authority) by the Issuer or the Sponsor under the U.S. federal securities or other applicable laws or in accordance with the Basic Documents, including filing with the SEC, if applicable and required by applicable law, a copy or copies of (A) the Monthly Servicer’s Certificates described in Section 3.01(b)(i) (under Form 10-D or any other applicable form), (B) the Semi-Annual Servicer’s Certificates described in Section 4.01(c)(ii) (under Form 10-D or any other applicable form), (C) the annual statements of compliance, attestation reports and other certificates described in Section 3.03 and (D) the Annual Accountant’s Report (and any attestation required under Regulation AB) described in Section 3.04. In addition, the appropriate officer or officers of the Servicer shall (in its separate capacity as Servicer) sign the Sponsor’s annual report on Form 10-K (and any other applicable SEC or other reports, attestations, certifications and other documents), to the extent that the Servicer’s signature is required by, and consistent with, the U.S. federal securities laws and/or any other applicable law.

  • Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts.

  • How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.

  • COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.

  • Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA. (b) If applicable, once the transfer of PII has been accomplished in accordance with the EA’s written election to do so, Contractor agrees to return or destroy all PII when the purpose that necessitated its receipt by Contractor has been completed. Thereafter, with regard to all PII (including without limitation, all hard copies, archived copies, electronic versions, electronic imaging of hard copies) as well as any and all PII maintained on behalf of Contractor in a secure data center and/or cloud-based facilities that remain in the possession of Contractor or its Subcontractors, Contractor shall ensure that PII is securely deleted and/or destroyed in a manner that does not allow it to be retrieved or retrievable, read or reconstructed. Hard copy media must be shredded or destroyed such that PII cannot be read or otherwise reconstructed, and electronic media must be cleared, purged, or destroyed such that the PII cannot be retrieved. Only the destruction of paper PII, and not redaction, will satisfy the requirements for data destruction. Redaction is specifically excluded as a means of data destruction. (c) Contractor shall provide the EA with a written certification of the secure deletion and/or destruction of PII held by the Contractor or Subcontractors. (d) To the extent that Contractor and/or its subcontractors continue to be in possession of any de-identified data (i.e., data that has had all direct and indirect identifiers removed), they agree not to attempt to re-identify de-identified data and not to transfer de-identified data to any party.

  • Documents, Records, etc All documents, records, data, apparatus, equipment and other physical property, whether or not pertaining to Confidential Information, which are furnished to the Executive by the Company or are produced by the Executive in connection with the Executive’s employment will be and remain the sole property of the Company. The Executive will return to the Company all such materials and property as and when requested by the Company. In any event, the Executive will return all such materials and property immediately upon termination of the Executive’s employment for any reason. The Executive will not retain with the Executive any such material or property or any copies thereof after such termination.

  • Files and Records Within thirty (30) business days following the Closing Date, Seller shall deliver to Purchaser at Purchaser’s expense the Records, to the extent not previously delivered. For a period of seven (7) years after the Closing Date, Purchaser shall maintain the Records, and Seller shall have access thereto during normal business hours upon advance written notice to Purchaser to audit the same in connection with federal, state or local regulatory or tax matters, resolution of existing disputes or contract compliance matters affecting Seller.

  • Inspection of Property; Books and Records; Discussions Keep proper books of records and account in which full, true and correct entries in conformity with GAAP and all Requirements of Law shall be made of all dealings and transactions in relation to its business and activities; and permit representatives of any Lender (upon reasonable advance notice coordinated through the Administrative Agent) to visit and inspect any of its properties and examine and make abstracts from any of its books and records at any reasonable time and as often as may reasonably be desired and to discuss the business, operations, properties and financial and other condition of the Borrower and its Subsidiaries with officers and employees of the Borrower and its Subsidiaries and with its independent certified public accountants.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!