Common use of Extensions Clause in Contracts

Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this Specification. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this Specification. ICANN and the respective Registry Operator shall work together to agree on such new objects’ data escrow specifications.

Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this SpecificationAppendix. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this SpecificationAppendix. ICANN and the respective Registry Operator shall work together to agree on such new objects’ data escrow specifications.

Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis base to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this Specification[1]. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this Specificationsection 3.1. ICANN and the respective Registry Operator shall work together to agree on such new objects’ data escrow specifications.

Extensions. If a Registry Operator ▇▇▇▇▇ offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this Specification. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section Section 3.1 of this Specification. ICANN cxDA and the respective Registry Operator ▇▇▇▇▇ shall work together to agree on such new objects’ data escrow specifications.

Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this SpecificationAppendix. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this SpecificationAppendix. ICANN and the respective Registry Operator shall work together to agree on such new objects’ data escrow specifications.

Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this SpecificationAppendix. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this SpecificationAppendix. ICANN and the respective Registry Operator shall work together to mutually agree on such new objects’ data escrow specificationsspecifications including those listed in Section 9, reference 6 of this Appendix.

Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this Specification. Appendix. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this Specification. Appendix. ICANN and the respective Registry Operator shall work together to agree on such new objects’ data escrow specifications.

Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this SpecificationAppendixSpecification. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this SpecificationAppendixSpecification. ICANN and the respective Registry Operator shall work together to agree on such new objects’ data escrow specifications.