Structure of this document Sample Clauses

Structure of this document. 1.1 Part A of this Agreement sets out the key terms for the Buyer and Seller.‌ 1.2 Part B sets out the general legal terms that commonly apply to this kind of agreement. The definitions and rules of interpretation in Part B apply in this Agreement. PART A‌
Sample 1
AutoNDA by SimpleDocs
Structure of this document. ‌ The document consists of four main sections. The connections between the BEACONING Ecosystem and the typical technologies in educational environments such as learning management systems (LMSs) or systems for educational collaboration, communications and context-awareness providers, will be described in the first section. Following that standards used internally will be documented in two sections covering those among the elements of the system and those about the content. The final section about standards will focus on the data layer.
Sample 1
Structure of this document. 1.2.1 This document is set out in four sections (with supporting appendices) in the sequence listed below;
Sample 1
Structure of this document. ‌ The document consists of three main sections. The in-depth market analysis of the education gaming in EU is presented, followed by an overview of the state of the art of the technology in using games for engaging students in inclusive education. The final section is a discussion about how to evaluate project outcomes in ways that not only serve for validation but also for actionable feedback towards further development. At the end of each section, there is a reflection exercise to derive lessons and portable ideas for the BEACONING project. The text includes numerous examples linked to the assertions and claims about the state of the market and the technology.
Sample 1
Structure of this document. ‌ The structure of this document has been widely introduced while describing the individual components. Hence, the following Chapter 2 introduces Colosseum, SWORD, XXXXX, whereas Chapter 3 presents monitoring-related aspects such as VISOR, the TSDB selection, AXE, as well as the MetricsCollector in detail. The remaining parts of the document address further aspects of the Exe- cutionware in Chapter 4 such as the operation of testbeds and the provisioning of an access point for users such as the social network [5]. Finally, Chapter 5 con- cludes the document with an overview of the components, and their download location. D5.1.2—Product Executionware Page 20 of 62 2‌ CLOUDIATOR Overall, CLOUDIATOR is a multi-tenant-capable Web-based software service. Its features can be separated into registries, deployment functionality, automatic adaptation, and the specification of monitoring requirements. This chapter gives a more extended description on three of the CLOUDIATOR tools that have already been introduced in Section 1.2.1: COLOSSEUM as the entry point to the system; SWORD providing the resource allocation functionality; and XXXXX for the life- cycle handling of component instances. The overall CLOUDIATOR component layout is also summarised in Figure 2.1. API call dataflow domain of paasage operator Axe monitoring and adapt adation orchestration Axe SRL- engine Colosseum registries sword deployment engine Time-series database (TSDB) Axe cross-cloud aggregators cloud aggregators Figure 2.1: Detailed CLOUDIATOR components running in the domain of the PaaSage operator. 2.1 COLOSSEUM‌ COLOSSEUM is the central access point to interact with CLOUDIATOR and hence, the Executionware. In consequence, it offers APIs that clients as well as higher- level components such as the Upperware can use. Moreover, COLOSSEUM con- tains several registries that contain intermediate data necessary to control and surveil actual deployments. The following sections first introduce the various registries (cf. Section 2.1.1) and then present the REST-based as well as the browser-based API in Section 2.1.2. 2.1.1 Registries‌
Sample 1
Structure of this document. The remainder of this document comprises a number of core parts, which are:  Chapter 2 provides some background information about the Project, together with considerations applicable to the Ethical and Data Protection Framework under discussion.  Chapters 3, 4 5 & 6 discuss respectively: the approach to participant evaluation and support, data protection legislation, background to ethics approach, and combining experience and evidence based practices.  Chapter 7 sets out the CareWell Ethics and Data Protection Framework.  Chapter 8 summarises the main Directives and legislation applicable to data protection.  Chapter 9 sets out the approach to activities relating to managing the project’s adherence to ethical and data protection requirements. Additionally, the following appendices provide more detailed background information:  Appendix A. Various value frameworks – both binding and non-binding ones - that have informed the development of more operational guidance.  Appendix B. Compilation of currently available information on how to achieve age-friendly and accessible technology design.  Appendix C. Consent forms used by the Consortium to be signed by participants enrolled in the Project.  Appendix D. Bibliography and references that are mentioned throughout the Framework.
Sample 1
Structure of this document. To a great extent the challenges and principles identified above are reflected in the structure of this document. Chapter 2 provides and explanation of the main concepts used in this document. Chapter 3 deals with collecting baseline end-user information, which is guided by principle 1. The section explains the needs assessment that was carried out among 21 European game studios. In structured interviews with key personnel of the studios we collected information about the ways that game studios view and deal with emerging technologies.
Sample 1
AutoNDA by SimpleDocs

Related to Structure of this document

  • Disclosure of this Agreement The Employee hereby authorizes the Company to notify others, including but not limited to customers of the Company and any of the Employee’s future employers or prospective business associates, of the terms and existence of this Agreement and the Employee’s continuing obligations to the Company hereunder.

  • Nature of this Agreement 3.1. This Agreement is a framework agreement within the meaning of regulation 2(1) of the Public Contracts (Scotland) Regulations 2015. Call-off Contracts are public contracts within the meaning of that regulation. 3.2. This Agreement is a multi-supplier framework agreement and the contractors that are party to it are the Framework Contractors. No other contractors are party to the Framework Agreement. 3.3. This Agreement is a multi-user framework agreement and the public bodies that are party to it are the Framework Public Bodies. No other public bodies are party to the Framework Agreement. 3.4. The Contractor acknowledges that it is not the exclusive supplier of the Services to Framework Public Bodies and as such no guarantee of work or volume of work has been granted by any Framework Public Body. 3.5. The Contractor acknowledges that the Framework Public Bodies are separate legal persons and as such the Authority has no liability in relation to the performance or non- performance of other Framework Public Bodies' obligations under this Framework Agreement or any Call-off Contracts.

  • Construction of this Agreement The Parties agree that each Party and its legal counsel have reviewed and revised this Agreement and that any rule of construction to the effect that ambiguities are to be resolved against the drafting Party shall not apply in the interpretation of this Agreement or any amendments or exhibits thereto.

  • SCOPE OF THIS AGREEMENT 2.1. This Agreement, including Parts A through L, Tables One and Two and exhibits, specifies the rights and obligations of each Party with respect to the establishment, purchase, and sale of Local Interconnection, Collocation, resale of Telecommunications Services and Unbundled Network Elements. Certain terms used in this Agreement shall have the meanings defined in PART A – DEFINITIONS, or as otherwise elsewhere defined throughout this Agreement. Other terms used but not defined in this Agreement will have the meanings ascribed to them in the Act and in the FCC’s and the Commission’s rules, regulations and orders. PART B sets forth the general terms and conditions governing this Agreement. The remaining Parts set forth, among other things, descriptions of the services, pricing, technical and business requirements, and physical and network security requirements.

  • Modification of this Agreement This Agreement may not be modified, nor may compliance with any of its terms be waived, except as noted in Section 11.1, “Notices to Parties,” regarding change in personnel or place, and except by written instrument executed and approved in the same manner as this Agreement. Contractor shall cooperate with Department to submit to the Director of CMD any amendment, modification, supplement or change order that would result in a cumulative increase of the original amount of this Agreement by more than 20% (CMD Contract Modification Form).

  • Variation of this Agreement ‌ This Agreement may be varied during its term by agreement in writing by the parties subject to the ratification process of the Union.

  • Operation of this Agreement This Agreement shall take effect on and from the date of this Agreement. The parties must execute and enter into this Agreement as soon as possible after the Development Consent is granted and prior to the issue of any Construction Certificate that relates to any building work, other than demolition, excavation, piling, shoring and ancillary work for construction purposes including site hoardings and temporary site sheds that relates to works contained in DA-152/2021/B.

  • Amendment of this Agreement No provision of this Agreement may be changed, waived, discharged or terminated orally, but only by an instrument in writing signed by the party against whom enforcement of the change, waiver, discharge or termination is sought, and no amendment of this Agreement shall be effective until approved in a manner consistent with the 1940 Act and rules and regulations thereunder and any applicable SEC exemptive order therefrom.

  • SCOPE OF THIS CONTRACT What is covered by this contract?

  • Effective Date of this Agreement This Agreement shall become effective (the "Effective Date") upon the date of your acceptance hereof, as set forth below.

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