Title Registration and Cape Town Provisions
Title Registration and Cape Town Provisions Sample Clauses
Related to Title Registration and Cape Town Provisions
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Limitations on Subsequent Registration Rights From and after the date of this Agreement, the Company shall not, without the prior written consent of Holders holding a majority of the Registrable Securities enter into any agreement with any holder or prospective holder of any securities of the Company giving such holder or prospective holder any registration rights the terms of which are pari passu with or senior to the registration rights granted to the Holders hereunder.
Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Expenses of Registration All expenses incurred in connection with registrations, filings or qualifications pursuant to Sections 2 and 3, including, without limitation, all registration, listing and qualifications fees, printers, legal and accounting fees shall be paid by the Company.
Installation and Use Rights You may install and use any number of copies of the software on your devices.
LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.
Registration of Physical Location Required For each phone number that you use for the Service, you must register with VoicePro the physical location where you are using a Device with the Service with that phone number. Each time you move the Device to another location, you must register that new location. If you do not register that new location, any call you make using the 911 Dialing feature may be sent to an emergency center near the previously registered address. You will register your initial location of use when you subscribe to the Service. Thereafter, you may register a new location by following the instructions from the “911″ registration link on the VoicePro web account dashboard features page if applicable. For purposes of the 911 Dialing feature, you may only register one location at a time for each phone line you use for a Device with the Service.
Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]
Registration Procedures In connection with the Company’s registration obligations hereunder, the Company shall:
