RDF/XML Syntax Specification (Revised) (original) (raw)

Abstract

The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web.

This document defines anXMLsyntax for RDF called RDF/XML in terms ofNamespaces in XML, theXML Information Setand XML Base. The formal grammar for the syntax is annotated with actions generating triples of theRDF graphas defined inRDF Concepts and Abstract Syntax. The triples are written using theN-TriplesRDF graph serializing format which enables more precise recording of the mapping in a machine processable form. The mappings are recorded as tests cases, gathered and published inRDF Test Cases.

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

Publication as a Proposed Recommendationdoes not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This is one document in a set of six(Primer, Concepts, Syntax, Semantics, Vocabulary, and Test Cases) intended to jointly replace the original Resource Description Framework specifications, RDF Model and Syntax (1999 Recommendation) and RDF Schema (1999 Proposed Recommendation). It has been developed by the RDF Core Working Group as part of the W3C Semantic Web Activity (Activity Statement, Group Charter) for publication on 15 December 2003.

The design expressed in earlier versions of these documents has been widely reviewed and satisfies the Working Group's chartered technical requirements. The Working Group has addressed all comments received, making changes as necessary. Many implementations have been reported, covering among them all features of the specification. Changes to this document since the Second Last Call Working Draft are detailed in the Appendix B.

W3C Advisory Committee Representatives are now invited to submit their formal review via Web form, as described in the Call for Review. Additional comments may be sent to a Team-only list, w3t-semweb-review@w3.org. The public is invited to send comments to www-rdf-comments@w3.org(archive) and to participate in general discussion of related technology on www-rdf-interest@w3.org (archive). The review period extends until .

The W3C maintains a list of any patent disclosures related to this work.

1 Introduction

This document defines theXML [XML]syntax for RDF graphs which was originally defined in theRDF Model & Syntax [RDF-MS] W3C Recommendation. Subsequent implementations of this syntax and comparison of the resulting RDF graphs have shown that there was ambiguity — implementations generated different graphs and certain syntax forms were not widely implemented.

This document revises theoriginal RDF/XML grammarin terms ofXML Information Set [INFOSET] information items which moves away from the rather low-level details of XML, such as particular forms of empty elements. This allows the grammar to be more precisely recorded and the mapping from the XML syntax to the RDF Graph more clearly shown. The mapping to the RDF graph is done by emitting statements in the form defined in theN-Triplessection ofRDF Test Cases [RDF-TESTS]which creates an RDF graph, that has semantics defined byRDF Semantics [RDF-SEMANTICS].

The complete specification of RDF consists of a number of documents:

• RDF Primer [RDF-PRIMER]
• RDF Concepts and Abstract Syntax [RDF-CONCEPTS]
• RDF Semantics [RDF-SEMANTICS]
• RDF/XML Syntax (this document)
• RDF Vocabulary Description Language 1.0: RDF Schema [RDF-VOCABULARY]
• RDF Test Cases [RDF-TESTS]

For a longer introduction to the RDF/XML syntax with a historical perspective, seeRDF: Understanding the Striped RDF/XML Syntax [STRIPEDRDF].

2 An XML Syntax for RDF

This section introduces the RDF/XML syntax, describes how it encodes RDF graphs and explains this with examples. If there is any conflict between this informal description and the formal description of the syntax and grammar in sections6 Syntax Data Model and7 RDF/XML Grammar, the latter two sections take precedence.

2.1 Introduction

TheRDF Concepts and Abstract Syntax [RDF-CONCEPTS]defines theRDF Graph data model (Section 3.1) and theRDF Graph abstract syntax (Section 6). Along with theRDF Semantics [RDF-SEMANTICS]this provides an abstract syntax with a formal semantics for it. The RDF graph hasnodesand labeled directed arcs_that link pairs of nodes and this is represented as a set of RDF tripleswhere each triple contains a_subject node, predicate and object node. Nodes areRDF URI references, RDF literalsor are blank nodes. Blank nodes may be given a document-local, non-RDF URI references identifier called ablank node identifier. Predicates areRDF URI referencesand can be interpreted as either a relationship between the two nodes or as defining an attribute value (object node) for some subject node.

In order to encode the graph in XML, the nodes and predicates have to be represented in XML terms — element names, attribute names, element contents and attribute values. RDF/XML uses XMLQNamesas defined in Namespaces in XML [XML-NS]to representRDF URI references. All QNames have a namespace name which is a URI reference and a shortlocal name. In addition, QNames can either have a short prefixor be declared with the default namespace declaration and have none (but still have a namespace name)

TheRDF URI referencerepresented by a QName is determined by appending thelocal namepart of the QName after thenamespace name (URI reference) part of the QName. This is used to shorten theRDF URI referencesof all predicates and some nodes.RDF URI references identifying subject and object nodes can also be stored as XML attribute values.RDF literals, which can only be object nodes, become either XML element text content or XML attribute values.

A graph can be considered a collection of paths of the form node, predicate arc, node, predicate arc, node, predicate arc, ... node which cover the entire graph. In RDF/XML these turn into sequences of elements inside elements which alternate between elements for nodes and predicate arcs. This has been called a series of node/arc stripes. The node at the start of the sequence turns into the outermost element, the next predicate arc turns into a child element, and so on. The stripes generally start at the top of an RDF/XML document and always begin with nodes.

Several RDF/XML examples are given in the following sections building up to complete RDF/XML documents. Example 7is the first complete RDF/XML document.

2.2 Node Elements and Property Elements

An RDF graph is given in Figure 1where the nodes are represented as ovals and contain theirRDF URI referenceswhere they have them, all the predicate arcs are labeled withRDF URI referencesandplain literalnodes have been written in rectangles.

If we follow one node, predicate arc ... , node path through the graph shown in Figure 2:

The left hand side of the Figure 2 graph corresponds to the node/predicate arc stripes:

1. Node with RDF URI reference http://www.w3.org/TR/rdf-syntax-grammar
2. Predicate Arc labeled with RDF URI reference http://example.org/terms/editor
3. Node with no RDF URI reference
4. Predicate Arc labeled with RDF URI reference http://example.org/terms/homePage
5. Node with RDF URI reference http://purl.org/net/dajobe/

In RDF/XML, the sequence of 5 nodes and predicate arcs on the left hand side of Figure 2 corresponds to the usage of five XML elements of two types, for the graph nodes and predicate arcs. These are conventionally called node elements and_property elements_ respectively. In the striping shown inExample 1, rdf:Description is the node element (used three times for the three nodes) andex:editor and ex:homePage are the two property elements.

<rdf:Description> <ex:editor> <rdf:Description> <ex:homePage> <rdf:Description> </rdf:Description> </ex:homePage> </rdf:Description> </ex:editor> </rdf:Description>

The Figure 2 graph consists of some nodes that areRDF URI references(and others that are not) and this can be added to the RDF/XML using the rdf:about attribute on node elements to give the result in Example 2:

<rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://www.w3.org/TR/rdf-syntax-grammar"> ex:editor rdf:Description ex:homePage <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://purl.org/net/dajobe/">

Adding the other two paths through the Figure 1graph to the RDF/XML inExample 2gives the result in Example 3(this example fails to show that the blank node is shared between the two paths, see 2.10):

<rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://www.w3.org/TR/rdf-syntax-grammar"> ex:editor rdf:Description ex:homePage <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://purl.org/net/dajobe/">

<rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://www.w3.org/TR/rdf-syntax-grammar"> ex:editor rdf:Description ex:fullNameDave Beckett

<rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://www.w3.org/TR/rdf-syntax-grammar"> dc:titleRDF/XML Syntax Specification (Revised)

2.3 Multiple Property Elements

There are several abbreviations that can be used to make common uses easier to write down. In particular, it is common that a subject node in the RDF graph has multiple outgoing predicate arcs. RDF/XML provides an abbreviation for the corresponding syntax when a node element about a resource has multiple property elements. This can be abbreviated by using multiple child property elements inside the node element describing the subject node.

Taking Example 3, there are two node elements that can take multiple property elements. The subject node with URI referencehttp://www.w3.org/TR/rdf-syntax-grammarhas property elements ex:editor and ex:titleand the node element for the blank node can take ex:homePageand ex:fullName. This abbreviation gives the result shown in Example 4(this example does show that there is a single blank node):

<rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://www.w3.org/TR/rdf-syntax-grammar"> ex:editor rdf:Description ex:homePage <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://purl.org/net/dajobe/"> ex:fullNameDave Beckett dc:titleRDF/XML Syntax Specification (Revised)

2.4 Empty Property Elements

When a predicate arc in an RDF graph points to an object node which has no further predicate arcs, which appears in RDF/XML as an empty node element<rdf:Description rdf:about="..."> </rdf:Description>(or <rdf:Description rdf:about="..." />) this form can be shortened. This is done by using the RDF URI referenceof the object node as the value of an XML attribute rdf:resourceon the containing property element and making the property element empty.

In this example, the property element ex:homePagecontains an empty node element with theRDF URI reference http://purl.org/net/dajobe/. This can be replaced with the empty property element form giving the result shown inExample 5:

<rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://www.w3.org/TR/rdf-syntax-grammar"> ex:editor rdf:Description <ex:homePage rdf:resource="" title="undefined" rel="noopener noreferrer">http://purl.org/net/dajobe/"/> ex:fullNameDave Beckett dc:titleRDF/XML Syntax Specification (Revised)

2.5 Property Attributes

When a property element's content is string literal, it may be possible to use it as an XML attribute on the containing node element. This can be done for multiple properties on the same node element only if the property element name is not repeated (required by XML — attribute names are unique on an XML element) and any in-scope xml:lang on the property element's string literal (if any) are the same (see Section 2.7) This abbreviation is known as a _Property Attribute_and can be applied to any node element.

This abbreviation can also be used when the property element isrdf:type and it has an rdf:resource attribute the value of which is interpreted as aRDF URI reference object node.

In Example 5:, there are two property elements with string literal content, the dc:title and ex:fullNameproperty elements. These can be replaced with property attributes giving the result shown in Example 6:

<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar" dc:title="RDF/XML Syntax Specification (Revised)"> ex:editor <rdf:Description ex:fullName="Dave Beckett"> <ex:homePage rdf:resource="" title="undefined" rel="noopener noreferrer">http://purl.org/net/dajobe/"/>

2.6 Completing the Document: Document Element and XML Declaration

To create a complete RDF/XML document, the serialization of the graph into XML is usually contained inside an rdf:RDFXML element which becomes the top-level XML document element. Conventionally the rdf:RDF element is also used to declare the XML namespaces that are used, although that is not required. When there is only one top-level node element insiderdf:RDF, the rdf:RDF can be omitted although any XML namespaces must still be declared.

The XML specification also permits an XML declaration at the top of the document with the XML version and possibly the XML content encoding. This is optional but recommended.

Completing the RDF/XML could be done for any of the correct complete graph examples fromExample 4 onwards but taking the smallestExample 6 and adding the final components, gives a complete RDF/XML representation of the originalFigure 1 graph in Example 7:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar" dc:title="RDF/XML Syntax Specification (Revised)"> ex:editor <rdf:Description ex:fullName="Dave Beckett"> <ex:homePage rdf:resource="http://purl.org/net/dajobe/" />

It is possible to omit rdf:RDF inExample 7 above since there is only onerdf:Description inside rdf:RDF but this is not shown here.

2.7 Languages: xml:lang

RDF/XML permits the use of the xml:lang attribute as defined by2.12 Language Identificationof XML 1.0 [XML]to allow the identification of content language. The xml:lang attribute can be used on any node element or property element to indicate that the included content is in the given language. Typed literalswhich includes XML literalsare not affected by this attribute. The most specific in-scope language present (if any) is applied to property element string literal content or property attribute values. The xml:lang="" form indicates the absence of a language identifier.

Some examples of marking content languages for RDF properties are shown inExample 8:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="" title="undefined" rel="noopener noreferrer">http://purl.org/dc/elements/1.1/"> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://www.w3.org/TR/rdf-syntax-grammar"> dc:titleRDF/XML Syntax Specification (Revised) <dc:title xml:lang="en">RDF/XML Syntax Specification (Revised) <dc:title xml:lang="en-US">RDF/XML Syntax Specification (Revised)

<rdf:Description rdf:about="http://example.org/buecher/baum" xml:lang="de"> dc:titleDer Baum dc:descriptionDas Buch ist au�ergew�hnlich <dc:title xml:lang="en">The Tree

2.8 XML Literals: rdf:parseType="Literal"

RDF allows XML literals([RDF-CONCEPTS] Section 5, XML Content within an RDF graph) to be given as the object node of a predicate. These are written in RDF/XML as content of a property element (not a property attribute) and indicated using therdf:parseType="Literal" attribute on the containing property element.

An example of writing an XML literal is given inExample 9 where there is a single RDF triple with the subject nodeRDF URI reference http://example.org/item01, the predicateRDF URI reference http://example.org/stuff/1.0/prop (fromex:prop) and the object node with XML literal content beginning a:Box.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/item01"> <ex:prop rdf:parseType="Literal" xmlns:a="" title="undefined" rel="noopener noreferrer">http://example.org/a#"><a:Box required="true"> <a:widget size="10" /> <a:grommit id="23" />

2.9 Typed Literals: rdf:datatype

RDF allowstyped literalsto be given as the object node of a predicate. Typed literals consist of a literal string and a datatypeRDF URI reference. These are written in RDF/XML using the same syntax for literal string nodes in the property element form (not property attribute) but with an additionalrdf:datatype="datatypeURI"attribute on the property element. Any RDF URI reference can be used in the attribute.

An example of an RDFtyped literalis given in Example 10 where there is a single RDF triple with the subject nodeRDF URI reference http://example.org/item01, the predicateRDF URI reference http://example.org/stuff/1.0/size (fromex:size) and the object node with thetyped literal("123", http://www.w3.org/2001/XMLSchema#int) to be interpreted as anW3C XML Schema [XML-SCHEMA2] datatype int.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/item01"> <ex:size rdf:datatype="123" title="undefined" rel="noopener noreferrer">http://www.w3.org/2001/XMLSchema#int">123

2.10 Identifying Blank Nodes: rdf:nodeID

Blank nodes in the RDF graph are distinct but have no RDF URI reference identifier. It is sometimes required that the same graph blank node is referred to in the RDF/XML in multiple places, such as at the subject and object of several RDF triples. In this case, a blank node identifiercan be given to the blank node for identifying it in the document. Blank node identifiers in RDF/XML are scoped to the containing XML Information Setdocument information item. A blank node identifier is used on a node element to replacerdf:about="RDF URI reference"or on a property element to replacerdf:resource="RDF URI reference"with rdf:nodeID="blank node identifier"in both cases.

Taking Example 7 and explicitly giving a blank node identifier of abc to the blank node in it gives the result shown in Example 11. The second rdf:Description property element is about the blank node.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar" dc:title="RDF/XML Syntax Specification (Revised)"> <ex:editor rdf:nodeID="abc"/>

<rdf:Description rdf:nodeID="abc" ex:fullName="Dave Beckett"> <ex:homePage rdf:resource="" title="undefined" rel="noopener noreferrer">http://purl.org/net/dajobe/"/>

2.11 Omitting Blank Nodes: rdf:parseType="Resource"

Blank nodes (not RDF URI reference nodes) in RDF graphs can be written in a form that allows the<rdf:Description> </rdf:Description> pair to be omitted. The omission is done by putting anrdf:parseType="Resource"attribute on the containing property element that turns the property element into a property-and-node element, which can itself have both property elements and property attributes. Property attributes and the rdf:nodeID attribute are not permitted on property-and-node elements.

Taking the earlier Example 7, the contents of the ex:editor property element could be alternatively done in this fashion to give the form shown in Example 12:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar" dc:title="RDF/XML Syntax Specification (Revised)"> <ex:editor rdf:parseType="Resource"> ex:fullNameDave Beckett <ex:homePage rdf:resource="" title="undefined" rel="noopener noreferrer">http://purl.org/net/dajobe/"/>

2.12 Omitting Nodes: Property Attributes on an empty Property Element

If all of the property elements on a blank node element have string literal values with the same in-scope xml:langvalue (if present) and each of these property elements appears at most once and there is at most one rdf:type property element with a RDF URI reference object node, these can be abbreviated by moving them to be property attributes on the containing property element which is made an empty element.

Taking the earlier Example 5, the ex:editor property element contains a blank node element with two property elementsex:fullname and ex:homePage.ex:homePage is not suitable here since it does not have a string literal value, so it is being_ignored_ for the purposes of this example. The abbreviated form removes the ex:fullName property element and adds a new property attribute ex:fullName with the string literal value of the deleted property element to the ex:editor property element. The blank node element becomes implicit in the now emptyex:editor property element. The result is shown inExample 13.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar" dc:title="RDF/XML Syntax Specification (Revised)"> <ex:editor ex:fullName="Dave Beckett" />

2.13 Typed Node Elements

It is common for RDF graphs to have rdf:type predicates from subject nodes. These are conventionally called typed nodes in the graph, or typed node elements in the RDF/XML. RDF/XML allows this triple to be expressed more concisely. by replacing the rdf:Description node element name with the namespaced-element corresponding to theRDF URI reference of the value of the type relationship. There may, of course, be multiple rdf:typepredicates but only one can be used in this way, the others must remain as property elements or property attributes.

The typed node elements are commonly used in RDF/XML with the built-in classes in the RDF vocabulary:rdf:Seq, rdf:Bag, rdf:Alt,rdf:Statement, rdf:Property andrdf:List.

For example, the RDF/XML in Example 14could be written as shown in Example 15.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/thing"> <rdf:type rdf:resource="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/Document"/> dc:titleA marvelous thing

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <ex:Document rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/thing"> dc:titleA marvelous thing

2.14 Abbreviating URIs: rdf:ID and xml:base

