NOTIFICATION OF PUBLIC EVENTS AND MEETINGS 2 A. CONTRACTOR shall notify ADMINISTRATOR of any public event or meeting funded in 3 whole or in part by the COUNTY, except for those events or meetings that are intended solely to serve 4 clients or occur in the normal course of business.
5 B. CONTRACTOR shall notify ADMINISTRATOR at least thirty (30) business days in advance 6 of any applicable public event or meeting. The notification must include the date, time, duration, 7 location and purpose of the public event or meeting. Any promotional materials or event related flyers 8 must be approved by ADMINISTRATOR prior to distribution. 9
Modification and Waivers The Indenture permits, with certain exceptions as therein provided (including, but not limited to the exceptions set forth in Section 15.11(i)), the amendment of the Indenture and the modification of the rights and obligations of the Issuer and the rights of the holders of the Notes under the Indenture at any time by the Issuer with the consent of the holders of not less than 66 2/3% in aggregate principal amount of the series of Notes of which this Note is a part then outstanding and all other Securities (as defined in the Indenture) then outstanding under the Indenture and affected by such amendment and modification. The Indenture also contains provisions permitting the holders of a majority in aggregate principal amount of the series of Notes of which this Note is a part then outstanding and all other Securities then outstanding under the Indenture and affected thereby, on behalf of the holders of all such Securities, to waive compliance by the Issuer with certain provisions of the Indenture and certain past defaults under the Indenture and their consequences. Any such consent or waiver by the holder of this Note shall be conclusive and binding upon such holder and upon all future holders of this Note and of any Note issued upon the registration of transfer hereof or in exchange herefor or in lieu hereof whether or not notation of such consent or waiver is made upon this Note. The determination of whether particular Securities are “outstanding” will be made in accordance with the Indenture. Any action by the holder of this Note shall bind all future holders of this Note, and of any Note issued in exchange or substitution hereof or in place hereof, in respect of anything done or permitted by the Issuer or by the Trustee in pursuance of such action. New Notes authenticated and delivered after the execution of any agreement modifying, amending or supplementing this Note may bear a notation in a form approved by the Issuer as to any matter provided for in such modification, amendment or supplement to the Indenture or the Notes. New Notes so modified as to conform, in the opinion of the Issuer, to any provisions contained in any such modification, amendment or supplement may be prepared by the Issuer, authenticated by the Trustee and delivered in exchange for this Note.
ADDITIONS AND DELETIONS The author of this document has added information needed for its completion. The author may also have revised the text of the original AIA standard form. An Additions and Deletions Report that notes added information as well as revisions to the standard form text is available from the author and should be reviewed. A vertical line in the left margin of this document indicates where the author has added necessary information and where the author has added to or deleted from the original AIA text. This document has important legal consequences. Consultation with an attorney is encouraged with respect to its completion or modification.
COMPLETION OF MEET AND NEGOTIATION 24.1 During the term of this Agreement, the Association expressly waives and relinquishes the right to meet and negotiate and agrees that the District shall not be obligated to meet and negotiate with respect to any subject or matter whether referred to or covered in this Agreement or not, even though each subject or matters may not have been within the knowledge or contemplation of either or both the District or the Association at the time they met and negotiated on and executed this Agreement, and even though such subjects or matters were proposed and later withdrawn.
Amendments, Modifications and Waivers No amendment, modification or waiver in respect of this Agreement shall be effective against any party unless it shall be in writing and signed by Parent, the Company and Stockholder.
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.
Execution of Amendments, Supplements or Waivers The Trustee shall sign any amendment, supplement or waiver authorized pursuant to this Article IX if the amendment, supplement or waiver does not adversely affect the rights, duties, liabilities or immunities of the Trustee. If it does, the Trustee may, but need not, sign it. In signing or refusing to sign such amendment, supplement or waiver, the Trustee shall be entitled to receive, and shall be fully protected in relying upon, an Officer’s Certificate and an Opinion of Counsel to the effect that the execution of such amendment, supplement or waiver has been duly authorized, executed and delivered by the Company and that, subject to applicable bankruptcy, insolvency, fraudulent transfer, fraudulent conveyance, reorganization, moratorium and other laws now or hereinafter in effect affecting creditors’ rights or remedies generally and to general principles of equity (including standards of materiality, good faith, fair dealing and reasonableness), whether considered in a proceeding at law or at equity, such amendment, supplement or waiver is a valid and binding agreement of the Company, enforceable against the Company in accordance with its terms.
Ratification and Confirmation of Agreement In the event of a conflict between the terms of this Amendment and the Agreement, it is the intention of the parties that the terms of this Amendment shall control and the Agreement shall be interpreted on that basis. To the extent the provisions of the Agreement have not been amended by this Amendment, the parties hereby confirm and ratify the 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
ADDITION, DELETION OR MODIFICATION OF FUNDS The Parties hereto may agree, from time to time, to add other Funds to provide additional funding media for the Contracts, or to delete, combine, or modify existing Funds, by amending Schedule A hereto. Upon such amendment to Schedule A, any applicable reference to a Fund, AVIF, or its Shares herein shall include a reference to any such additional Fund. Schedule A, as amended from time to time, is incorporated herein by reference and is a part hereof.
