RDF Schema Sample Clauses

RDF Schema. The data stored in Marmotta for representing content item metadata currently uses properties from several well-known RDF vocabularies: LDP Containers: the membership of content parts in their content item is modeled using the vocabulary defined for containers as part of the Linked Data Platform specification [SAM14]; most importantly, the ldp:contains property defines the relation between a content part and the content item it is part of Dublin Core: basic descriptions and provenance information is provided using the Dublin Core vocabulary [DCT12]; the properties currently used are dc:title (name of content part), dc:created (creation date of content part), dc:creator (creator of content part, either user, extractor, or tool), dc:source (URI of content part this part was derived from) and dc:type (symbolic type representation) Figure 1 shows the representation of a content part (result of an analysis proces) in the Apache Marmotta Metadata Explorer. Note the URI schema used for generating the content part URI and the contexts, as well as the Dublin Core properties used to describe provenance information. Beyond these two basic vocabularies, implementations of extractor services are generally free to choose any schema that is necessary. Extractor services should, however, strive to use the vocabularies defined by WP33. The MICO API will provide specific support for these vocabularies once they have been completed.
Sample 1
AutoNDA by SimpleDocs

Related to RDF Schema

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • Technology Research Analyst Job# 1810 General Characteristics

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • 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.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate PNG’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. PNG shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

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