Signature, Languages, Depositary Functions, Notifications Clause Samples

This clause outlines the procedures and requirements related to the signing of the agreement, the official languages in which it is executed, the responsibilities of the depositary (the entity that holds the official copy of the agreement), and the methods for issuing formal notifications among the parties. It typically specifies who is authorized to sign, which language versions are considered authentic, how the depositary manages the agreement and amendments, and how notifications such as ratifications or withdrawals are communicated. The core function of this clause is to ensure the agreement is properly executed, maintained, and communicated, thereby preventing misunderstandings and ensuring all parties are informed and bound by the same terms.
Signature, Languages, Depositary Functions, Notifications. (a) This Agreement shall be signed in a single original in the English and French languages, both texts (b) This Agreement shall remain open for signature at Vienna until December 31, 1973. (c) The original of this Agreement, when no longer open for signature, shall be deposited with the Director General. (2) Official texts shall be established by the Director General, after consultation with the interested Governments, in such other languages as the Assembly may designate. (a) The Director General shall transmit two copies, certified by him, of the signed text of this Agreement to the Governments of the countries that have signed it and, on request, to the Government of any other country. (b) The Director General shall transmit two copies, certified by him, of any amendment to this Agreement to the Governments of all countries of the Special Union and, on request, to the Government of any other country. (c) The Director General shall, on request, furnish the Government of any country that has signed this Agreement, or that accedes to it, with two copies of the Classification of Figurative Elements, certified by him, in the English or French language. (4) The Director General shall register this Agreement with the Secretariat of the United Nations. (5) The Director General shall notify the Governments of all countries party to the Paris Convention for the Protection of Industrial Property of: (i) signatures under paragraph (1); (ii) deposits of instruments of ratification or accession under Article 12(2); (iii) the date of entry into force of this Agreement under Article 13(1); (iv) declarations made under Article 4(5); (v) declarations and notifications made in accordance with Article 12(3); (vi) declarations made under Article 16(2); (vii) withdrawals of any declarations, notified under Article 16(3); (viii) acceptances of amendments to this Agreement under Article 11(3); (ix) the dates on which such amendments enter into force; (x) denunciations received under Article 15. 1. Pending the entry into force of the Vienna Agreement Establishing an International Classification of the Figurative Elements of Marks, a provisional Committee of Experts is hereby set up at the International Bureau of the World Intellectual Property Organization (WIPO). 2. The provisional Committee shall include a representative of each country having signed or acceded to the said Agreement. Intergovernmental organizations specialized in the field of marks, of which at least one of ...
Signature, Languages, Depositary Functions, Notifications a) This Agreement shall be signed in a single original in the English and French languages, both texts being equally authentic. b) This Agreement shall remain open for signature at Vienna until December 31, 1973. c) The original of this Agreement, when no longer open for signature, shall be deposited with the Director General. (2) Official texts shall be established by the Director General, after consultation with the interested Governments, in such other languages as the Assembly may designate. (3) a) The Director General shall transmit two copies, certified by him, of the signed text of this Agreement to the Governments of the countries that have signed it and, on request, to the Government of any other country.
Signature, Languages, Depositary Functions, Notifications. (a) This Act shall be signed in a single original in the English and French languages, both texts being equally authentic, and shall be deposited with the Director General. (b) Official texts of this Act shall be established by the Director General, after consultation with the interested Governments and within two months from the date of signature of this Act, in the two other languages, Russian and Spanish, in which, together with the languages referred to in subparagraph (a), authentic texts of the Convention Establishing the World Intellectual Property Organization were signed. (c) Official texts of this Act shall be established by the Director General, after consultation with the interested Governments, in the Arabic, German, Italian and Portuguese languages, and such other languages as the Assembly may designate. (2) This Act shall remain open for signature until December 31, 1977. (a) The Director General shall transmit two copies, certified by him, of the signed text of this Act to the Governments of all countries of the Special Union and, on request, to the Government of any other country. 第 14 条 署名、用語、寄託及び通報 (1)(a) この改正協定は、ひとしく正文である英語及びフランス語による本書1通について署名するものとし、事務局長に寄託する。 (b) 事務局長は、関係政府と協議の上、この改正協定の署名の日から2箇月以内に、(a)の言語とともに世界知的所有権機関を設立する条約の署名本書の言語であるロシア語及びスペイン語によるこの改正協定の公定訳文を作成する。 (c) 事務局長は、関係政府と協議の上、アラビア語、ドイツ語、イタリア語、ポルトガル語及び総会が指定する他の言語によるこの改正協定の公定 訳文を作成する。 (2) この改正協定は、1977 年 12 月 31 日まで、署名のために開放しておく。 (3)(a) 事務局長は、すべての同盟国政府に対し、及び要請があったときはその他の国の政府に対 し、この改正協定の署名本書の謄本2通を認証 して送付する。 (b) The Director General shall transmit two copies, certified by him, of any amendment to this Act to the Governments of all countries of the Special Union and, on request, to the Government of any other country. (4) The Director General shall register this Act with the Secretariat of the United Nations. (5) The Director General shall notify the Governments of all countries party to the Paris Convention for the Protection of Industrial Property of: (i) signatures under paragraph (1); (ii) deposits of instruments of ratification or accession under Article 9(3); (iii) the date of entry into force of this Act under Article 9(4)(a); (iv) acceptances of amendments to this Act under Article 8(3); (v) the dates on which such amendments enter into force; (vi) denunciations received under Article 12. (b) 事務局長は、すべての同盟国政府に対し、及び要請があったときはその他の国の政府に対 し、この改正協定の修正の謄本2通を認証して送付する。 (4) 事務局長は、この改正協定を国際連合事務局に登録する。 (5) 事務局長は、工業所有権の保護に関するパリ条約のすべての締約国政府に次の事項を通報す る。 (i) (1)の署名 (ii) 第9条(3)の批准書又は加入書の寄託 (...
Signature, Languages, Depositary Functions, Notifications a. This Act shall be signed in a single original in the English and French languages, both texts being equally authentic, and shall be deposited with the Director General. b. Official texts of this Act shall be established by the Director General, after consultation with the interested Governments and within two months from the date of signature of this Act, in the two other languages, Russian and Spanish, in which, together with the languages referred to in subparagraph (a), authentic texts of the Convention Establishing the World Intellectual Property Organization were signed. c. Official texts of this Act shall be established by the Director General, after consultation with the interested Governments, in the Arabic, German, Italian and Portuguese languages, and such other languages as the Assembly may designate. 2. This Act shall remain open for signature until December 31, 1977. 3. a. The Director General shall transmit two copies, certified by him, of the signed text of this Act to the Governments of all countries of the Special Union and, on request, to the Government of any other country.

Related to Signature, Languages, Depositary Functions, Notifications

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (b) With respect to renewal of domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-­‐Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (c) In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b). (d) Registry Operator shall provide public query-­‐based DNS lookup service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.

  • Per-­‐Registrar Transactions Report This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-­‐TLD, the A-­‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 02 iana-­‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in ▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/assignments/registrar-­‐ids 03 total-­‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-­‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-­‐adds-­‐1-­‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES