Editor's Draft of RDF/XML Syntax Specification (Revised)

Grammar General Notation.
Notation	Meaning
event . accessor	The value of an event accessor.
`rdf:` X	A URI as defined in section 5.1 .
"ABC"	A Unicode string of characters A, B, C in order.

Grammar Event Matching Events </th> </tr> Notation.
Notation	Meaning
A == B	Event accessor A is equal to matches expression B.
A != B	A is not equal to B.
A \| B \| ...	The A, B, ... terms are alternatives.
A - B	The term terms in A but not excluding all the term terms in B.
anyURI .	Any URI.
anyString .	Any string.
list(item1, item2, ...); list()	An ordered list of events. An empty list.
set(item1, item2, ...); set()	An unordered set of events. An empty set.
*	Zero or more of preceding term.
?	Zero or one of preceding term.
+	One or more of preceding term.
root(acc1 == value1, acc2 == value2, ...)	Match a Root Event with accessors.
start-element(acc1 == value1, acc2 == value2, ...) children end-element()	Match a sequence of Element Event with accessors, a possibly empty list of events as element content and an End Element Event .
attribute(acc1 == value1, acc2 == value2, ...)	Match an Attribute Event with accessors.
text()	Match a Text Event .

Grammar Action Notation.
Notation	Meaning
A := B	Assigns A the value B.
concat(A, B, ..)	A string created by concatenating the terms in order.
resolve( e , s )	A string created by interpreting s as a relative URI reference to the · base-uri · accessor of · Element Event · e as defined in Section 5.3 Resolving URIs . The resulting string represents an <a href="http://www.w3.org/TR/2003/WD-rdf-concepts-20030123/#dfn-URI-reference"> RDF URI Reference reference .
generated-blank-node-id()	A string value for a new distinct generated <a href="http://www.w3.org/TR/2003/WD-rdf-concepts-20030123/#dfn-blank-node-id"> Blank Node Identifier blank node identifier as defined in section 5.2 Identifiers .
event . accessor := value	Sets an event accessor to the given value.
uri(identifier := value)	Create a new URI Reference Event .
bnodeid(identifier := value)	Create a new Blank Node blank node Identifier Event . See also section 5.2 Identifiers .
literal(literal-value := string, literal-language := language, ...)	Create a new Plain Literal Event .
typed-literal(literal-value := string, deleted text: <br /> literal-language := language, ...)	Create a new Typed Literal Event .

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

coreSyntaxTerms | rdf:Description | rdf:li

All the syntax terms from the RDF Namespace vocabulary in section 5.1 which are used in deleted text: the RDF/XML.

rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID

The <a href="http://www.w3.org/TR/2003/WD-rdf-concepts-20030123/#dfn-URI-reference"> RDF URI References references that are allowed on node elements.

7.2.6 Production propertyElementURIs

anyURI - ( coreSyntaxTerms | rdf:Description | oldTerms )

7.2.7 Production propertyAttributeURIs

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

The <a href="http://www.w3.org/TR/2003/WD-rdf-concepts-20030123/#dfn-URI-reference"> RDF URI References 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

ws * ( nodeElement ws * )*

7.2.11 Production nodeElement

