Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1.
6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <▇▇▇▇▇://▇▇▇.▇▇▇-‐▇▇▇▇.▇▇▇/▇▇▇▇/▇▇▇▇/▇▇▇▇>.
6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released.
6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Certificate of Occupancy The Contractor’s obligation under the Contract is to install the Work in accordance with the Contract Documents, obtain the Certificate of Occupancy from the State Fire Marshal or his deputy, and forward it to the Design Professional as a part of the final close out procedures. The Design Professional’s obligation is to design the Work to comply with the applicable codes and to qualify for a Certificate of Occupancy.
Name Collision Occurrence Management 6.1. No-‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
Certificate of Occupancy; Licenses All certifications, permits, franchises, licenses, consents, authorizations, and approvals, including, certificates of completion and occupancy permits, required for the legal use, occupancy and operation of the Property have been obtained and are in full force and effect. The use being made of the Property is in conformity with the certificate of occupancy issued for the Property.
Notice to Proceed - Site Improvements The Recipient shall not commence, or cause to be commenced, any site improvements or other work on the Land until the Director has issued a Notice to Proceed to the Recipient. Such Notice to Proceed will not be issued until the Director is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and has completed any land acquisition required by the Project. A Notice to Proceed shall be required for all Project prime contractors or direct procurement initiated by the Recipient following execution of this Agreement.