Reservations and Declarations Clause Samples

Reservations and Declarations. The first non-drafting elements that may limit the uniform application of the Conventions are reservations and declarations. Reservations are defined by the 1969 Vienna Convention as: […] a unilateral statement, however phrased or named, made by a State, when signing, ratifying, accepting, approving or acceding to a treaty, whereby it pur- ports to exclude or to modify the legal effect of certain provisions of the treaty in their application to that State.201 In substance, reservations allow each State to be part of an international convention with certain ad hoc adjustments. Declarations are not defined in the 1969 Vienna Convention. However, as discussed above,202 they can be considered as either disguised reservations or political statements with limited impact in international public law. It follows that if many different reservations and declarations were made admissible, they would undermine the whole purpose of the Conven- tions.203 During the 1929 Warsaw Conference, the possibility of allowing ▇▇▇▇▇- vations in the text was discussed. The delegate for Italy voiced the concern that such an inclusion would jeopardize the envisaged uniformity: 201 1969 Vienna Convention, Article 2(1)(d). 202 See, section 3.2.4.3(4). 203 On the effect of reservations, see, ▇▇▇▇▇▇▇ ▇▇▇▇, International Law 693 (8th edition, Cambridge University Press, 2017); ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇ ▇▇▇▇▇▇, Droit International Public 195-203 (8th edition, LGDJ). Il reste dans le procès-verbal que la Délégation italienne considère qu’une Con- vention pour unifier certaines règles ne peut insérer des réserves qui troublent précisément l’unification. En effet, s’il s’agit d’unifier on ne peut admettre que cette unification n’existe pas ou que cette unification soit boiteuse.204 It was however decided, given the purpose of uniformity, to refuse on principle any reservations unless specially allowed.205 Thus, the Additional Protocol to the 1929 Warsaw Convention only authorizes reservations with respect to State flights. Article 40 of the 1929 Warsaw Convention also authorizes High Contracting Parties to declare that said convention does not apply to all or any of its overseas territories. Similar provisions are found in the 1955 Hague Protocol.206 In the same vein, Article 56 of the 1999 Montreal Convention provides that States can submit a declaration if they have two or more territorial units in which different systems of law are applicable in relation to matters dealt with...
View SourceView Similar (4)
Reservations and Declarations. 1. No reservations may be made to this Convention but declarations authorised by Articles 39, 40, 50, 52, 53, 54, 55, 57, 58 and 60 may be made in accordance with these provisions. 2. Any declaration or subsequent declaration or any withdrawal of a declaration made under this Convention shall be notified in writing to the Depositary.
View SourceView Similar (2)
Reservations and Declarations. Although many human rights treaties do not allow reservations to be entered, and generally agree that reservations and declarations can compromise the goals and objectives of a treaty, Article 28, paragraph 2 of the CEDAW allows reservations and declarations to be formulated, as long as they are compatible with the goals of the convention. This article has led to problems with the convention’s implementation: the reservations effectively legitimate fragmentation of the convention, and grant prevalence to the sovereignty of the state.26 The article also gives each state free reign to decide whether or not these reservations and declarations are compatible with the goals of the convention. ▇▇▇▇▇▇▇ believes that this has led to 26 ▇▇▇▇▇▇, “Analysis of the State, Justifications, and Ratification of the CEDAW,” 51-52. an abuse of reservations. She also states that by formulating reservations and declarations, the states show their unwillingness to uphold their obligations to the convention. Morocco and other Arab states have entered reservations and declarations about some of the most fundamental articles of the convention text. Reservations formulated to article 2 allow states to free themselves of any obligation to adopt policies and measures that will put an end to discrimination against women.27 This jeopardizes the essential purpose of the convention: to eliminate all forms of discrimination against women.
View Source
Reservations and Declarations. The UK and the Signatory Andean Countries have made a political declaration on the future trading relationship between the UK and the Signatory Andean Countries. They have also made joint declarations to aid the operation and interpretation of the UK-Andean Countries Trade Agreement.
View Source
Reservations and Declarations. 1. By a written notification addressed to the Secretary General of the Council of Europe, any Party to the Convention may, at the time of signature of this Protocol or when depositing its instrument of ratification, acceptance or approval, declare that it avails itself of the reservation(s) provided for in Articles 7, paragraphs 9.a and 9.b, Article 8, paragraph 13, and Article 17 of this Protocol. No other reservations may be made. 2. By a written notification addressed to the Secretary General of the Council of Europe, any Party to the Convention may, at the time of signature of this Protocol or when depositing its instrument of ratification, acceptance or approval, make the declaration(s) identified in Articles 7, paragraphs 2.b and 8; Article 8, paragraph 11; Article 9, paragraphs l.b and 5; Article 10, paragraph 9; Article 12, paragraph 3; and Article 18, paragraph 2, of this Protocol. 3. By a written notification addressed to the Secretary General of the Council of Europe, any Party to the Convention shall make any declaration(s), notifications or communications identified in Article 7, paragraphs 5.a and e; Article 8, paragraphs 4, and 10.a and b; Article 14, paragraphs 7.c and 10.b; and Article 17, paragraph 2, of this Protocol according to the terms specified therein.
View Source
Reservations and Declarations. 1. No reservations or exceptions may be made to this Agreement. 2. Paragraph 1 does not preclude a State, when signing, ratifying, accepting or approving this Agreement, from making declarations or statements, however phrased or named, with a view, inter alia, to the harmonization of its laws and regulations with the provisions of this Agreement, provided that such declarations or statements do not purport to exclude or to modify the legal effect of the provisions of this Agreement in their application to that State.
View Source

