File Naming Conventions. Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”; {type} is replaced by: “full”, if the data represents a Full Deposit; “diff”, if the data represents a Differential Deposit; “thin”, if the data represents a Bulk Registration Data Access file, as specified in Section 3 of Specification 4; {#} is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.
File Naming Conventions. Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where:
5.1 {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used;
5.2 {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”;
5.3 {type} is replaced by:
File Naming Conventions. Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where:
5.1. {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used;
5.2. {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”;
5.3. {type} is replaced by:
(1) “full”, if the data represents a Full Deposit;
(2) “diff”, if the data represents a Differential Deposit;
(3) “thin”, if the data represents a Bulk Registration Data Access file, as
(4) thick-{gurid}", if the data represent Thick Registration Data from a specific registrar, as defined in Section 3.2 of Specification 4. The {gurid} element must be replaced with the IANA Registrar ID associated with the data.
5.4. {#} is replaced by the position of the file in a series of files, beginning with
5.5. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”:
File Naming Conventions. Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where:
5.1. {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII- compatible form (A-Label) must be used;
5.2. {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009- 08-02”;
5.3. {type} is replaced by:
(1) “full”, if the data represents a Full Deposit;
(2) “diff”, if the data represents a Differential Deposit;
(3) “thin”, if the data represents a Bulk Registration Data Access file, as
5.4. {#} is replaced by the position of the file in a series of files, beginning with
5.5. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”:
5.6. {ext} is replaced by “sig” if it is a digital signature file of the quasi- homonymous file. Otherwise it is replaced by “ryde”.
File Naming Conventions. Each Produced PDF Paginated Document file will be named with the beginning Xxxxx Number. Each Produced TIFF image and corresponding text file shall be named with the unique Xxxxx Number of the page of document. In the event the Xxxxx Number contains a symbol and/or character that cannot be included in a file name, the symbol and/or character will be omitted from the file name.
File Naming Conventions. Files will be named according to the following convention:
5.1. {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII- compatible form (A-Label) must be used;
5.2. {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”;
File Naming Conventions. Files shall be named according to the following convention: <gTLD>_<YYYY-MM-DD>_<FILE>_<type>_<comp>_<encrypt>_S<#>_R<rev>.<ext> where:
4.1.1 <gTLD> is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-label must be used;
4.1.2 <YYYY-MM-DD> is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”;
4.1.3 <FILE> is replaced with the file type as indicated in 4.8 below;
4.1.4 <type> is replaced by:
(1) “full”, if the data represents a full deposit;
(2) “inc”, if the data represents an incremental deposit;
4.1.5 <comp> is replaced by the name of compression algorithm used, see section 4.10:
4.1.6 <encrypt> is replaced by the corresponding encryption algorithm used, see section 4.10:
4.1.7 <#> is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”.
4.1.8 <rev> is replaced by the number of revision (or resend) of the file beginning with “0”:
4.1.9 <ext> is replaced by “data” if the file contains actual data (may be compressed and/or encrypted) or “sig” for the digital signature file of the corresponding data file.
File Naming Conventions. Each document shall be uniquely identifiable together with its version. See the table below for the way to name files. Other document types should also follow this logic. File naming conventions: Deliverables D D[WP#].[D#]_[Short Title]_[version#]. [extension] D1.1_ProjectHandbookv1.0.doc Meeting Minutes MM MM_[type of meeting, e.g. EB or WPL#]_[YYYYMMDD ].[extension] MM_WPL_20191001.doc Presentation P P[WP#]_[Conference Title]_[version#].[ext ension] P3-XYconference- v1.ppt Periodic Report PR PR[period#]- [version#]. [extension] PR1-v0.0.doc
File Naming Conventions. Files shall be named according to the following convention: <{gTLD>}_<{YYYY-MM- DD>}_<{FILE>}_<{type>_<comp>_<encrypt>}_S<{#>}_R<{rev>}{.<ext>} where:
4.1.1 <{gTLD>} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-labelcompatible form (A-Label) must be used;
4.1.2 <{YYYY-MM-DD>} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”;
4.1.3 <{FILE>} is replaced with the file type as indicated in sections 4.8 belowand 4.9;
4.1.4 <{type>} is replaced by:
(1) “full”, if the data represents a full deposit;
(2) “inc”, if the data represents an incremental deposit;
4.1.5 <comp> is replaced by the name of compression algorithm used, see section 4.10:
4.1.6 <encrypt> is replaced by the corresponding encryption algorithm used, see section 4.10:
File Naming Conventions. Files uploaded to the FTPS server should conform to the following naming convention: *** *** Portions of this agreement marked by *** have been omitted pursuant to a request for confidential treatment. Omitted material for which confidential treatment has been requested has been filed separately with the Securities and Exchange Commission. ***