start-element( URI == nodeElementURIs
attributes == set(( idAttr | nodeIdAttr | aboutAttr Â )?, deleted text: <a href="#bagIdAttr"> bagIdAttr </a> ?, 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:

7.2.12 Production ws

If an attribute A text event matching white space defined by [XML] definition a White Space with <em> a </em>. <a href="#eventterm-attribute-URI"> URI Rule [3] S deleted text: == <code> rdf:bagID </code> is present, <em> n </em> := uri( <a href="#eventterm-identifier-identifier"> identifier </a> := resolve( <em> e </em>, concat("#", <em> a </em>. <a href="#eventterm-attribute-string-value"> string-value </a> ))) then in any order: section Common Syntactic Constructs

deleted text: <ul> <li> <p>

<a id="nodeElementStatement5" name="nodeElementStatement5"> S5 7.2.13 Production propertyEltList deleted text: Add the following statement to the graph: </p> <div class="ntripleOuter"> <div class="ntripleInner">

<em> n </em>. <a href="#eventterm-identifier-string-value"> string-value

ws <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag> . </code> * ( propertyElt ws * ) *

<a href="#nodeElementStatement1"> S1 7.2.14 Production propertyElt </li> <li> Statements from <a href="#nodeElementStatement2"> S2

resourcePropertyElt and <a href="#nodeElementStatement3"> S3 | literalPropertyElt in any order

Statements generated by the propertyEltList | parseTypeLiteralPropertyElt children by S4 | parseTypeResourcePropertyElt in document order

If the statement was generated by S4 | parseTypeCollectionPropertyElt from a propertyElt | parseTypeOtherPropertyElt and has an existing identifier e . subject | emptyPropertyElt then

If element s e := has e . subject . Otherwise s := bnodeid( identifier := generated-blank-node-id())

Then reify the statement with event s using the reification rules in section 7.3 URI and =


rdf:li

then apply the bag list expansion rules on element e .parent in section 7.5 7.4 deleted text: on event n to give a new URI u . Then the following statement is added to the graph:

7.2.12 Production ws

A text event matching white space defined by [XML] definition White Space Rule [3] S in section Common Syntactic Constructs

7.2.13 Production propertyEltList

ws * ( propertyElt ws * ) *

7.2.14 Production propertyElt

If element e has e . URI =


rdf:li

then apply the list expansion rules on element e .parent in section 7.4 to give a new URI u and e and e . URI := u .

deleted text: NOTE: The action of this production must be done before the actions of any sub-matches ( <a href="#resourcePropertyElt"> resourcePropertyElt </a> ... <a href="#emptyPropertyElt"> emptyPropertyElt </a> ). 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. </p> <h4> <a id="resourcePropertyElt" name="resourcePropertyElt"> 7.2.15 Production resourcePropertyElt </a> </h4> <div class="productionOuter"> <div class="productionInner"> <p> start-element( <a href="#eventterm-element-URI"> URI </a> == <a href="#propertyElementURIs"> propertyElementURIs </a> ), <br /> <a href="#eventterm-element-attributes"> attributes </a> == set( <a href="#idAttr"> idAttr </a> ?)) <br /> <a href="#ws"> ws </a> * <a href="#nodeElement"> nodeElement </a> <a href="#ws"> ws </a> * <br /> end-element() </p> </div> </div> <p> For element <em> e </em>, and the single contained nodeElement <em> n , first n must be processed using production nodeElement . 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 in section 7.3 and e . subject := i

7.2.16 Production literalPropertyElt

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

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 in section 7.3 and 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 , then 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 an XML literal in 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.

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 in section 7.3 and e . subject := i .

7.2.18 Production parseTypeResourcePropertyElt from


rdf:parseType="Literal"

content is an XML Literal .

This specification allows some freedom to choose exactly what string is used as the lexical form of an XML Literal. Whatever string is used, it MUST correspond to an XML document when enclosed within a start and end element tag, and its canonicalization (without comments, as defined in Exclusive XML Canonicalization [ XML-XC14N ]) MUST be the same as the same canonicalization of the literal text l . It is often acceptable to use l without any changes but this is incorrect if, for example, l uses entity references or namespace prefixes defined in the outer XML document.

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:

e .parent. subject . string-value < e . URI > n . string-value .

Test: Indicated by test004.rdf and test004.nt

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 in section 7.3 and 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 production nodeElement .

7.2.19 Production parseTypeCollectionPropertyElt

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

For element event e with possibly empty nodeElementList 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:

e .parent. subject . string-value < e . URI > n . string-value .

otherwise the following statement is added to the graph:

e .parent. subject . string-value < e . URI > <http://www.w3.org/1999/02/22-rdf-syntax-ns#nil> .

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

If s is empty, no further work is performed.

For each event n in s deleted text: , the following statement is added to the graph:

n . string-value <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#List> .

For each event n in s </em> and the corresponding element event <em> f </em> in <em> l </em>, the following statement is added to the graph: </p> <div class="ntripleOuter"> <div class="ntripleInner"> <p> <code> <em> n </em>. <a href="#eventterm-identifier-string-value"> string-value </a> <http://www.w3.org/1999/02/22-rdf-syntax-ns#first> <em> f </em>. <a href="#eventterm-identifier-string-value"> string-value </a> . </code> </p> </div> </div> <p> For each consecutive, consecutive and overlapping pairs pair of events ( n , o ) in s , the following statement is added to the graph:

n . string-value <http://www.w3.org/1999/02/22-rdf-syntax-ns#rest> o . 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 <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 production parseTypeLiteralPropertyElt was 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 )?, deleted text: <a href="#bagIdAttr"> bagIdAttr </a> ?, 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:

e .parent. subject . string-value < e . URI > o . string-value .

and then if i is given, the above statement is reified with uri( identifier := resolve( e , concat("#", i . string-value ))) using the reification rules in section 7.3 .

Test: Indicated by test002.rdf and test002.nt

Test: Indicated by test005.rdf and test005.nt

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())

deleted text: If optional <code> rdf:bagID </code> attribute <em> b </em> is given, <em> n </em> := uri( <a href="#eventterm-identifier-identifier"> identifier </a> := resolve( <em> e </em>, concat("#", <em> b </em>. <a href="#eventterm-attribute-string-value"> string-value </a> ))) </p> <p> The following are done in any order:

For all propertyAttr attributes a (in any order)

If a . URI == rdf:type then the following statement is added to the graph:

r . string-value <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> < a . string-value > .

Otherwise a . string-value MUST be a Unicode [UNICODE] string 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:

r . string-value < a . URI > o . string-value .

If event <em> n </em> was created, then for each statement above: <em> s </em> := bnodeid( <a href="#eventterm-identifier-identifier"> identifier Test: Indicated by test013.rdf := generated-blank-node-id()), reify and test013.nt

Test: Indicated by test014.rdf and test014.nt

Add the statement with event <em> s </em> using the reification rules in <a href="#section-Reification"> section 7.3 </a>, apply the bag expansion rules in <a href="#section-Bag-Expand"> section 7.5 </a> on event <em> n </em> to give URI <em> u </em> and add the following statement is added to the graph: </p> <div class="ntripleOuter"> <div class="ntripleInner"> <p> <code> <em> n </em>. <a href="#eventterm-identifier-string-value"> string-value </a> < <em> u </em> > <em> s </em>. <a href="#eventterm-identifier-string-value"> string-value </a> ; . </code> </p> </div> </div> <div class="note"> <p> <strong> Test: </strong> Indicated by <a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test013.rdf"> test013.rdf </a> and <a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test013.nt"> test013.nt </a> </p> </div> <div class="note"> <p> <strong> Test: </strong> Indicated by <a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test014.rdf"> test014.rdf </a> and <a href="http://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test014.nt"> test014.nt </a> </p> </div> </li> <li> <p> Add the following following statement to the graph:

e .parent. subject . string-value < e . URI > r . string-value .

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 in section 7.3 .

deleted text: <li> <p> If event <em> n </em> was created, add the following statement to the graph: </p> <div class="ntripleOuter"> <div class="ntripleInner"> <p> <code> <em> n </em>. <a href="#eventterm-identifier-string-value"> string-value </a> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag> . </code> </p> </div> </div> </li>

7.2.22 Production idAttr

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

Constraint: : constraint-id applies 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 )

