Common data elements Sample Clauses

Common data elements. In the following sections we describe in a concise form all the data elements that have been defined following the survey. Whenever possible, each element is expressed in both the CIDOC-CRM ontology and in the EpiDoc schema. Annex 3 contains the detailed description of each element in both formalisms, together with examples. The metadata elements have been grouped into different categories corresponding to different EAGLE objects: Information Carrier, Inscription, Transcription, Translation and Visual Representation. This metadata structure and codification is based in the EAGLE CIDOC CRM model which covers every aspect of the information that needs to be represented and is perfectly coupled with the rest of the conceptual models. At the same time, EpiDoc is a community work that aims to create recommendations and tools that can be used in the encoding of epigraphic documents. The guidelines11 have reached a high quality standard thanks to the active collaboration of the community and the execution of several pilot projects. In this case, for those elements that falls within the scope of EpiDoc, its corresponding codification is presented, taking advantage on the fact that these guidelines are domain-specific and tailored to the needs of text encoding.
Sample 1
AutoNDA by SimpleDocs
Common data elements. ‌ In the following sections we describe in a concise form all the data elements that have been defined following the survey. Whenever possible, each element is expressed in both an RDF encoding of the CIDOC-CRM ontology and in EpiDoc. Annex 3 contains the detailed description of each element in both formalisms, together with examples. Several namespaces have been used in the RDF encoding: Namespace name Abbreviation Namespace URL CIDOC CRM crm xxxx://xxx.xxxxx-xxx.xxx/cidoc-crm/ RESOURCE DESCRIPTION FRAMEWORK rdf xxxx://xxx.x0.xxx/1999/02/22-rdf-syntax-ns# RESOURCE DESCRIPTION FRAMEWORK SCHEMA rdfs xxxx://xxx.x0.xxx/2000/01/rdf-schema# LINKED ANCIENT WORLD DATA lawd xxxx://xxxx.xxxx/ontology/ XXXXXXX CORE dc xxxx://xxxx.xxx/dc/elements/1.1/ BRITISH MUSEUM bmo xxxx://xxxxxxxxxx.xxxxxxxxxxxxx.xxx/id/ontology/ OPEN ANNOTATION COLLABORATION oa xxxx://xxx.xxxxxxxxxxxxxx.xxx/ns/ FRIEND OF A FRIEND foaf xxxx://xxxxx.xxx/foaf/0.1/ cnt xxxx://xxx.x0.xxx/2011/content# DUBLIN CORE TYPE dctype xxxx://xxxx.xxx/dc/dcmitype/ cito xxxx://xxxx.xxx/spar/cito/ DUBLIN CORE TERMS dcterms xxxx://xxxx.xxx/dc/terms/ ONTOLOGY WEB LANGUAGE owl xxxx://xxx.x0.xxx/2002/07/owl# As stated in the CIDOC CRM RDFS schema (xxxx://xxx.xxxxx- xxx.xxx/xxxx/xxxxx_xxx_x0.0.0_xxxxxxxx_xxxxxxx.xxxx), because RDF does not support properties of properties we can create our own EAGLE subproperties for CRM properties that have a type property such as "P3 has note" like this: <rdf:Property rdf:about="P3_parts_description"> <rdfs:domain rdf:resource="E1_CRM_Entity"/> <rdfs:range rdf:resource="http//xxx.x0.xxx/0000/00/xxx-xxxxxx"/> <rdfs:subPropertyOf rdf:resource="P3_has_note"/> </rdf:Property> In the following sections we will be introducing custom EAGLE properties to the CRM model in order to represent the relations between some elements. The name of those properties will start with the letter “P” followed by “EGL” for EAGLE and a text identifying the meaning of the property. Also, primitive values "E60 Number", "E61 Time Primitive" and "E62 String" are represented as rdf literals. The metadata elements have been grouped into different categories corresponding to the different EAGLE objects: Metadata, Inscription, Epigraphical Field, Monument, Translation, and Visual Representation (Image, 3D Model and Video). This metadata structure and codification is based in the EAGLE CIDOC CRM model which covers every aspect of the information that needs to be represented and is perfectly coupled with the rest of ...
Sample 1

Related to Common data elements

  • Contract Database Metadata Elements Title: Fallsburg Central School District and Fallsburg Central School Custodial Unit, CSEA Local 1000, AFSCME, AFL-CIO, Xxxxxxxx County Local 853 (2001) Employer Name: Fallsburg Central School District Union: Fallsburg Central School Custodial Unit, CSEA, AFSCME, AFL-CIO Local: Xxxxxxxx County Local 853, 1000 Effective Date: 07/01/2001 Expiration Date: 06/30/2006 PERB ID Number: 5011 Unit Size: Number of Pages: 17 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 by and between the FALLSBURG CENTRAL SCHOOL DISTRICT and CSEA, Local 1000 AFSCME, AFL-CIO Fallsburg Central School Custodial Unit Xxxxxxxx County Local 853 July 1, 2001 — June 30, 2006 TABLE OF CONTENTS PREAMBLE 1 ARTICLE 1 - Applicable Law 1 ARTICLE 2 - Recognition 1 ARTICLE 3 - Management Rights 2 ARTICLE 4 - Work Schedule 2 ARTICLE 5 - Overtime 3 ARTICLE 6 - Holidays 4 ARTICLE 7 - Vacations 4 ARTICLE 8 - Vacancies and Promotions 5 ARTICLE 9 - Grievance Procedure and Employee Disciplinary Procedure 5 ARTICLE 10 - Compatibility With Law 6 ARTICLE 11 - Union Rights 6 ARTICLE 12 - Leave Provisions 6 ARTICLE 13 - Health Insurance 8 ARTICLE 14 - Retirement 9 ARTICLE 15 - Supplemental Allowance 9 ARTICLE 16 - Child Care Leave 9 ARTICLE 17 - Dental Insurance 10 ARTICLE 18 - Disability Insurance 10 ARTICLE 19 - Joint Labor/Management Committee 10 APPENDIXA............. .................. ...... ................................................................. 12 LONGEVITY 13 DIFFERENTIALS 14 HEAD CUSTODIAN SALARYSCHEDULE 15 PREAMBLE Agreement made as of September 17, 2003, between the Board of Education of Fallsburg Central School District (“District”) and Civil Service Employees Association, Inc., Local 1000, AFSCME, AFL-CIO, Fallsburg School District Unit, Xxxxxxxx County Local 853 (“Association”).

  • Elements Defines the individual components under each indicator

  • Design Elements The School shall implement and maintain the following essential design elements of its educational program:

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

  • Neutral Elements In order to determine whether a product originates, it shall not be necessary to determine the origin of the following which might be used in its manufacture:

  • Unbundled Network Elements 35.4.1. The charges that CLEC shall pay to Sprint for Unbundled Network Elements are set forth in Table One of this Agreement. 35.5. Collocation

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