Concepts. The Agreement is adapted to the specific situation of non-commercial research sponsored by public funding. Its basic premise is that the Mutually Agreed Terms, as stipulated in CBD Art 15, are a bilateral contract con- cluded between providers and users, resulting from their fair negotiations on the terms of access and ben- efit sharing. Involved parties are encouraged to take account of each others specific needs and circumstances, reflect- ing on the type of envisaged research (e.g. ecological vs. phytopharmacological research) and the specifics of the research (e.g. difficulties in identifying taxa, sharing 4 INTRODUCTION 3 See: Swiss Academy of Sciences (2010) ABS Program 2003–2010. of material). For the provider, this may include means to monitor the use of genetic resources. We assumed the following basic scenario: ◾ The resources are accessed by a researcher under the lead and responsibility of a research institute. ◾ The research is non-commercial, aiming at providing publicly available results. The results have therefore to be published. ◾ Unexpected research results may trigger reflections towards their utilisation in a commercial context. ◾ Benefits are non-monetary as a rule. They usually accrue during the research process. ◾ Genetic resources might be transferred to third par- ties under a framework of customary cooperation by research institutes. The analysis of research types and access situations car- ried out by the ABS-team led to the following conclu- sions:
Concepts. 1. The Peace Agreements reflect a national consensus. They have been endorsed by the various sectors represented in the Assembly of Civil Society and outside it. Their progressive implementation must fulfil the legitimate aspirations of Guatemalans and, at the same time, unite the efforts of all behind these common objectives.
Concepts. □ Identify and describe major facility concepts including safety, security, sustainability, flexibility, community use, utilities, and any other issues or special considerations that impact space requirements and/or costs
Concepts. Recast No. 1, valid from 09/06/2021
Concepts. 6.1.1 Disclosing party, refers to the party providing the confidential information herein for the purpose of this Agreement.
Concepts. For the purposes of this Agreement:
Concepts. 1.1. Concerned: person to whom Personal Data relates.
Concepts. As of the Effective Date, the Parties have agreed on the Concepts for each Venue. As used herein, the Concept for the Signature Restaurant (as may be amended from time to time pursuant to the terms of this Agreement) is referred to herein as the “Signature Restaurant Concept,” the Concept for the Lobby Pub (as may be amended from time to time pursuant to the terms of this Agreement) is referred to herein as the “Lobby Pub Concept,” and the Concept for the Pool Bar (as may be amended from time to time pursuant to the terms of this Agreement) is referred to herein as the “Pool Bar Concept.” The Parties acknowledge and agree that: (a) Manager and/or any of its Affiliates shall own all rights, title and interest in and to the Signature Restaurant Concept (in such context, the “Manager Concepts”), and (b) Owner shall own all rights, title and interest in and to the Lobby Pub Concept and the Pool Bar Concept (collectively, the “Owner Concepts”). In the event Manager desires to materially modify any of the Manager Concepts, Manager shall present any such proposed modification(s) (along with any estimated costs in order to undertake any such modifications) to Owner for its review and approval, which approval may be granted by Owner in its sole discretion. Any change with respect to the Signature Restaurant Concept shall automatically be a Manager Concept.
Concepts. This protocol defines the following structure of Atom feeds published by a server to expose one or more collection(s) of semantic descriptions: An overview feed which lists the collections of semantic descriptions that the server manages a collection feed for each collection of semantic descriptions that each links to a corresponding snapshots feed and a corresponding fragments feed a snapshots feed for each collection. Each snapshot represents the state of a collection at point of time a fragments feed for each collection. Each fragment is created because it is the new representation of a topic that has changed. Semantic collections can be represented as topic maps or OWL-compliant RDF/XML. The protocol also specifies how a client should interpret and process these feeds in order to syndicate the server's semantic descriptions. A client that wishes to maintain a local semantic collection in sync with one held on the server first fetches the most recent snapshot for the required collection. It then subscribes to the feed of change fragments for that collection. This feed lists fragments of which each represent one or more changes in the underlying semantic collection. These fragments are created and an entry added to the feed when a topic is updated, added or deleted from the collection. The next time the client pulls the feed it updates its local collection with the new version of the topic.