deleted text: <a id="bagIdAttr" name="bagIdAttr"> 7.2.25 Production bagIdAttr </a> </h4> <div class="productionOuter"> <div class="productionInner"> <p> attribute( <a href="#eventterm-attribute-URI"> URI </a> == <code> rdf:bagID </code>, <br />      <a href="#eventterm-attribute-string-value"> string-value </a> == <a href="#rdf-id"> rdf-id </a> ) </p> </div> </div> <p> <strong> Constraint: </strong>: <a href="#constraint-id"> constraint-id </a> applies to the values of <code> rdf:bagID </code> attributes </p> <h4> 7.2.26 7.2.25 Production propertyAttr

attribute( URI == propertyAttributeURIs ,
     string-value == anyString )

7.2.27 7.2.26 Production resourceAttr

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

7.2.28 7.2.27 Production datatypeAttr

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

7.2.29 7.2.28 Production parseLiteral

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

7.2.30 7.2.29 Production parseResource

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

7.2.31 7.2.30 Production parseCollection

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

7.2.32 7.2.31 Production parseOther

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

7.2.33 7.2.32 Production URI-reference

An attribute · string-value · interpreted as an RDF URI Reference reference .

7.2.34 7.2.33 Production literal

Any XML element content that is allowed according to [XML] definition Content of Elements Rule [43] content . in section 3.1 Start-Tags, End-Tags, and Empty-Element Tags

The string-value for the resulting event is discussed in section 7.2.17 .

7.2.35 7.2.34 Production rdf-id

An attribute · string-value · matching any legal [XML-NS] token NCName

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:

s p o .

add the following statements to the graph:

r . string-value <http://www.w3.org/1999/02/22-rdf-syntax-ns#subject> s .
r . string-value <http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate> p .
r . string-value <http://www.w3.org/1999/02/22-rdf-syntax-ns#object> o .
r . 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 reference u := concat("http://www.w3.org/1999/02/22-rdf-syntax-ns#_", e . li-counter ), increment the e . li-counter property by 1 and return u .
deleted text:
7.5 Bag 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 . bag-li-counter ), increment the e . bag-li-counter property by 1 and return u .
<h2> <a id="section-Serialising" name="section-Serialising"> 8 Serializing an RDF Graph to RDF/XML </a> </h2> <p> There are some RDF Graphs as defined in the RDF Concepts and Abstract Syntax deleted text: Working Draft. that cannot be serialized in RDF/XML. These are those that: </p> <dl> <dt> Use property names that cannot be turned into XML namespace-qualified names. <br /> </dt> <dd> An XML namespace-qualified name ( <a href="http://www.w3.org/TR/REC-xml-names/#dt-qname"> QName </a> ) 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- <a href="http://www.w3.org/TR/REC-xml-names/#NT-NCName"> NCName </a> character, ensuring that the first character of the name is a <a href="http://www.w3.org/TR/REC-xml#NT-Letter"> Letter </a> or '_'. If the URI ends in a non- <a href="http://www.w3.org/TR/REC-xml-names/#NT-NCName"> NCName </a> character then throw a "this graph cannot be serialized in RDF/XML" exception or error. </dd> <dt> Use inappropriate reserved names as properties <br /> </dt> <dd> For example, a property with the same URI as any of the <a href="#syntaxTerms"> syntaxTerms </a> production. </dd> </dl>

A more detailed discussion of the issues of serializing the Implementation Note (Informative): When an RDF Graph graph is serialized to RDF/XML is given and has an XML Schema Datatype (XSD), it SHOULD be written in [UNPARSING] . This describes using the original syntax without the subsequently added rdf:nodeID attribute a form that now allows all graphs with blank nodes to be serialized. 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 in RDF in HTML: Approaches deleted text: <a href="#ref-rdf-in-xhtml"> [RDF-IN-XHTML] </a> and it concludes that there is no single embedding method that satisfies all applications and remains simple. </p> <p> The recommended approach is to not embed RDF/XML in HTML/XHTML but rather to use <code> <link> </code> element in the <code> <head> </code> element of the HTML/HTML to point at a separate RDF/XML document. This approach has been used for several years by the Dublin Core Metadata Initiative (DCMI) on its Web site.

To use this technique, the <link> element href 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 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] however rel="alternative" rel="alternate" may also be appropriate. See HTML 4.01 link types and , XHTML Modularization - — LinkTypes and XHTML 2.0 — LinkTypes for further information. 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.

Example 21: Using link in XHTML with an external RDF/XML document ( example21.html linking to example21.rdf )

<?xml version="1.0" encoding='iso-8859-1'?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>My document</title> <meta http-equiv="Content-type" content='text/html; charset="iso-8859-1"' /> <link rel="alternate" type="application/rdf+xml" title="RDF Version" href="example21.rdf" /> </head> <body> <h1>My document</h1> </body> </html>

10 Acknowledgments Using RDF/XML with SVG (Informative)

The following people provided valuable contributions to There is a standardized approach for associating RDF compatible metadata with SVG — the document:

Dan Brickley, W3C/ILRT

Jeremy Carroll, HP Labs Bristol

Bijan Parsia, MIND Lab at metadata element which was explicitly designed for this purpose as defined in Section 21 Metadata of the Scalable Vector Graphics (SVG) 1.0 Specification [SVG] and Section 21 Metadata of the Scalable 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 1 and figure 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).

11 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. 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 , G. Klyne, J. Carroll, Editors, World Wide Web Consortium Working Draft, work in progress, 5 September 2003. This version of the RDF Concepts and Abstract Syntax is http://www.w3.org/TR/2003/WD-rdf-concepts-20030905/. The latest version of the RDF Concepts and Abstract Syntax is at http://www.w3.org/TR/rdf-concepts/.

