Geographical Indications and Appellations of Origin Sample Clauses

Geographical Indications and Appellations of Origin. 1. Each Party shall ensure in its legal system adequate and effective means to protect geographical indications and appellations of origin in respect of any product, ina manner consistent with the TRIPS Agreement. 2. Each Party shall provide the means for any person, including natural persons and legal entities, or governmental entities of the other Party, to seek protection for geographical indications or appellations of origin. Each Party shall accept applications without requiring the intercession of the other Party on behalf of its persons. 3. Where a geographical indication or designation of origin protected under this Agreement is homonymous with the geographical name of a geographical area outside the territory of the Parties, each Party may permit its use to describe and present a spirit drink or aromatised drink from the geographical area to which the latter refers, provided that it has been used traditionally and consistently, its use for that purpose is regulated by the country of origin and the spirit drink or aromatised drink is not presented to consumers in a misleading manner as originating in the Party concerned. 4. Uruguay and Chile shall protect the geographical indications and appellations of origin listed in Annex 10.11 from the date of entry into force of this Agreement, and the geographical indications and appellations of origin listed in Annex 10.11.4 from the time each case is agreed upon by the Commission, for use on goods originating in accordance with the legal system of the Parties. 5. For the purposes of the implementation and operation of this Chapter, the Parties shall establish a Committee on Geographical Indications and Names of Origin (hereinafter referred to as the "Committee"). The Committee shall be composed of government representatives competent in intellectual property matters (2).
AutoNDA by SimpleDocs
Geographical Indications and Appellations of Origin. 1. Each Party shall recognize and protect the geographical indications and appellations of origin of the other Party, as established in this Article. 2. No Party shall permit the importation, manufacture or sale of a good that uses a geographical indication or appellation of origin protected in the other Party, unless it has been manufactured and certified therein, pursuant to its legislation applicable to that good. 3. Paragraphs 1 and 2 shall only have effect with respect to those geographical indications and appellations of origin protected by the domestic legislation of the Party that is claiming protection and the definition of which is consistent with Article 22 (1) of the Agreement on Trade-Related Aspects of Intellectual Property Rights. Further, to gain protection, each Party shall notify the other Party of the geographical indications or appellations of origin which, fulfilling the above-mentioned requirements, shall be considered within the scope of the protection. 4. All of the above shall be understood without prejudice to the recognition that the Parties may grant to homonymous geographical indications and appellations of origin that legitimately could belong to a non-Party.
Geographical Indications and Appellations of Origin. Article 16-38. Protection of Geographical Indications and Appellations of Origin. 1. Each Party shall protect geographical indications and appellations of origin, under the terms of its legislation. 2. In relation to geographical indications and appellations of origin, each Party shall establish the legal means for interested persons to prevent: a) the use of any means in the designation or presentation of the product that indicates or suggests that the product in question comes from a territory, region or locality other than the true place of origin, in such a way as to mislead the public as to the geographical origin of the product; and b) any other use that constitutes an act of unfair competition within the meaning of Article 10 bis of the Paris Convention. 3. The Parties shall, ex officio, if their legislation so permits, or at the request of an interested party, refuse or invalidate the registration of a trademark containing or consisting of a geographical indication or appellation of origin in respect of goods not originating in the territory indicated, if the use of such indication in the trademark for such goods in that Party is of such a nature as to mislead the public as to the true place of origin. 4. Paragraphs 2 and 3 shall apply to any geographical indication or appellation of origin which, while correctly indicating the territory, region or locality in which the goods originate, gives the public a false idea that the goods originate in another territory, region or locality. 5. With respect to geographical indications and appellations of origin, each Party shall establish the means to prevent the importation, manufacture or sale of a good that uses a geographical indication or appellation of origin protected in another Party, unless it has been produced and certified in that Party, in accordance with the laws, regulations and standards applicable to that good.
Geographical Indications and Appellations of Origin. Protection of Geographical Indications and Appellations of Origin.

Related to Geographical Indications and Appellations of Origin

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.

  • Territory 33.1 This Agreement applies to the territory in which CenturyLink operates as an ILEC in the State. CenturyLink shall be obligated to provide services under this Agreement only within this territory. 33.2 Notwithstanding any other provision of this Agreement, CenturyLink may terminate this Agreement as to a specific operating territory or portion thereof pursuant to Section 6.7 of this Agreement.

  • Country and Territory Names The country and territory names (including their IDN variants, where applicable) contained in the following internationally recognized lists shall be withheld from registration or allocated to Registry Operator at All Levels: the short form (in English) of all country and territory names contained on the ISO 3166-1 list, as updated from time to time, including the European Union, which is exceptionally reserved on the ISO 3166-1 list, and its scope extended in August 1999 to any application needing to represent the name European Union <xxxx://xxx.xxx.xxx/iso/support/country_codes/iso_3166_code_lists/iso-3166-1_decoding_table.htm>; the United Nations Group of Experts on Geographical Names, Technical Reference Manual for the Standardization of Geographical Names, Part III Names of Countries of the World; and the list of United Nations member states in 6 official United Nations languages prepared by the Working Group on Country Names of the United Nations Conference on the Standardization of Geographical Names; provided, that the reservation of specific country and territory names (including their IDN variants according to the registry operator IDN registration policy, where applicable) may be released to the extent that Registry Operator reaches agreement with the applicable government(s). Registry Operator must not activate such names in the DNS; provided, that Registry Operator may propose the release of these reservations, subject to review by ICANN’s Governmental Advisory Committee and approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Geographical Scope 1. Without prejudice to Annex IV, this Agreement shall apply: (a) to the land territory, internal waters, and the territorial sea of a Party and the air-space above the territory of a Party in accordance with international law; as well as (b) beyond the territorial sea, with respect to measures taken by a Party in the exercise of its sovereign rights or jurisdiction in accordance with international law. 2. Annex I applies with respect to Norway.

  • Geographic Scope The "Territory," which defines the geographic scope of the covenants contained in this Section 7, shall extend to and include all of the states (or foreign equivalent) in which the Company does business as M&A advisors or private placement equity advisors.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.

  • Monopolies and Exclusive Service Suppliers 1. Each Party shall ensure that any monopoly supplier of a service in its territory does not, in the supply of the monopoly service in the relevant market, act in a manner inconsistent with that Party's Schedule of specific commitments. 2. Where a Party's monopoly supplier competes, either directly or through an affiliated company, in the supply of a service outside the scope of its monopoly rights and which is subject to that Party's Schedule of specific commitments, the Party shall ensure that such a supplier does not abuse its monopoly position to act in its territory in a manner inconsistent with such commitments. 3. If a Party has reason to believe that a monopoly supplier of a service of the other Party is acting in a manner inconsistent with paragraphs 1 or 2 above, it may request that Party establishing, maintaining or authorising such supplier to provide specific information concerning the relevant operations. 4. The provisions of this Article shall also apply to cases of exclusive service suppliers, where a Party, formally or in effect: (a) authorises or establishes a small number of service suppliers; and (b) substantially prevents competition among those suppliers in its territory.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

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