DOMAIN NAME SPECIFIC CONDITIONS Sample Clauses

DOMAIN NAME SPECIFIC CONDITIONS. If the Order is a .INFO domain name, the Registrant, must also agree to the following terms:
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
DOMAIN NAME SPECIFIC CONDITIONS. If the Order is a .CLUB domain name, the Registrant agrees to the following terms:
Sample 1Sample 2Sample 3See All (6)
DOMAIN NAME SPECIFIC CONDITIONS. If the Order is a .UK domain name, the Registrant, must also agree to the following terms:
Sample 1Sample 2
DOMAIN NAME SPECIFIC CONDITIONS. If the Order is a .PW domain name, the Registrant, must also agree to the following terms:
Sample 1Sample 2
DOMAIN NAME SPECIFIC CONDITIONS. If the Order is a .NAME Defensive Registration, the Registrant, must also agree to the following terms:
Sample 1
DOMAIN NAME SPECIFIC CONDITIONS. If the Order is a .PRO domain name, the Registrant, must also agree to the following terms: You are aware that registering a .PRO domain name, involves you contracting with RegistryPro, and agreeing to their Terms and Conditions of Domain Name Registration available on their website at xxxx://xxxxxxxx.xxx/legal/user-terms
Sample 1

Related to DOMAIN NAME SPECIFIC CONDITIONS

  • Specific Conditions If applicable, specific conditions required after a risk assessment will be included in Exhibit G. Grantee shall adhere to the specific conditions listed therein.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

Time is Money Join Law Insider Premium to draft better contracts faster.