[RDF-TESTS]

RDF Test Cases , J. Grant and D. Beckett, Editors, World Wide Web Consortium Working Draft, work in progress, 5 September 2003. This version of the RDF Test Cases is http://www.w3.org/TR/2003/WD-rdf-testcases-20030905/. The latest version of the RDF Test Cases is at 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 , P. Hayes, Editor. World Wide Web Consortium Working Draft, work in progress, 5 September 2003. This version of the RDF Semantics is http://www.w3.org/TR/2003/WD-rdf-mt-20030905. The latest version of the RDF Semantics is at http://www.w3.org/TR/rdf-mt.

[RDF-PRIMER]

RDF Primer , F. Manola, E. Miller, Editors, World Wide Web Consortium Working Draft, work in progress, 5 September 2003. This version of the RDF Primer is http://www.w3.org/TR/2003/WD-rdf-primer-20030905. The latest version of the RDF Primer is at http://www.w3.org/TR/rdf-primer.

[RDF-VOCABULARY]

RDF Vocabulary Description Language 1.0: RDF Schema , D. Brickley, R.V. Guha, Editors, World Wide Web Consortium Working Draft, work in progress, 5 September 2003. This version of the RDF Vocabulary Description Language is http://www.w3.org/TR/2003/WD-rdf-schema-20030905. The latest version of the RDF Vocabulary Description Language is at 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 the RELAX NG XML version . These formats are described in RELAX 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

# # 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_<n> 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 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 between Drafts 23 January 2003 and 05 September 2003 (Informative)

Changes between the 23 January 2003 last call working draft and 05 September 2003 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

hodder-01 — RDF in HTML ( syntaxLCC-002 )

Updated 9 Using RDF/XML with HTML and XHTML to add new example, correct the meta rel attribute value and link to XHTML2's section on link types. after comment by Hodder which was accepted by the RDF Core WG.

reagle-01 — XMLLiteral equality

Updated 6 Syntax Data Model , 7.2.17 Production parseTypeLiteralPropertyElt and 7.2.33 Production literal (was 7.2.34 in previous draft) after comment by Reagle and others to more precisely describe XML literals for equality which was accepted by the RDF Core WG with changes to several documents to use only Exclusive Canonicalization with comments and empty InclusiveNamespaces PrefixList. See 7.2.17 Production parseTypeLiteralPropertyElt for the full description.

[XML] timbl-01 — bagid needed ( syntaxLCC-004 )

Extensible Markup Language (XML) 1.0, Second Edition The RDF Core WG decided , T. Bray, J. Paoli, C.M. Sperberg-McQueen to accept this comment and E. Maler, Editors. World Wide Web Consortium. 6 October 2000. remove bagID. This version is http://www.w3.org/TR/2000/REC-xml-20001006. latest version meant changes to remove all references to rdf:bagID being permitted. Section 2.17 Reifying Statements changed title, removed rdf:bagID discussion and Example 21. Section 3 Terminology removed bagID from syntax names. Section 5.2 Identifiers removed bagID from discussion of XML URI references. Section 5.4 Constraints is available at http://www.w3.org/TR/REC-xml. removed bagID from constraint-id . Section 6.1.2 Element Event removed bag-id-counter accessor. Section 6.1.4 Attribute Event removed bagID from allowed non-namespaced attributes. 7.2.2 Production coreSyntaxTerms removed rdf:bagID. 7.2.4 Production oldTerms added rdf:bagID and link to the LC Issue. 7.2.11 Production nodeElement removed use of bagIDAttr production, removed actions when bagID found and removed S1-4 labels. 7.2.21 Production emptyPropertyElt removed use of bagIDAttr production and removed actions when bagID found. 7.2.25 Production bagID deleted (7.2.26-7.2.35 then renumbered), Section 7.5 Bag Expansion Rules deleted.

[XML-NS] timbl-03 — collection clutter

Namespaces Updated Section 7.2.19 Production parseTypeCollectionPropertyElt to remove the redundant triple in XML rdf:parseType="Collection" after the RDF Core WG accepted this comment.

xmlsch-02 — Whitespace facets
, 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

Updated 6.1.9 Typed Literal Event to add a note that the whitespace facet in W3C XML Schema datatypes does not affect RDF lexical-to-value mapping after the proposal is available at http://www.w3.org/TR/REC-xml-names. to address the issue approved in RDF Core telcon 2003-05-09.

[INFOSET] Language tags in Typed Literals

XML Information Set Updated 2.9 Typed Literals deleted text: , 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 6.1.9 Typed Literal Event , 6.3 Grammar Notation , 7.2.16 Production literalPropertyElt , 7.2.17 Production parseTypeLiteralPropertyElt after removal of XML Information set language tag from all typed literals including rdf:XMLLiteral as approved in RDF Core telcon 2003-05-09. Also added N-Triples escapes for URI references to 6.1.6 URI Reference Event as added to 6.1.9 deleted text: is available at http://www.w3.org/TR/xml-infoset. </dd>

Appendix B.2: Editorial Revisions

[URIS] efth-01 — change namespace URIs

RFC 2396 - Uniform Resource Identifiers (URI): Generic Syntax Removed two informative notes about potentially changing the rdf namespace URIs in 5.1 The RDF Namespace and Vocabulary deleted text: , T. Berners-Lee, R. Fielding and L. Masinter, IETF, August 1998. This document is http://www.isi.edu/in-notes/rfc2396.txt. 7.2.5 Production nodeElementURIs . After the resolution of this issue and action recorded in RDF Core WG 2003-04-11 telcon .

deleted text: [RDF-CONCEPTS]