RDF/XML allows further abbreviating RDF URI references in XML attributes in two ways. The XML Infoset provides a base URI attribute xml:basethat sets the base URI for resolving relative RDF URI references, otherwise the base URI is that of the document. The base URI applies to all RDF/XML attributes that deal with RDF URI references which are rdf:about,rdf:resource, rdf:IDand rdf:datatype.

The rdf:ID attribute on a node element (not property element, that has another meaning) can be used instead ofrdf:about and gives a relative RDF URI reference equivalent to #concatenated with the rdf:ID attribute value. So for example if rdf:ID="name", that would be equivalent to rdf:about="#name". rdf:ID provides an additional check since the same name can only appear once in the scope of an xml:base value (or document, if none is given), so is useful for defining a set of distinct, related terms relative to the same RDF URI reference.

Both forms require a base URI to be known, either from an in-scopexml:base or from the URI of the RDF/XML document.

Example 16 shows abbreviating the nodeRDF URI reference of http://example.org/here/#snack using anxml:base of http://example.org/here/ and an rdf:ID on the rdf:Description node element. The object node of the ex:prop predicate is an absolute RDF URI referenceresolved from the rdf:resource XML attribute value using the in-scope base URI to give theRDF URI reference http://example.org/here/fruit/apple.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ex="http://example.org/stuff/1.0/" xml:base="" title="undefined" rel="noopener noreferrer">http://example.org/here/"> <rdf:Description rdf:ID="snack"> <ex:prop rdf:resource="fruit/apple"/>

2.15 Container Membership Property Elements: rdf:li and rdf:_n

RDF has a set of container membership properties and corresponding property elements that are mostly used with instances of therdf:Seq, rdf:Bag and rdf:Altclasses which may be written as typed node elements. The list properties arerdf:_1, rdf:_2 etc. and can be written as property elements or property attributes as shown inExample 17. There is an rdf:lispecial property element that is equivalent tordf:_1, rdf:_2 in order, explained in detail in section 7.4. The mapping to the container membership properties is always done in the order that the rdf:li special property elements appear in XML — the document order is significant. The equivalent RDF/XML to Example 17 written in this form is shown in Example 18.

<rdf:RDF xmlns:rdf="" title="undefined" rel="noopener noreferrer">http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Seq rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/favourite-fruit"> <rdf:_1 rdf:resource="" title="undefined" rel="noopener noreferrer">http://example.org/banana"/> <rdf:_2 rdf:resource="" title="undefined" rel="noopener noreferrer">http://example.org/apple"/> <rdf:_3 rdf:resource="" title="undefined" rel="noopener noreferrer">http://example.org/pear"/>

<rdf:RDF xmlns:rdf="" title="undefined" rel="noopener noreferrer">http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Seq rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/favourite-fruit"> <rdf:li rdf:resource="" title="undefined" rel="noopener noreferrer">http://example.org/banana"/> <rdf:li rdf:resource="" title="undefined" rel="noopener noreferrer">http://example.org/apple"/> <rdf:li rdf:resource="" title="undefined" rel="noopener noreferrer">http://example.org/pear"/>

2.16 Collections: rdf:parseType="Collection"

RDF/XML allows an rdf:parseType="Collection"attribute on a property element to let it contain multiple node elements. These contained node elements give the set of subject nodes of the collection. This syntax form corresponds to a set of triples connecting the collection of subject nodes, the exact triples generated are described in detail inSection 7.2.19 Production parseTypeCollectionPropertyElt. The collection construction is always done in the order that the node elements appear in the XML document. Whether the order of the collection of nodes is significant is an application issue and not defined here.

Example 19 shows a collection of three nodes elements at the end of the ex:hasFruitproperty element using this form.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ex="" title="undefined" rel="noopener noreferrer">http://example.org/stuff/1.0/"> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/basket"> <ex:hasFruit rdf:parseType="Collection"> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/banana"/> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/apple"/> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/pear"/>

2.17 Reifying Statements: rdf:ID

The rdf:ID attribute can be used on a property element to reify the triple that it generates (Seesection 7.3 Reification Rules for the full details). The identifier for the triple should be constructed as aRDF URI referencemade from the relative URI reference# concatenated with the rdf:ID attribute value, resolved against the in-scope base URI. So for example ifrdf:ID="triple", that would be equivalent to the RDF URI referenceformed from relative URI reference #triple against the base URI. Each (rdf:ID attribute value, base URI) pair has to be unique in an RDF/XML document, see constraint-id.

Example 20 shows a rdf:IDbeing used to reify a triple made from the ex:propproperty element giving the reified triple theRDF URI reference http://example.org/triples/#triple1.

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ex="http://example.org/stuff/1.0/" xml:base="" title="undefined" rel="noopener noreferrer">http://example.org/triples/"> <rdf:Description rdf:about="" title="undefined" rel="noopener noreferrer">http://example.org/"> <ex:prop rdf:ID="triple1">blah

3 Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described inRFC 2119 [KEYWORDS].

All use of string without further qualification refers to a Unicode[UNICODE] character string; a sequence of characters represented by a code point in Unicode. (Such as defined in [CHARMOD] in section3.4 Strings).

4 RDF MIME Type, File Extension and Macintosh File Type

The Internet media type / MIME type for RDF/XML is "application/rdf+xml" — see RFC 3032 [RFC-3023] section 8.18.