Related to Reservations and Declarations

  • Exceptions and Reservations There are excepted and reserved from the demise in favour of the Lessor and all others now entitled or who may become entitled: - the free and uninterrupted passage and running of water sewage electricity telephone and other services or supplies from and to other parts of the Property and the Building in and through the Pipes which now are or may after the date of this Lease during the Term be in under or over the Premises; the right to construct and to maintain in on under or over the Premises at any time during the Term any Pipes for the benefit of any part of the land and the Building; the right at any time during the term and upon reasonable notice except in cases of emergency to enter the Premises: - to inspect the condition and state of repair of the Premises; to inspect cleanse connect or to repair remove replace with others alter or execute any works whatever to or in connection with the Pipes easements or services referred to in Clause 2.3 (a) and 2.3 (b); to view the state and condition of and repair and maintain the Premises and any other buildings erected on the land after the date of this Lease; to carry out work or do anything whatsoever comprised within the Lessor’s obligations within this Lease; to take schedules or inventories of fixtures fittings and other items to be yielded up on the expiry of the Term; to exercise any of the rights granted to the Lessor by this Lease; the right to erect scaffolding for the purpose of inspecting repairing or cleaning the Premises and the Building after the date of this Lease notwithstanding that such scaffolding may temporarily restrict the access to or use and enjoyment of the Premises; the rights of light air support shelter protection and all other easements and rights now or after the date of this Lease belonging to or enjoyed by other parts of the Premises and any adjoining property owned by or in the possession of the Lessor; and the right to reasonable access to the Premises for the purpose of cleaning and maintaining in good repair and condition the lifts (if any) that open into the Premises.

  • Reservations and Exceptions 1. Articles 3, 4, 6 and 12 shall not apply to: (a) Any existing non-conforming measure that is maintained by: (i) With respect to Japan: (A) The central government or a prefecture, as set out in its Schedule in Annex I; or (B) A local government other than prefectures; (ii) With respect to the Republic of Peru: (A) The central government or a regional government, as set out in its Schedule in Annex I; or (B) A local government (b) The continuation or prompt renewal of any non-conforming measure referred to in subparagraph (a); or (c) An amendment or modification to any non-conforming measure referred to in subparagraph (a), provided that the amendment or modification does not decrease the conformity of the measure as it existed immediately before the amendment or modification, with Articles 3, 4, 6 and 12. 2. Articles 3, 4, 6 and 12 shall not apply to any measure that a Contracting Party adopts or maintains with respect to sectors, sub-sectors and activities set out in its Schedule in Annex II. 3. Neither Contracting Party shall, under any measure adopted after the date of entry into force of this Agreement and covered by its Schedule in Annex II, require an investor of the other Contracting Party, by reason of its nationality, to sell or otherwise dispose of an investment that exists at the time the measure becomes effective. 4. In cases where a Contracting Party makes an amendment or a modification to any existing non-conforming measure set out in its Schedule in Annex I or where a Contracting Party adopts any new or more restrictive measure with respect to sectors, sub-sectors or activities set out in its Schedule in Annex II after the entry into force of this Agreement, the Contracting Party shall, prior to the implementation of the amendment or modification or the new or more restrictive measure, or in exceptional circumstances, as soon as possible thereafter: (a) Notify the other Contracting Party of detailed information on such amendment, modification or measure; and (b) Hold, upon request by the other Contracting Party, consultations in good-faith with that other Contracting Party. 5. Each Contracting Party shall endeavour, where appropriate, to reduce or eliminate the reservations specified in its Schedules in Annexes I and II respectively. 6. Articles 3, 4, 6 and 12 shall not apply to any measure covered by the exceptions to, or derogations from, obligations under Articles 3 and 4 of the TRIPS Agreement, as specifically provided in Articles 3 through 5 of the TRIPS Agreement. 7. Articles 3, 4, 6 and 12 shall not apply to any measure that a Contracting Party adopts or maintains with respect to government procurement.

  • Limitations and Restrictions Deduction of Rollovers and Transfers – A deduction is not allowed for rollover or transfer contributions.

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

  • 6Amendments 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 (iii) in the immediately preceding sentence shall not be considered an Alternative Amendment hereunder and therefore shall not supersede or delay the effectiveness of the Board Amendment. If, following the submission of the Alternative Amendment to the ICANN Board of Directors, the Alternative Amendment receives Registry Operator Approval, the Alternative Amendment shall supersede the Board Amendment and shall be deemed an Approved Amendment hereunder (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 Alternative Amendment to Registry Operator, which effective date shall deemed the Amendment Effective Date hereunder), unless, within a period of sixty (60) calendar days following the date that the Working Group notifies the ICANN Board of Directors of Registry Operator Approval of such Alternative Amendment (during which time ICANN shall engage with the Working Group with respect to the Alternative Amendment), the ICANN Board of Directors 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, rejects the Alternative Amendment. If (A) the Alternative Amendment does not receive Registry Operator Approval within thirty (30) calendar days of submission of such Alternative Amendment to the Applicable Registry Operators (and the Working Group shall notify ICANN of the date of such submission), or (B) the ICANN Board of Directors rejects the Alternative Amendment by such two-thirds vote, the Board Amendment (and not the Alternative Amendment) 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 to Registry Operator (which effective date shall deemed the Amendment Effective Date hereunder). If the ICANN Board of Directors rejects an Alternative Amendment, the board shall publish a written rationale setting forth its analysis of the criteria set forth in Sections 7.6(f)(i) through 7.6(f)(iii). The ability of the ICANN Board of Directors to reject an Alternative Amendment hereunder does not relieve the Board of the obligation to ensure that any Board Amendment meets the criteria set forth in Section 7.6(e)(i) through 7.6(e)(v). (g) In the event that Registry Operator believes an Approved Amendment does not meet the substantive requirements set out in this Section 7.6 or has been adopted in contravention of any of the procedural provisions of this Section 7.6, Registry Operator may challenge the adoption of such Special Amendment pursuant to the dispute resolution provisions set forth in Article 5, except that such arbitration shall be conducted by a three-person arbitration panel. Any such challenge must be brought within sixty (60) calendar days following the date ICANN provided notice to Registry Operator of the Approved Amendment, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. The Approved Amendment will be deemed not to have amended this Agreement during the pendency of the dispute resolution process. (h) Registry Operator may apply in writing to ICANN for an exemption from the Approved Amendment (each such request submitted by Registry Operator hereunder, an “Exemption Request”) during the thirty (30) calendar day period following the date ICANN provided notice to Registry Operator of such Approved Amendment. Each Exemption Request will set forth the basis for such request and provide detailed support for an exemption from the Approved Amendment. An Exemption Request may also include a detailed description and support for any alternatives to, or a variation of, the Approved Amendment proposed by such Registry Operator. An Exemption Request may only be granted upon a clear and convincing showing by Registry Operator that compliance with the Approved Amendment conflicts with applicable laws or would have a material adverse effect on the long-term financial condition or results of operations of Registry Operator. No Exemption Request will be granted if ICANN determines, in its reasonable discretion, that granting such Exemption Request would be materially harmful to registrants or result in the denial of a direct benefit to registrants. Within ninety (90) calendar days of ICANN’s receipt of an Exemption Request, ICANN shall either approve (which approval may be conditioned or consist of alternatives to or a variation of the Approved Amendment) or deny the Exemption Request in writing, during which time the Approved Amendment will not amend this Agreement. If the Exemption Request is approved by ICANN, the Approved Amendment will not amend this Agreement; provided, that any conditions, alternatives or variations of the Approved Amendment required by ICANN shall be effective and, to the extent applicable, will amend this Agreement as of the Amendment Effective Date. If such Exemption Request is denied by ICANN, the Approved Amendment will amend this Agreement as of the Amendment Effective Date (or, if such date has passed, such Approved Amendment shall be deemed effective immediately on the date of such denial), provided that Registry Operator may, within thirty (30) calendar days following receipt of ICANN’s determination, appeal ICANN’s decision to deny the Exemption Request pursuant to the dispute resolution procedures set forth in Article 5. The Approved Amendment will be deemed not to have amended this Agreement during the pendency of the dispute resolution process. For avoidance of doubt, only Exemption Requests submitted by Registry Operator that are approved by ICANN pursuant to this Section 7.6(j), agreed to by ICANN following mediation pursuant to Section 5.1 or through an arbitration decision pursuant to Section 5.2 shall exempt Registry Operator from any Approved Amendment, and no Exemption Request granted to any other Applicable Registry Operator (whether by ICANN or through arbitration) shall have any effect under this Agreement or exempt Registry Operator from any Approved Amendment. (i) Except as set forth in this Section 7.6, Section 7.7 and as otherwise set forth in this Agreement and the Specifications hereto, no amendment, supplement or modification of this Agreement or any provision hereof shall be binding unless executed in writing by both parties, and nothing in this Section 7.6 or Section 7.7 shall restrict ICANN and Registry Operator from entering into bilateral amendments and modifications to this Agreement negotiated solely between the two parties. No waiver of any provision of this Agreement shall be binding unless evidenced by a writing signed by the party waiving compliance with such provision. No waiver of any of