Resource Description Framework (RDF): Concepts and Abstract Syntax pfps-19 — namespace v vocabulary
, G. Klyne, J. Carroll, Editors, World Wide Web Consortium Last Call Working Draft, work in progress, 23 January 2003. This version of
Throughout: Changed the RDF Concepts term "namespace" to be used to refer to XML namespaces and Abstract Syntax is http://www.w3.org/TR/2003/WD-rdf-concepts-20030123/. The latest version the term "vocabulary" be used to refer to collections of names ( RDF URI references ) after the RDF Concepts and Abstract Syntax Core WG accepted is at http://www.w3.org/TR/rdf-concepts/. this comment.

deleted text: [RDF-TESTS]

RDF Test Cases williams-01 , J. Grant — Nodes and D. Beckett, Editors, World Wide Web Consortium Last Call Working Draft, work arcs terminology

Throughout: Changed arc to be predicate arc when talking about the thing in progress, 23 January 2003. This version the graph picture. Removed use of 'labeling' when not talking about the RDF Test Cases is http://www.w3.org/TR/2003/WD-rdf-testcases-20030123/. The latest version picture. Replaced arc with predicate when talking about part of an RDF triple. Changes after RDF Core WG discussion 2003-06-06 on the use of arc and RDF Test Cases Core WG decision is at http://www.w3.org/TR/rdf-testcases/.

[KEYWORDS] 2003-03-21 on the resolution of issue williams-01

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

deleted text: [RFC-3023]

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

[RDF-MIMETYPE-ID]

application/rdf+xml Media Type Registration , Internet-Draft draft-w3c-rdfcore-rdfxml-mediatype-01, A. Swartz, 23 August 2002.

[XML-BASE] </dt> <dd> <span class="diff-old-a">deleted text: </span> XML Base 2.1 Introduction , 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 2nd paragraph modified and split into two to mention namespace names more and prefixes less after editorial comments in section 4.2 of XML Base Schema WG comments on RDF documents deleted text: is at http://www.w3.org/TR/xmlbase. </dd> <dt> [XML-XC14N] Notes on Whitespace Normalization for XML Schema Datatypes

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 Added an implementation note to 8 Serializing an RDF Graph to RDF/XML that when generating RDF/XML, if XSD support is at http://www.w3.org/TR/xml-exc-c14n. provided, the whitespaced normalized form should be used.
deleted text:

Informational References

<dt> [CHARMOD] Grammar Notation
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 Split the Character Model is http://www.w3.org/TR/2002/WD-charmod-20020220. The latest version huge table of the Character Model notation in 6.3 Grammar Notation is at http://www.w3.org/TR/charmod. into three smaller ones for general, matching and action notation. Reworded the introduction to this section to match.

[RDF-SEMANTICS] XML Canonicalization

RDF Semantics Reworded 7.2.17 Production parseTypeLiteralPropertyElt , P. Hayes, Editor. World Wide Web Consortium Last Call Working Draft, work in progress, 23 January 2003. This version to give the method how to get the lexical form (Unicode string) of XML literals from the RDF Semantics is http://www.w3.org/TR/2003/WD-rdf-mt-20030123. The latest version XML Infoitems inside the rdf:parseType="Literal" content using Exclusive XML Canonicalization. A clarification after it was noticed the output of exc-C14N was an sequence of the RDF Semantics is at http://www.w3.org/TR/rdf-mt. octets not a Unicode string.

[RDF-PRIMER] Unicode NFC

RDF Primer , F. Manola, E. Miller, Editors, World Wide Web Consortium last Call Working Draft, work Added references to NFC checking for Unicode strings used as literal values in progress, 23 January 2003. This version of the RDF Primer is http://www.w3.org/TR/2003/WD-rdf-primer-20030123. The latest version of the RDF Primer 7.2.11 Production nodeElement , 7.2.16 Production literalPropertyElt and 7.2.21 Production emptyPropertyElt . Added new normative references Unicode [UNICODE] and Normal Form C [NFC] . After comment by Patel-Schneider 2003-08-05 deleted text: is at http://www.w3.org/TR/rdf-primer. </dd> <dt> <span class="diff-old-a">deleted text: </span> [RDF-VOCABULARY]
RDF Vocabulary Description Language 1.0: RDF Schema , D. Brickley, R.V. Guha, Editors, World Wide Web Consortium Last Call Working Draft, work in progress, 23 January 2003. This version definiton
Added a definition of the RDF Vocabulary Description Language is http://www.w3.org/TR/2003/WD-rdf-schema-20030123. to Section 5.1 The deleted text: latest version of the RDF Namespace and Vocabulary deleted text: Description Language is at http://www.w3.org/TR/rdf-schema.

[STRIPEDRDF] </a>

RDF: Understanding and edited the Striped RDF/XML Syntax wording slightly from suggestion by Patel-Schneider 2003-08-07 deleted text: , D. Brickley, W3C, 2001. This document is http://www.w3.org/2001/10/stripes/. </dd> <dt> [XPATH] RDF/XML in SVG

XML Path Language (XPath) Version 1.0 Added informative section 10 Using RDF/XML with SVG , J. Clark (renumbering Acknowledgements to 11, 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 References to 12) to add pointers to where the SVG 1.0 and 1.1 specifications describe using RDF/XML inside SVG. Added after the original comment from Chris Lilley is at http://www.w3.org/TR/xpath. as actioned by the RDF Core WG telcon 2003-04-04 .

[SAX2] Conformance

SAX Simple API for XML, version 2 Added section 5.5 Conformance , D. Megginson, SourceForge, 5 May 2000. This document is http://sax.sourceforge.net/. as actioned after RDF Core WG telcon 2003-07-18 to define the terms RDF Document and RDF/XML Document as well as conformance to this specification.

[UNPARSING] Review by Graham Klyne

