Licensing Terminology Sample Clauses

Licensing Terminology. Instance. You create an “instance” of the software by executing the software’s setup or install procedure. You also create an instance of the software by duplicating an existing instance. References to the “software” in this agreement include “instances” of the software. • Run an Instance. You “run an instance” of the software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory.
AutoNDA by SimpleDocs
Licensing Terminology. Instance. You create an “instance” of the software by executing the software’s setup or install procedure. You also create an instance of the software by duplicating an existing instance. References to the “software” in this agreement include “instances” of the software. • Run an Instance. You “run an instance” of the software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory. • Operating System Environment (“OSE”). An “operating system environment” or “OSE” is
Licensing Terminology. Instance. You create an “instance” of the software by executing the software’s setup or install procedure. You also create an instance of the software by duplicating an existing instance. References to the “software” in this agreement include “instances” of the software. • Operating System Environment (OSE). An “operating system environment” or “OSE” is: (i) all or part of an operating system instance, or all or part of a virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights; and (ii) instances of applications, if any, configured to run on the operating system instance or parts identified above. A virtual operating system environment is configured to run on a virtual (or otherwise emulated) hardware system. • Server. A server is a physical hardware system capable of running server software. A hardware partition or blade is considered to be a separate physical hardware system. • Hardware Thread. A hardware thread is either a physical core or a hyper-thread in a physical processor. • Virtual Core. A virtual core is the unit of processing power in a virtual (or otherwise emulated) hardware system. A virtual core is the virtual representation of one or more hardware threads. Virtual OSEs use one or more virtual cores.
Licensing Terminology. Instance. You create an “instance” of software by executing the software's setup or install procedure. You also create an instance of software by duplicating an existing instance. References to software in this agreement include “instances” of the software. • Run an Instance. You “run an instance” of software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory. • Operating System Environment. An “operating system environment” is • all or part of an operating system instance, or all or part of a virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and • instances of applications, if any, configured to run on the operating system instance or parts identified above. There are two types of operating system environments, physical and virtual. A physical operating system environment is configured to run directly on a physical hardware system. The operating system instance used to run hardware virtualization software (e.g. Microsoft Virtual Server or similar technologies) or to provide hardware virtualization services (e.g. Microsoft virtualization technology or similar technologies) is considered part of the physical operating system environment. A virtual operating system environment is configured to run on a virtual (or otherwise emulated) hardware system. A physical hardware system can have either or both of the following: • one physical operating system environment • one or more virtual operating system environments. • Server. A server is a physical hardware system capable of running server software. A hardware partition or blade is considered to be a separate physical hardware system. • Physical and Virtual Processors. A physical processor is a processor in a physical hardware system. Physical operating system environments use physical processors. A virtual processor is a processor in a virtual (or otherwise emulated) hardware system. Virtual operating system environments use virtual processors. A virtual processor is considered to have the same number of threads and cores as each physical processor on the underlying physical hardware system. • Assigning a License. To assign a license means simply to designate that license to one server, device or user.
Licensing Terminology. Instance. You create an “instance” of software by executing the software’s setup or install procedure. You also create an instance of software by duplicating an existing instance. References to software in this agreement include “instances” of the software. • Run an Instance. You “run an instance” of software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory. • Operating System Environment (“OSE”). An “operating system environment” or “OSE” is • all or part of an operating system instance, or all or part of a virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique 1 LICENSOR: These terms include Microsoft trademarks. If you include a trademark footnote in the End User License Agreement for the Unified Solution to give notice of your own trademarks or other third party trademarks, then add the following wording to your trademark footnote: “All other trademarks are the property of their respective owners.”
Licensing Terminology. Instance. You create an “instance” of the software by executing the
Licensing Terminology. ISV Royalty Agreement XXXX • Instance. You create an “instance” of the software by executing the software’s setup or install procedure. You also create an instance of the software by duplicating an existing instance. References to the “software” in this agreement include “instances” of the software. • Run an Instance. You “run an instance” of the software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory. • Operating System Environment (“OSE”). An “operating system environment” or “OSE” is
AutoNDA by SimpleDocs
Licensing Terminology 

