Proposals for the amendment Sample Clauses

Proposals for the amendment of Articles 53(5), (9) and (11), 54, 55(4) to (8), 56, and 57, may be initiated by any State member of the Assembly, by the Executive Committee, or by the Director General.
AutoNDA by SimpleDocs

Related to Proposals for the amendment

  • The Amendment This Amendment has been duly and validly executed by an authorized executive officer of Borrower and constitutes the legal, valid and binding obligation of Borrower enforceable against Borrower in accordance with its terms.

  • Amendments and Waiver No modification of or amendment to this Agreement shall be valid or binding unless set forth in writing and duly executed by both of the parties hereto and no waiver of any breach of any term or provision of this Agreement shall be effective or binding unless made in writing and signed by the party purporting to give the same and, unless otherwise provided, shall be limited to the specific breach waived.

  • Effect of the Amendment The Agreement will be deemed amended to the extent herein provided, and, except as specifically amended hereby, will continue in full force and effect in accordance with its original terms. This Amendment supersedes any previous understandings, commitments, or representations whatsoever, whether oral or written, related to the subject matter of this Amendment. Both parties agree that this Amendment will constitute an integral, nonseverable part of the Agreement and be governed by its provisions, except that if the Agreement and this Amendment have specific provisions that are inconsistent, the specific provisions contained in this Amendment will govern.

  • Amendments; Consents and Waivers No modification, amendment or waiver of, or with respect to, any provision of this Agreement, and all other agreements, instruments and documents delivered thereto, nor consent to any departure by the Seller from any of the terms or conditions thereof shall be effective unless it shall be in writing and signed by each of the parties hereto, the written consent of the Indenture Trustee on behalf of the Noteholders is given and confirmation from each Rating Agency that such action will not result in a downgrade, withdrawal or qualification of any rating assigned to a Class of Notes is received. The Seller shall provide the Indenture Trustee and each Rating Agency with such proposed modifications, amendments or waivers. Any waiver or consent shall be effective only in the specific instance and for the purpose for which given. No consent to or demand by the Seller in any case shall, in itself, entitle it to any other consent or further notice or demand in similar or other circumstances. The Seller acknowledges that in connection with the intended assignment by the Depositor of all of its right, title and interest in and to each Timeshare Loan to the Issuer, the Issuer intends to issue the Notes, the proceeds of which will be used by the Issuer to purchase the Timeshare Loans from the Depositor under the terms of the Sale Agreement.

  • Amendments and Waivers (a) If the ICANN Board of Directors determines that an amendment to this Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment. (b) Prior to submitting a Special Amendment for Registry Operator Approval, ICANN shall first consult in good faith with the Working Group regarding the form and substance of such Special Amendment. The duration of such consultation shall be reasonably determined by ICANN based on the substance of the Special Amendment. Following such consultation, ICANN may propose the adoption of a Special Amendment by publicly posting such amendment on its website for no less than thirty (30) calendar days (the “Posting Period”) and providing notice of such proposed amendment to the Applicable Registry Operators in accordance with Section 7.9. ICANN will consider the public comments submitted on a Special Amendment during the Posting Period (including comments submitted by the Applicable Registry Operators). (c) If, within one hundred eighty (180) calendar days following the expiration of the Posting Period (the “Approval Period”), the ICANN Board of Directors approves a Special Amendment (which may be in a form different than submitted for public comment, but must address the subject matter of the Special Amendment posted for public comment, as modified to reflect and/or address input from the Working Group and public comments), ICANN shall provide notice of, and submit, such Special Amendment for approval or disapproval by the Applicable Registry Operators. If, during the sixty (60) calendar day period following the date ICANN provides such notice to the Applicable Registry Operators, such Special Amendment receives Registry Operator Approval, such Special Amendment shall be deemed approved (an “Approved Amendment”) by the Applicable Registry Operators, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Approved Amendment to Registry Operator (the “Amendment Effective Date”). In the event that a Special Amendment does not receive Registry Operator Approval, the Special Amendment shall be deemed not approved by the Applicable Registry Operators (a “Rejected Amendment”). A Rejected Amendment will have no effect on the terms and conditions of this Agreement, except as set forth below. (d) If the ICANN Board of Directors reasonably determines that a Rejected Amendment falls within the subject matter categories set forth in Section 1.2 of Specification 1, the ICANN Board of Directors may adopt a resolution (the date such resolution is adopted is referred to herein as the “Resolution Adoption Date”) requesting an Issue Report (as such term is defined in ICANN’s Bylaws) by the Generic Names Supporting Organization (the “GNSO”) regarding the substance of such Rejected Amendment. The policy development process undertaken by the GNSO pursuant to such requested Issue Report is referred to herein as a “PDP.” If such PDP results in a Final Report supported by a GNSO Supermajority (as defined in ICANN’s Bylaws) that either (i) recommends adoption of the Rejected Amendment as Consensus Policy or (ii) recommends against adoption of the Rejected Amendment as Consensus Policy, and, in the case of (i) above, the Board adopts such Consensus Policy, Registry Operator shall comply with its obligations pursuant to Section 2.2 of this Agreement. In either case, ICANN will abandon the Rejected Amendment and it will have no effect on the terms and conditions of this Agreement. Notwithstanding the foregoing provisions of this Section 7.6(d), the ICANN Board of Directors shall not be required to initiate a PDP with respect to a Rejected Amendment if, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject matter of such Rejected Amendment was the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation. (e) If (a) a Rejected Amendment does not fall within the subject matter categories set forth in Section 1.2 of Specification 1, (b) the subject matter of a Rejected Amendment was, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation, or (c) a PDP does not result in a Final Report supported by a GNSO Supermajority that either (A) recommends adoption of the Rejected Amendment as Consensus Policy or (B) recommends against adoption of the Rejected Amendment as Consensus Policy (or such PDP has otherwise been abandoned or terminated for any reason), then, in any such case, such Rejected Amendment may still be adopted and become effective in the manner described below. In order for the Rejected Amendment to be adopted, the following requirements must be satisfied: (i) the subject matter of the Rejected Amendment must be within the scope of ICANN’s mission and consistent with a balanced application of its core values (as described in ICANN’s Bylaws); (ii) the Rejected Amendment must be justified by a Substantial and Compelling Reason in the Public Interest, must be likely to promote such interest, taking into account competing public and private interests that are likely to be affected by the Rejected Amendment, and must be narrowly tailored and no broader than reasonably necessary to address such Substantial and Compelling Reason in the Public Interest; (iii) to the extent the Rejected Amendment prohibits or requires conduct or activities, imposes material costs on the Applicable Registry Operators, and/or materially reduces public access to domain name services, the Rejected Amendment must be the least restrictive means reasonably available to address the Substantial and Compelling Reason in the Public Interest; (iv) the ICANN Board of Directors must submit the Rejected Amendment, along with a written explanation of the reasoning related to its determination that the Rejected Amendment meets the requirements set out in subclauses (i) through (iii) above, for public comment for a period of no less than thirty (30) calendar days; and (v) following such public comment period, the ICANN Board of Directors must (a) engage in consultation (or direct ICANN management to engage in consultation) with the Working Group, subject matter experts, members of the GNSO, relevant advisory committees and other interested stakeholders with respect to such Rejected Amendment for a period of no less than sixty (60) calendar days; and (b) following such consultation, reapprove the Rejected Amendment (which may be in a form different than submitted for Registry Operator Approval, but must address the subject matter of the Rejected Amendment, as modified to reflect and/or address input from the Working Group and public comments) by the affirmative vote of at least two-­‐thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such eligibility, including ICANN’s Conflict of Interest Policy (a “Board Amendment”). Such Board Amendment shall, subject to Section 7.6(f), be deemed an Approved Amendment, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Board Amendment to Registry Operator (which effective date shall be deemed the Amendment Effective Date hereunder). Notwithstanding the foregoing, a Board Amendment may not amend the registry fees charged by ICANN hereunder, or amend this Section 7.6. (f) Notwithstanding the provisions of Section 7.6(e), a Board Amendment shall not be deemed an Approved Amendment if, during the thirty (30) calendar day period following the approval by the ICANN Board of Directors of the Board Amendment, the Working Group, on the behalf of the Applicable Registry Operators, submits to the ICANN Board of Directors an alternative to the Board Amendment (an “Alternative Amendment”) that meets the following requirements: (i) sets forth the precise text proposed by the Working Group to amend this Agreement in lieu of the Board Amendment; (ii) addresses the Substantial and Compelling Reason in the Public Interest identified by the ICANN Board of Directors as the justification for the Board Amendment; and (iii) compared to the Board Amendment is: (a) more narrowly tailored to address such Substantial and Compelling Reason in the Public Interest, and (b) to the extent the Alternative Amendment prohibits or requires conduct or activities, imposes material costs on Affected Registry Operators, or materially reduces access to domain name services, is a less restrictive means to address the Substantial and Compelling Reason in the Public Interest. Any proposed amendment that does not meet the requirements of subclauses (i) through

  • Amendments, Supplements and Waivers The Company and the Trustee may amend or supplement the Indenture or the Notes or waive compliance with any provision of the Indenture or the Notes in the manner, and subject to the terms, set forth in Section 7.05 and Article 8 of the Indenture.

  • Modifications, Amendments and Waivers This Agreement may not be modified or amended, or any provision thereof waived, except in a writing signed by all the parties to this Agreement.

  • Entire Agreement; Amendment and Waiver This Agreement constitutes the entire understanding of the parties hereto and supersedes all prior understanding among such parties. This Agreement may be amended, and the observance of any term of this Agreement may be waived, with (and only with) the written consent of the Company and the Holders holding a majority of the then outstanding Registrable Securities.

  • Entire Agreement; Amendments and Waivers This Agreement (including the schedules and exhibits hereto) represents the entire understanding and agreement between the parties hereto with respect to the subject matter hereof and can be amended, supplemented or changed, and any provision hereof can be waived, only by written instrument making specific reference to this Agreement signed by the party against whom enforcement of any such amendment, supplement, modification or waiver is sought. No action taken pursuant to this Agreement, including without limitation, any investigation by or on behalf of any party, shall be deemed to constitute a waiver by the party taking such action of compliance with any representation, warranty, covenant or agreement contained herein. The waiver by any party hereto of a breach of any provision of this Agreement shall not operate or be construed as a further or continuing waiver of such breach or as a waiver of any other or subsequent breach. No failure on the part of any party to exercise, and no delay in exercising, any right, power or remedy hereunder shall operate as a waiver thereof, nor shall any single or partial exercise of such right, power or remedy by such party preclude any other or further exercise thereof or the exercise of any other right, power or remedy. All remedies hereunder are cumulative and are not exclusive of any other remedies provided by law.

  • Consent and Waiver The Stockholder hereby gives any consents or waivers that are reasonably required for the consummation of the Merger under the terms of any agreements to which the Stockholder is a party or pursuant to any rights the Stockholder may have.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!