Unparsing RDF/XML Editorial and wording changes to several sections 2.1 , 2.7 , 2.10 , 4 , 5.2 , 6.1 , 6.1.2 , 6.3 , 7.2.1 , 7.2.19 , 7.3 , 11 References after Graham Klyne's review for RDF Core WG.

Remove document statuses from document body
, J. J. Carroll, HP Labs Technical Report, HPL-2001-294, 2001. This

Removed the use of document is available at http://www.hpl.hp.com/techreports/2001/HPL-2001-294.html. status words (Working Draft, Recommendation etc.) throughout the document body RDF Core WG telcon 2003-07-18 . These remain in the references (correct) and status (yet to be edited) sections.

[RELAXNG] Review by Jeremy Carroll

RELAX NG Specification Changes to several sections after Jeremy Carroll's review , James Clark 2003-07-07 for the RDF Core WG. 1 Introduction Removed (process, historical) paragraph 2. 2.1 Introduction Rewordings — subject 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 object nodes don't use QNames. 2.2 Node Elements and Property Elements Use "left hand side of figure 2" to describe the path. Minor words.
2.14 Abbreviating URI References Added note that a base URI is required either from xml:base or the URI of the RELAX NG Specification document. 7.2.19 Production parseTypeCollectionPropertyElt is at http://www.oasis-open.org/committees/relax-ng/spec.html. Minor words.

[RELAXNG-COMPACT] Editorial comments on section 2

2.11 Omitting Blank Nodes: rdf:parseType="Resource" deleted text: RELAX NG Compact Syntax </a> , 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] reworded to clarify which property element was discussed. 2.12 Omitting Nodes: Property Attributes on an empty Property Element

reworded to explain moving the property element to a property attribute 2.15 Container Membership Property Elements: rdf:li and rdf:_ n deleted text: RDF in HTML: Approaches </a> added note that document order matters here. 2.16 Collections: rdf:parseType="Collection" , Sean B. Palmer, 2002 added note that document order matters here. After comments in personal communication to the editor 2003-06-17.

[RFC-2731] Editorial comments

RFC 2731 - Encoding Dublin Core Metadata in HTML Minor fixes to 7.2.15 Production resourcePropertyElt , John Kunze, DCMI, December 1999.

and 7.2.16 Production literalPropertyElt A Syntax Schemas (Informative)

This appendix contains (not 7.12 as in the comment) after comments by Palmer , 2003-06-10
XML schemas for validating RDF/XML forms. These are example schemas for information only and are not part of this specification.

Reserved Names

5.1 The RDF Namespace 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 Remove the restriction on namespace names starting with the deleted text: RELAX NG XML version . These formats namespace URI. 6 Syntax Data Model Add how to remove reserved XML Names when they are described in RELAX NG element names. 6.1.2 Element Event ( [RELAXNG] Expand the details of how to remove remove XML Names when they are attribute names. Updates after several comments by Patel-Schneider starting 2003-05-22 deleted text: ) and RELAX NG Compact ( [RELAXNG-COMPACT] 2003-06-04 ).

Note: The RNGC schema has been updated to attempt and after approval to match change in RDF Core WG 2003-06-06 telcon .

Status of Notes

In sections 4 , 5.1 , 5.2 , 5.3 , 6.1.8 , 6.1.9 , 7.2.4 , 7.2.16 . Reviewed the grammar but this has not been checked status of Notes and marked those specifically that are informative such as implementation or used to validate RDF/XML.
interoperability notes. After action recorded in RDF Core telcon 2003-03-28 .

Missing case in parseOther

7.2.31 Production parseOther (was 7.2.32 in previous draft) added the case "Collection" which had been mistakenly omitted after the comment by Patel-Schneider , 2003-05-09.

RELAX NG sufixes

Renamed the informative RELAX NG schemas in A.1 RELAX NG Compact Schema deleted text: for RDF/XML </a> to use suffixes .rnc (compact version) and .rng (XML version) after comment by Prud'hommeaux , 2003-05-06.

Citing Namespaces in 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:bagID | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype # syntaxTerms = coreSyntaxTerms | rdf:Description | rdf:li # oldTerms = rdf:aboutEach | rdf:aboutEachPrefix # 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_<n> 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 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 * - ( rdf:RDF | rdf:ID | rdf:about | rdf:bagID | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:li | rdf:aboutEach | rdf:aboutEachPrefix | xml:* ) { (idAttr | nodeIdAttr | aboutAttr )?, bagIdAttr?, xmllang?, xmlbase?, propertyAttr*, propertyEltList }
Throughout, changed to use the correct document title Namespaces in XML after a private editorial comment to the editor 2003-05-04.

Editorial comments 4.3 from XML Schema WG
# It is not possible to say "and not things # beginning with _ in the rdf: namespace" in RELAX NG.

ws = " " 2.4 Empty Property Elements first sentence modified after editorial comments in section 4.3 of XML Schema WG comments on RDF documents

Editorial comments ( syntaxLCC-001 )
# 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

Spellings, grammar, CSS style and suggested rewordings after editorial comments from Lesch, 2003-02-25 . In particular the small two-paragraph informative section 2.18 has been merged into section 1 introduction . Many excessive capitalizations were removed.

Minor editorial

1 letter change after comment from Dürst, 2003-01-30

Blank node identifier clarification
propertyEltList = propertyElt*

Additional clarification added to 5.2 , 6.1.7 and 6.3 (bnodeid definition) as described 2003-01-30 after coment by Patel-Schneider, 2003-01-28 .

Appendix B.3: Issues requiring no document revisions

# Should be something like: # ws* , ( propertyElt , ws* )* # but RELAXNG does this by default, ignoring whitespace separating tags. chas-01 — aboutEachPrefix
propertyElt = resourcePropertyElt | literalPropertyElt | parseTypeLiteralPropertyElt | parseTypeResourcePropertyElt | parseTypeCollectionPropertyElt | parseTypeOtherPropertyElt | emptyPropertyElt

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