Related to Licensing Terminology

  • Terminology All personal pronouns used in this Agreement, whether used in the masculine, feminine, or neuter gender, shall include all other genders; and the singular shall include the plural, and vice versa. Titles of Articles and Sections are for convenience only and neither limit nor amplify the provisions of this Agreement itself.

  • Definitions and Accounting Terms Section 1.01.

  • DATA PROCESSING TERMS For the purposes of the Data Protection Legislation, the Sponsor is the Controller, the Participating Site is the Sponsor's Processor and the PIC is the Sub-Processor of the Participating Site in relation to all Processing of Personal Data that is Processed for the purpose of this Study and for any future research use under the Controllership of the Sponsor, that would not have taken place but for this Agreement regardless where that Processing takes place. The Parties acknowledge that whereas the Sponsor is the Controller in accordance with Clause 3.2, the PIC is the Controller of the Personal Data collected for the purpose of providing clinical care to the Participants. This Personal Data may be the same Personal Data, collected transparently and processed for research and for care purposes under the separate Controllerships of the Sponsor and PIC. Where the PIC is the Participating Site's Sub-Processor and thus where the Processing is undertaken by the PIC for the purposes of the Study, Clauses 3.5 to 3.9 below will apply. For the avoidance of doubt, such Clauses do not apply where the PIC is Processing the Participant Personal Data as a Controller. The PIC agrees only to Process Personal Data for and on behalf of the Participating Site in accordance with the instructions of the Participating Site or Sponsor and for the purpose of the Study and to ensure the Sponsor’s and Participating Site’s compliance with the Data Protection Legislation; The PIC agrees to comply with the obligations applicable to Processors described by Article 28 GDPR including, but not limited to, the following: to implement and maintain appropriate technical and organisational security measures sufficient to comply at least with the obligations imposed on the Controller by Article 28(1); to not engage another Processor without the prior written authorisation of the Sponsor (Article 28(2)); to Process the Personal Data only on documented instructions from the Participating Site or Sponsor unless required to do otherwise by legislation, in which case the PIC shall notify the Participating Site before Processing, or as soon as possible after Processing if legislation requires that the Processing occurs immediately, unless legislation prohibits such notification on important grounds of public interest (Article 28(3a)).; to ensure that personnel authorised to Process Personal Data are under confidentiality obligations (Article 28(3b)); to take all measures required by Article 32 GDPR in relation to the security of processing (Article 28(3c)); to respect the conditions described in Article 28(2) and (4) for engaging another Processor (Article 28(3d)); to, taking into account the nature of the Processing, assist the Participating Site and/or the Sponsor, by appropriate technical and organisational measures, insofar as this is possible, to respond to requests for exercising Data Subjects’ rights (Article 28(3e)); to assist the Controller, to ensure compliance with the obligations pursuant to Articles 32 to 36 GDPR taking into account the nature of the Processing and the information available to the PIC (Article 28(3f)); to, at the choice of the Sponsor, destroy or return all Personal Data to the Sponsor at the expiry or early termination of the Agreement, unless storage is legally required (Article 28(3g)) or where that Personal Data is held by the PIC as Controller for the purpose of clinical care or other legal purposes; and

  • Gender and Development 24. The Borrower shall ensure that the principles of gender equity aimed at increasing Project benefits and impacts on women in the Project area consistent with ADB’s Policy on Gender and Development (1998) are followed during implementation of the Project, including (a) equal pay to men and women for work of equal value; (b) enabling working conditions for women workers; and (c) taking necessary actions to encourage women living in the Project area to participate in the design and implementation of the Project activities.

  • Accounting Terms and Determinations Unless otherwise specified herein, all accounting terms used herein shall be interpreted and all accounting determinations hereunder shall be made in accordance with GAAP.

Time is Money Join Law Insider Premium to draft better contracts faster.