Common use of File Naming Conventions Clause in Contracts

File Naming Conventions. Files will be named according to the following convention: 4.1 {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; 4.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.3 {type} is replaced by: (1) “full”, if the data represents a Full Deposit; (2) “diff”, if the data represents a Differential Deposit; 4.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”. 4.5 {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: 4.6 {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.

Appears in 1 contract

Sources: Registry Agreement

File Naming Conventions. Files will shall be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{FILE}_{type}_S{#}_R{rev}{.ext} where: 4.1 4.1.1 {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; 4.2 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.3 4.1.3 {FILE} is replaced with the file type as indicated in sections 4.8 and 4.9; 4.1.4 {type} is replaced by: (1) “full”, if the data represents a Full Depositfull deposit; (2) “diffinc”, if the data represents a Differential Depositan incremental deposit; 4.4 4.1.5 {#} 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.5 4.1.6 {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: 4.6 4.1.7 {ext.ext} is replaced by “sig.sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”” nothing.

Appears in 1 contract

Sources: Registry Agreement