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.
View SourceView Similar (17)
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.
View SourceView Similar (15)
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 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.
View SourceView Similar (6)
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:
View SourceView Similar (3)
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.
View Source
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.
View Source

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.

  • 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.

  • Inspection of Reports The Depositary shall make available for inspection by holders of Receipts at the Corporate Office and at such other places as it may from time to time deem advisable during normal business hours any reports and communications received from the Company that are both received by the Depositary as the holder of deposited Preferred Stock and made generally available to the holders of the Preferred Stock. In addition, the Depositary shall transmit certain notices and reports to the holders of Receipts as provided in Section 5.05.

  • 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.