Serialisation of models as Linked Data Sample Clauses

Serialisation of models as Linked Data. ‌ The goal of this feature is to serialise models or parts of models in a uniform format, to allow. The Resource Description Framework (RDF) and the concepts from Linked Data should be used for the serialisation format. Details which update the description from D3.1.1 can be found in section 3.3.1. The result can then be for example uploaded to a Linked Data server, where it can be further connected to other data and queried using SPARQL. This is a general feature that can be used throughout the procedure. This feature should be capable to:  Receive one or several models as input.  Create the Linked Data based on the input. o It is strongly recommended to use the Global identifier (see section 2.3.2) as the URI for the RDF resources (if applicable) and to directly transform the parts from the Property collector (also section 2.3.2) directly into triples, in order to allow linking the data to other Linked Data sources.
Sample 1
AutoNDA by SimpleDocs

Related to Serialisation of models as Linked Data

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.

  • Security of All Software Components Supplier will inventory all software components (including open source software) used in Deliverables, and provide such inventory to Accenture upon request. Supplier will assess whether any such components have any security defects or vulnerabilities that could lead to a Security Incident. Supplier will perform such assessment prior to providing Accenture with access to such software components and on an on-going basis thereafter during the term of the Agreement. Supplier will promptly notify Accenture of any identified security defect or vulnerability and remediate same in a timely manner. Supplier will promptly notify Accenture of its remediation plan. If remediation is not feasible in a timely manner, Supplier will replace the subject software component with a component that is not affected by a security defect or vulnerability and that does not reduce the overall functionality of the Deliverable(s).

  • Technical Data For the purpose of this Agreement, "TECHNICAL DATA" shall mean all information of the Company in written, graphic or tangible form relating to any and all products which are developed, formulated and/or manufactured by the Company, as such information exists as of the Effective Date or is developed by the Company during the term hereof.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • 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

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Limited Software Warranty MyECheck represents, warrants, and covenants that: MyECheck warrants to the original end user (“Customer”), and not to subsequent end users, of the Extreme Networks software product (“Software”) that for ninety (90) days from the date of installation of the Software from MyECheck, the Software shall substantially conform with the specification for the Software at the (“Documentation”). MyECheck does not warrant (i) that the Software is error free, (ii) that Customer will be able to operate the Software without problems or interruptions or (iii) that the Software will be free of vulnerability to intrusion or attack. Except for the limited warranty set forth in this section, the Software is provided “AS IS.”

  • Product Warranty for Software Deliverables During the Project warranty period, defects in the materials or workmanship of the Software Deliverables specified and furnished by or through Contractor shall be repaired or replaced by Contractor at no cost or expense to the Authorized User. Contractor shall extend the Project warranty period by the cumulative period(s) of time, after notification, during which the Software Deliverables require servicing or replacement (down time) or is in the possession of the Contractor, its agents, officers, Subcontractors, distributors, resellers or employees . The Commissioner agrees that Contractor is not responsible for any modification of the Software Deliverables made by an Authorized User without Contractor’s approval.

  • Other Methods of Procurement of Goods and Works The following table specifies the methods of procurement, other than International Competitive Bidding, which may be used for goods and works. The Procurement Plan shall specify the circumstances under which such methods may be used: Procurement Method

  • Notification of Modifications of Licensed Materials From time to time Publisher may add, change, or modify portions of the Licensed Materials, or migrate the Licensed Materials to other formats. When such changes, modifications, or migrations occur, the Licensor shall give notice of any such changes to Licensee as soon as is practicable, but in no event less than sixty (60) days in advance of modification. Such a notice may also be given directly by the Publisher to the Licensee. If any of the changes, modifications, or migrations renders the Licensed Materials substantially less useful to the Licensee, the Participating Institutions or their Authorized Users, the Licensee may seek to terminate this Agreement for breach pursuant to the termination provisions of this Agreement in Section XI, below.

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