parseTypeLiteralPropertyElt = element * - ( rdf:RDF | rdf:ID | rdf:about | rdf:bagID | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | xml:* ) { idAttr?, parseLiteral, xmllang?, xmlbase?, literal } krech-01 — emptyPropertyElt ambiguity ( syntaxLCC-003 )
parseTypeResourcePropertyElt = element * - ( rdf:RDF | rdf:ID | rdf:about | rdf:bagID | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | xml:* ) { idAttr?, parseResource, xmllang?, xmlbase?, propertyEltList }

After rdf:bagID was removed from the language for last call issue timbl-01 , this comment by Krech required no action.

parseTypeCollectionPropertyElt = element * - ( rdf:RDF | rdf:ID | rdf:about | rdf:bagID | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix ) { idAttr?, xmllang?, xmlbase?, parseCollection, nodeElementList } hendler-01 — literals in parsetype collection
parseTypeOtherPropertyElt = element * - ( rdf:RDF | rdf:ID | rdf:about | rdf:bagID | rdf:parseType | rdf:resource | rdf:nodeID | rdf:datatype | rdf:Description | rdf:aboutEach | rdf:aboutEachPrefix | xml:* ) { idAttr?, xmllang?, xmlbase?, parseOther, any }

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

nodeIdAttr = attribute rdf:nodeID { IDsymbol } xmlsch-08 — xsi:type
aboutAttr = attribute rdf:about { URI-reference }

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

resourceAttr = attribute rdf:resource { URI-reference } xmlsch-10 — cannonical syntax
datatypeAttr = attribute rdf:datatype { URI-reference }

parseLiteral = attribute rdf:parseType { "Literal" } postponed parseResource = attribute rdf:parseType { "Resource" }

parseCollection = attribute rdf:parseType { "Collection" } xmlsch-11 — layering on xml
parseOther = attribute rdf:parseType { text }

URI-reference = string clarification given literal = any

IDsymbol = xsd:NMTOKEN xmlsch-12 — capricious syntax
any = mixed { element * { attribute * { text }*, any }* }

postponed

B Changes C Revisions since Working Draft 05 September 2003 (Informative)

Changes since the 8 November 2002 05 September 2003 working draft

(Newest at top)

5.1 RDF Namespace Correct the rdf:_ n phrasing to forbid rdf:_0 and anything with leading zeros.

5.1 RDF Namespace Forbid XML namespaces with a namespace URI that is a prefix of the RDF or XML namespace URI references.

5.2 Identifiers Blank nodeIDs in RDF/XML These are scoped to the infoset document infoitem.

Section 2 Added links to the N-Triples answers for all the complex examples

Updated References

7.2.1 parseTypeLiteralPropertyElt Removed reference to RDF Concepts canonicalization are divided into non-editorial and added new paragraph describing the freedom on the lexical forms of XML Literal.
Added Exclusive XML Canonicalization [ XML-XC14N ] to normative references.

Updated links to match RDF Concepts new definitions

Status, abstract, notes: Updated

Appendix C (now Appendix B). Removed older editorial. The non-editorial changes to leave only also list consquential editorial changes. Editorial changes are those since the last working draft. ( Appendix C which do not result in 8 November 2002 draft )

Appendix B Other Syntax Schemas (Informative) . Deleted. ( Appendix B any change in 8 November 2002 draft )

Appendix A Issues . Deleted. ( the meaning of an RDF document or the behaviour of an RDF application.

Appendix A in 8 November 2002 draft )

6.1.6 Identifier Event. Split this into URI Reference Event (6.1.6) C.1: Non-Editorial Revisions and Blank Node Identifier event (6.1.7) .

NFC
6.3 Grammar Notation

Add clarifications that Unicode Normal Form C (NFC) checks apply to Unicode strings in 7.2.16 deleted text: split notation identifier() with uri() and bnodeid(). 7.2.17 after proposal 2003-09-18 from issues arising from comment by Patel-Schneider 2003-08-07

Blank nodeID text

Updated the grammar to use these.

Added generated-blank-node-id() grammar notation to explictly show when such things are generated

blank node identifier description in 5.2 Identifiers expanded and constraints in 6.1.7 Blank Node Identifiers description including rdf:nodeID values and generated ones

5.3 Base URIs retitled Resolving URIs

6.3 Grammar Notation Identifier Event deleted text: Added resolve() grammar action notation to explicitly note when URI resolving is done as RDF URI References are built from string content clarify that some blank node identifiers may need to be generated and in-scope base URIs.

6.1.8 XML Literal Event. Replaced with Typed Literal Event .
6.3 Grammar Notation . Replaced grammar action notation xml() with typed-literal()
This matches the terms in RDF Concepts.

Replaced rdfs:XMLLiteral with rdf:XMLLiteral in 5.1 RDF Namespace , 7.2.1 parseTypeLiteralPropertyElt .

Previous changes there are listed in restrictions on those generated names. Change made consequent to discussion after the changes section review by Jeremy Carroll 2003-09-22 of the previous 8 November 2002
Appendix C.2: Editorial Revisions working draft.

None

None

