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: {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}.{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 specified in Section 3 of Specification 4; ; 5.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”. 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 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}.{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-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 specified in Section 3 of Specification 4; ; 5.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”. 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-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-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-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 specified in Section 3 of Specification 4; ; 5.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”. 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-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: {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; "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. {#} 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-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-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 specified in Section 3 of Specification 4; ; (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 “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-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: : (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 specified in Section 3 of Specification 4; ; 5.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”. 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. 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 specified in Section 3 of Specification 4; ; (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 “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 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: : (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 specified in Section 3 of Specification 4; ; (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 “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”.

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-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 specified in Section 3 of Specification 4; ; (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 “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”.

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 specified in Section 3 of Specification 4; ; (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 “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”: {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}.{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-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 specified in Section 3 of Specification 4; ; 5.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”. 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-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: : (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 specified in Section section 3 of Specification 4; ; 5.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”. . 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. 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; “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. {#} 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: {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 2.1 of Specification 4Appendix 5A; "thick-{gurid}", if the data represents Thick Registration Data from a specific registrar, as defined in Section 2.2 of Appendix 5A. The {gurid} element must be replaced with the IANA Registrar ID associated with the data. {#} 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-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-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 specified in Section 3 of Specification 4; ; 5.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”. 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. 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-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 specified in Section 3 of Specification 4; ; 5.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”. . 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-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: : (1) “full”, if the data represents a Full Deposit; ; (2) “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; ; 5.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”. . 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. 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 specified in Section 3 of Specification 4; ; 5.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”. 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-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}.{extgTLD}_{YYYYMMMMDD}_{type}_S{#}_R{rev}.{ext} where: : 5.1. {gTLD} is replaced with the gTLD name; in case of an IDN-TLDIDNMTLD, the ASCII-ASCIIM compatible form (A-LabelAMLabel) must be used; ; 5.2. {YYYY-MM-DDYYYYMMMMDD} 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:00Z2009M08M02T00:00Z, the string to be used would be “2009-08-02M 08M02”; ; 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 specified in Section 3 of Specification 4; ; 5.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”. 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-quasiM 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-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 specified in Section 3 2 of Specification 4; Appendix 5; 5.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”. 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. Files will be named according to the following thefollowing 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 wouldbe “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 specified in Section 3 of Specification 4; ; 5.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”. 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. 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-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 specified in Section 3 2 of Specification 4; Appendix 5; 5.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”. 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-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-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 specified in Section 3 2 of Appendix 53 of Specification 4; ; (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 “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”.

File Naming Conventions. Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{extgTLD}_{YYYYLMMLDD}_{type}_S{#}_R{rev}.{ext} where: : 5.1. {gTLD} is replaced with the gTLD name; in case of an IDN-TLDIDNLTLD, the ASCII-compatible ASCIILcompatible form (A-LabelALLabel) must be used; ; 5.2. {YYYY-MM-DDYYYYLMMLDD} 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:00Z2009L08L02T00:00Z, the string to be used would be “2009-08-022009L08L02”; ; 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 specified in Section 3 of Specification 4; ; 5.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”. 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 quasiLhomonymous file. Otherwise it is replaced by “ryde”.

File Naming Conventions. Files will shall be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{extDD}_{FILE}_{type}_S{#}_R{rev}{.ext} where: : 4.1.1 {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-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 Error! Reference source not found. and 4.9; 4.1.4 {type} is replaced by: : (1) “full”, if the data represents a Full Deposit; full deposit; (2) “diffinc”, 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; an incremental deposit; 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.1.6 {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: : 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.

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-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 5.1 of Specification 4Appendix 5A; "thick-{gurid}", if the data represents Registration Data from a specific registrar, as defined in Section 5.2 of Appendix 5A. The {gurid} element must be replaced with the IANA Registrar ID associated with the data. {#} 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”: and {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.