Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include: (a) accident, death or severe injury to any person; (b) damaged or dislodged fixed equipment; (c) flooding of Project Highway; and (d) any other unusual occurrence.
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 <xxxx://xxxxxxxx.xxxxx.xxx/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) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>. 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 <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Required Liability Insurance; Personal Property During the full term of the Housing Agreement, Resident agrees to obtain and maintain at Resident’s expense a policy of personal liability insurance (i.e., renter’s liability insurance) from a licensed insurance carrier in the United States, with coverage of at least $100,000 per occurrence at actual replacement cost, covering Owner’s losses of any kind arising from fire, smoke or water and caused by Resident’s negligence and/or by Resident’s animal. The liability insurance requirement and the existence or limits of any such insurance will not reduce or supersede Resident’s obligations under this Housing Agreement, except to the extent Owner charges and Resident pays for a waiver of this insurance requirement as provided below. Resident is not obligated to purchase insurance from any specific provider and may arrange its own personal liability insurance policy from any insurer of Resident’s choosing meeting the requirements of this paragraph, in which case Resident agrees to provide written proof of the required personal liability insurance coverage, including causing Owner and Manager to be listed as named interested parties on such insurance coverage, by mailing the proof of insurance to P.O. Box 18999, Atlanta, GA 31126-1399. Owner will provide instructions prior to move-in for submitting proof of insurance or purchasing a compliant insurance policy; Resident’s failure to comply with these insurance requirements will be a breach by Resident with Owner reserving its remedies but will not give Resident any right of termination. If Resident fails or chooses not to provide sufficient proof of compliant personal liability insurance to Owner by the Start Date, or if Resident’s insurance is cancelled during the term of this Housing Agreement, then Owner may, at its option, waive Resident’s obligation to provide such insurance and obtain its own coverage in Owner’s name for the same limited risks (up to $100,000 per occurrence from fire, smoke or water damage caused accidentally by Resident’s negligence and/or by Resident’s animal) at Owner’s expense; in such case, Resident agrees to pay as consideration for this waiver to $15.00 per installment as additional Rent during the remaining term of this Agreement, of which Owner would retain up to $5.00 per installment as an administrative fee and use the remaining portion to procure such insurance for itself. This waiver is not insurance, does not release Resident from liability for other damage or causes and does not cover Resident’s personal property. Owner strongly recommends that Resident maintain insurance covering Resident’s personal property or belongings, which Resident may elect to purchase. Neither Owner nor any of its employees, representatives or agents assumes any liability, directly or indirectly, for loss or damage to the personal property of Resident or others by fire, theft or any other cause. Any personal property remaining in the bedroom space and/or apartment at the end of the Term or after earlier termination of this Agreement will be considered abandoned by Resident and may be disposed of by Owner at the risk and expense of Resident, with Owner maintaining a landlord’s lien for unpaid rent as provided by law. Owner will not be liable or responsible for storage or disposition of the Resident’s personal property. If there are multiple individuals comprising Resident, then all references to and obligations of Resident in this paragraph 8 will apply to each such individual, separately.