**Registration Note (Informative):**For the state of the MIME type registration, consultIANA MIME Media Types[[IANA-MEDIA-TYPES]

It is recommended that RDF/XML files have the extension".rdf" (all lowercase) on all platforms.

It is recommended that RDF/XML files stored on Macintosh HFS file systems be given a file type of "rdf "(all lowercase, with a space character as the fourth letter).

5 Global Issues

5.1 The RDF Namespace and Vocabulary

**Note (Informative):**The names aboutEach and aboutEachPrefix were removed from the language and the RDF vocabulary by the RDF Core Working Group. See the resolution of issuesrdfms-abouteach andrdfms-abouteachprefixfor further information.

**Note (Informative):**The names List, first,rest and nil were added for issuerdfms-seq-representation. The names XMLLiteral and datatype were added to support RDF datatyping. The name nodeID was added for issuerdfms-syntax-incomplete. See theRDF Core Issues Listfor further information.

TheRDF namespace URI reference (or namespace name) ishttp://www.w3.org/1999/02/22-rdf-syntax-ns#and is typically used in XML with the prefix rdfalthough other prefix strings may be used. The RDF Vocabularyis identified by this namespace name and consists of the following names only:

Syntax names — not concepts

RDF Description ID about parseType resource li nodeID datatype

Class names

Seq Bag Alt Statement Property XMLLiteral List

Property names

subject predicate object type value first rest _n
where n is a decimal integer greater than zero with no leading zeros.

Resource names

nil

Any other names are not defined and SHOULD generate a warning when encountered, but should otherwise behave normally.

Within RDF/XML documents it is not permitted to use XML namespaces whose namespace name is the�RDF namespace URI reference�concatenated with additional characters.

Throughout this document the terminology rdf:_name_will be used to indicate name is from the RDF vocabulary and it has a RDF URI reference of the concatenation of the�RDF namespace URI reference� and name. For example, rdf:type has the RDF URI reference http://www.w3.org/1999/02/22-rdf-syntax-ns#type

5.2 Identifiers

TheRDF Graph(RDF Concepts and Abstract Syntax Section 3) defines three types of nodes and one type of predicate:

RDF URI reference nodes and predicates

RDF URI references (RDF Concepts and Abstract Syntax Section 3.1) can be either:

• given as XML attribute values interpreted as relative URI references that are resolved against the in-scope base URI as described in section 5.3to give absolute RDF URI references
• transformed from XML namespace-qualified element and attribute names (QNames)
• transformed from rdf:ID attribute values.

Within RDF/XML, XML QNames are transformed intoRDF URI referencesby appending the XML local name to the namespace name (URI reference). For example, if the XML namespace prefix foo has namespace name (URI reference)http://example.org/somewhere/ then the QNamefoo:bar would correspond to the RDF URI referencehttp://example.org/somewhere/bar. Note that this restricts whichRDF URI references can be made and the same URI can be given in multiple ways.

The rdf:ID values are transformed intoRDF URI referencesby appending the attribute value to the result of appending "#" to the in-scope base URI which is defined inSection 5.3 Resolving URIs

Literal nodes (always object nodes)

RDF literals (RDF Concepts and Abstract Syntax 6.5) are eitherplain literals (ibid), ortyped literals (ibid). The latter includes XML literals (ibid section 5, XML Content within an RDF graph).

Blank Node Identifiers

Blank nodes have distinct identity in the RDF graph. When the graph is written in a syntax such as RDF/XML, these blank nodes may need graph-local identifiers and a syntax in order to preserve this distinction. These local identifiers are calledblank node identifiersand are used in RDF/XML as values of the rdf:nodeID attribute with the syntax given in Production nodeIdAttr. Blank node identifiers in RDF/XML are scoped to the XML Information Setdocument information item.

If no blank node identifier is given explicitly as anrdf:nodeID attribute value then one will need to be generated (using generated-blank-node-id, see section 6.3.3). Such generated blank node identifiers must not clash with any blank node identifiers derived from rdf:nodeID attribute values. This can be implemented by any method that preserves the distinct identity of all the blank nodes in the graph, that is, the same blank node identifier is not given for different blank nodes. One possible method would be to add a constant prefix to all the rdf:nodeID attribute values and ensure no generated blank node identifiers ever used that prefix. Another would be to map all rdf:nodeID attribute values to new generated blank node identifiers and perform that mapping on all such values in the RDF/XML document.

5.3 Resolving URIs

RDF/XML supports XML Base [XML-BASE]which defines a�base-uri�accessor for each�root event� and�element event�. Relative URI references are resolved intoRDF URI referencesaccording to the algorithm specified inXML Base [XML-BASE](and RFC 2396). These specifications do not specify an algorithm for resolving a fragment identifier alone, such as #foo, or the empty string "" into anRDF URI reference. In RDF/XML, a fragment identifier is transformed into aRDF URI referenceby appending the fragment identifier to the in-scope base URI. The empty string is transformed into anRDF URI referenceby substituting the in-scope base URI.

An empty same document reference "" resolves against the URI part of the base URI; any fragment part is ignored. SeeUniform Resource Identifiers (URI) [URIS] section 4.2

**Implementation Note (Informative):**When using a hierarchical base URI that has no path component (/), it must be added before using as a base URI for resolving.

5.4 Constraints

constraint-id

Each application of production idAttrmatches an attribute. The pair formed by the�string-value�accessor of the matched attribute and the�base-uri�accessor of the matched attribute is unique within a single RDF/XML document.

The syntax of the names must match therdf-id production.

5.5 Conformance

Definition:

An RDF Document is a serialization of anRDF Graph into a concrete syntax.

Definition:

An RDF/XML Document is anRDF Document written in the recommended XML transfer syntax for RDF as defined in this document.

Conformance:

An RDF/XML Document is aconforming RDF/XML document if it adheres to the specification defined in this document.

6 Syntax Data Model

This document specifies the syntax of RDF/XML as a grammar on an alphabet of symbols. The symbols are called events in the style of the [XPATH] Information Set Mapping. A sequence of events is normally derived from an XML document, in which case they are in document order as defined below in Section 6.2 Information Set Mapping. The sequence these events form are intended to be similar to the sequence of events produced by the [SAX2] XML API from the same XML document. Sequences of events may be checked against the grammar to determine whether they are or are not syntactically well-formed RDF/XML.

The grammar productions may include actions which fire when the production is recognized. Taken together these actions define a transformation from any syntactically well-formed RDF/XML sequence of events into an RDF graph represented in theN-Tripleslanguage.

The model given here illustrates one way to create a representation of an RDF Graphfrom an RDF/XML document. It does not mandate any implementation method — any other method that results in a representation of the sameRDF Graphmay be used.

In particular:

• This specification permits anyrepresentationof an RDF graph (see [RDF-CONCEPTS]); in particular, it does not require the use ofN-Triples.
• This specification does not require the use of[XPATH] or [SAX2]
• This specification places no constraints on the order in which software transforming RDF/XML into a representation of a graph, constructs the representation of the graph.
• Software transforming RDF/XML into a representation of a graph MAY eliminate duplicate predicate arcs.

The syntax does not support non-well-formed XML documents, nor documents that otherwise do not have an XML Information Set; for example, that do not conform toNamespaces in XML [XML-NS].

The Infoset requires support forXML Base [XML-BASE]. RDF/XML uses the information item property [base URI], discussed insection 5.3

This specification requires an XML Information Set [INFOSET]which supports at least the following information items and properties for RDF/XML:

document information item

[document element], [children], [base URI]

element information item

[local name], [namespace name], [children], [attributes], [parent], [base URI]

attribute information item

[local name], [namespace name], [normalized value]

character information item

[character code]

There is no mapping of the following items to data model events:

processing instruction information item

unexpanded entity reference information item

comment information item

document type declaration information item

unparsed entity information item

notation information item

namespace information item

Other information items and properties have no mapping to syntax data model events.

Element information items with reserved XML Names (See Namein XML 1.0) are not mapped to data model element events. These are all those with property [prefix] beginning with xml (case independent comparison) and all those with [prefix] property having no value and which have [local name] beginning withxml (case independent comparison).

All information items contained inside XML elements matching theparseTypeLiteralPropertyEltproduction formXML literalsand do not follow this mapping. SeeparseTypeLiteralPropertyEltfor further information.

This section is intended to satisfy the requirements forConformancein the [INFOSET] specification. It specifies the information items and properties that are needed to implement this specification.

6.1 Events

There are nine types of event defined in the following subsections. Most events are constructed from an Infoset information item (except for URI reference,blank node,plain literal andtyped literal). The effect of an event constructor is to create a new event with a unique identity, distinct from all other events. Events have accessor operations on them and most have the string-value accessor that may be a static value or computed.

6.1.1 Root Event

Constructed from adocument information itemand takes the following accessors and values.

document-element

Set to the value of document information item property [document-element].

children

Set to the value of document information item property [children].

base-uri

Set to the value of document information item property [base URI].

language

Set to the empty string.

6.1.2 Element Event

Constructed from an element information itemand takes the following accessors and values:

local-name

Set to the value of element information item property [local name].

namespace-name

Set to the value of element information item property [namespace name].

children

Set to the value of element information item property [children].

base-uri

Set to the value of element information item property [base URI].

attributes

Made from the value of element information item property [attributes] which is a set of attribute information items.

If this set contains an attribute information item xml:lang ( [namespace name] property with the value "http://www.w3.org/XML/1998/namespace" and [local name] property value "lang") it is removed from the set of attribute information items and the �language� accessor is set to the [normalized-value] property of the attribute information item.

All remaining reserved XML Names (See Name in XML 1.0) are now removed from the set. These are, all attribute information items in the set with property [prefix] beginning with xml (case independent comparison) and all attribute information items with [prefix] property having no value and which have [local name] beginning withxml (case independent comparison) are removed. Note that the [base URI] accessor is computed by XML Base before anyxml:base attribute information item is deleted.

The remaining set of attribute information items are then used to construct a new set of Attribute Events which is assigned as the value of this accessor.

URI

Set to the string value of the concatenation of the value of the namespace-name accessor and the value of the local-name accessor.

URI-string-value

The value is the concatenation of the following in this order "<", the escaped value of the�URI�accessor and ">".

The escaping of the�URI�accessor uses the N-Triples escapes for URI references as described in 3.3 URI References.

li-counter

Set to the integer value 1.

language

Set from the�attributes� as described above. If no value is given from the attributes, the value is set to the value of the language accessor on the parent event (either aRoot Event or anElement Event), which may be the empty string.

subject

Has no initial value. Takes a value that is anIdentifier event. This accessor is used on elements that deal with one node in the RDF graph, this generally being the subject of a statement.

6.1.3 End Element Event

Has no accessors. Marks the end of the containing element in the sequence.

6.1.4 Attribute Event

Constructed from an attribute information itemand takes the following accessors and values:

local-name

Set to the value of attribute information item property [local name].

namespace-name

Set to the value of attribute information item property [namespace name].

string-value

Set to the value of the attribute information item property [normalized value] as specified by[XML] (if an attribute whose normalized value is a zero-length string, then the string-value is also a zero-length string).

URI

If �namespace-name� is present, set to a string value of the concatenation of the value of the�namespace-name� accessor and the value of the�local-name� accessor. Otherwise if �local-name� isID, about, resource, parseType or type, set to a string value of the concatenation of the�RDF namespace URI reference� and the value of the �local-name� accessor. Other non-namespaced �local-name� accessor values are forbidden.

The support for a limited set of non-namespaced names is REQUIRED and intended to allow RDF/XML documents specified in[RDF-MS] to remain valid; new documents SHOULD NOT use these unqualified attributes and applications MAY choose to warn when the unqualified form is seen in a document.

The construction ofRDF URI references from XML attributes can generate the sameRDF URI references from different XML attributes. This can cause ambiguity in the grammar when matching attribute events (such as whenrdf:about and about XML attributes are both present). Documents that have this are illegal.

URI-string-value

The value is the concatenation of the following in this order "<", the escaped value of the �URI�accessor and ">".

The escaping of the�URI�accessor uses the N-Triples escapes for URI references as described in 3.3 URI References.

6.1.5 Text Event

Constructed from a sequence of one or more consecutivecharacter information items. Has the single accessor:

string-value

Set to the value of the string made from concatenating the [character code] property of each of the character information items.

6.1.6 URI Reference Event

An event for aRDF URI referenceswhich has the following accessors:

identifier

Takes a string value used as anRDF URI reference.

string-value

The value is the concatenation of "<", the escaped value of the �identifier� accessor and ">"

The escaping of the �identifier� accessor value uses the N-Triples escapes for URI references as described in3.3 URI References.

These events are constructed by giving a value for the�identifier� accessor.

For further information on identifiers in the RDF graph, seesection 5.2.

6.1.7 Blank Node Identifier Event

An event for ablank node identifier which has the following accessors:

identifier

Takes a string value.

string-value

The value is a function of the value of the�identifier� accessor. The value begins with "_:" and the entire value MUST match theN-Triples nodeID production. The function MUST preserve distinct blank node identity as discussed in in section 5.2 Identifiers.

These events are constructed by giving a value for the�identifier� accessor.

For further information on identifiers in the RDF graph, seesection 5.2.

6.1.8 Plain Literal Event

An event for a plain literal which can have the following accessors:

literal-value

Takes a string value.

literal-language

Takes a string value used as a language tag in an RDF plain literal.

string-value

The value is calculated from the other accessors as follows.

If �literal-language� is the empty string then the value is the concatenation of """ (1 double quote), the escaped value of the�literal-value� accessor and """ (1 double quote).

Otherwise the value is the concatenation of """ (1 double quote), the escaped value of the�literal-value� accessor ""@" (1 double quote and a '@'), and the value of the�literal-language� accessor.

The escaping of the �literal-value� accessor value uses the N-Triples escapes for strings as described in 3.2 Strings for escaping certain characters such as ".

These events are constructed by giving values for the�literal-value� and�literal-language� accessors.

Interoperability Note (Informative): Literals beginning with a Unicode combining character are allowed however they may cause interoperability problems. See [CHARMOD] for further information.

6.1.9 Typed Literal Event

An event for a typed literal which can have the following accessors:

literal-value

Takes a string value.

literal-datatype

Takes a string value used as an RDF URI reference.

string-value

The value is the concatenation of the following in this order """ (1 double quote), the escaped value of the�literal-value� accessor, """ (1 double quote), "^^<", the escaped value of the�literal-datatype� accessor and ">".

The escaping of the �literal-value� accessor value uses the N-Triples escapes for strings as described in 3.2 Strings for escaping certain characters such as ". The escaping of the �literal-datatype� accessor value must use the N-Triples escapes for URI references as described in3.3 URI References.

These events are constructed by giving values for the�literal-value�and�literal-datatype� accessors.

Interoperability Note (Informative): Literals beginning with a Unicode combining character are allowed however they may cause interoperability problems. See [CHARMOD] for further information.

Implementation Note (Informative): In XML Schema (part 1) [XML-SCHEMA1],white space normalizationoccurs during validation according to the value of the whiteSpace facet. The syntax mapping used in this document occurs after this, so the whiteSpace facet formally has no further effect.

6.2 Information Set Mapping

To transform the Infoset into the sequence of events in document order, each information item is transformed as described above to generate a tree of events with accessors and values. Each element event is then replaced as described below to turn the tree of events into a sequence in document order.

1. The original element event
2. The value of thechildrenaccessor recursively transformed, a possibly empty ordered list of events.
3. An end element event

6.3 Grammar Notation

The following notation is used to describe matching the sequence of data model events as given in Section 6and the actions to perform for the matches. The RDF/XML grammar is defined in terms of mapping from these matched data model events to triples, using notation of the form:

number event-type event-content

where the event-content is an expression matching_event-types_ (as defined in Section 6.1), using notation given in the following sections. The number is used for reference purposes. The grammar action may include generating new triples to the graph, written inN-Triplesformat.

The following sections describe the general notation used and that for event matching and actions.

6.3.1 Grammar General Notation

Grammar General Notation.

6.3.2 Grammar Event Matching Notation

Grammar Event Matching Notation.

6.3.3 Grammar Action Notation

Grammar Action Notation.

7 RDF/XML Grammar

7.1 Grammar summary

7.2 Grammar Productions

7.2.1 Grammar start

If the RDF/XML is a standalone XML document (identified by presentation as an application/rdf+xml RDF MIME type object, or by some other means) then the grammar may start with production doc or production nodeElement.

If the content is known to be RDF/XML by context, such as when RDF/XML is embedded inside other XML content, then the grammar can either start at Element Event RDF(only when an element is legal at that point in the XML) or at production nodeElementList(only when element content is legal, since this is a list of elements). For such embedded RDF/XML, the�base-uri�value on the outermost element must be initialized from the containing XML since noRoot Event will be available. Note that if such embedding occurs, the grammar may be entered several times but no state is expected to be preserved.

7.2.2 Production coreSyntaxTerms

rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype

A subset of the syntax terms from the RDF vocabulary insection 5.1which are used in RDF/XML.

7.2.3 Production syntaxTerms

coreSyntaxTerms | rdf:Description | rdf:li

All the syntax terms from the RDF vocabulary insection 5.1which are used in RDF/XML.

7.2.4 Production oldTerms

rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID

These are the names from the RDF vocabularythat have been withdrawn from the language. See the resolutions of Issue rdfms-aboutEach-on-object, Issue rdfms-abouteachprefix and Last Call Issue timbl-01for further information.

7.2.5 Production nodeElementURIs

anyURI - ( coreSyntaxTerms | rdf:li | oldTerms )

The RDF URI references that are allowed on node elements.

7.2.6 Production propertyElementURIs

anyURI - ( coreSyntaxTerms | rdf:Description | oldTerms )

The URIs that are allowed on property elements.

7.2.7 Production propertyAttributeURIs

anyURI - ( coreSyntaxTerms | rdf:Description | rdf:li | oldTerms )

The RDF URI references that are allowed on property attributes.

7.2.8 Production doc

root(document-element == RDF,
children == list(RDF))

7.2.9 Production RDF

start-element(URI == rdf:RDF,
attributes == set())
nodeElementList
end-element()

7.2.10 Production nodeElementList

7.2.11 Production nodeElement

start-element(URI == nodeElementURIs
attributes == set((idAttr | nodeIdAttr | aboutAttr�)?, propertyAttr*))
propertyEltList
end-element()

For node element e, the processing of some of the attributes has to be done before other work such as dealing with children events or other attributes. These can be processed in any order:

• If there is an attribute a with_a_.URI == rdf:ID, then_e_.subject := uri(identifier := resolve(e, concat("#", a.string-value))).
• If there is an attribute a with_a_.URI == rdf:nodeID, then_e_.subject := bnodeid(identifier:=a.string-value).
• If there is an attribute a with_a_.URI == rdf:about then_e_.subject := uri(identifier := resolve(e, a.string-value)).

If e.subject is empty, then e.subject := bnodeid(identifier := generated-blank-node-id()).

The following can then be performed in any order:

• If e.URI != rdf:Descriptionthen the following statement is added to the graph:
  _e_.[subject](#eventterm-element-subject).[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> _e_.[URI-string-value](#eventterm-element-URI-string-value) .
• If there is an attribute a_in propertyAttr with_a.URI == rdf:typethen_u_:=uri(identifier:=resolve(a.string-value)) and the following tiple is added to the graph:
  _e_.[subject](#eventterm-element-subject).[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> _u_.[string-value](#eventterm-identifier-string-value) .
• For each attribute a matchingpropertyAttr (and not rdf:type), the Unicode string a.string-valueSHOULD be in Normal Form C[NFC],o := literal(literal-value := a.string-value, literal-language := e.language) and the following statement is added to the graph:
• Handle thepropertyEltList children events in document order.

7.2.12 Production ws

7.2.13 Production propertyEltList

7.2.14 Production propertyElt

If element e has_e_.URI =rdf:li then apply the list expansion rules on element e.parent insection 7.4to give a new URI u and_e_.URI := u.

The action of this production must be done before the actions of any sub-matches (resourcePropertyElt ... emptyPropertyElt). Alternatively the result must be equivalent to as if it this action was performed first, such as performing as the first action of all of the sub-matches.

7.2.15 Production resourcePropertyElt

start-element(URI == propertyElementURIs ),
attributes == set(idAttr?))
ws* nodeElement ws*
end-element()

For element e, and the single contained nodeElement_n_, first n must be processed using productionnodeElement. Then the following statement is added to the graph:

If the rdf:ID attribute a is given, the above statement is reified with_i_ := uri(identifier := resolve(e, concat("#", a.string-value))) using the reification rules insection 7.3and e.subject := i

7.2.16 Production literalPropertyElt

start-element(URI == propertyElementURIs ),
attributes == set(idAttr?, datatypeAttr?))
text()
end-element()

Note that the empty literal case is defined in productionemptyPropertyElt.

For element e, and the text event t. The Unicode string t.string-value SHOULD be in Normal Form C[NFC]. If the rdf:datatype attribute d is given then o := typed-literal(literal-value := t.string-value, literal-datatype := d.string-value) otherwise_o_ := literal(literal-value := t.string-value, literal-language := e.language) and the following statement is added to the graph:

If the rdf:ID attribute a is given, the above statement is reified with_i_ := uri(identifier := resolve(e, concat("#", a.string-value))) using the reification rules insection 7.3and e.subject := i.

7.2.17 Production parseTypeLiteralPropertyElt

start-element(URI == propertyElementURIs ),
attributes == set(idAttr?, parseLiteral))
literal
end-element()

For element e and the literal _l_that is the rdf:parseType="Literal" content.l is not transformed by the syntax data model mapping into events (as noted in 6 Syntax Data Model) but remains an XML Infoset of XML Information items.

l is transformed into the lexical form of anXML literalin the RDF graph x (a Unicode string) by the following algorithm. This does not mandate any implementation method — any other method that gives the same result may be used.

1. Use l to construct an XPath[XPATH] node-set(a document subset)
2. Apply Exclusive XML Canonicalization [XML-XC14N]) with comments and with emptyInclusiveNamespaces PrefixListto this node-set to give a sequence of octets s
3. This sequence of octets s can be considered to be a UTF-8 encoding of some Unicode string x (sequence of Unicode characters)
4. The Unicode string x is used as the lexical form of l
5. This Unicode string_x_ SHOULD be in NFC Normal Form C[NFC]

Then o := typed-literal(literal-value := x, literal-datatype := http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral ) and the following statement is added to the graph:

If the rdf:ID attribute a is given, the above statement is reified with_i_ := uri(identifier := resolve(e, concat("#", a.string-value))) using the reification rules insection 7.3and e.subject := i.

7.2.18 Production parseTypeResourcePropertyElt

start-element(URI == propertyElementURIs ),
attributes == set(idAttr?, parseResource))
propertyEltList
end-element()

For element e with possibly empty element content c.

n := bnodeid(identifier := generated-blank-node-id()).

Add the following statement to the graph:

If the rdf:ID attribute a is given, the statement above is reified with_i_ := uri(identifier := resolve(e, concat("#", a.string-value))) using the reification rules insection 7.3and e.subject := i.

If the element content c is not empty, then use event_n_ to create a new sequence of events as follows:

start-element(URI := rdf:Description,
subject := n,
attributes := set())
c
end-element()

Then process the resulting sequence using productionnodeElement.

7.2.19 Production parseTypeCollectionPropertyElt

start-element(URI == propertyElementURIs ),
attributes == set(idAttr?, parseCollection))
nodeElementList
end-element()

For element event e with possibly emptynodeElementList l. Set_s_:=list().

For each element event f in l,n := bnodeid(identifier := generated-blank-node-id()) and append n to s to give a sequence of events.

If s is not empty, n is the first event identifier in_s_ and the following statement is added to the graph:

otherwise the following statement is added to the graph:

_e_.parent.[subject](#eventterm-element-subject).[string-value](#eventterm-identifier-string-value) _e_.[URI-string-value](#eventterm-element-URI-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#nil> .

If the rdf:ID attribute a is given, either of the the above statements is reified with_i_ := uri(identifier := resolve(e, concat("#", a.string-value))) using the reification rules insection 7.3.

If s is empty, no further work is performed.

For each event n in s and the corresponding element event f in l, the following statement is added to the graph:

_n_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#first> _f_.[string-value](#eventterm-identifier-string-value) .

For each consecutive and overlapping pair of events (n, o) in s, the following statement is added to the graph:

_n_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#rest> _o_.[string-value](#eventterm-identifier-string-value) .

If s is not empty, n is the last event identifier in s, the following statement is added to the graph:

_n_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#rest> <http://www.w3.org/1999/02/22-rdf-syntax-ns#nil> .

7.2.20 Production parseTypeOtherPropertyElt

start-element(URI == propertyElementURIs ),
attributes == set(idAttr?, parseOther))
propertyEltList
end-element()

All rdf:parseType attribute values other than the strings "Resource", "Literal" or "Collection" are treated as if the value was "Literal". This production matches and acts as if productionparseTypeLiteralPropertyEltwas matched. No extra triples are generated for other rdf:parseType values.

7.2.21 Production emptyPropertyElt

start-element(URI == propertyElementURIs ),
attributes == set(idAttr?, ( resourceAttr | nodeIdAttr )?, propertyAttr*))
end-element()

• If there are no attributes or only the optional rdf:ID attribute _i_then o := literal(literal-value:="", literal-language := e.language) and the following statement is added to the graph:
  and then if i is given, the above statement is reified with uri(identifier := resolve(e, concat("#", i.string-value))) using the reification rules insection 7.3.
• Otherwise
  • If rdf:resource attribute i is present, then_r_ := uri(identifier := resolve(e, i.string-value))
  • If rdf:nodeID attribute i is present, then_r_ := bnodeid(identifier := i.string-value)
  • If neither,r := bnodeid(identifier := generated-blank-node-id())
    The following are done in any order:
  • For all propertyAttrattributes a (in any order)
    * If a.URI == rdf:type then u:=uri(identifier:=resolve(a.string-value)) and the following triple is added to the graph:
    _r_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> _u_.[string-value](#eventterm-identifier-string-value) .
    * Otherwise Unicode string_a_.string-value SHOULD be in Normal Form C[NFC],o := literal(literal-value := a.string-value, literal-language := e.language) and the following statement is added to the graph:
  • Add the following statement to the graph:
    and then if rdf:ID attribute i is given, the above statement is reified with uri(identifier := resolve(e, concat("#", i.string-value))) using the reification rules insection 7.3.

7.2.22 Production idAttr

attribute(URI == rdf:ID,
string-value == rdf-id)

Constraint:: constraint-idapplies to the values of rdf:ID attributes

7.2.23 Production nodeIdAttr

attribute(URI == rdf:nodeID,
string-value == rdf-id)

7.2.24 Production aboutAttr

attribute(URI == rdf:about,
string-value == URI-reference)

7.2.25 Production propertyAttr

7.2.26 Production resourceAttr

attribute(URI == rdf:resource,
string-value == URI-reference)

7.2.27 Production datatypeAttr

attribute(URI == rdf:datatype,
string-value == URI-reference)

7.2.28 Production parseLiteral

attribute(URI == rdf:parseType,
string-value == "Literal")

7.2.29 Production parseResource

attribute(URI == rdf:parseType,
string-value == "Resource")

7.2.30 Production parseCollection

attribute(URI == rdf:parseType,
string-value == "Collection")

7.2.31 Production parseOther

attribute(URI == rdf:parseType,
string-value == anyString - ("Resource" | "Literal" | "Collection") )

7.2.32 Production URI-reference

7.2.33 Production literal

7.2.34 Production rdf-id

An attribute �string-value�matching any legal[XML-NS] tokenNCName

7.3 Reification Rules

For the given URI reference event r and the statement with terms s, p and _o_corresponding to the N-Triples:

add the following statements to the graph:

_r_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#subject> _s_ .
_r_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate> _p_ .
_r_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#object> _o_ .
_r_.[string-value](#eventterm-identifier-string-value) <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement> .

7.4 List Expansion Rules

For the given element e, create a new RDF URI reference u := concat("http://www.w3.org/1999/02/22-rdf-syntax-ns#\_",_e_.[li-counter](#eventterm-element-liCounter)), increment the_e_.li-counterproperty by 1 and return u.

8 Serializing an RDF Graph to RDF/XML

There are some RDF Graphsas defined inRDF Concepts and Abstract Syntaxthat cannot be serialized in RDF/XML. These are those that:

Use property names that cannot be turned into XML namespace-qualified names.

An XML namespace-qualified name (QName) has restrictions on the legal characters such that not all property URIs can be expressed as these names. It is recommended that implementors of RDF serializers, in order to break a URI into a namespace name and a local name, split it after the last XML non-NCName character, ensuring that the first character of the name is aLetter or '_'. If the URI ends in a non-NCName character then throw a "this graph cannot be serialized in RDF/XML" exception or error.

Use inappropriate reserved names as properties

For example, a property with the same URI as any of thesyntaxTerms production.

**Implementation Note (Informative):**When an RDF graph is serialized to RDF/XML and has an XML Schema Datatype (XSD), it SHOULD be written in a form that does not require whitespace processing. XSD support is NOT required by RDF or RDF/XML so this is optional.

9 Using RDF/XML with HTML and XHTML

If RDF/XML is embedded inside HTML or XHTML this can add many new elements and attributes, many of which will not be in the appropriate DTD. This embedding causes validation against the DTD to fail. The obvious solution of changing or extending the DTD is not practical for most uses. This problem has been analyzed extensively by Sean B. Palmer inRDF in HTML: Approaches [RDF-IN-XHTML]and it concludes that there is no single embedding method that satisfies all applications and remains simple.

The recommended approach is to not embed RDF/XML in HTML/XHTML but rather to use <link> element in the <head>element of the HTML/HTML to point at a separate RDF/XML document. This approach has been used for several years by theDublin Core Metadata Initiative (DCMI)on its Web site.

To use this technique, the <link> elementhref should point at the URI of the RDF/XML content and the type attribute should be used with the value of"application/rdf+xml", the proposed MIME type for RDF/XML, see Section 4

The value of the rel attribute may also be set to indicate the relationship; this is an application dependent value. The DCMI has used and recommended rel="meta" when linking in RFC 2731 — Encoding Dublin Core Metadata in HTML[RFC-2731] howeverrel="alternate" may also be appropriate. SeeHTML 4.01 link types,XHTML Modularization — LinkTypesandXHTML 2.0 — LinkTypesfor further information on the values that may be appropriate for the different versions of HTML.

Example 21 shows using this method with the link tag inside an XHTML document to link to an external RDF/XML document.

My document

10 Using RDF/XML with SVG (Informative)

There is a standardized approach for associating RDF compatible metadata with SVG — the metadata element which was explicitly designed for this purpose as defined in Section 21 Metadataof theScalable Vector Graphics (SVG) 1.0 Specification [SVG]andSection 21 Metadataof theScalable Vector Graphics (SVG) 1.1 Specification [SVG11].

This document contains two example graphs in SVG with such embedded RDF/XML inside the metadata element:figure 1andfigure 2.

11 Acknowledgments (Informative)

The following people provided valuable contributions to the document:

• Dan Brickley, W3C/ILRT
• Jeremy Carroll, HP Labs, Bristol
• Graham Klyne, Nine by Nine
• Bijan Parsia, MIND Lab at University of Maryland at College Park

This document is a product of extended deliberations by the RDF Core working group, whose members have included: Art Barstow (W3C) Dave Beckett (ILRT), Dan Brickley (W3C/ILRT), Dan Connolly (W3C), Jeremy Carroll (Hewlett Packard), Ron Daniel (Interwoven Inc), Bill dehOra (InterX), Jos De Roo (AGFA), Jan Grant (ILRT), Graham Klyne (Clearswift and Nine by Nine), Frank Manola (MITRE Corporation), Brian McBride (Hewlett Packard), Eric Miller (W3C), Stephen Petschulat (IBM), Patrick Stickler (Nokia), Aaron Swartz (HWG), Mike Dean (BBN Technologies / Verizon), R. V. Guha (Alpiri Inc), Pat Hayes (IHMC), Sergey Melnik (Stanford University), Martyn Horner (Profium Ltd).

This specification also draws upon an earlier RDF Model and Syntax document edited by Ora Lassilla and Ralph Swick, and RDF Schema edited by Dan Brickley and R. V. Guha. RDF and RDF Schema Working group members who contributed to this earlier work are: Nick Arnett (Verity), Tim Berners-Lee (W3C), Tim Bray (Textuality), Dan Brickley (ILRT / University of Bristol), Walter Chang (Adobe), Sailesh Chutani (Oracle), Dan Connolly (W3C), Ron Daniel (DATAFUSION), Charles Frankston (Microsoft), Patrick Gannon (CommerceNet), RV Guha (Epinions, previously of Netscape Communications), Tom Hill (Apple Computer), Arthur van Hoff (Marimba), Renato Iannella (DSTC), Sandeep Jain (Oracle), Kevin Jones, (InterMind), Emiko Kezuka (Digital Vision Laboratories), Joe Lapp (webMethods Inc.), Ora Lassila (Nokia Research Center), Andrew Layman (Microsoft), Ralph LeVan (OCLC), John McCarthy (Lawrence Berkeley National Laboratory), Chris McConnell (Microsoft), Murray Maloney (Grif), Michael Mealling (Network Solutions), Norbert Mikula (DataChannel), Eric Miller (OCLC), Jim Miller (W3C, emeritus), Frank Olken (Lawrence Berkeley National Laboratory), Jean Paoli (Microsoft), Sri Raghavan (Digital/Compaq), Lisa Rein (webMethods Inc.), Paul Resnick (University of Michigan), Bill Roberts (KnowledgeCite), Tsuyoshi Sakata (Digital Vision Laboratories), Bob Schloss (IBM), Leon Shklar (Pencom Web Works), David Singer (IBM), Wei (William) Song (SISU), Neel Sundaresan (IBM), Ralph Swick (W3C), Naohiko Uramoto (IBM), Charles Wicksteed (Reuters Ltd.), Misha Wolf (Reuters Ltd.), Lauren Wood (SoftQuad).

12 References

Normative References

[RDF-MS]

Resource Description Framework (RDF) Model and Syntax Specification, O. Lassila and R. Swick, Editors. World Wide Web Consortium. 22 February 1999. This version is http://www.w3.org/TR/1999/REC-rdf-syntax-19990222\. The latest version of RDF M&S is available at http://www.w3.org/TR/REC-rdf-syntax.

[XML]

Extensible Markup Language (XML) 1.0, Second Edition, T. Bray, J. Paoli, C.M. Sperberg-McQueen and E. Maler, Editors. World Wide Web Consortium. 6 October 2000. This version is http://www.w3.org/TR/2000/REC-xml-20001006\. latest version of XML is available at http://www.w3.org/TR/REC-xml.

[XML-NS]

Namespaces in XML, T. Bray, D. Hollander and A. Layman, Editors. World Wide Web Consortium. 14 January 1999. This version is http://www.w3.org/TR/1999/REC-xml-names-19990114\. The latest version of Namespaces in XML is available at http://www.w3.org/TR/REC-xml-names.

[INFOSET]

XML Information Set, J. Cowan and R. Tobin, Editors. World Wide Web Consortium. 24 October 2001. This version is http://www.w3.org/TR/2001/REC-xml-infoset-20011024\. The latest version of XML Information set is available at http://www.w3.org/TR/xml-infoset.

[URIS]

RFC 2396 — Uniform Resource Identifiers (URI): Generic Syntax, T. Berners-Lee, R. Fielding and L. Masinter, IETF, August 1998. This document is http://www.isi.edu/in-notes/rfc2396.txt.

[RDF-CONCEPTS]

Resource Description Framework (RDF): Concepts and Abstract Syntax, Klyne G., Carroll J. (Editors), W3C Proposed Recommendation (work in progress), 15 December 2003. This version is http://www.w3.org/TR/2003/PR-rdf-concepts-20031215/. The latest version is http://www.w3.org/TR/rdf-concepts/.

[RDF-TESTS]

RDF Test Cases, Grant J., Beckett D. (Editors), W3C Proposed Recommendation (work in progress), 15 December 2003. This version is http://www.w3.org/TR/2003/PR-rdf-testcases-20031215/. The latest version is http://www.w3.org/TR/rdf-testcases/.

[KEYWORDS]

RFC 2119 — Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, IETF. March 1997. This document is http://www.ietf.org/rfc/rfc2119.txt.

[RFC-3023]

RFC 3032 — XML Media Types, M. Murata, S. St.Laurent, D.Kohn, IETF. January 2001. This document is http://www.ietf.org/rfc/rfc3023.txt.

[IANA-MEDIA-TYPES]

MIME Media Types, The Internet Corporation for Assigned Names and Numbers (IANA). This document is http://www.iana.org/assignments/media-types/.

[XML-BASE]

XML Base, J. Marsh, Editor, W3C Recommendation. World Wide Web Consortium, 27 June 2001. This version of XML Base is http://www.w3.org/TR/2001/REC-xmlbase-20010627\. The latest version of XML Base is at http://www.w3.org/TR/xmlbase.

[XML-XC14N]

Exclusive XML Canonicalization Version 1.0, J. Boyer, D.E. Eastlake 3rd, J. Reagle, Authors/Editors. W3C Recommendation. World Wide Web Consortium, 18 July 2002. This version of Exclusive XML Canonicalization is http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718\. The latest version of Canonical XML is at http://www.w3.org/TR/xml-exc-c14n.

[UNICODE]

The Unicode Standard, Version 3, The Unicode Consortium, Addison-Wesley, 2000. ISBN 0-201-61633-5, as updated from time to time by the publication of new versions. (See http://www.unicode.org/unicode/standard/versions/ for the latest version and additional information on versions of the standard and of the Unicode Character Database).

[NFC]

Unicode Normalization Forms, Unicode Standard Annex #15, Mark Davis, Martin D�rst. (See http://www.unicode.org/unicode/reports/tr15/ for the latest version).

Informational References

[CHARMOD]

Character Model for the World Wide Web 1.0, M. D�rst, F. Yergeau, R. Ishida, M. Wolf, A. Freytag, T Texin, Editors, World Wide Web Consortium Working Draft, work in progress, 20 February 2002. This version of the Character Model is http://www.w3.org/TR/2002/WD-charmod-20020220\. The latest version of the Character Model is at http://www.w3.org/TR/charmod.

[RDF-SEMANTICS]

RDF Semantics, Hayes P. (Editor), W3C Proposed Recommendation (work in progress), 15 December 2003. This version is http://www.w3.org/TR/2003/PR-rdf-mt-20031215/. The latest version is http://www.w3.org/TR/rdf-mt/.

[RDF-PRIMER]

RDF Primer, F. Manola, E. Miller, Editors, W3C Proposed Recommendation (work in progress), 15 December 2003. This version is http://www.w3.org/TR/2003/PR-rdf-primer-20031215/. The latest version is at http://www.w3.org/TR/rdf-primer/.

[RDF-VOCABULARY]

RDF Vocabulary Description Language 1.0: RDF Schema, Brickley D., Guha R.V. (Editors), W3C Proposed Recommendation (work in progress), 15 December 2003. This version is http://www.w3.org/TR/2003/PR-rdf-schema-20031215/. The latest version is http://www.w3.org/TR/rdf-schema/.

[STRIPEDRDF]

RDF: Understanding the Striped RDF/XML Syntax, D. Brickley, W3C, 2001. This document is http://www.w3.org/2001/10/stripes/.

[SVG]

Scalable Vector Graphics (SVG) 1.0 Specification, J. Ferraiolo (editor), 4 September 2001, W3C Recommendation. This version of SVG is http://www.w3.org/TR/2001/REC-SVG-20010904\. The latest version of SVG is at http://www.w3.org/TR/SVG.

[SVG11]

Scalable Vector Graphics (SVG) 1.1 Specification, J. Ferraiolo, J. FUJISAWA, D. Jackson (editors), 14 January 2003, W3C Recommendation. This version of SVG is http://www.w3.org/TR/2003/REC-SVG11-20030114/. The latest version of SVG is at http://www.w3.org/TR/SVG11.

[XPATH]

XML Path Language (XPath) Version 1.0, J. Clark and S. DeRose, Editors. World Wide Web Consortium, 16 November 1999. This version of XPath is http://www.w3.org/TR/1999/REC-xpath-19991116\. The latest version of XPath is at http://www.w3.org/TR/xpath.

[SAX2]

SAX Simple API for XML, version 2, D. Megginson, SourceForge, 5 May 2000. This document is http://sax.sourceforge.net/.

[UNPARSING]

Unparsing RDF/XML, J. J. Carroll, HP Labs Technical Report, HPL-2001-294, 2001. This document is available at http://www.hpl.hp.com/techreports/2001/HPL-2001-294.html.

[RELAXNG]

RELAX NG Specification, James Clark and MURATA Makoto, Editors, OASIS Committee Specification, 3 December 2001. This version of RELAX NG is http://www.oasis-open.org/committees/relax-ng/spec-20011203.html. The latest version of the RELAX NG Specification is at http://www.oasis-open.org/committees/relax-ng/spec.html.

[RELAXNG-COMPACT]

RELAX NG Compact Syntax, James Clark, Editor. OASIS Committee Specification, 21 November 2002. This document is http://www.oasis-open.org/committees/relax-ng/compact-20021121.html.

[RDF-IN-XHTML]

RDF in HTML: Approaches, Sean B. Palmer, 2002

[RFC-2731]

RFC 2731 — Encoding Dublin Core Metadata in HTML, John Kunze, DCMI, December 1999.

[XML-SCHEMA1]

XML Schema Part 1: Structures, H.S. Thompson, D. Beech, M. Maloney, N. Mendelsohn, Editors, World Wide Web Consortium Recommendation, 2 May 2001. This version of XML Schema Part 1: Structures is http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/. The latest version of XML Schema Part 1: Structures is at http://www.w3.org/TR/xmlschema-1.

[XML-SCHEMA2]

XML Schema Part 2: Datatypes, P.V. Biron, A. Malhotra, Editors, World Wide Web Consortium Recommendation, 2 May 2001. This version of XML Schema Part 2: Datatypes is http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/. The latest version of XML Schema Part 2: Datatypes is at http://www.w3.org/TR/xmlschema-2\.

A Syntax Schemas (Informative)

This appendix contains XML schemas for validating RDF/XML forms. These are example schemas for information only and are not part of this specification.

A.1 RELAX NG Compact Schema (Informative)

This is an example schema in RELAX NG Compact (for ease of reading) for RDF/XML. Applications can also use theRELAX NG XML version. These formats are described inRELAX NG ([RELAXNG]) and RELAX NG Compact ([RELAXNG-COMPACT]).

**Note:**The RNGC schema has been updated to attempt to match the grammar but this has not been checked or used to validate RDF/XML.

RELAX NG Compact Schema for RDF/XML Syntax

This schema is for information only and NON-NORMATIVE

It is based on one originally written by James Clark in

http://lists.w3.org/Archives/Public/www-rdf-comments/2001JulSep/0248.html

and updated with later changes.

namespace local = "" namespace rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#" datatypes xsd = "http://www.w3.org/2001/XMLSchema-datatypes"

start = doc

I cannot seem to do this in RNGC so they are expanded in-line

coreSyntaxTerms = rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype

syntaxTerms = coreSyntaxTerms | rdf:Description | rdf:li

oldTerms = rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID

nodeElementURIs = * - ( coreSyntaxTerms | rdf:li | oldTerms )

propertyElementURIs = * - ( coreSyntaxTerms | rdf:Description | oldTerms )

propertyAttributeURIs = * - ( coreSyntaxTerms | rdf:Description | rdf:li | oldTerms )

Also needed to allow rdf:li on all property element productions

since we can't capture the rdf:li rewriting to rdf_ in relaxng

Need to add these explicitly

xmllang = attribute xml:lang { text } xmlbase = attribute xml:base { text }

and to forbid every other xml:* attribute, element

doc = RDF | nodeElement

RDF = element rdf:RDF { xmllang?, xmlbase?, nodeElementList }

nodeElementList = nodeElement*

Should be something like:

ws* , ( nodeElement , ws* )*

but RELAXNG does this by default, ignoring whitespace separating tags.

nodeElement = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:li | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID ) { (idAttr | nodeIdAttr | aboutAttr )?, xmllang?, xmlbase?, propertyAttr*, propertyEltList }

It is not possible to say "and not things

beginning with _ in the rdf: namespace" in RELAX NG.

ws = " "

Not used in this RELAX NG schema; but should be any legal XML

whitespace defined by http://www.w3.org/TR/2000/REC-xml-20001006#NT-S

propertyEltList = propertyElt*

Should be something like:

ws* , ( propertyElt , ws* )*

but RELAXNG does this by default, ignoring whitespace separating tags.

propertyElt = resourcePropertyElt | literalPropertyElt | parseTypeLiteralPropertyElt | parseTypeResourcePropertyElt | parseTypeCollectionPropertyElt | parseTypeOtherPropertyElt | emptyPropertyElt

resourcePropertyElt = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { idAttr?, xmllang?, xmlbase?, nodeElement }

literalPropertyElt = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { (idAttr | datatypeAttr )?, xmllang?, xmlbase?, text }

parseTypeLiteralPropertyElt = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { idAttr?, parseLiteral, xmllang?, xmlbase?, literal }

parseTypeResourcePropertyElt = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { idAttr?, parseResource, xmllang?, xmlbase?, propertyEltList }

parseTypeCollectionPropertyElt = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { idAttr?, xmllang?, xmlbase?, parseCollection, nodeElementList }

parseTypeOtherPropertyElt = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { idAttr?, xmllang?, xmlbase?, parseOther, any }

emptyPropertyElt = element * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { idAttr?, (resourceAttr | nodeIdAttr)?, xmllang?, xmlbase?, propertyAttr* }

idAttr = attribute rdf:ID { IDsymbol }

nodeIdAttr = attribute rdf:nodeID { IDsymbol }

aboutAttr = attribute rdf:about { URI-reference }

propertyAttr = attribute * - ( local:* | rdf:RDF | rdf:ID | rdf:about | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:li | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID | xml:* ) { string }

resourceAttr = attribute rdf:resource { URI-reference }

datatypeAttr = attribute rdf:datatype { URI-reference }

parseLiteral = attribute rdf:parseType { "Literal" }

parseResource = attribute rdf:parseType { "Resource" }

parseCollection = attribute rdf:parseType { "Collection" }

parseOther = attribute rdf:parseType { text }

URI-reference = string

literal = any

IDsymbol = xsd:NMTOKEN

any = mixed { element * { attribute * { text }, any } }

B Revisions since Draft 10 October 2003 (Informative)

Changes since 10 October 2003 second last call working draft

These are are divided into non-editorial and editorial. The non-editorial changes also list consquential editorial changes. Editorial changes are those which do not result in any change in the meaning of an RDF document or the behaviour of an RDF application.

Appendix B.1: Non-Editorial Revisions

None

Appendix B.2: Editorial Revisions

German Translation

Fix the German in Example 8in section 2.7 after thecomment by Benjamin Nowack

No property attributes on rdf:parseType="Resource"

2.5Update to reflect the syntax definition that property attributes cannot be used with rdf:parseType="Resource" as pointed out bycomment by Sabadello 2003-10-30

URI Encoding

6.1.6,6.1.8,6.1.9after proposal by Jeremy Carroll
6.1.2,6.1.4Added element/attribute URI-string-value accessors
7.2.11,7.2.21Added use of new uri event for the rdf:type cases
7.2.11 (<e.URI> and <a.URI>),7.2.15 (<e.URI>)7.2.16 (<e.URI>)7.2.17 (<e.URI>)7.2.18 (<e.URI>)7.2.19 (<e.URI> twice)7.2.21 (<e.URI> twice, <a.URI> once) changed from X.URI to X.URI-string-value (anywhere "<"..">" appeared in the grammar action without a hardcoded URI reference)
7.2.32Replace action wording with "An RDF URI reference"
All changed as outlined inproposal 2003-10-06aftercomment by Patel-Schneider 2003-10-29

Appendix B.3: Issues requiring no document revisions

None