Upon occurrence of the Sample Clauses

The "Upon occurrence of the" clause serves as a conditional trigger within a contract, specifying that certain rights, obligations, or actions become effective only when a particular event or circumstance takes place. In practice, this clause is often used to link contractual consequences to events such as a party's default, a change in law, or the achievement of a milestone. By clearly tying contractual effects to defined occurrences, this clause ensures that parties understand when specific provisions are activated, thereby reducing ambiguity and helping to manage risk.
Upon occurrence of the event provided in the head paragraph of this Clause, any of the Shareholders may request, by way of notice delivered to the other Shareholders, to PASA, AG TELECOM, Venus RJ Participações S.A., EDSP75, LF

Related to Upon occurrence of the

  • Occurrence of Default Any Transfer hereunder shall be subordinate and subject to the provisions of this Lease, and if this Lease shall be terminated during the term of any Transfer, Landlord shall have the right to: (i) treat such Transfer as cancelled and repossess the Subject Space by any lawful means, or (ii) require that such Transferee attorn to and recognize Landlord as its landlord under any such Transfer. If Tenant shall be in default under this Lease, Landlord is hereby irrevocably authorized, as Tenant’s agent and attorney-in-fact, to direct any Transferee to make all payments under or in connection with the Transfer directly to Landlord (which Landlord shall apply towards Tenant’s obligations under this Lease) until such default is cured. Such Transferee shall rely on any representation by Landlord that Tenant is in default hereunder, without any need for confirmation thereof by Tenant. Upon any assignment, the assignee shall assume in writing all obligations and covenants of Tenant thereafter to be performed or observed under this Lease. No collection or acceptance of rent by Landlord from any Transferee shall be deemed a waiver of any provision of this Article 14 or the approval of any Transferee or a release of Tenant from any obligation under this Lease, whether theretofore or thereafter accruing. In no event shall Landlord’s enforcement of any provision of this Lease against any Transferee be deemed a waiver of Landlord’s right to enforce any term of this Lease against Tenant or any other person. If Tenant’s obligations hereunder have been guaranteed, Landlord’s consent to any Transfer shall not be effective unless the guarantor also consents to such Transfer.

  • Transfer of Collateral upon Occurrence of Termination Event Upon the occurrence of a Termination Event and the Transfer to the Purchase Contract Agent of the Applicable Ownership Interest in Debentures, the Applicable Ownership Interest in the Treasury Portfolio or the Treasury Securities, as the case may be, underlying the Corporate Units and the Treasury Units pursuant to the terms of the Pledge Agreement, the Purchase Contract Agent shall request transfer instructions with respect to the Applicable Ownership Interest in Debentures, the Applicable Ownership Interest in the Treasury Portfolio or Treasury Securities, as the case may be, from each Holder by written request mailed to such Holder at its address as it appears in the Security Register. Upon book-entry transfer of the Corporate Units or Treasury Units or delivery of a Corporate Unit Certificate or Treasury Unit Certificate to the Purchase Contract Agent with such transfer instructions, the Purchase Contract Agent shall transfer the Applicable Ownership Interest in Debentures, the Applicable Ownership Interest in the Treasury Portfolio or Treasury Securities, as the case may be, underlying such Corporate Units or Treasury Units, as the case may be, to such Holder by book-entry transfer, or other appropriate procedures, in accordance with such instructions. In the event a Holder of Corporate Units or Treasury Units fails to effect such Transfer or delivery, the Applicable Ownership Interest in Debentures, the Applicable Ownership Interest in the Treasury Portfolio or Treasury Securities, as the case may be, underlying such Corporate Units or Treasury Units, as the case may be, and any interest thereon, shall be held in the name of the Purchase Contract Agent or its nominee in trust for the benefit of such Holder, until such Corporate Units or Treasury Units are transferred or the Corporate Unit Certificate or Treasury Unit Certificate is surrendered or such Holder provides satisfactory evidence that such Corporate Unit Certificate or Treasury Unit Certificate has been destroyed, mutilated, lost or stolen, together with any indemnity that may be required by the Purchase Contract Agent and the Company. In the case of the Treasury Portfolio or any Treasury Securities, the Purchase Contract Agent may dispose of the subject securities for cash and pay the applicable portion of such cash to the Holders in lieu of such Holders’ Applicable Ownership Interest in such Treasury Portfolio, or any Treasury Securities, where such Holder would otherwise have been entitled to receive less than $1,000 of any such security.

  • Absence of Events of Default Except for matters described in the SEC Documents and/or this Agreement, no Event of Default, as defined in the respective agreement to which the Company is a party, and no event which, with the giving of notice or the passage of time or both, would become an Event of Default (as so defined), has occurred and is continuing, which would have a Material Adverse Effect on the Company's business, properties, prospects, financial condition or results of operations.

  • 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>.

  • 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.