7.2.2 coreSyntaxTerms	`rdf:RDF` \| `rdf:ID` \| `rdf:about` \| `deleted text: rdf:bagID </code> \| rdf:parseType </code> \| rdf:resource \| rdf:nodeID \| rdf:datatype`
7.2.3 syntaxTerms	coreSyntaxTerms \| `rdf:Description` \| `rdf:li`
7.2.4 oldTerms	`rdf:aboutEach` \| `rdf:aboutEachPrefix` \| `rdf:bagID`
7.2.5 nodeElementURIs	anyURI - ( coreSyntaxTerms \| `rdf:li` \| oldTerms )
7.2.6 propertyElementURIs	anyURI - ( coreSyntaxTerms \| `rdf:Description` \| oldTerms )
7.2.7 propertyAttributeURIs	anyURI - ( coreSyntaxTerms \| `rdf:Description` \| `rdf:li` \| oldTerms )
7.2.8 doc	root( document-element == RDF , children == list( RDF ))
7.2.9 RDF	start-element( URI == `rdf:RDF`, attributes == set()) nodeElementList end-element()
7.2.10 nodeElementList	ws * ( nodeElement ws * )*
7.2.11 nodeElement	start-element( URI == nodeElementURIs attributes == set(( idAttr \| nodeIdAttr \| aboutAttr Â )?, deleted text: <a href="#bagIdAttr"> bagIdAttr </a> ?, propertyAttr *)) propertyEltList end-element()
7.2.12 ws	A text event matching white space defined by [XML] definition White Space Rule [3] S in section Common Syntactic Constructs
7.2.13 propertyEltList	ws * ( propertyElt ws * ) *
7.2.14 propertyElt	resourcePropertyElt \| literalPropertyElt \| parseTypeLiteralPropertyElt \| parseTypeResourcePropertyElt \| parseTypeCollectionPropertyElt \| parseTypeOtherPropertyElt \| emptyPropertyElt
7.2.15 resourcePropertyElt	start-element( URI == propertyElementURIs ), attributes == set( idAttr ?)) ws * nodeElement ws * end-element()
7.2.16 literalPropertyElt	start-element( URI == propertyElementURIs ), attributes == set( idAttr ?, datatypeAttr ?)) text() end-element()
7.2.17 parseTypeLiteralPropertyElt	start-element( URI == propertyElementURIs ), attributes == set( idAttr ?, parseLiteral )) literal end-element()
7.2.18 parseTypeResourcePropertyElt	start-element( URI == propertyElementURIs ), attributes == set( idAttr ?, parseResource )) propertyEltList end-element()
7.2.19 parseTypeCollectionPropertyElt	start-element( URI == propertyElementURIs ), attributes == set( idAttr ?, parseCollection )) nodeElementList end-element()
7.2.20 parseTypeOtherPropertyElt	start-element( URI == propertyElementURIs ), attributes == set( idAttr ?, parseOther )) propertyEltList end-element()
7.2.21 emptyPropertyElt	start-element( URI == propertyElementURIs ), attributes == set( idAttr ?, ( resourceAttr \| nodeIdAttr )?, deleted text: <a href="#bagIdAttr"> bagIdAttr </a> ?, propertyAttr *)) end-element()
7.2.22 idAttr	attribute( URI == `rdf:ID`, string-value == rdf-id )
7.2.23 nodeIdAttr	attribute( URI == `rdf:nodeID`, string-value == rdf-id )
7.2.24 aboutAttr	attribute( URI == `rdf:about`, string-value == URI-reference )
deleted text: <a href="#bagIdAttr"> 7.2.25 </a> <a href="#bagIdAttr"> bagIdAttr </a> </td> <td> attribute( <a href="#eventterm-attribute-URI"> URI </a> == <code> rdf:bagID </code>, <a href="#eventterm-attribute-string-value"> string-value </a> == <a href="#rdf-id"> rdf-id </a> ) </td> </tr> <tr valign="top"> <td> 7.2.26 7.2.25 propertyAttr	attribute( URI == propertyAttributeURIs , string-value == anyString )
7.2.27 7.2.26 resourceAttr	attribute( URI == `rdf:resource`, string-value == URI-reference )
7.2.28 7.2.27 datatypeAttr	attribute( URI == `rdf:datatype`, string-value == URI-reference )
7.2.29 7.2.28 parseLiteral	attribute( URI == `rdf:parseType`, string-value == "Literal")
7.2.30 7.2.29 parseResource	attribute( URI == `rdf:parseType`, string-value == "Resource")
7.2.31 7.2.30 parseCollection	attribute( URI == `rdf:parseType`, string-value == "Collection")
7.2.32 7.2.31 parseOther	attribute( URI == `rdf:parseType`, string-value == anyString - ("Resource" \| "Literal") "Literal" \| "Collection") )
7.2.33 7.2.32 URI-reference	An attribute · string-value · interpreted as an RDF URI Reference reference .
7.2.34 7.2.33 literal	Any XML element content that is allowed according to [XML] definition Content of Elements Rule [43] content . in section 3.1 Start-Tags, End-Tags, and Empty-Element Tags
7.2.35 7.2.34 rdf-id	An attribute · string-value · matching any legal [XML-NS] token NCName

Editor's Draft of RDF/XML Syntax Specification (Revised)

Editor's Draft of W3C Working Draft 23 January 2 October 2003

5.5 Conformance </h2> <p> This document specifies the syntax of RDF/XML as a grammar on an

<a id="nodeElementStatement5" name="nodeElementStatement5"> S5 7.2.13 Production propertyEltList deleted text: Add the following statement to the graph: </p> <div class="ntripleOuter"> <div class="ntripleInner">

<a href="#nodeElementStatement1"> S1 7.2.14 Production propertyElt </li> <li> Statements from <a href="#nodeElementStatement2"> S2

10 Acknowledgments Using RDF/XML with SVG (Informative)

11 Acknowledgments (Informative)

11 12 References

Normative References

Informational References

A Syntax Schemas (Informative)

A.1 RELAX NG Compact Schema (Informative)

Informational References

and 7.2.16 Production literalPropertyElt A Syntax Schemas (Informative)

Appendix A in 8 November 2002 draft )

Appendix C.2: Editorial Revisions working draft.