Please refer to the delete: <a href="http://www.w3.org/2001/sw/RDFCore/errata#rdf-schema"> check the insert: <a href="http://www.w3.org/2014/rdf1.1-errata"> errata for any errors or issues reported since publication. insert: </p>
insert: <p>This document is also available in this document, which non-normative format: insert: <a href="diff.html" rel="alternate"> diff w.r.t. 2004 Recommendation insert: </a> insert: </p>
insert: <p>The English version of this specification is the only normative version. Non-normative insert: <a href="http://www.w3.org/Consortium/Translation/"> translations insert: </a> may include some normative corrections. delete: </p> delete: <p> See also delete: <a href="http://www.w3.org/2001/sw/RDFCore/translation/rdf-schema"> translations delete: </a> . be available.
Copyright © 2004 © 2004-2014 delete: <acronym title="World Wide Web Consortium"> insert: <abbr title="World Wide Web Consortium"> W3C delete: </acronym> insert: </abbr> ® ® ( delete: <acronym title="Massachusetts Institute of Technology"> insert: <abbr title="Massachusetts Institute of Technology"> MIT delete: </acronym> insert: </abbr> , delete: <a href="http://www.ercim.org/"> delete: <acronym title="European Research Consortium for Informatics and Mathematics"> insert: <a href="http://www.ercim.eu/"> insert: <abbr title="European Research Consortium for Informatics and Mathematics"> ERCIM delete: </acronym> insert: </abbr> , Keio insert: </a> , insert: <a href="http://ev.buaa.edu.cn/"> Beihang ), All Rights Reserved. insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> liability , trademark , and document use and delete: <a href="http://www.w3.org/Consortium/Legal/copyright-software"> software licensing delete: </a> rules apply.
insert: <hr />The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This specification describes how to use RDF to describe RDF vocabularies. This specification defines a RDF Schema provides a data-modelling vocabulary for this purpose and defines other built-in RDF vocabulary initially specified in the RDF Model and Syntax Specification. delete: </p> delete: <div class="status"> delete: <h2 class="nonum"> delete: <a id="status" name="status"> RDF data. RDF Schema is an extension of the basic RDF vocabulary. insert: </p>
insert: </section>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> publications and the latest revision of this technical report can be found in the insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> technical reports index at http://www.w3.org/TR/.
delete: </div> delete: <h2> delete: <a id="ch_contents" name="ch_contents"> delete: </a> insert: <p>This document is an edited version of the 2004 RDF Schema Recommendation. The purpose of this revision is to make this document available as part of the RDF 1.1 document set. Changes are limited to errata, revised references, terminology updates, and adaptations to the introduction. The title of the document was changed from "RDF Vocabulary Description Language 1.0: RDF Schema" to "RDF Schema 1.1". The technical content of the document is unchanged. Details of the changes are listed in the insert: <a href="#PER-changes"> Changes insert: </a> section. Since the edits to this document do not constitute a technical change the Director decided no new implementation report was required. insert: </p>
insert: <p>This document was published by the insert: <a href="http://www.w3.org/2011/rdf-wg/"> RDF Working Group insert: </a> as a Recommendation. If you wish to make comments regarding this document, please send them to insert: <a href="mailto:public-rdf-comments@w3.org"> public-rdf-comments@w3.org insert: </a> ( insert: <a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe"> subscribe insert: </a> , insert: <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/"> archives insert: </a> ). All comments are welcome. insert: </p>
insert: <p>This document has been reviewed by insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> Members, by software developers, and by other insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> groups and interested parties, and is endorsed by the Director as a insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> Recommendation. It is a stable document and may be used as reference material or cited from another document. insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> 's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. insert: </p>
insert: <p>This document was produced by a group operating under the insert: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/" rel="w3p:patentRules" about="" id="sotd_patent"> 5 February 2004 insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> Patent Policy insert: </a> . insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> maintains a insert: <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/46168/status"> public list of any patent disclosures insert: </a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains insert: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential"> Essential Claim(s) insert: </a> must disclose the information in accordance with insert: <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure"> section 6 of the insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> Patent Policy insert: </a> . insert: </p>
insert: </section>The Resource Description Framework (RDF) is a general-purpose language RDF Schema provides a data-modelling vocabulary for representing information in the Web. delete: </p> delete: <p> This specification is one of several [ delete: <a href="#ref-rdf-primer"> RDF-PRIMER delete: </a> ] [ delete: <a href="#ref-rdf-syntax"> RDF-SYNTAX delete: </a> ] [ delete: <a href="#ref-rdf-concepts"> RDF-CONCEPTS delete: </a> ] [ delete: <a href="#ref-rdf-semantics"> RDF-SEMANTICS delete: </a> ] [ delete: <a href="#ref-rdf-tests"> RDF-TESTS delete: </a> ] related to RDF. The reader is referred to the delete: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#rdfschema"> RDF schema chapter delete: </a> in the RDF Primer [ delete: <a href="#ref-rdf-primer"> RDF-PRIMER delete: </a> ] for an informal introduction and examples of the use of the concepts specified in this document. delete: </p> delete: <p> This specification introduces RDF's vocabulary description language, RDF Schema. RDF data. It is complemented by several companion documents which describe RDF's XML encoding the basic concepts and abstract syntax of RDF [ delete: <a href="#ref-rdf-syntax"> RDF-SYNTAX delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-RDF11-CONCEPTS"> RDF11-CONCEPTS insert: </a> insert: </cite> ], mathematical foundations the formal semantics of RDF [ delete: <a href="#ref-rdf-semantics"> RDF-SEMANTICS delete: </a> ] and Resource Description Framework (RDF): Concepts and Abstract Syntax insert: <cite> insert: <a class="bibref" href="#bib-RDF11-MT"> RDF11-MT insert: </a> insert: </cite> ], and various concrete syntaxes for RDF, such as Turtle [ delete: <a href="#ref-rdf-concepts"> RDF-CONCEPTS delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-TURTLE"> TURTLE insert: </a> insert: </cite> ], TriG, [ insert: <cite> insert: <a class="bibref" href="#bib-TRIG"> TRIG insert: </a> insert: </cite> ], and JSON-LD [ insert: <cite> insert: <a class="bibref" href="#bib-JSON-LD"> JSON-LD insert: </a> insert: </cite> ]. The RDF Primer [ delete: <a href="#ref-rdf-primer"> RDF-PRIMER delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-RDF11-PRIMER"> RDF11-PRIMER insert: </a> insert: </cite> ] provides an informal introduction and examples of the use of the concepts specified in this document.
This document is intended to provide a clear specification of the RDF vocabulary description language RDF Schema to those who find the formal semantics specification, RDF Semantics specification [ delete: <a href="#ref-rdf-semantics"> RDF-SEMANTICS delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-RDF11-MT"> RDF11-MT insert: </a> insert: </cite> ] daunting. Thus, this document duplicates material also specified in the RDF Semantics specification . specification. Where there is disagreement between this document and the RDF Semantics specification, the RDF Semantics specification should be taken to be correct.
RDF properties may be thought of as attributes of resources and in this sense correspond to traditional attribute-value pairs. RDF properties also represent relationships between resources. delete: </p> delete: <p> RDF however, provides no mechanisms for describing these properties, nor does it provide any mechanisms for describing the relationships between these properties and other resources. That is the role of the RDF vocabulary description language, RDF Schema. RDF Schema defines classes and properties that may be used to describe classes, properties and other resources. delete: </p> delete: <p> This document does not specify a vocabulary of descriptive properties such as "author". Instead it specifies mechanisms that may be used to name and describe properties and the classes of resource they describe. delete: </p> delete: <p> RDF's vocabulary description language, RDF Schema, is a is a insert: <a href="http://www.w3.org/TR/rdf11-mt/#semantic-extensions-and-entailment-regimes"> semantic extension (as delete: <a href="http://www.w3.org/TR/rdf-mt/#intro"> defined delete: </a> in [ delete: <a href="#ref-rdf-semantics"> RDF-SEMANTICS delete: </a> ]) insert: </a> of RDF. It provides mechanisms for describing groups of related resources and the relationships between these resources. RDF Schema vocabulary descriptions are is written in RDF using the terms described in this document. These resources are used to determine characteristics of other resources, such as the domains and ranges of properties.
The RDF vocabulary description language Schema class and property system is similar to the type systems of object-oriented programming languages such as Java. RDF Schema differs from many such systems in that instead of defining a class in terms of the properties its instances may have, the RDF vocabulary description language RDF Schema describes properties in terms of the classes of resource to which they apply. This is the role of the domain and range mechanisms described in this specification. For example, we could define the eg:author
property to have a domain of eg:Document
and a range of eg:Person
, whereas a classical object oriented system might typically define a class eg:Book
with an attribute called eg:author
of type eg:Person
. Using the RDF approach, it is easy for others to subsequently define additional properties with a domain of eg: Document
or a range of eg:Person
. This can be done without the need to re-define the original description of these classes. One benefit of the RDF property-centric approach is that it allows anyone to extend the description of existing resources, one of the architectural principles of the Web [ delete: <a
href="#rdfnotcite"> insert: <cite> insert: <a class="bibref" href="#bib-BERNERS-LEE98"> BERNERS-LEE98 insert: </cite> ].
This specification does not attempt to enumerate all the possible forms of vocabulary description that are useful for representing the meaning of RDF classes and properties. Instead, the RDF vocabulary description Schema strategy is to acknowledge that there are many techniques through which the meaning of classes and properties can be described. Richer vocabulary or 'ontology' languages such as DAML+OIL, W3C's OWL [ delete: <a href="#ref-owl"> OWL delete: </a> ] language, insert: <cite> insert: <a class="bibref" href="#bib-OWL2-OVERVIEW"> OWL2-OVERVIEW insert: </a> insert: </cite> ], inference rule languages and other formalisms (for example temporal logics) will each contribute to our ability to capture meaningful generalizations about data in the Web. RDF vocabulary designers can create and deploy Semantic Web applications using the RDF vocabulary description language 1.0 facilities, while exploring richer vocabulary description languages that share this general approach.
The language defined in this specification consists of a collection of RDF resources that can be used to describe properties of other RDF resources (including properties) in application-specific RDF vocabularies. The core vocabulary is defined in a namespace informally called 'rdfs' insert: <code> rdfs insert: </code>
here. That namespace is identified by the URI-Reference IRI insert: </p>
insert: <code> http://www.w3.org/2000/01/rdf-schema# and is insert: </code>
insert: </blockquote>
and is conventionally associated with the prefix 'rdfs'. insert: <code> rdfs: insert: </code>
. This specification also uses the prefix 'rdf' insert: <code> rdf: insert: </code>
to refer to the delete: <a
href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-Namespace"> RDF namespace delete: </a> http://www.w3.org/1999/02/22-rdf-syntax-ns#. delete: </p> insert: <p> insert: </p>
insert: <blockquote> insert: <code> http://www.w3.org/1999/02/22-rdf-syntax-ns# insert: </code>
insert: </blockquote>
For convenience and readability, this specification uses an abbreviated form to represent URI-References. IRIs. A name of the form prefix:suffix should be interpreted as a URI-Reference IRI consisting of the URI-Reference IRI associated with the prefix concatenated with the suffix.
delete: <h2> delete: <a name="ch_classes" id="ch_classes"> insert: </section> Resources may be divided into groups called classes. The members of a class are known as instances of the class. Classes are themselves resources. They are often identified by delete: <a
href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-URIref"> RDF URI References insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-IRIs"> IRIs and may be described using RDF properties. The delete: <a
href="#ch_type"> insert: <a href="#ch_type"> rdf:type
property may be used to state that a resource is an instance of a class.
RDF distinguishes between a class and the set of its instances. Associated with each class is a set, called the class extension of the class, which is the set of the instances of the class. Two classes may have the same set of instances but be different classes. For example, the tax office may define the class of people living at the same address as the editor of this document. The Post Office may define the class of people whose address has the same zip code as the address of the author. It is possible for these classes to have exactly the same instances, yet to have different properties. Only one of the classes has the property that it was defined by the tax office, and only the other has the property that it was defined by the Post Office.
A class may be a member of its own class extension and may be an instance of itself.
The group of resources that are RDF Schema classes is itself a class called delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
.
If a class C is a subclass of a class C', then all instances of C will also be instances of C'. The rdfs:subClassOf
property may be used to state that one class is a subclass of another. The term super-class is used as the inverse of subclass. If a class C' is a super-class of a class C, then all instances of C are also instances of C'.
The RDF Concepts and Abstract Syntax [ delete: <a href="#ref-rdf-concepts"> RDF-CONCEPTS delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-RDF11-CONCEPTS"> RDF11-CONCEPTS insert: </a> insert: </cite> ] specification defines the RDF concept of an delete: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Datatypes"> insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes"> RDF datatype . All datatypes are classes. The instances of a class that is a datatype are the members of the value space of the datatype.
delete: <h4> delete: <a id="ch_resource" name="ch_resource" /> insert: <section id="ch_resource" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"> All things described by RDF are called resources , and are instances of the class rdfs:Resource
. This is the class of everything. All other classes are subclasses of this class. rdfs:Resource
is an instance of delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
.
This is the class of resources that are RDF classes. rdfs:Class
is an instance of rdfs:Class.
The class rdfs:Literal
is the class of delete: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Literals"> insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal"> literal values such as strings and integers. Property values such as textual strings are examples of RDF literals. Literals may be delete: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-plain-literal"> plain delete: </a> or delete: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-typed-literal"> typed delete: </a> . A typed literal insert: </p>
insert: <code> rdfs:Literal insert: </code>
is an instance of a datatype class. This specification does not define the class of plain literals. delete: </p> delete: <p> delete: <code> rdfs:Literal delete: </code> is an instance of delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
. rdfs:Literal is a delete: <a
href="#def-subclass"> insert: <a href="#def-subclass"> subclass of delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource .
rdfs:Datatype
is the class of datatypes. All instances of rdfs:Datatype
correspond to the delete: <a
href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Datatypes"> insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes"> RDF model of a datatype described in the RDF Concepts specification [ delete: <a
href="#ref-rdf-concepts"> RDF-CONCEPTS delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-RDF11-CONCEPTS"> RDF11-CONCEPTS insert: </a> insert: </cite> ]. rdfs:Datatype
is both an instance of and a subclass of delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
. Each instance of rdfs:Datatype
is a subclass of rdfs:Literal.
The class insert: <code> rdf:langString insert: </code>
is the class of insert: <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string"> language-tagged string values insert: </a> . insert: <code> rdf:langString insert: </code>
is an instance of insert: <code> rdfs:Datatype insert: </code>
and a insert: <a href="#def-subclass"> subclass insert: </a> of insert: <a href="#ch_literal"> insert: <code> rdfs:Literal insert: </code>
insert: </a> . insert: </p>
insert: <em> This section is non-normative. insert: </em> insert: </p>
insert: <p> The class insert: <code> rdf:HTML insert: </code>
is the class of insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-html"> HTML literal values insert: </a> . insert: <code> rdf:HTML insert: </code>
is an instance of insert: <code> rdfs:Datatype insert: </code>
and a insert: <a href="#def-subclass"> subclass insert: </a> of insert: <a href="#ch_literal"> insert: <code> rdfs:Literal insert: </code>
insert: </a> . insert: </p>
insert: <em> This section is non-normative. insert: </em> insert: </p>
The class rdf:XMLLiteral
is the class of delete: <a
href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral"> insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-XMLLiteral"> XML literal values . rdf:XMLLiteral
is an instance of rdfs:Datatype
and a subclass of delete: <a
href="#ch_literal"> insert: <a href="#ch_literal"> rdfs:Literal
.
rdf:Property
is the class of RDF properties. rdf:Property
is an instance of delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
.
The RDF Concepts and Abstract Syntax specification [ delete: <a href="#ref-rdf-concepts"> RDF-CONCEPTS delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-RDF11-CONCEPTS"> RDF11-CONCEPTS insert: </a> insert: </cite> ] describes the concept of an RDF property as a relation between subject resources and object resources.
delete: <p> delete: <a name="def-subproperty" id="def-subproperty"> delete: </a> insert: <p id="def-subproperty"> This specification defines the concept of subproperty. The rdfs:subPropertyOf
property may be used to state that one property is a subproperty of another. If a property P is a subproperty of property P', then all pairs of resources which are related by P are also related by P'. The term super-property is often used as the inverse of subproperty. If a property P' is a super-property of a property P, then all pairs of resources which are related by P are also related by P'. This specification does not define a top property that is the super-property of all properties.
The basic facilities provided by rdfs:domain
and rdfs:range
do not provide any direct way to indicate property restrictions that are local to a class. Although it is possible to combine use delete: <a
href="#ch_domain"> insert: <a href="#ch_domain"> rdfs:domain
and rdfs:range
with sub-property hierarchies, direct support for such declarations are provided by richer delete: <a href="http://www.w3.org/2001/sw/WebOnt/"> Web Ontology delete: </a> languages such as OWL [ delete: <a href="#ref-owl"> OWL delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-OWL2-OVERVIEW"> OWL2-OVERVIEW insert: </a> insert: </cite> ].
rdfs:range
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to state that the values of a property are instances of one or more classes.
The triple
delete: <p> insert: <code> P rdfs:range C delete: </p> insert: </code>
states that P is an instance of the class delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
, that C is an instance of the class rdfs:Class
and that the resources denoted by the objects of triples whose predicate is P are instances of the class C.
Where P has more than one rdfs:range property, then the resources denoted by the objects of triples with predicate P are instances of all the classes stated by the rdfs:range
properties.
The rdfs:range
property can be applied to itself. The rdfs:range of rdfs:range
is the class delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
. This states that any resource that is the value of an rdfs:range
property is an instance of delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
.
The rdfs:range
property is applied to properties. This can be represented in RDF using the delete: <a
href="#ch_domain"> insert: <a href="#ch_domain"> rdfs:domain
property. The delete: <a
href="#ch_domain"> insert: <a href="#ch_domain"> rdfs:domain
of rdfs:range
is the class rdf:Property
. This states that any resource with an rdfs:range
property is an instance of rdf:Property
.
rdfs:domain
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to state that any resource that has a given property is an instance of one or more classes.
A triple of the form:
delete: <p> insert: <code> P rdfs:domain C delete: </p> insert: </code>
states that P is an instance of the class rdf:Property
, that C is a instance of the class rdfs:Class
and that the resources denoted by the subjects of triples whose predicate is P are instances of the class C.
Where a property P has more than one rdfs:domain property, then the resources denoted by subjects of triples with predicate P are instances of all the classes stated by the rdfs:domain
properties.
The rdfs:domain
property may be applied to itself. The rdfs:domain of rdfs:domain
is the class delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
. This states that any resource with an rdfs:domain
property is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
.
The rdfs:range
of rdfs:domain
is the class rdfs:Class
. This states that any resource that is the value of an rdfs:domain
property is an instance of rdfs:Class
.
rdf:type
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to state that a resource is an instance of a class.
A triple of the form:
delete: <p> insert: <code> R rdf:type C delete: </p> insert: </code>
states that C is an instance of delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
and R is an instance of C.
The rdfs:domain
of rdf:type
is rdfs:Resource . The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdf:type is delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
.
The property rdfs:subClassOf
is an instance of rdf:Property
that is used to state that all the instances of one class are instances of another.
A triple of the form:
delete: <p> insert: <code> C1 rdfs:subClassOf C2 delete: </p> insert: </code>
states that C1 is an instance of delete: <a
href="#ch_class"> insert: <a href="#ch_class"> rdfs:Class
, C2 is an instance of delete: <a
href="#ch_class"> rdfs:Class delete: </a> delete: </code> and C1 is a delete: <a
href="#def-subclass"> subclass delete: </a> of C2. The delete: <code> rdfs:subClassOf delete: </code> property is transitive. delete: </p> delete: <p> The delete: <a href="#ch_domain"> delete: <code> rdfs:domain delete: </code> delete: </a> of delete: <code> rdfs:subClassOf delete: </code> is delete: <code> rdfs:Class
and C1 is a insert: <a href="#def-subclass"> subclass insert: </a> of C2. The insert: <code> rdfs:subClassOf insert: </code>
property is transitive. insert: </p>
The insert: <a href="#ch_domain"> insert: <code> rdfs:domain insert: </code>
insert: </a> of insert: <code> rdfs:subClassOf insert: </code>
is insert: <code> insert: <a href="#ch_class"> rdfs:Class insert: </a> insert: </code>
. The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdfs:subClassOf
is rdfs:Class
.
The property rdfs:subPropertyOf
is an instance of rdf:Property
that is used to state that all resources related by one property are also related by another.
A triple of the form:
delete: <p> insert: <code> P1 rdfs:subPropertyOf P2 delete: </p> insert: </code>
states that P1 is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
, P2 is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
and P1 is a delete: <a
href="#def-subproperty"> insert: <a href="#def-subproperty"> subproperty of P2. The rdfs:subPropertyOf
property is transitive.
The rdfs:domain
of rdfs:subPropertyOf
is delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
. The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdfs:subPropertyOf is delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
.
rdfs:label
is an instance of rdf:Property
that may be used to provide a human-readable version of a resource's name.
A triple of the form:
delete: <p> insert: <code> R rdfs:label L delete: </p> insert: </code>
states that L is a human readable label for R.
The rdfs:domain
of rdfs:label
is delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource
. The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdfs:label is delete: <a
href="#ch_literal"> insert: <a href="#ch_literal"> rdfs:Literal
.
Multilingual labels are supported using the delete: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-Literal"> insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal"> language tagging facility of RDF literals.
delete: <h4> delete: <a id="ch_comment" name="ch_comment"> delete: </a> insert: </section> rdfs:comment
is an instance of rdf:Property
that may be used to provide a human-readable description of a resource.
A triple of the form:
delete: <p> insert: <code> R rdfs:comment L delete: </p> insert: </code>
states that L is a human readable description of R.
The rdfs:domain
of rdfs:comment
is delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource
. The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdfs:comment is delete: <a
href="#ch_literal"> insert: <a href="#ch_literal"> rdfs:Literal
.
A textual comment helps clarify the meaning of RDF classes and properties. Such in-line documentation complements the use of both formal techniques (Ontology and rule languages) and informal (prose documentation, examples, test cases). A variety of documentation forms can be combined to indicate the intended meaning of the classes and properties described in an RDF vocabulary. Since RDF vocabularies are expressed as RDF graphs, vocabularies defined in other namespaces may be used to provide richer documentation.
Multilingual documentation is supported through use of the delete: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-Literal"> insert: <a href="http://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal"> language tagging facility of RDF literals.
delete: <h2> delete: <a id="ch_domainrange" name="ch_domainrange"> delete: </a> insert: </section>insert: <em> This section is non-normative. insert: </em> insert: </p>
This specification introduces an RDF vocabulary for describing the meaningful use of properties and classes in RDF data. For example, an RDF vocabulary might describe limitations on the types of values that are appropriate for some property, or on the classes to which it makes sense to ascribe such properties.
The RDF Vocabulary Description language RDF Schema provides a mechanism for describing this information, but does not say whether or how an application should use it. For example, while an RDF vocabulary can assert that an author
property is used to indicate resources that are instances of the class Person
, it does not say whether or how an application should act in processing that range information. Different applications will use this information in different ways. For example, data checking tools might use this to help discover errors in some data set, an interactive editor might suggest appropriate values, and a reasoning application might use it to infer additional information from instance data.
RDF vocabularies can describe relationships between vocabulary items from multiple independently developed vocabularies. Since URI-References IRIs are used to identify classes and properties in on the Web, it is possible to create new properties that have a domain
or range
whose value is a class defined in another namespace.
Additional classes and properties, including constructs for representing containers and RDF statements, and for deploying RDF vocabulary descriptions in the World Wide Web Web, are defined in this section.
delete: <h3> delete: <a id="ch_containervocab" name="ch_containervocab"> insert: <section class="informative" id="ch_containervocab" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">insert: <em> This section is non-normative. insert: </em> insert: </p>
RDF containers are resources that are used to represent collections. An delete: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#containers"> introduction delete: </a> to RDF containers with examples may be found in the RDF Primer [ delete: <a href="#ref-rdf-primer"> RDF-PRIMER delete: </a> ]. The same resource may appear in a container more than once. Unlike containment in the physical world, a container may be contained in itself.
Three different kinds of container are defined. Whilst the formal semantics [ delete: <a href="#ref-rdf-semantics"> RDF-SEMANTICS delete: </a> insert: <cite> insert: <a class="bibref" href="#bib-RDF11-MT"> RDF11-MT insert: </a> insert: </cite> ] of all three classes of container are identical, different classes may be used to indicate informally further information. An rdf:Bag is used to indicate that the container is intended to be unordered. An rdf:Seq is used to indicate that the order indicated by the numerical order of the delete: <a href="#ch_containermembershipproperty"> insert: <a href="#ch_containermembershipproperty"> container member ship membership properties of the container is intended to be significant. An rdf:Alt container is used to indicate that typical processing of the container will be to select one of the members.
Just as a hen house may have the property that it is made of wood, that does not mean that all the hens it contains are made of wood, a property of a container is not necessarily a property of all of its members.
RDF containers are defined by the following classes and properties.
delete: <h4> delete: <a id="ch_container" name="ch_container"> delete: </a> insert: <section id="ch_container" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"> The rdfs:Container
class is a super-class of the RDF Container classes, i.e. rdf:Bag
, delete: <a
href="#ch_seq"> insert: <a href="#ch_seq"> rdf:Seq
, delete: <a
href="#ch_alt"> insert: <a href="#ch_alt"> rdf:Alt
.
The rdf:Bag
class is the class of RDF 'Bag' containers. It is a subclass of delete: <a
href="#ch_container"> insert: <a href="#ch_container"> rdfs:Container
. Whilst formally it is no different from an rdf:Seq
or an delete: <a
href="#ch_alt"> insert: <a href="#ch_alt"> rdf:Alt
, the rdf:Bag
class is used conventionally to indicate to a human reader that the container is intended to be unordered.
The rdf:Seq
class is the class of RDF 'Sequence' containers. It is a subclass of delete: <a
href="#ch_container"> insert: <a href="#ch_container"> rdfs:Container
. Whilst formally it is no different from an rdf:Bag
or an delete: <a
href="#ch_alt"> insert: <a href="#ch_alt"> rdf:Alt
, the rdf:Seq
class is used conventionally to indicate to a human reader that the numerical ordering of the container membership properties of the container is intended to be significant.
The rdf:Alt
class is the class of RDF 'Alternative' containers. It is a subclass of delete: <a
href="#ch_container"> insert: <a href="#ch_container"> rdfs:Container
. Whilst formally it is no different from an rdf:Seq
or an delete: <a
href="#ch_bag"> insert: <a href="#ch_bag"> rdf:Bag
, the rdf:Alt
class is used conventionally to indicate to a human reader that typical processing will be to select one of the members of the container. The first member of the container, i.e. the value of the delete: <a
href="#ch_containermembershipproperty"> insert: <a href="#ch_containermembershipproperty"> rdf:_1
property, is the default choice.
The rdfs:ContainerMembershipProperty
class has as instances the properties rdf:_1, rdf:_2, rdf:_3 ...
that are used to state that a resource is a member of a container. rdfs:ContainerMembershipProperty
is a delete: <a
href="#def-subclass"> insert: <a href="#def-subclass"> subclass of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
. Each instance of rdfs:ContainerMembershipProperty
is an delete: <a
href="#ch_subpropertyof"> insert: <a href="#ch_subpropertyof"> rdfs:subPropertyOf
the delete: <a
href="#ch_member"> insert: <a href="#ch_member"> rdfs:member
property.
Given a container C, a triple of the form:
delete: <p> insert: <code> C rdf:_nnn O delete: </p> insert: </code>
where insert: <code> nnn insert: </code>
is the decimal representation of an integer greater than 0 with no leading zeros, states that O is a member of the container C.
Container membership properties may be applied to resources other than containers.
delete: <h4> delete: <a id="ch_member" name="ch_member"> delete: </a> insert: </section> rdfs:member
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is a super-property of all the container membership properties i.e. each container membership property has an rdfs:subPropertyOf
relationship to the property rdfs:member
.
The rdfs:domain
of rdfs:member
is delete: <a
href="#ch_resource"> rdfs:Resource delete: </a> delete: </code> . The delete: <a
href="#ch_range"> delete: <code> rdfs:range delete: </code> delete: </a> of delete: <code> rdfs:member delete: </code> is delete: <code> rdfs:Resource
. delete: </p> delete: <h3> delete: <a id="ch_collectionvocab" name="ch_collectionvocab"> The insert: <a href="#ch_range"> insert: <code> rdfs:range insert: </code>
insert: </a> of insert: <code> rdfs:member insert: </code>
is insert: <code> insert: <a href="#ch_resource"> rdfs:Resource insert: </a> insert: </code>
. insert: </p>
insert: <em> This section is non-normative. insert: </em> insert: </p>
RDF containers are open in the sense that the core RDF specifications define no mechanism to state that there are no more members. The RDF Collection vocabulary of classes and properties can describe a closed collection, i.e. one that can have no more members. The reader is referred to the delete: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#collections"> collections delete: </a> section of the RDF primer for an informal introduction to collections with examples.
A collection is represented as a list of items, a representation that will be familiar to those with experience of Lisp and similar programming languages. There is a delete: <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-Syntax-parsetype-Collection"> insert: <a href="http://www.w3.org/TR/turtle/#collections"> shorthand notation in the RDF/XML Turtle syntax specification [ delete: <a href="#ref-rdf-syntax"> RDF-SYNTAX delete: </a> ] for representing collections.
delete: <p> delete: <strong> insert: <div class="note">RDFS does not require that there be only one first element of a list-like structure, or even that a list-like structure have a first element.
delete: <h4> delete: <a id="ch_list" name="ch_list"> delete: </a> insert: </div> rdf:List
is an instance of rdfs:Class
that can be used to build descriptions of lists and other list-like structures.
rdf:first
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that can be used to build descriptions of lists and other list-like structures.
A triple of the form:
delete: <p> insert: <code> L rdf:first O delete: </p> insert: </code>
states that there is a first-element relationship between L and O.
The rdfs:domain
of rdf:first
is rdf:List
. The rdfs:range
of rdf:first
is rdfs:Resource
.
rdf:rest
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that can be used to build descriptions of lists and other list-like structures.
A triple of the form:
delete: <p> insert: <code> L rdf:rest O delete: </p> insert: </code>
states that there is a rest-of-list relationship between L and O.
The rdfs:domain
of rdf:rest
is rdf:List
. The rdfs:range
of rdf:rest
is rdf:List
.
The resource rdf:nil
is an instance of delete: <a
href="#ch_list"> insert: <a href="#ch_list"> rdf:List
that can be used to represent an empty list or other list-like structure.
A triple of the form:
delete: <p> insert: <code> L rdf:rest rdf:nil delete: </p> insert: </code>
states that L is an instance of delete: <a
href="#ch_list"> insert: <a href="#ch_list"> rdf:List
that has one item; that item can be indicated using the rdf:first
property.
The original RDF Model and Syntax Specification [ delete: <a href="#rdfmscite"> RDFMS delete: </a> ] defined a vocabulary for describing RDF statements without stating them. [ delete: <a href="#rdfmscite"> RDFMS delete: </a> ] did not provide a formal semantics for this vocabulary, and the informal definition that was provided was somewhat inconsistent. The current RDF specification does not assign a normative formal semantics to this vocabulary. However, an intended meaning of this vocabulary (which generally clarifies the intent of the [ delete: <a href="#rdfmscite"> RDFMS delete: </a> ] definition) is described here. An informal introduction to the reification vocabulary, with examples, may be found in the RDF Primer [ delete: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#reification"> RDF-PRIMER delete: </a> ]. delete: </p> delete: <h4> delete: <a id="ch_statement" name="ch_statement"> delete: </a> insert: <em> This section is non-normative. insert: </em> insert: </p>
insert: <section id="ch_statement" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"> rdf:Statement
is an instance of rdfs:Class.
It is intended to represent the class of RDF statements. An RDF statement is the statement made by a token of an RDF delete: <a
href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-triples"> triple delete: </a> . triple. The subject of an RDF statement is the instance of delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource
identified by the subject of the triple. The predicate of an RDF statement is the instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
identified by the predicate of the triple. The object of an RDF statement is the instance of delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource
identified by the object of the triple. rdf:Statement
is in the domain of the properties rdf:predicate
, rdf:subject
and rdf:object
. Different individual rdf:Statement
instances may have the same values for their rdf:predicate
, rdf:subject
and rdf:object
properties.
rdf:subject
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to state the subject of a statement.
A triple of the form:
delete: <p> insert: <code> S rdf:subject R delete: </p> insert: </code>
states that S is an instance of delete: <code> delete: <a
href="#ch_statement"> rdf:Statement delete: </a> delete: </code> and that the subject of S is R. delete: </p> delete: <p class="schemacomment"> The delete: <a
href="#ch_domain"> delete: <code> rdfs:domain delete: </code> delete: </a> of delete: <code> rdf:subject delete: </code> is rdf:Statement
and that the subject of S is R. insert: </p>
The insert: <a href="#ch_domain"> insert: <code> rdfs:domain insert: </code>
insert: </a> of insert: <code> rdf:subject insert: </code>
is insert: <code> insert: <a href="#ch_statement"> rdf:Statement insert: </a> insert: </code>
. The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdf:subject
is rdfs:Resource
.
rdf:predicate is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to state the predicate of a statement.
A triple of the form:
delete: <p> insert: <code> S rdf:predicate P delete: </p> insert: </code>
states that S is an instance of delete: <a
href="#ch_statement"> insert: <a href="#ch_statement"> rdf:Statement
, that P is an instance of rdf:Property
and that the delete: <a
href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-data-model"> predicate delete: </a> of S is P.
The rdfs:domain
of rdf:predicate
is delete: <a
href="#ch_statement"> insert: <a href="#ch_statement"> rdf:Statement
and the delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
is delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource
.
rdf:object is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to state the object of a statement.
A triple of the form:
delete: <p> insert: <code> S rdf:object O delete: </p> insert: </code>
states that S is an instance of delete: <a
href="#ch_statement"> insert: <a href="#ch_statement"> rdf:Statement
and that the object of S is O.
The rdfs:domain
of rdf:object
is delete: <a
href="#ch_statement"> insert: <a href="#ch_statement"> rdf:Statement
. The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdf:object
is rdfs:Resource
.
The following utility classes and properties are defined in the RDF core namespaces.
delete: <h4> delete: <a id="ch_seealso" name="ch_seealso"> delete: </a> insert: <section id="ch_seealso" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"> rdfs:seeAlso
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to indicate a resource that might provide additional information about the subject resource.
A triple of the form:
delete: <p> insert: <code> S rdfs:seeAlso O delete: </p> insert: </code>
states that the resource O may provide additional information about S. It may be possible to retrieve representations of O from the Web, but this is not required. When such representations may be retrieved, no constraints are placed on the format of those representations.
The rdfs:domain
of rdfs:seeAlso
is delete: <a
href="#ch_resource"> rdfs:Resource delete: </a> delete: </code> . The delete: <code> delete: <a
href="#ch_range"> rdfs:range delete: </a> delete: </code> of delete: <code> rdfs:seeAlso delete: </code> is delete: <code> rdfs:Resource
. delete: </p> delete: <h4> delete: <a id="ch_isdefinedby" name="ch_isdefinedby"> delete: </a> The insert: <code> insert: <a href="#ch_range"> rdfs:range insert: </a> insert: </code>
of insert: <code> rdfs:seeAlso insert: </code>
is insert: <code> insert: <a href="#ch_resource"> rdfs:Resource insert: </a> insert: </code>
. insert: </p>
rdfs:isDefinedBy
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that is used to indicate a resource defining the subject resource. This property may be used to indicate an RDF vocabulary in which a resource is described.
A triple of the form:
delete: <p> insert: <code> S rdfs:isDefinedBy O delete: </p> insert: </code>
states that the resource O defines S. It may be possible to retrieve representations of O from the Web, but this is not required. When such representations may be retrieved, no constraints are placed on the format of those representations. rdfs:isDefinedBy
is a delete: <a
href="#def-subproperty"> insert: <a href="#def-subproperty"> subproperty of delete: <a
href="#ch_seealso"> insert: <a href="#ch_seealso"> rdfs:seeAlso
.
The rdfs:domain
of rdfs:isDefinedBy
is delete: <a
href="#ch_resource"> rdfs:Resource delete: </a> delete: </code> . The delete: <code> delete: <a
href="#ch_range"> rdfs:range delete: </a> delete: </code> of delete: <code> rdfs:isDefinedBy delete: </code> is delete: <code> rdfs:Resource
. delete: </p> delete: <h4> delete: <a id="ch_value" name="ch_value"> delete: </a> The insert: <code> insert: <a href="#ch_range"> rdfs:range insert: </a> insert: </code>
of insert: <code> rdfs:isDefinedBy insert: </code>
is insert: <code> insert: <a href="#ch_resource"> rdfs:Resource insert: </a> insert: </code>
. insert: </p>
rdf:value
is an instance of delete: <a
href="#ch_property"> insert: <a href="#ch_property"> rdf:Property
that may be used in describing structured values.
rdf:value has no meaning on its own. It is provided as a piece of vocabulary that may be used in idioms such as illustrated in delete: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example16"> example 16 delete: </a> of the RDF primer below: insert: </p>
insert: <div class="example"><http://www.example.com/2002/04/products#item10245> <http://www.example.org/terms/weight> [ delete: <a href="#ref-rdf-primer"> RDF-PRIMER delete: </a> ]. rdf:value 2.4 ; <http://www.example.org/terms/units> <http://www.example.org/units/kilograms> ] . insert: </pre>insert: </div>
Despite the lack of formal specification of the meaning of this property, there is value in defining it to encourage the use of a common idiom in examples of this kind.
The rdfs:domain
of rdf:value
is delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource
. The delete: <a
href="#ch_range"> insert: <a href="#ch_range"> rdfs:range
of rdf:value
is delete: <a
href="#ch_resource"> insert: <a href="#ch_resource"> rdfs:Resource
.
insert: <em> This table presents section is non-normative. insert: </em> insert: </p>
insert: <p>The tables in this section provide an overview of the vocabulary of RDF, drawing together vocabulary originally defined in the RDF Model and Syntax specification with classes and properties that originate with RDF Schema. delete: </p> delete: <h3> delete: <a id="ch_sumclasses" name="ch_sumclasses"> delete: </a> RDF Schema vocabulary. insert: </p>
insert: <section id="ch_sumclasses" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">Class name | comment |
---|---|
insert: <a href="#ch_resource"> rdfs:Resource insert: </a> | The class resource, everything. |
insert: <a href="#ch_literal"> rdfs:Literal insert: </a> | The class of literal values, e.g. textual strings and integers. |
rdf:XMLLiteral insert: <a href="#ch_langstring"> rdf:langString insert: </a> | The class of XML literals language-tagged string literal values. |
rdfs:Class insert: <a href="#ch_html"> rdf:HTML insert: </a> | The class of classes. HTML literal values. |
rdf:Property insert: <a href="#ch_xmlliteral"> rdf:XMLLiteral insert: </a> | The class of RDF properties. XML literal values. |
rdfs:Datatype insert: <a href="#ch_class"> rdfs:Class insert: </a> | The class of RDF datatypes. classes. |
rdf:Statement insert: <a href="#ch_property"> rdf:Property insert: </a> | The class of RDF statements. properties. |
insert: <a href="#ch_datatype"> rdfs:Datatype insert: </a> insert: </td> | insert: <td>The class of RDF datatypes. insert: </td> | insert: </tr>
insert: <a href="#ch_statement"> rdf:Statement insert: </a> insert: </td> | insert: <td>The class of RDF statements. insert: </td> | insert: </tr>
insert: <a href="#ch_bag"> rdf:Bag insert: </a> | The class of unordered containers. |
insert: <a href="#ch_seq"> rdf:Seq insert: </a> | The class of ordered containers. |
insert: <a href="#ch_alt"> rdf:Alt insert: </a> | The class of containers of alternatives. |
insert: <a href="#ch_container"> rdfs:Container insert: </a> | The class of RDF containers. |
insert: <a href="#ch_containermembershipproperty"> rdfs:ContainerMembershipProperty insert: </a> | The class of container membership properties, rdf:_1, rdf:_2, ..., all of which are sub-properties of 'member'. |
insert: <a href="#ch_list"> rdf:List insert: </a> | The class of RDF Lists. |
Property name | comment | domain | range |
---|---|---|---|
insert: <a href="#ch_type"> rdf:type insert: </a> | The subject is an instance of a class. | rdfs:Resource | rdfs:Class |
insert: <a href="#ch_subclassof"> rdfs:subClassOf insert: </a> | The subject is a subclass of a class. | rdfs:Class | rdfs:Class |
insert: <a href="#ch_subpropertyof"> rdfs:subPropertyOf insert: </a> | The subject is a subproperty of a property. | rdf:Property | rdf:Property |
insert: <a href="#ch_domain"> rdfs:domain insert: </a> | A domain of the subject property. | rdf:Property | rdfs:Class |
insert: <a href="#ch_range"> rdfs:range insert: </a> | A range of the subject property. | rdf:Property | rdfs:Class |
insert: <a href="#ch_label"> rdfs:label insert: </a> | A human-readable name for the subject. | rdfs:Resource | rdfs:Literal |
insert: <a href="#ch_comment"> rdfs:comment insert: </a> | A description of the subject resource. | rdfs:Resource | rdfs:Literal |
insert: <a href="#ch_member"> rdfs:member insert: </a> | A member of the subject resource. | rdfs:Resource | rdfs:Resource |
insert: <a href="#ch_first"> rdf:first insert: </a> | The first item in the subject RDF list. | rdf:List | rdfs:Resource |
insert: <a href="#ch_rest"> rdf:rest insert: </a> | The rest of the subject RDF list after the first item. | rdf:List | rdf:List |
insert: <a href="#ch_seealso"> rdfs:seeAlso insert: </a> | Further information about the subject resource. | rdfs:Resource | rdfs:Resource |
insert: <a href="#ch_isdefinedby"> rdfs:isDefinedBy insert: </a> | The definition of the subject resource. | rdfs:Resource | rdfs:Resource |
insert: <a href="#ch_value"> rdf:value insert: </a> | Idiomatic property used for structured values (see the RDF Primer for delete: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#example16"> an example delete: </a> of its usage). values. | rdfs:Resource | rdfs:Resource |
insert: <a href="#ch_subject"> rdf:subject insert: </a> | The subject of the subject RDF statement. | rdf:Statement | rdfs:Resource |
insert: <a href="#ch_predicate"> rdf:predicate insert: </a> | The predicate of the subject RDF statement. | rdf:Statement | rdfs:Resource |
insert: <a href="#ch_object"> rdf:object insert: </a> | The object of the subject RDF statement. | rdf:Statement | rdfs:Resource |
In addition to these classes and properties, RDF also uses properties called rdf:_1
, rdf:_2
, rdf:_3
... etc., each of which is both a sub-property of rdfs:member
and an instance of the class rdfs:ContainerMembershipProperty
. There is also an instance of rdf:List
called rdf:nil
that is an empty rdf:List
.
insert: <em> This section is non-normative. insert: </em> insert: </p>
The RDF Schema design was originally produced by the RDF Schema Working Group (1997-2000). The current specification is largely an editorial clarification of that design, and has benefited greatly from the hard work of the RDF Core Working Group members , and from implementation feedback from many members of the delete: <a href="http://www.w3.org/RDF/Interest/"> insert: <a href="http://www.w3.org/RDF/Interest/"> RDF Interest Group . In 2013-2014 Guus Schreiber edited this document on behalf of the insert: <a href="http://www.w3.org/2011/rdf-wg/"> RDF Working Group insert: </a> to bring it in line with the RDF 1.1 specifications.
David Singer of IBM was the chair of the original RDF Schema group throughout most of the development of this specification; we thank David for his efforts and thank IBM for supporting him and us in this endeavor. Particular thanks are also due to Andrew Layman for his editorial work on early versions of this specification.
The original RDF Schema Working Group membership included:
Nick Arnett (Verity), Dan Brickley (ILRT / University of Bristol), Walter Chang (Adobe), Sailesh Chutani (Oracle), Ron Daniel (DATAFUSION), Charles Frankston (Microsoft), Joe Lapp (webMethods Inc.), Patrick Gannon (CommerceNet), RV Guha (Epinions, previously of Netscape Communications), Tom Hill (Apple Computer), Renato Iannella (DSTC), Sandeep Jain (Oracle), Kevin Jones, (InterMind), Emiko Kezuka (Digital Vision Laboratories), Ora Lassila (Nokia Research Center), Andrew Layman (Microsoft), John McCarthy (Lawrence Berkeley National Laboratory), Michael Mealling (Network Solutions), Norbert Mikula (DataChannel), Eric Miller (OCLC), Frank Olken (Lawrence Berkeley National Laboratory), Sri Raghavan (Digital/Compaq), Lisa Rein (webMethods Inc.), Tsuyoshi Sakata (Digital Vision Laboratories), Leon Shklar (Pencom Web Works), David Singer (IBM), Wei (William) Song (SISU), Neel Sundaresan (IBM), Ralph Swick (W3C), ( insert: <abbr title="World Wide Web Consortium"> W3C insert: </abbr> ), Naohiko Uramoto (IBM), Charles Wicksteed (Reuters Ltd.), Misha Wolf (Reuters Ltd.)
delete: <h2> delete: <a id="ch_appendix_figs" name="ch_appendix_figs"> delete: </a> insert: </section>insert: <em> This section is non-normative. insert: </em> insert: </p>
insert: <p>Changes delete: </h2> delete: <p> The following is an outline of the main changes made to this specification, latest first, since the Last Call Working Draft of delete: <a href="http://www.w3.org/TR/2003/WD-rdf-schema-20030123/"> 23 January 2003 delete: </a> . See the delete: <a href="http://www.w3.org/2001/sw/RDFCore/20030123-issues/#schema"> Last Call issue tracking document delete: </a> for details of the specific issues raised regarding this specification. RDF 1.1 Recommendation
Changes for RDF 1.1 Proposed Edited Recommendation insert: </p>
insert: <ul> rdf:langString insert: </code>
and insert: <code> rdf:HTML insert: </code>
. rdf:HTML insert: </code>
and insert: <code> rdf:XMLLiteral insert: </code>
as non-normative.