LineDisruptionEvent (Event Sample Clauses

LineDisruptionEvent (Event. This event is fired in case of line disruptions. It provides:  Id of the RailML Line representation  Starting time of the disruption  Time at which the disruption will end (for planned operations)  Reason of the disruption Disruption starting time and, possibly, ending time shall be used to calculate the width of the box that will represent the disruption itself. The geographical extension of the disruption (from the RailML ID) shall be used to xx- xxxxxxx the height of the box.
AutoNDA by SimpleDocs
LineDisruptionEvent (Event. It is the same event used by TG. The corresponding line on TD shall be marked as unavailable.

Related to LineDisruptionEvent (Event

  • Market Disruption Event Section 6.3(a) of the Equity Definitions is hereby replaced in its entirety by the following:

  • Adjustment events In the event the General Partner (i) declares or pays a dividend on any Class of its outstanding REIT Shares in REIT Shares or makes a distribution to all holders of any Class of its outstanding REIT Shares in REIT Shares, (ii) subdivides any Class of its outstanding REIT Shares, or (iii) combines any Class of its outstanding REIT Shares into a smaller number of REIT Shares with respect to any Class of REIT Shares, then a corresponding adjustment to the number of outstanding Partnership Units of the applicable Class necessary to maintain the proportionate relationship between the number of outstanding Partnership Units of such Class to the number of outstanding REIT Shares of such Class shall automatically be made. Additionally, in the event that any other entity shall become General Partner pursuant to any merger, consolidation or combination of the General Partner with or into another entity (the “Successor Entity”), the number of outstanding Partnership Units of each Class shall be adjusted by multiplying such number by the number of shares of the Successor Entity into which one REIT Share of such Class is converted pursuant to such merger, consolidation or combination, determined as of the date of such merger, consolidation or combination. Any adjustment to the number of outstanding Partnership Units of any Class shall become effective immediately after the effective date of such event retroactive to the record date, if any, for such event; provided, however, that if the General Partner receives a Notice of Redemption after the record date, but prior to the effective date of such dividend, distribution, subdivision or combination, or such merger, consolidation or combination, the number of outstanding Partnership Units of any Class shall be determined as if the General Partner had received the Notice of Redemption immediately prior to the record date for such dividend, distribution, subdivision or combination or such merger, consolidation or combination. If the General Partner takes any other action affecting the REIT Shares other than actions specifically described above and, in the opinion of the General Partner such action would require an adjustment to the number of Partnership Units to maintain the proportionate relationship between the number of outstanding Partnership Units to the number of outstanding REIT Shares, the General Partner shall have the right to make such adjustment to the number of Partnership Units, to the extent permitted by law, in such manner and at such time as the General Partner, in its sole discretion, may determine to be appropriate under the circumstances.

  • Adjustment event If an adjustment event arises in respect of a taxable supply made by a supplier under the Agreement, the amount payable by the recipient under clause 20.3 will be recalculated to reflect the adjustment event and a payment will be made by the recipient to the supplier or by the supplier to the recipient as the case requires.

  • Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”):

  • Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

  • Contact in Event of Unauthorized Transfer If you believe your Card and/or access code has been lost or stolen or that someone has transferred or may transfer money from your account without your permission, either call us immediately at:

  • Emergency Thresholds The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. Critical Function Emergency Threshold DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.

  • Authority Event of Default Any of the following events shall constitute an event of default by the Authority ("Authority Event of Default”), when not caused by a Developer Event of Default:

  • Whenever an Event of Default shall have happened and be subsisting, in addition to any other rights or remedies provided herein, the Note, by law or otherwise:

  • Developer Default Each of the following shall be an Event of Default by Developer:

Time is Money Join Law Insider Premium to draft better contracts faster.