Resource Description Framework

Uses your system voice; voice and rate in settings.

Snapshot

≈ 7 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

The Resource Description Framework (RDF) is a method to describe and exchange graph data. It was originally designed as a data model for metadata by the World Wide Web Consortium (W3C). It provides a variety of syntax notations and formats, of which the most widely used is Turtle (Terse RDF Triple Language). RDF is a directed graph composed of triple statements. An RDF graph statement is represented by: (1) a node for the subject, (2) an arc from subject to object, representing a predicate, and (3) a node for the object. Each of these parts can be identified by a Internationalized Resource Identifier (IRI). An object can also be a literal value. This simple, flexible data model has a lot of expressive power to represent complex situations, relationships, and other things of interest, while also being appropriately abstract. RDF was adopted as a W3C recommendation in 1999. The RDF 1.0 specification was published in 20041, and the RDF 1.1 specification in 2014. SPARQL is a standard query language for RDF graphs. RDF Schema (RDFS), Web Ontology Language (OWL) and SHACL (Shapes Constraint Language) are ontology languages that are used to describe RDF data.

The Resource Description Framework (RDF) is a method to describe and exchange graph data. It was originally designed as a data model for metadata by the World Wide Web Consortium (W3C). It provides a variety of syntax notations and formats, of which the most widely used is Turtle (Terse RDF Triple Language). RDF is a directed graph composed of triple statements. An RDF graph statement is represented by: (1) a node for the subject, (2) an arc from subject to object, representing a predicate, and (3) a node for the object. Each of these parts can be identified by a Internationalized Resource Identifier (IRI). An object can also be a literal value. This simple, flexible data model has a lot of expressive power to represent complex situations, relationships, and other things of interest, while also being appropriately abstract. RDF was adopted as a W3C recommendation in 1999. The RDF 1.0 specification was published in 2004, and the RDF 1.1 specification in 2014. SPARQL is a standard query language for RDF graphs. RDF Schema (RDFS), Web Ontology Language (OWL) and SHACL (Shapes Constraint Language) are ontology languages that are used to describe RDF data.

RDF topics

Vocabulary

The vocabulary defined by the RDF specification is as follows:

Classes

Properties

rdf

: an instance of rdf:Property used to state that a resource is an instance of a class : the first item in the subject RDF list : the rest of the subject RDF list after rdf:first : idiomatic property used for structured values : the subject of the RDF statement : the predicate of the RDF statement : the object of the RDF statement rdf:Statement , rdf:subject , rdf:predicate , rdf:object are used for reification (see below).

rdfs

: the subject is a subclass of a class : the subject is a subproperty of a property : a domain of the subject property : a range of the subject property : a human-readable name for the subject : a description of the subject resource : a member of the subject resource : further information about the subject resource : the definition of the subject resource This vocabulary is used as a foundation for RDF Schema, where it is extended. PREFIX ex: SELECT ?capital ?country WHERE { ?x ex:cityname ?capital ; ex:isCapitalOf ?y . ?y ex:countryname ?country ; ex:isInContinent ex:Africa . } Other non-standard ways to query RDF graphs include: RDQL, precursor to SPARQL, SQL-like Versa, compact syntax (non–SQL-like), solely implemented in 4Suite (Python). RQL, one of the first declarative languages for uniformly querying RDF schemas and resource descriptions, implemented in RDFSuite. SeRQL, part of Sesame XUL has a template element in which to declare rules for matching data in RDF. XUL uses RDF extensively for data binding. SHACL Advanced Features specification (W3C Working Group Note), the most recent version of which is maintained by the SHACL Community Group, defines support for SHACL Rules, used for data transformations, inferences and mappings of RDF based on SHACL shapes. "Eric Miller" . . "Dr." . . Equivalently, it can be written in standard Turtle (syntax) format as: @prefix eric: . @prefix contact: . @prefix rdf: . eric:me contact:fullName "Eric Miller" . eric:me contact:mailbox . eric:me contact:personalTitle "Dr." . eric:me rdf:type contact:Person . Or more concisely, using a common shorthand syntax of Turtle as: @prefix eric: . @prefix contact: . @prefix rdf: . eric:me contact:fullName "Eric Miller" ; contact:mailbox ; contact:personalTitle "Dr." ; rdf:type contact:Person . Or, it can be written in RDF/XML format as: Eric Miller Dr. "NY" . In this example, " urn:x-states:New%20York " is the URI for a resource that denotes the US state New York, " http://purl.org/dc/terms/alternative " is the URI for a predicate (whose human-readable definition can be found here ), and "NY" is a literal string. Note that the URIs chosen here are not standard, and do not need to be, as long as their meaning is known to whatever is reading them. "Tony Benn" . "Wikipedia" . To an English-speaking person, the same information could be represented simply as: The title of this resource, which is published by Wikipedia, is 'Tony Benn' However, RDF puts the information in a formal way that a machine can understand. The purpose of RDF is to provide an encoding and interpretation mechanism so that resources can be described in a way that particular software can understand it; in other words, so that software can access and use information that it otherwise could not use. Both versions of the statements above are wordy because one requirement for an RDF resource (as a subject or a predicate) is that it be unique. The subject resource must be unique in an attempt to pinpoint the exact resource being described. The predicate needs to be unique in order to reduce the chance that the idea of Title or Publisher will be ambiguous to software working with the description. If the software recognizes http://purl.org/dc/elements/1.1/title (a specific definition for the concept of a title established by the Dublin Core Metadata Initiative), it will also know that this title is different from a land title or an honorary title or just the letters t-i-t-l-e put together. The following example, written in Turtle, shows how such simple claims can be elaborated on, by combining multiple RDF vocabularies. Here, we note that the primary topic of the Wikipedia page is a "Person" whose name is "Tony Benn": @prefix rdf: . @prefix foaf: . @prefix dc: . dc:publisher "Wikipedia" ; dc:title "Tony Benn" ; foaf:primaryTopic [ a foaf:Person ; foaf:name "Tony Benn" ] .

Text derived from https://en.wikipedia.org/w/index.php?oldid=1369295525 under CC BY-SA 4.0; modifications have been made.

References

  1. ↩Wikipedia publication date (×1) · confidence 0.95 https://en.wikipedia.org/w/index.php?oldid=1369295525