Registry Overview Sample Clauses

Registry Overview. NASS grants to Participant access to its Registry. Users authorized by NASS and the Vendor can upload qualified de-identified medical data in the Registry (the “Participant Data”), and access certain reports and aggregate data made available through the Technology. NASS and Vendor shall provide to the Participant certain implementation, training and support services as applicable. Participant shall comply with NASS policies and procedures related to use and access to the Registry, as may be developed and updated from time to time by NASS (the “Policies and Procedures”), along with any other such policies or rules developed by NASS or the Vendor. All of the Participant Data shall remain the Participant’s property, and NASS will only use it in accordance with the provisions of this Agreement. Should Participant wish to subscribe to a Vendor extended service offering they may do so at an additional cost, with the prior written approval of NASS. Such extended service offerings will require a separate agreement between a Participant and Vendor, which must be approved by NASS if such extended service offerings build on or are dependent upon participation in the Registry. In these cases, Vendor will handle data transfer into the NASS Registry at no additional cost to the Participant.
Sample 1
AutoNDA by SimpleDocs

Related to Registry Overview

  • Registry Operator has (i) ceased to conduct its business in the ordinary course; or (ii) filed for bankruptcy, become insolvent or anything analogous to any of the foregoing under the laws of any jurisdiction anywhere in the world; or

  • Registry Lock Registry Operator may offer the Registry Lock service, which is a registry service that allows an authorized representative from the sponsoring Registrar, request the activation or deactivation of any of the following EPP statuses: serverUpdateProhibited, serverDeleteProhibited and⁄or serverTransferProhibited. SPECIFICATION 1 CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.

  • Accreditation of Online Schools The District will implement a system of accrediting its online schools, as defined in section 22-30.7- 102(9.5), C.R.S. This system shall adhere to section 00-00-000, C.R.S., including a review of the online school’s alignment to the quality standards outlined in section 22-30.7-105(3)(b), C.R.S., and compliance with statutory or regulatory requirements, in accordance with section 22-30.7-103(3)(m), C.R.S.

  • Reservations for Registry Operations 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Obligations of Registry Operator to TLD Community Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-­‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • 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.

  • COVENANTS OF REGISTRY OPERATOR Registry Operator covenants and agrees with ICANN as follows:

  • Department of State Registration Consistent with Title XXXVI, F.S., the Contractor and any subcontractors that assert status, other than a sole proprietor, must provide the Department with conclusive evidence of a certificate of status, not subject to qualification, if a Florida business entity, or of a certificate of authorization if a foreign business entity.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!