RDF / RDFS Sample Clauses

RDF / RDFS. The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. It is particularly intended for representing metadata about Web resources, such as the title, author, and modification date of a Web page, copyright and licensing information about a Web document, or the availability schedule for some shared resource. However, by generalizing the concept of a "Web resource", RDF can also be used to represent information about things that can be identified on the Web, even when they cannot be directly retrieved on the Web [11]. The underlying structure of any expression in RDF is a collection of triples, each consisting of a subject, a predicate (also called a property) and an object [12]. RDF Schema (or RDFS) is an extensible knowledge representation language, providing basic elements for the description of ontologies, otherwise called RDF vocabularies, intended to structure RDF resources. The first version was published by W3C in April 1998, and the final W3C recommendation was released in February 2004. In addition to inheriting basic features from Frame Systems, RDFS provides ontology constructs that make relations less dependent on concepts: users can define relations as an instance of rdf:Property, describe inheritance relations between relations using rdfs:subPropertyOf, and then associate defined relations with classes using rdfs:domain or rdfs:range [13].
AutoNDA by SimpleDocs

Related to RDF / RDFS

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Where one Contracting Party or its designated agency has guaranteed any indemnity against non-commercial risks in respect of an investment by any of its investors in the territory of the other Contracting Party and has made payment to such investors in respect of their claims under this Agreement, the other Contracting Party agrees that the first Contracting Party or its designated agency is entitled by virtue of subrogation to exercise the rights and assert the claims of those investors. The subrogated rights or claims shall not exceed the original rights or claims of such investors.

  • Your Billing Rights Keep this Document for Future Use This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • OGS Centralized Contract Modifications OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • OGS Centralized Contract Terms and Conditions have been renumbered as depicted in the following chart: Current Amended Section Title 4.25 4.26 Severability 4.26 4.27 Entire Agreement

  • CONTRACTOR STAFF WITHIN AUTHORIZED USER AGREEMENT The provisions of this section shall apply unless otherwise agreed in the Authorized User Agreement. All employees of the Contractor, or of its Subcontractors, who shall perform under an Authorized User Agreement, shall possess the necessary qualifications, training, licenses, and permits as may be required within the jurisdiction where the Services specified are to be provided or performed, and shall be legally entitled to work in such jurisdiction. All Business Entities that perform Services under the Contract on behalf of Contractor shall, in performing the Services, comply with all applicable Federal, State, and local laws concerning employment in the United States. Staffing Changes within Authorized User Agreement

  • wire Unbundled ISDN Digital Loops These will be provisioned according to industry standards for 2-Wire Basic Rate ISDN services and will come standard with a test point, OC, and a DLR. NewPhone will be responsible for providing BellSouth with a Service Profile Identifier (SPID) associated with a particular ISDN-capable Loop and customer. With the SPID, BellSouth will be able to adequately test the circuit and ensure that it properly supports ISDN service.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • END USER AGREEMENTS (“EUA H-GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC

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