Illness injury, or pregnancy-related condition of a member of the employee’s immediate family where the employee’s presence is reasonably necessary for the health and welfare of the employee or affected family member;
Illness or Disability If, because of Employee’s illness or other disability for a continuous period of more than 45 days, Employee is unable to render the services required by the Company as provided herein, the Company may terminate Employee’s employment hereunder by written notice to Employee at least 30 days in advance of such termination. Upon such termination Employee shall not be entitled to any further payments of any nature, except for payment of (a) any earned but unpaid Annual Base Salary, (b) any unpaid bonuses and (c) unreimbursed business expenses (collectively, “Payable Amounts”). All Payable Amounts shall become due and payable on the date of such termination.
Illness During Vacation (The following clause is applicable to full-time employees only)
Damage Near End of Term If at any time during the last six (6) months of the term of this Lease there is damage for which the cost to repair exceeds one month's Base Rent, whether or not an Insured Loss, Lessor may, at Lessor's option, terminate this Lease effective sixty (60) days following the date of occurrence of such damage by giving written notice to Lessee of Lessor's election to do so within thirty (30) days after the date of occurrence of such damage. Provided, however, if Lessee at that time has an exercisable option to extend this Lease or to purchase the Premises, then Lessee may preserve this Lease by (a) exercising such option, and (b) providing Lessor with any shortage in insurance proceeds (or adequate assurance thereof) needed to make the repairs on or before the earlier of (i) the date which is ten (10) days after Lessee's receipt of Lessor's written notice purporting to terminate this Lease, or (ii) the day prior to the date upon which such option expires. If Lessee duly exercises such option during such period and provides Lessor with funds (or adequate assurance thereof) to cover any shortage in insurance proceeds, Lessor shall, at Lessor's expense repair such damage as soon as reasonably possible and this Lease shall continue in full force and effect. If Lessee fails to exercise such option and provide such funds or assurance during such period, then this Lease shall terminate as of the date set forth in the first sentence of this Paragraph 9.5.
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).
Illness Leave Employees on an illness leave shall use all of their available entitlement time (i.e., vacation and paid or unpaid personal days) prior to using excused unpaid time.
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.
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>.
Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.
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.
