Common use of File Naming Conventions Clause in Contracts

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}.{extgTLD}_{YYYY‐MM‐DD}_{type}_S{#}_R{rev}.{ext} where: 5.1. {gTLD} is replaced with the gTLD name; in case of an IDN-TLDIDN‐TLD, the ASCII-compatible ASCII‐compatible form (A-LabelA‐Label) must be used; 5.2. {YYYY-MM-DDYYYY‐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:00Z2009‐08‐02T00:00Z, the string to be used would be “2009-08-022009‐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 specified in Section 3.2 3 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 withwith “1”; in case of a lone file, this must be replaced by “1”. 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”.