CGA Prescribed Occurrence between the date of this agreement and 8.00am on the Second Court Date, ensure that no CGA Prescribed Occurrence occurs; and
CGA Prescribed Occurrence Sample Clauses
Related to CGA Prescribed 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>.
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.
Accidents and Dangerous Occurrences The Hirer must report all accidents involving injury to the public to a member of the Village Hall management committee as soon as possible and complete the relevant section in the Village Hall’s accident book. Any failure of equipment belonging to the Village Hall or brought in by the Hirer must also be reported as soon as possible. Certain types of accident or injury must be reported on a special form to the local authority. The Hall Secretary will give assistance in completing this form. This is in accordance with the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 1995 (RIDDOR).
Material Occurrences Promptly notify Agent in writing upon the occurrence of (a) any Event of Default or Default; (b) any event, development or circumstance whereby any financial statements or other reports furnished to Agent fail in any material respect to present fairly, in accordance with GAAP consistently applied, the financial condition or operating results of any Borrower as of the date of such statements; (c) any accumulated retirement plan funding deficiency which, if such deficiency continued for two plan years and was not corrected as provided in Section 4971 of the Code, could subject any Borrower to a tax imposed by Section 4971 of the Code; (d) each and every default by any Borrower which might result in the acceleration of the maturity of any Indebtedness, including the names and addresses of the holders of such Indebtedness with respect to which there is a default existing or with respect to which the maturity has been or could be accelerated, and the amount of such Indebtedness; and (e) any other development in the business or affairs of any Borrower which could reasonably be expected to have a Material Adverse Effect; in each case describing the nature thereof and the action Borrowers propose to take with respect thereto.
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.
What if a Prohibited Transaction Occurs If a “prohibited transaction”, as defined in Section 4975 of the Internal Revenue Code, occurs, the Xxxxxxxxx Education Savings Account could be disqualified. Rules similar to those that apply to Traditional IRAs will apply.
Notice of Event of Default If the Mortgagee shall have Actual Knowledge of an Event of Default or of a Default arising from a failure to pay Rent, the Mortgagee shall give prompt written notice thereof to the Owner Trustee, the Owner Participant, Lessee, and each Note Holder. Subject to the terms of Sections 2.13, 4.03, 4.04, 4.08, 5.02 and 5.03 hereof, the Mortgagee shall take such action, or refrain from taking such action, with respect to such Event of Default or Default (including with respect to the exercise of any rights or remedies hereunder) as the Mortgagee shall be instructed in writing by a Majority in Interest of Note Holders. Subject to the provisions of Section 5.03, if the Mortgagee shall not have received instructions as above provided within 20 days after mailing notice of such Event of Default to the Note Holders, the Mortgagee may, subject to instructions thereafter received pursuant to the preceding provisions of this Section 5.01, take such action, or refrain from taking such action, but shall be under no duty to take or refrain from taking any action, with respect to such Event of Default or Default as it shall determine advisable in the best interests of the Note Holders; PROVIDED, HOWEVER, that the Mortgagee may not sell the Aircraft or any Engine without the consent of a Majority in Interest of Note Holders. For all purposes of this Trust Indenture, in the absence of Actual Knowledge on the part of the Mortgagee, the Owner Trustee or the Owner Participant, the Mortgagee, the Owner Trustee or the Owner Participant, as the case may be, shall not be deemed to have knowledge of a Default or an Event of Default (except, in the case of the Mortgagee, the failure of Lessee to pay any installment of Basic Rent within one Business Day after the same shall become due, if any portion of such installment was then required to be paid to the Mortgagee, which failure shall constitute knowledge of a Default) unless notified in writing by Lessee, the Owner Trustee, the Owner Participant or one or more Note Holders.
Default under Specified Transaction The party, any Credit Support Provider of such party or any applicable Specified Entity of such party (1) defaults under a Specified Transaction and, after giving effect to any applicable notice requirement or grace period, there occurs a liquidation of, an acceleration of obligations under, or an early termination of, that Specified Transaction, (2) defaults, after giving effect to any applicable notice requirement or grace period, in making any payment or delivery due on the last payment, delivery or exchange date of, or any payment on early termination of, a Specified Transaction (or such default continues for at least three Local Business Days if there is no applicable notice requirement or grace period) or (3) disaffirms, disclaims, repudiates or rejects, in whole or in part, a Specified Transaction (or such action is taken by any person or entity appointed or empowered to operate it or act on its behalf);
Performance; No Default The Company shall have performed and complied with all agreements and conditions contained in this Agreement required to be performed or complied with by it prior to or at the Closing and after giving effect to the issue and sale of the Notes (and the application of the proceeds thereof as contemplated by Section 5.14) no Default or Event of Default shall have occurred and be continuing.
Happen After We Receive Your Letter When we receive your letter, we must do two things:
