Database Ontology Sample Clauses

Database Ontology. The database ontology describes the fields of a database and the meaning of specific terms in the database. In the tables in this chapter an overview of all the field in the database is given. The fields are ordered according to table. In the figure 3 on overview of the relationships between tables is given. The first column in the tables represent the database field, the second and third column the type of entry that is allowed for these field and the last column a description of the field. Table of Contents Table Number Table Title Page Number A Particle Table 30 0 Components Table(s) 31 0 Overall Particle Measurement Table 36 0 Dimensions Table 36 0 Agglomeration Table 39 0 Surface Table 39 0 Surface Component Table 0 0 Medium table 41 0 Medium components table 43 0 Dispersion/ preparation protocol table 44 0 Shape Measurement Technique Table 46 0 Size Measurement Technique Table 46 0 Surface Area Measurement Technique Table 47 0 Surface Charge Measurement Technique Table 48 0 Solubility Measurement Technique Table 48 0 Surface Reactivity Measurement Technique Table 49 0 Overall (Eco)Toxicity Measurement Table 49 0 Model Table 50 0 Exposure Table 50 0 Species Table 52 0 Endpoint Table in vitro 53 0 Endpoint Table in vivo 55 0 Assay protocol 57 Field Entry restriction List options Remarks
AutoNDA by SimpleDocs
Database Ontology. The field in the database are explained in the tables in this chapter. The software tool that is developed for entry of experimental data into the database is a software tool that is constantly under development. Moreover the tool has been built with limited resources and even though from a scientific point of view the tool is sufficiently detailed, it is not very user friendly. Nevertheless the tool works using a specific methodology for data extraction. This methodology is completely in compliance with the type of information that should be extracted from the studies (as explained in chapter 2Error! Reference source not found.). For this reason it is smart to think about the structuring of experimental data according to this methodology in any given study in order to be able to enter data efficiently into the database. The methodology asks for the addition of a particle to a given study first. Therefore it is recommended to start making a list of all particles that are investigated in any experimental study. Then the data that are available regarding this particle should be ordered. For every type of data the medium and the protocol should be defined (unless data is provided just like that in which case they should be entered as “provided”). From the materials and methods and results in any study the preparation method of particles dispersions, and the relevant medium in which the particles were dispersed should be described. (for many characterization methods like TEM and SEM the dispersion medium is dried or removed, still the medium in which the particle was dispersed before sample preparation should be added as the relevant medium). For use in the tool it is easy to add different measurements to a specific combination of a medium and protocol so it makes sense to put the tests done under these condition together. In Table 11 the conceptual idea for the structuring of the data is provided. In Appendix C an example is worked out. It is also recommended to write down the most important details on the particle, the preparation protocol, the medium type of tests straight away.

Related to Database Ontology

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Web Hosting If Customer submits a Service Order(s) for web hosting services, the following terms shall also apply:

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Processes Any employer, employee, trade union or employer’s association may at any point in time apply for an exemption from any of the provisions of this Collective Agreement. The applicant is required to complete and submit in writing with the relevant office of the Council, a fully and properly completed prescribed application for exemption form, accompanied by all relevant supporting documentation.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Geological and Archeological Specimens If, during the execution of the Work, the Contractor, any Subcontractor, or any servant, employee, or agent of either should uncover any valuable material or materials, such as, but not limited to, treasure trove, geological specimens, archival material, archeological specimens, or ore, the Contractor acknowledges that title to the foregoing is vested in the Owner. The Contractor shall notify the Owner upon the discovery of any of the foregoing, shall take reasonable steps to safeguard it, and seek further instruction from the Design Professional. Any additional cost incurred by the Contractor shall be addressed under the provision for changed conditions. The Contractor agrees that the Geological and Water Resources Division and the Historic Preservation Division of the Georgia Department of Natural Resources may inspect the Work at reasonable times.

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