Ergebnis für URL: http://www.w3.org/TR/REC-rdf-syntax/ [1]W3C
RDF/XML Syntax Specification (Revised)
W3C Recommendation 10 February 2004
Document Status Update, 1 December 2023
The Latest version link was fixed: it is intended to point to the latest version
of the document for this version of RDF (i.e. RDF 1.0).
This version:
[2]http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/
Latest version:
[3]http://www.w3.org/TR/rdf10-xml/
Previous version:
[4]http://www.w3.org/TR/2003/PR-rdf-syntax-grammar-20031215/
Editor:
[5]Dave Beckett (University of Bristol)
Series editor:
[6]Brian McBride (Hewlett Packard Labs)
Please refer to the [7]errata for this document, which may include some normative
corrections.
See also [8]translations.
[9]Copyright © 2004 [10]W3C^® ([11]MIT, [12]ERCIM, [13]Keio), All Rights
Reserved. W3C [14]liability, [15]trademark, [16]document use and [17]software
licensing rules apply.
____________________________________________________________________________
Abstract
The Resource Description Framework (RDF) is a general-purpose language for
representing information in the Web.
This document defines an [18]XML syntax for RDF called RDF/XML in terms of
[19]Namespaces in XML, the [20]XML Information Set and [21]XML Base. The
[22]formal grammar for the syntax is annotated with actions generating triples of
the [23]RDF graph as defined in [24]RDF Concepts and Abstract Syntax. The triples
are written using the [25]N-Triples RDF 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 in [26]RDF Test Cases.
Status of this Document
This document has been reviewed by W3C Members and other interested parties, and
it has been endorsed by the Director as a [27]W3C Recommendation. W3C's role in
making the Recommendation is to draw attention to the specification and to
promote its widespread deployment. This enhances the functionality and
interoperability of the Web.
This is one document in a [28]set of six ([29]Primer, [30]Concepts, [31]Syntax,
[32]Semantics, [33]Vocabulary, and [34]Test Cases) intended to jointly replace
the original Resource Description Framework specifications, [35]RDF Model and
Syntax (1999 Recommendation) and [36]RDF Schema (2000 Candidate Recommendation).
It has been developed by the [37]RDF Core Working Group as part of the [38]W3C
Semantic Web Activity ([39]Activity Statement, [40]Group Charter) for publication
on 10 February 2004.
Changes to this document since the [41]Proposed Recommendation Working Draft are
detailed in the [42]change log.
The public is invited to send comments to [43]www-rdf-comments@w3.org
([44]archive) and to participate in general discussion of related technology on
[45]www-rdf-interest@w3.org ([46]archive).
A list of [47]implementations is available.
The W3C maintains a list of [48]any patent disclosures related to this work.
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
[49]W3C technical reports index at http://www.w3.org/TR/.
____________________________________________________________________________
Table of Contents
1 [50]Introduction
2 [51]An XML Syntax for RDF
2.1 [52]Introduction
2.2 [53]Node Elements and Property Elements
2.3 [54]Multiple Property Elements
2.4 [55]Empty Property Elements
2.5 [56]Property Attributes
2.6 [57]Completing the Document: Document Element and XML Declaration
2.7 [58]Languages: xml:lang
2.8 [59]XML Literals: rdf:parseType="Literal"
2.9 [60]Typed Literals: rdf:datatype
2.10 [61]Identifying Blank Nodes: rdf:nodeID
2.11 [62]Omitting Blank Nodes: rdf:parseType="Resource"
2.12 [63]Omitting Nodes: Property Attributes on an empty Property Element
2.13 [64]Typed Node Elements
2.14 [65]Abbreviating URI References: rdf:ID and xml:base
2.15 [66]Container Membership Property Elements: rdf:li and rdf:_n
2.16 [67]Collections: rdf:parseType="Collection"
2.17 [68]Reifying Statements: rdf:ID
3 [69]Terminology
4 [70]RDF MIME Type, File Extension and Macintosh File Type
5 [71]Global Issues
5.1 [72]The RDF Namespace and Vocabulary
5.2 [73]Identifiers
5.3 [74]Resolving URIs
5.4 [75]Constraints
5.5 [76]Conformance
6 [77]Syntax Data Model
6.1 [78]Events
6.2 [79]Information Set Mapping
6.3 [80]Grammar Notation
7 [81]RDF/XML Grammar
7.1 [82]Grammar Summary
7.2 [83]Grammar Productions
7.3 [84]Reification Rules
7.4 [85]List Expansion Rules
8 [86]Serializing an RDF Graph to RDF/XML
9 [87]Using RDF/XML with HTML and XHTML
10 [88]Using RDF/XML with SVG
11 [89]Acknowledgments
12 [90]References
Appendices
A [91]Syntax Schemas (Informative)
A.1 [92]RELAX NG Compact Syntax Schema (Informative)
B [93]Revisions since Working Draft 10 October 2003 (Informative)
____________________________________________________________________________
1 Introduction
This document defines the [94]XML [95][XML] syntax for RDF graphs which was
originally defined in the [96]RDF Model & Syntax [97][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 the [98]original RDF/XML grammar in terms of [99]XML
Information Set [100][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 the [101]N-Triples section of [102]RDF
Test Cases [103][RDF-TESTS] which creates an RDF graph, that has semantics
defined by [104]RDF Semantics [105][RDF-SEMANTICS].
The complete specification of RDF consists of a number of documents:
* [106]RDF Primer [107][RDF-PRIMER]
* [108]RDF Concepts and Abstract Syntax [109][RDF-CONCEPTS]
* [110]RDF Semantics [111][RDF-SEMANTICS]
* RDF/XML Syntax (this document)
* [112]RDF Vocabulary Description Language 1.0: RDF Schema
[113][RDF-VOCABULARY]
* [114]RDF Test Cases [115][RDF-TESTS]
For a longer introduction to the RDF/XML syntax with a historical perspective,
see [116]RDF: Understanding the Striped RDF/XML Syntax [117][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 sections
[118]6 Syntax Data Model and [119]7 RDF/XML Grammar, the latter two sections take
precedence.
2.1 Introduction
The [120]RDF Concepts and Abstract Syntax [121][RDF-CONCEPTS] defines the
[122]RDF Graph data model (Section 3.1) and the [123]RDF Graph abstract syntax
(Section 6). Along with the [124]RDF Semantics [125][RDF-SEMANTICS] this provides
an abstract syntax with a formal semantics for it. The RDF graph has [126]nodes
and labeled directed arcs that link pairs of nodes and this is represented as a
set of [127]RDF triples where each triple contains a subject node, predicate and
object node. Nodes are [128]RDF URI references, [129]RDF literals or are
[130]blank nodes. Blank nodes may be given a document-local, non-[131]RDF URI
references identifier called a [132]blank node identifier. Predicates are
[133]RDF URI references and 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 XML [134]QNames as defined in [135]Namespaces in
XML [136][XML-NS] to represent [137]RDF URI references. All QNames have a
[138]namespace name which is a URI reference and a short [139]local name. In
addition, QNames can either have a short [140]prefix or be declared with the
default namespace declaration and have none (but still have a namespace name)
The [141]RDF URI reference represented by a QName is determined by appending the
[142]local name part of the QName after the [143]namespace name (URI reference)
part of the QName. This is used to shorten the [144]RDF URI references of all
predicates and some nodes. [145]RDF URI references identifying subject and object
nodes can also be stored as XML attribute values. [146]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. [147]Example 7 is the first complete RDF/XML
document.
2.2 Node Elements and Property Elements
Graph for RDF/XML Example
Figure 1: Graph for RDF/XML Example ([148]SVG version)
An RDF graph is given in [149]Figure 1 where the nodes are represented as ovals
and contain their [150]RDF URI references where they have them, all the predicate
arcs are labeled with [151]RDF URI references and [152]plain literal nodes have
been written in rectangles.
If we follow one node, predicate arc ... , node path through the graph shown in
[153]Figure 2:
One Path Through the Graph
Figure 2: One Path Through the Graph ([154]SVG version)
The left hand side of the [155]Figure 2 graph corresponds to the node/predicate
arc stripes:
1. Node with [156]RDF URI reference http://www.w3.org/TR/rdf-syntax-grammar
2. Predicate Arc labeled with [157]RDF URI reference
http://example.org/terms/editor
3. Node with no [158]RDF URI reference
4. Predicate Arc labeled with [159]RDF URI reference
http://example.org/terms/homePage
5. Node with [160]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
[161]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 in [162]Example 1,
rdf:Description is the node element (used three times for the three nodes) and
ex:editor and ex:homePage are the two property elements.
Example 1: Striped RDF/XML (nodes and predicate arcs)
The [163]Figure 2 graph consists of some nodes that are [164]RDF 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 [165]Example 2:
Example 2: Node Elements with RDF URI references added
Adding the other two paths through the [166]Figure 1 graph to the RDF/XML in
[167]Example 2 gives the result in [168]Example 3 (this example fails to show
that the blank node is shared between the two paths, see [169]2.10):
Example 3: Complete description of all graph paths
Dave Beckett
RDF/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 [170]Example 3, there are two node elements that can take multiple
property elements. The subject node with URI reference
http://www.w3.org/TR/rdf-syntax-grammar has property elements ex:editor and
ex:title and the node element for the blank node can take ex:homePage and
ex:fullName. This abbreviation gives the result shown in [171]Example 4 (this
example does show that there is a single blank node):
Example 4: Using multiple property elements on a node element
Dave Beckett
RDF/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
(or ) this form can be shortened. This is done by using the
[172]RDF URI reference of the object node as the value of an XML attribute
rdf:resource on the containing property element and making the property element
empty.
In this example, the property element ex:homePage contains an empty node element
with the [173]RDF URI reference http://purl.org/net/dajobe/. This can be replaced
with the empty property element form giving the result shown in [174]Example 5:
Example 5: Empty property elements
Dave Beckett
RDF/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 [175]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 is rdf:type and it
has an rdf:resource attribute the value of which is interpreted as a [176]RDF URI
reference object node.
In [177]Example 5:, there are two property elements with string literal content,
the dc:title and ex:fullName property elements. These can be replaced with
property attributes giving the result shown in [178]Example 6:
Example 6: Replacing property elements with string literal content into property
attributes
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:RDF XML 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 inside rdf: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 from [179]Example 4 onwards but taking the smallest [180]Example 6 and
adding the final components, gives a complete RDF/XML representation of the
original [181]Figure 1 graph in [182]Example 7:
Example 7: Complete RDF/XML description of Figure 1 graph ([183]example07.rdf
output [184]example07.nt)
It is possible to omit rdf:RDF in [185]Example 7 above since there is only one
rdf: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 by [186]2.12
Language Identification of [187]XML 1.0 [188][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.
[189]Typed literals which includes [190]XML literals are 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 in
[191]Example 8:
Example 8: Complete example of xml:lang ([192]example08.rdf output
[193]example08.nt)
RDF/XML Syntax Specification (Revised)
RDF/XML Syntax Specification (Revised)
RDF/XML Syntax Specification (Revised)
Der Baum
Das Buch ist außergewöhnlich
The Tree
2.8 XML Literals: rdf:parseType="Literal"
RDF allows [194]XML literals ([195][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 the rdf:parseType="Literal" attribute on the containing property element.
An example of writing an XML literal is given in [196]Example 9 where there is a
single RDF triple with the subject node [197]RDF URI reference
http://example.org/item01, the predicate [198]RDF URI reference
http://example.org/stuff/1.0/prop (from ex:prop) and the object node with XML
literal content beginning a:Box.
Example 9: Complete example of rdf:parseType="Literal" ([199]example09.rdf output
[200]example09.nt)
2.9 Typed Literals: rdf:datatype
RDF allows [201]typed literals to be given as the object node of a predicate.
Typed literals consist of a literal string and a datatype [202]RDF 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 additional
rdf:datatype="datatypeURI" attribute on the property element. Any [203]RDF URI
reference can be used in the attribute.
An example of an RDF [204]typed literal is given in [205]Example 10 where there
is a single RDF triple with the subject node [206]RDF URI reference
http://example.org/item01, the predicate [207]RDF URI reference
http://example.org/stuff/1.0/size (from ex:size) and the object node with the
[208]typed literal ("123", http://www.w3.org/2001/XMLSchema#int) to be
interpreted as an [209]W3C XML Schema [210][XML-SCHEMA2] datatype int.
Example 10: Complete example of rdf:datatype ([211]example10.rdf output
[212]example10.nt)
123
2.10 Identifying Blank Nodes: rdf:nodeID
[213]Blank nodes in the RDF graph are distinct but have no [214]RDF URI reference
identifier. It is sometimes required that the same graph [215]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 [216]blank node identifier can be given
to the [217]blank node for identifying it in the document. Blank node identifiers
in RDF/XML are scoped to the containing XML Information Set [218]document
information item. A [219]blank node identifier is used on a node element to
replace rdf:about="RDF URI reference" or on a property element to replace
rdf:resource="RDF URI reference" with rdf:nodeID="[220]blank node identifier" in
both cases.
Taking [221]Example 7 and explicitly giving a [222]blank node identifier of abc
to the blank node in it gives the result shown in [223]Example 11. The second
rdf:Description property element is about the blank node.
Example 11: Complete RDF/XML description of graph using rdf:nodeID identifying
the blank node ([224]example11.rdf output [225]example11.nt)
2.11 Omitting Blank Nodes: rdf:parseType="Resource"
[226]Blank nodes (not [227]RDF URI reference nodes) in RDF graphs can be written
in a form that allows the pair to be
omitted. The omission is done by putting an rdf: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 [228]Example 7, the contents of the ex:editor property element
could be alternatively done in this fashion to give the form shown in
[229]Example 12:
Example 12: Complete example using rdf:parseType="Resource" ([230]example12.rdf
output [231]example12.nt)
Dave Beckett
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:lang value (if present) and each of these
property elements appears at most once and there is at most one rdf:type property
element with a [232]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 [233]Example 5, the ex:editor property element contains a
blank node element with two property elements ex: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
empty ex:editor property element. The result is shown in [234]Example 13.
Example 13: Complete example of property attributes on an empty property element
([235]example13.rdf output [236]example13.nt)
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 the [237]RDF URI reference of the value of the type relationship. There may,
of course, be multiple rdf:type predicates 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 [238]RDF vocabulary: rdf:Seq, rdf:Bag, rdf:Alt, rdf:Statement, rdf:Property
and rdf:List.
For example, the RDF/XML in [239]Example 14 could be written as shown in
[240]Example 15.
Example 14: Complete example with rdf:type ([241]example14.rdf output
[242]example14.nt)
A marvelous thing
Example 15: Complete example using a typed node element to replace an rdf:type
([243]example15.rdf output [244]example15.nt)
A marvelous thing
2.14 Abbreviating URIs: rdf:ID and xml:base
RDF/XML allows further abbreviating [245]RDF URI references in XML attributes in
two ways. The XML Infoset provides a base URI attribute xml:base that sets the
base URI for resolving relative [246]RDF URI references, otherwise the base URI
is that of the document. The base URI applies to all RDF/XML attributes that deal
with [247]RDF URI references which are rdf:about, rdf:resource, rdf:ID and
rdf:datatype.
The rdf:ID attribute on a node element (not property element, that has another
meaning) can be used instead of rdf:about and gives a relative [248]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 [249]RDF URI
reference.
Both forms require a base URI to be known, either from an in-scope xml:base or
from the URI of the RDF/XML document.
[250]Example 16 shows abbreviating the node [251]RDF URI reference of
http://example.org/here/#snack using an xml: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 [252]RDF URI reference resolved from the rdf:resource
XML attribute value using the in-scope base URI to give the [253]RDF URI
reference http://example.org/here/fruit/apple.
Example 16: Complete example using rdf:ID and xml:base for shortening URIs
([254]example16.rdf output [255]example16.nt)
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 the rdf:Seq, rdf:Bag and rdf:Alt
classes which may be written as typed node elements. The list properties are
rdf:_1, rdf:_2 etc. and can be written as property elements or property
attributes as shown in [256]Example 17. There is an rdf:li special property
element that is equivalent to rdf:_1, rdf:_2 in order, explained in detail in
[257]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 [258]Example 17 written
in this form is shown in [259]Example 18.
Example 17: Complex example using RDF list properties ([260]example17.rdf output
[261]example17.nt)
Example 18: Complete example using rdf:li property element for list properties
([262]example18.rdf output [263]example18.nt)
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 in [264]Section 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.
[265]Example 19 shows a collection of three nodes elements at the end of the
ex:hasFruit property element using this form.
Example 19: Complete example of a RDF collection of nodes using
rdf:parseType="Collection" ([266]example19.rdf output [267]example19.nt)
2.17 Reifying Statements: rdf:ID
The rdf:ID attribute can be used on a property element to reify the triple that
it generates (See [268]section 7.3 Reification Rules for the full details). The
identifier for the triple should be constructed as a [269]RDF URI reference made
from the relative URI reference # concatenated with the rdf:ID attribute value,
resolved against the in-scope base URI. So for example if rdf:ID="triple", that
would be equivalent to the [270]RDF URI reference formed 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 [271]constraint-id.
[272]Example 20 shows a rdf:ID being used to reify a triple made from the ex:prop
property element giving the reified triple the [273]RDF URI reference
http://example.org/triples/#triple1.
Example 20: Complete example of rdf:ID reifying a property element
([274]example20.rdf output [275]example20.nt)
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 in [276]RFC 2119 [277][KEYWORDS].
All use of string without further qualification refers to a Unicode[278][UNICODE]
character string; a sequence of characters represented by a code point in
Unicode. (Such as defined in [279][CHARMOD] in section [280]3.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
[281]RFC 3023 [282][RFC-3023] section 8.18.
Registration Note (Informative): For the state of the MIME type registration,
consult [283]IANA MIME Media Types [284][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 issues [285]rdfms-abouteach and [286]rdfms-abouteachprefix for further
information.
Note (Informative): The names List, first, rest and nil were added for issue
[287]rdfms-seq-representation. The names XMLLiteral and datatype were added to
support RDF datatyping. The name nodeID was added for issue
[288]rdfms-syntax-incomplete. See the [289]RDF Core Issues List for further
information.
The RDF namespace URI reference (or namespace name) is
http://www.w3.org/1999/02/22-rdf-syntax-ns# and is typically used in XML with the
prefix rdf although other prefix strings may be used. The RDF Vocabulary is
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 [290]·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 [291]RDF URI reference of the
concatenation of the [292]·RDF namespace URI reference· and name. For example,
rdf:type has the [293]RDF URI reference
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
5.2 Identifiers
The [294]RDF Graph ([295]RDF Concepts and Abstract Syntax Section 3) defines
three types of nodes and one type of predicate:
[296]RDF URI reference nodes and predicates
[297]RDF URI references ([298]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
[299]section 5.3 to give absolute [300]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 into [301]RDF URI references by
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 QName foo:bar would
correspond to the RDF URI reference http://example.org/somewhere/bar. Note
that this restricts which [302]RDF URI references can be made and the same
URI can be given in multiple ways.
The [303]rdf:ID values are transformed into [304]RDF URI references by
appending the attribute value to the result of appending "#" to the
in-scope base URI which is defined in [305]Section 5.3 Resolving URIs
Literal nodes (always object nodes)
[306]RDF literals ([307]RDF Concepts and Abstract Syntax 6.5) are either
[308]plain literals (ibid), or [309]typed literals (ibid). The latter
includes [310]XML literals (ibid section 5, XML Content within an RDF
graph).
Blank Node Identifiers
[311]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 called [312]blank node
identifiers and are used in RDF/XML as values of the rdf:nodeID attribute
with the syntax given in [313]Production nodeIdAttr. Blank node
identifiers in RDF/XML are scoped to the XML Information Set [314]document
information item.
If no blank node identifier is given explicitly as an rdf:nodeID attribute
value then one will need to be generated (using generated-blank-node-id,
see section [315]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 [316]XML Base [317][XML-BASE] which defines a [318]·base-uri·
accessor for each [319]·root event· and [320]·element event·. Relative URI
references are resolved into [321]RDF URI references according to the algorithm
specified in [322]XML Base [323][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 an [324]RDF URI reference. In RDF/XML, a
fragment identifier is transformed into a [325]RDF URI reference by appending the
fragment identifier to the in-scope base URI. The empty string is transformed
into an [326]RDF URI reference by substituting the in-scope base URI.
Test: Indicated by [327]test001.rdf and [328]test001.nt
Test: Indicated by [329]test004.rdf and [330]test004.nt
Test: Indicated by [331]test008.rdf and [332]test008.nt
Test: Indicated by [333]test013.rdf and [334]test013.nt
Test: Indicated by [335]test016.rdf and [336]test016.nt
An empty same document reference "" resolves against the URI part of the base
URI; any fragment part is ignored. See [337]Uniform Resource Identifiers (URI)
[338][URIS] section 4.2
Test: Indicated by [339]test013.rdf and [340]test013.nt
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.
Test: Indicated by [341]test011.rdf and [342]test011.nt
5.4 Constraints
constraint-id
Each application of production [343]idAttr matches an attribute. The pair
formed by the [344]·string-value· accessor of the matched attribute and
the [345]·base-uri· accessor of the matched attribute is unique within a
single RDF/XML document.
The syntax of the names must match the [346]rdf-id production.
Test: Indicated by [347]test014.rdf and [348]test014.nt
5.5 Conformance
Definition:
An RDF Document is a serialization of an [349]RDF Graph into a concrete
syntax.
Definition:
An RDF/XML Document is an [350]RDF Document written in the recommended XML
transfer syntax for RDF as defined in this document.
Conformance:
An [351]RDF/XML Document is a conforming 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 [352][XPATH]
[353]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
[354]Section 6.2 Information Set Mapping. The sequence these events form are
intended to be similar to the sequence of events produced by the [355][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 the [356]N-Triples language.
The model given here illustrates one way to create a representation of an
[357]RDF Graph from an RDF/XML document. It does not mandate any implementation
method -- any other method that results in a representation of the same [358]RDF
Graph may be used.
In particular:
* This specification permits any [359]representation of an RDF graph (see
[360][RDF-CONCEPTS]); in particular, it does not require the use of
[361]N-Triples.
* This specification does not require the use of [362][XPATH] or [363][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 to
[364]Namespaces in XML [365][XML-NS].
The Infoset requires support for [366]XML Base [367][XML-BASE]. RDF/XML uses the
information item property [base URI], discussed in [368]section 5.3
This specification requires an XML Information Set [369][INFOSET] which supports
at least the following information items and properties for RDF/XML:
[370]document information item
[document element], [children], [base URI]
[371]element information item
[local name], [namespace name], [children], [attributes], [parent], [base
URI]
[372]attribute information item
[local name], [namespace name], [normalized value]
[373]character information item
[character code]
There is no mapping of the following items to data model events:
[374]processing instruction information item
[375]unexpanded entity reference information item
[376]comment information item
[377]document type declaration information item
[378]unparsed entity information item
[379]notation information item
[380]namespace information item
Other information items and properties have no mapping to syntax data model
events.
Element information items with reserved XML Names (See [381]Name in [382]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 with xml
(case independent comparison).
All information items contained inside XML elements matching the
[383]parseTypeLiteralPropertyElt production form [384]XML literals and do not
follow this mapping. See [385]parseTypeLiteralPropertyElt for further
information.
This section is intended to satisfy the requirements for [386]Conformance in the
[387][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 [388]URI reference,
[389]blank node, [390]plain literal and [391]typed 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 a [392]document information item and 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 [393]element information item and 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 [394]·language· accessor is set to the
[normalized-value] property of the attribute information item.
All remaining reserved XML Names (See [395]Name in [396]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 with xml (case
independent comparison) are removed. Note that the [base URI] accessor is
computed by XML Base before any xml:base attribute information item is
deleted.
The remaining set of attribute information items are then used to
construct a new set of [397]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 escaping of the [399]·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 [400]·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 a [401]Root Event or an [402]Element
Event), which may be the empty string.
subject
Has no initial value. Takes a value that is an [403]Identifier 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 [404]attribute information item and 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 [405][XML] (if an attribute whose normalized value
is a zero-length string, then the string-value is also a zero-length
string).
URI
If [406]·namespace-name· is present, set to a string value of the
concatenation of the value of the [407]·namespace-name· accessor and the
value of the [408]·local-name· accessor. Otherwise if [409]·local-name· is
ID, about, resource, parseType or type, set to a string value of the
concatenation of the [410]·RDF namespace URI reference· and the value of
the [411]·local-name· accessor. Other non-namespaced [412]·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 [413][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 of [414]RDF URI references from XML attributes can
generate the same [415]RDF URI references from different XML attributes.
This can cause ambiguity in the grammar when matching attribute events
(such as when rdf: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 escaping of the [417]·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 consecutive [418]character information
items. Has the single accessor:
string-value
Set to the value of the string made from concatenating the [[419]character
code] property of each of the character information items.
6.1.6 URI Reference Event
An event for a [420]RDF URI references which has the following accessors:
identifier
Takes a string value used as an [421]RDF URI reference.
string-value
The value is the concatenation of ""
The escaping of the [423]·identifier· accessor value uses the
[424]N-Triples escapes for URI references as described in [425]3.3 URI
References.
These events are constructed by giving a value for the [426]·identifier·
accessor.
For further information on identifiers in the RDF graph, see [427]section 5.2.
6.1.7 Blank Node Identifier Event
An event for a [428]blank node identifier which has the following accessors:
identifier
Takes a string value.
string-value
The value is a function of the value of the [429]·identifier· accessor.
The value begins with "_:" and the entire value MUST match the
[430]N-Triples [431]nodeID production. The function MUST preserve distinct
blank node identity as discussed in in section [432]5.2 Identifiers.
These events are constructed by giving a value for the [433]·identifier·
accessor.
For further information on identifiers in the RDF graph, see [434]section 5.2.
6.1.8 Plain Literal Event
An event for a [435]plain literal which can have the following accessors:
literal-value
Takes a string value.
literal-language
Takes a string value used as a [436]language tag in an RDF plain literal.
string-value
The value is calculated from the other accessors as follows.
If [437]·literal-language· is the empty string then the value is the
concatenation of """ (1 double quote), the escaped value of the
[438]·literal-value· accessor and """ (1 double quote).
Otherwise the value is the concatenation of """ (1 double quote), the
escaped value of the [439]·literal-value· accessor ""@" (1 double quote
and a '@'), and the value of the [440]·literal-language· accessor.
The escaping of the [441]·literal-value· accessor value uses the
[442]N-Triples escapes for strings as described in [443]3.2 Strings for
escaping certain characters such as ".
These events are constructed by giving values for the [444]·literal-value· and
[445]·literal-language· accessors.
Interoperability Note (Informative): Literals beginning with a Unicode combining
character are allowed however they may cause interoperability problems. See
[446][CHARMOD] for further information.
6.1.9 Typed Literal Event
An event for a [447]typed literal which can have the following accessors:
literal-value
Takes a string value.
literal-datatype
Takes a string value used as an [448]RDF URI reference.
string-value
The value is the concatenation of the following in this order """ (1
double quote), the escaped value of the [449]·literal-value· accessor, """
(1 double quote), "^^".
The escaping of the [451]·literal-value· accessor value uses the
[452]N-Triples escapes for strings as described in [453]3.2 Strings for
escaping certain characters such as ". The escaping of the
[454]·literal-datatype· accessor value must use the [455]N-Triples escapes
for URI references as described in [456]3.3 URI References.
These events are constructed by giving values for the [457]·literal-value· and
[458]·literal-datatype· accessors.
Interoperability Note (Informative): Literals beginning with a Unicode combining
character are allowed however they may cause interoperability problems. See
[459][CHARMOD] for further information.
Implementation Note (Informative): In [460]XML Schema (part 1)
[461][XML-SCHEMA1], [462]white space normalization occurs 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 [463]element event
2. The value of the [464]children accessor recursively transformed, a possibly
empty ordered list of events.
3. An [465]end element event
6.3 Grammar Notation
The following notation is used to describe matching the sequence of data model
events as given in [466]Section 6 and 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
action...
[467]N-Triples
where the event-content is an expression matching event-types (as defined in
[468]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 in [469]N-Triples format.
The following sections describe the general notation used and that for event
matching and actions.
6.3.1 Grammar General Notation
CAPTION: Grammar General Notation.
Notation Meaning
event.accessor The value of an event accessor.
rdf:X A URI as defined in [470]section 5.1.
"ABC" A string of characters A, B, C in order.
6.3.2 Grammar Event Matching Notation
CAPTION: Grammar Event Matching Notation.
Notation Meaning
A == B Event accessor A matches expression B.
A != B A is not equal to B.
A | B | ... The A, B, ... terms are alternatives.
A - B The terms in A excluding all the 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 [471]Root Event with accessors.
start-element(acc1 == value1,
acc2 == value2, ...)
children
end-element() Match a sequence of [472]Element Event with accessors, a possibly
empty list of events as element content and an [473]End Element Event.
attribute(acc1 == value1,
acc2 == value2, ...) Match an [474]Attribute Event with accessors.
text() Match a [475]Text Event.
6.3.3 Grammar Action Notation
CAPTION: 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 string s as a relative URI
reference to the [476]·base-uri· accessor of e as defined in [477]Section 5.3
Resolving URIs. The resulting string represents an [478]RDF URI reference.
generated-blank-node-id() A string value for a new distinct generated [479]blank
node identifier as defined in [480]section 5.2 Identifiers.
event.accessor := value Sets an event accessor to the given value.
uri(identifier := value) Create a new [481]URI Reference Event.
bnodeid(identifier := value) Create a new [482]Blank Node Identifier Event. See
also section [483]5.2 Identifiers.
literal(literal-value := string,
literal-language := language, ...) Create a new [484]Plain Literal Event.
typed-literal(literal-value := string, ...) Create a new [485]Typed Literal
Event.
7 RDF/XML Grammar
7.1 Grammar summary
[486]7.2.2 [487]coreSyntaxTerms rdf:RDF | rdf:ID | rdf:about | rdf:parseType |
rdf:resource | rdf:nodeID | rdf:datatype
[488]7.2.3 [489]syntaxTerms [490]coreSyntaxTerms | rdf:Description | rdf:li
[491]7.2.4 [492]oldTerms rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID
[493]7.2.5 [494]nodeElementURIs [495]anyURI - ( [496]coreSyntaxTerms | rdf:li |
[497]oldTerms )
[498]7.2.6 [499]propertyElementURIs [500]anyURI - ( [501]coreSyntaxTerms |
rdf:Description | [502]oldTerms )
[503]7.2.7 [504]propertyAttributeURIs [505]anyURI - ( [506]coreSyntaxTerms |
rdf:Description | rdf:li | [507]oldTerms )
[508]7.2.8 [509]doc root([510]document-element == [511]RDF, [512]children ==
list([513]RDF))
[514]7.2.9 [515]RDF start-element([516]URI == rdf:RDF, [517]attributes == set())
[518]nodeElementList
end-element()
[519]7.2.10 [520]nodeElementList [521]ws* ([522]nodeElement [523]ws* )*
[524]7.2.11 [525]nodeElement start-element([526]URI == [527]nodeElementURIs
[528]attributes == set(([529]idAttr | [530]nodeIdAttr | [531]aboutAttr )?,
[532]propertyAttr*))
[533]propertyEltList
end-element()
[534]7.2.12 [535]ws A [536]text event matching white space defined by [537][XML]
definition White Space Rule [3] [538]S in section [539]Common Syntactic
Constructs
[540]7.2.13 [541]propertyEltList [542]ws* ([543]propertyElt [544]ws* ) *
[545]7.2.14 [546]propertyElt [547]resourcePropertyElt | [548]literalPropertyElt |
[549]parseTypeLiteralPropertyElt | [550]parseTypeResourcePropertyElt |
[551]parseTypeCollectionPropertyElt | [552]parseTypeOtherPropertyElt |
[553]emptyPropertyElt
[554]7.2.15 [555]resourcePropertyElt start-element([556]URI ==
[557]propertyElementURIs ), [558]attributes == set([559]idAttr?))
[560]ws* [561]nodeElement [562]ws*
end-element()
[563]7.2.16 [564]literalPropertyElt start-element([565]URI ==
[566]propertyElementURIs ), [567]attributes == set([568]idAttr?,
[569]datatypeAttr?))
[570]text()
end-element()
[571]7.2.17 [572]parseTypeLiteralPropertyElt start-element([573]URI ==
[574]propertyElementURIs ), [575]attributes == set([576]idAttr?,
[577]parseLiteral))
[578]literal
end-element()
[579]7.2.18 [580]parseTypeResourcePropertyElt start-element([581]URI ==
[582]propertyElementURIs ), [583]attributes == set([584]idAttr?,
[585]parseResource))
[586]propertyEltList
end-element()
[587]7.2.19 [588]parseTypeCollectionPropertyElt start-element([589]URI ==
[590]propertyElementURIs ), [591]attributes == set([592]idAttr?,
[593]parseCollection))
[594]nodeElementList
end-element()
[595]7.2.20 [596]parseTypeOtherPropertyElt start-element([597]URI ==
[598]propertyElementURIs ), [599]attributes == set([600]idAttr?,
[601]parseOther))
[602]propertyEltList
end-element()
[603]7.2.21 [604]emptyPropertyElt start-element([605]URI ==
[606]propertyElementURIs ), [607]attributes == set([608]idAttr?, (
[609]resourceAttr | [610]nodeIdAttr )?, [611]propertyAttr*))
end-element()
[612]7.2.22 [613]idAttr attribute([614]URI == rdf:ID, [615]string-value ==
[616]rdf-id)
[617]7.2.23 [618]nodeIdAttr attribute([619]URI == rdf:nodeID, [620]string-value
== [621]rdf-id)
[622]7.2.24 [623]aboutAttr attribute([624]URI == rdf:about, [625]string-value ==
[626]URI-reference)
[627]7.2.25 [628]propertyAttr attribute([629]URI == [630]propertyAttributeURIs,
[631]string-value == [632]anyString)
[633]7.2.26 [634]resourceAttr attribute([635]URI == rdf:resource,
[636]string-value == [637]URI-reference)
[638]7.2.27 [639]datatypeAttr attribute([640]URI == rdf:datatype,
[641]string-value == [642]URI-reference)
[643]7.2.28 [644]parseLiteral attribute([645]URI == rdf:parseType,
[646]string-value == "Literal")
[647]7.2.29 [648]parseResource attribute([649]URI == rdf:parseType,
[650]string-value == "Resource")
[651]7.2.30 [652]parseCollection attribute([653]URI == rdf:parseType,
[654]string-value == "Collection")
[655]7.2.31 [656]parseOther attribute([657]URI == rdf:parseType,
[658]string-value == [659]anyString - ("Resource" | "Literal" | "Collection") )
[660]7.2.32 [661]URI-reference An [662]RDF URI reference.
[663]7.2.33 [664]literal Any XML element content that is allowed according to
[665][XML] definition Content of Elements Rule [43] [666]content. in section
[667]3.1 Start-Tags, End-Tags, and Empty-Element Tags
[668]7.2.34 [669]rdf-id An attribute [670]·string-value· matching any legal
[671][XML-NS] token [672]NCName
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 [673]RDF MIME type object, or by some other means) then the
grammar may start with production [674]doc or production [675]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
[676]Element Event [677]RDF (only when an element is legal at that point in the
XML) or at production [678]nodeElementList (only when element content is legal,
since this is a list of elements). For such embedded RDF/XML, the [679]·base-uri·
value on the outermost element must be initialized from the containing XML since
no [680]Root 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 in [681]section 5.1 which
are used in RDF/XML.
7.2.3 Production syntaxTerms
[682]coreSyntaxTerms | rdf:Description | rdf:li
All the syntax terms from the RDF vocabulary in [683]section 5.1 which are used
in RDF/XML.
7.2.4 Production oldTerms
rdf:aboutEach | rdf:aboutEachPrefix | rdf:bagID
These are the names from the [684]RDF vocabulary that have been withdrawn from
the language. See the resolutions of Issue [685]rdfms-aboutEach-on-object, Issue
[686]rdfms-abouteachprefix and Last Call Issue [687]timbl-01 for further
information.
Error Test: Indicated by [688]error001.rdf and [689]error002.rdf
7.2.5 Production nodeElementURIs
[690]anyURI - ( [691]coreSyntaxTerms | rdf:li | [692]oldTerms )
The [693]RDF URI references that are allowed on node elements.
7.2.6 Production propertyElementURIs
[694]anyURI - ( [695]coreSyntaxTerms | rdf:Description | [696]oldTerms )
The URIs that are allowed on property elements.
7.2.7 Production propertyAttributeURIs
[697]anyURI - ( [698]coreSyntaxTerms | rdf:Description | rdf:li | [699]oldTerms )
The [700]RDF URI references that are allowed on property attributes.
7.2.8 Production doc
root([701]document-element == [702]RDF,
[703]children == list([704]RDF))
7.2.9 Production RDF
start-element([705]URI == rdf:RDF,
[706]attributes == set())
[707]nodeElementList
end-element()
7.2.10 Production nodeElementList
[708]ws* ([709]nodeElement [710]ws* )*
7.2.11 Production nodeElement
start-element([711]URI == [712]nodeElementURIs
[713]attributes == set(([714]idAttr | [715]nodeIdAttr | [716]aboutAttr )?,
[717]propertyAttr*))
[718]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.[719]URI == rdf:ID, then e.[720]subject :=
uri([721]identifier := resolve(e, concat("#", a.[722]string-value))).
* If there is an attribute a with a.[723]URI == rdf:nodeID, then e.[724]subject
:= bnodeid([725]identifier:=a.[726]string-value).
* If there is an attribute a with a.[727]URI == rdf:about then e.[728]subject
:= uri([729]identifier := resolve(e, a.[730]string-value)).
If e.[731]subject is empty, then e.[732]subject := bnodeid([733]identifier :=
generated-blank-node-id()).
The following can then be performed in any order:
* If e.[734]URI != rdf:Description then the following statement is added to the
graph:
e.[735]subject.[736]string-value
e.[737]URI-string-value .
* If there is an attribute a in [738]propertyAttr with a.[739]URI == rdf:type
then u:=uri(identifier:=resolve(a.[740]string-value)) and the following tiple
is added to the graph:
e.[741]subject.[742]string-value
u.[743]string-value .
* For each attribute a matching [744]propertyAttr (and not rdf:type), the
Unicode string a.[745]string-value SHOULD be in Normal Form C[746][NFC], o :=
literal([747]literal-value := a.[748]string-value, [749]literal-language :=
e.[750]language) and the following statement is added to the graph:
e.[751]subject.[752]string-value a.[753]URI-string-value o.[754]string-value
.
* Handle the [755]propertyEltList children events in document order.
7.2.12 Production ws
A [756]text event matching white space defined by [757][XML] definition White
Space Rule [3] [758]S in section [759]Common Syntactic Constructs
7.2.13 Production propertyEltList
[760]ws* ([761]propertyElt [762]ws* ) *
7.2.14 Production propertyElt
[763]resourcePropertyElt | [764]literalPropertyElt |
[765]parseTypeLiteralPropertyElt | [766]parseTypeResourcePropertyElt |
[767]parseTypeCollectionPropertyElt | [768]parseTypeOtherPropertyElt |
[769]emptyPropertyElt
If element e has e.[770]URI = rdf:li then apply the list expansion rules on
element e.parent in [771]section 7.4 to give a new URI u and e.[772]URI := u.
The action of this production must be done before the actions of any sub-matches
([773]resourcePropertyElt ... [774]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([775]URI == [776]propertyElementURIs ),
[777]attributes == set([778]idAttr?))
[779]ws* [780]nodeElement [781]ws*
end-element()
For element e, and the single contained nodeElement n, first n must be processed
using production [782]nodeElement. Then the following statement is added to the
graph:
e.parent.[783]subject.[784]string-value e.[785]URI-string-value
n.[786]subject.[787]string-value .
If the rdf:ID attribute a is given, the above statement is reified with i :=
uri([788]identifier := resolve(e, concat("#", a.[789]string-value))) using the
reification rules in [790]section 7.3 and e.[791]subject := i
7.2.16 Production literalPropertyElt
start-element([792]URI == [793]propertyElementURIs ),
[794]attributes == set([795]idAttr?, [796]datatypeAttr?))
[797]text()
end-element()
Note that the empty literal case is defined in production [798]emptyPropertyElt.
For element e, and the text event t. The Unicode string t.[799]string-value
SHOULD be in Normal Form C[800][NFC]. If the rdf:datatype attribute d is given
then o := typed-literal([801]literal-value := t.[802]string-value,
[803]literal-datatype := d.[804]string-value) otherwise o :=
literal([805]literal-value := t.[806]string-value, [807]literal-language :=
e.[808]language) and the following statement is added to the graph:
e.parent.[809]subject.[810]string-value e.[811]URI-string-value
o.[812]string-value .
If the rdf:ID attribute a is given, the above statement is reified with i :=
uri([813]identifier := resolve(e, concat("#", a.[814]string-value))) using the
reification rules in [815]section 7.3 and e.[816]subject := i.
7.2.17 Production parseTypeLiteralPropertyElt
start-element([817]URI == [818]propertyElementURIs ),
[819]attributes == set([820]idAttr?, [821]parseLiteral))
[822]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 [823]6
Syntax Data Model) but remains an XML Infoset of XML Information items.
l is transformed into the lexical form of an [824]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.
1. Use l to construct an XPath[825][XPATH] [826]node-set (a [827]document
subset)
2. Apply [828]Exclusive XML Canonicalization [[829]XML-XC14N]) with comments and
with empty [830]InclusiveNamespaces PrefixList to 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[831][NFC]
Then o := typed-literal([832]literal-value := x, [833]literal-datatype :=
http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral ) and the following
statement is added to the graph:
e.parent.[834]subject.[835]string-value e.[836]URI-string-value
o.[837]string-value .
Test: Empty literal case indicated by [838]test009.rdf and [839]test009.nt
If the rdf:ID attribute a is given, the above statement is reified with i :=
uri([840]identifier := resolve(e, concat("#", a.[841]string-value))) using the
reification rules in [842]section 7.3 and e.[843]subject := i.
7.2.18 Production parseTypeResourcePropertyElt
start-element([844]URI == [845]propertyElementURIs ),
[846]attributes == set([847]idAttr?, [848]parseResource))
[849]propertyEltList
end-element()
For element e with possibly empty element content c.
n := bnodeid([850]identifier := generated-blank-node-id()).
Add the following statement to the graph:
e.parent.[851]subject.[852]string-value e.[853]URI-string-value
n.[854]string-value .
Test: Indicated by [855]test004.rdf and [856]test004.nt
If the rdf:ID attribute a is given, the statement above is reified with i :=
uri([857]identifier := resolve(e, concat("#", a.[858]string-value))) using the
reification rules in [859]section 7.3 and e.[860]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([861]URI := rdf:Description,
[862]subject := n,
[863]attributes := set())
c
end-element()
Then process the resulting sequence using production [864]nodeElement.
7.2.19 Production parseTypeCollectionPropertyElt
start-element([865]URI == [866]propertyElementURIs ),
[867]attributes == set([868]idAttr?, [869]parseCollection))
[870]nodeElementList
end-element()
For element event e with possibly empty [871]nodeElementList l. Set s:=list().
For each element event f in l, n := bnodeid([872]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.[873]subject.[874]string-value e.[875]URI-string-value
n.[876]string-value .
otherwise the following statement is added to the graph:
e.parent.[877]subject.[878]string-value e.[879]URI-string-value
.
If the rdf:ID attribute a is given, either of the the above statements is reified
with i := uri([880]identifier := resolve(e, concat("#", a.[881]string-value)))
using the reification rules in [882]section 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.[883]string-value
f.[884]string-value .
For each consecutive and overlapping pair of events (n, o) in s, the following
statement is added to the graph:
n.[885]string-value
o.[886]string-value .
If s is not empty, n is the last event identifier in s, the following statement
is added to the graph:
n.[887]string-value
.
7.2.20 Production parseTypeOtherPropertyElt
start-element([888]URI == [889]propertyElementURIs ),
[890]attributes == set([891]idAttr?, [892]parseOther))
[893]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 [894]parseTypeLiteralPropertyElt was matched.
No extra triples are generated for other rdf:parseType values.
7.2.21 Production emptyPropertyElt
start-element([895]URI == [896]propertyElementURIs ),
[897]attributes == set([898]idAttr?, ( [899]resourceAttr | [900]nodeIdAttr
)?, [901]propertyAttr*))
end-element()
* If there are no attributes or only the optional rdf:ID attribute i then o :=
literal([902]literal-value:="", [903]literal-language := e.[904]language) and
the following statement is added to the graph:
e.parent.[905]subject.[906]string-value e.[907]URI-string-value
o.[908]string-value .
and then if i is given, the above statement is reified with
uri([909]identifier := resolve(e, concat("#", i.[910]string-value))) using
the reification rules in [911]section 7.3.
Test: Indicated by [912]test002.rdf and [913]test002.nt
Test: Indicated by [914]test005.rdf and [915]test005.nt
* Otherwise
+ If rdf:resource attribute i is present, then r := uri([916]identifier :=
resolve(e, i.[917]string-value))
+ If rdf:nodeID attribute i is present, then r := bnodeid([918]identifier
:= i.[919]string-value)
+ If neither, r := bnodeid([920]identifier := generated-blank-node-id())
The following are done in any order:
+ For all [921]propertyAttr attributes a (in any order)
o If a.[922]URI == rdf:type then
u:=uri(identifier:=resolve(a.[923]string-value)) and the following
triple is added to the graph:
r.[924]string-value
u.[925]string-value .
o Otherwise Unicode string a.[926]string-value SHOULD be in Normal
Form C[927][NFC], o := literal([928]literal-value :=
a.[929]string-value, [930]literal-language := e.[931]language) and
the following statement is added to the graph:
r.[932]string-value a.[933]URI-string-value o.[934]string-value .
Test: Indicated by [935]test013.rdf and [936]test013.nt
Test: Indicated by [937]test014.rdf and [938]test014.nt
+ Add the following statement to the graph:
e.parent.[939]subject.[940]string-value e.[941]URI-string-value
r.[942]string-value .
and then if rdf:ID attribute i is given, the above statement is reified
with uri([943]identifier := resolve(e, concat("#",
i.[944]string-value))) using the reification rules in [945]section 7.3.
7.2.22 Production idAttr
attribute([946]URI == rdf:ID,
[947]string-value == [948]rdf-id)
Constraint:: [949]constraint-id applies to the values of rdf:ID attributes
7.2.23 Production nodeIdAttr
attribute([950]URI == rdf:nodeID,
[951]string-value == [952]rdf-id)
7.2.24 Production aboutAttr
attribute([953]URI == rdf:about,
[954]string-value == [955]URI-reference)
7.2.25 Production propertyAttr
attribute([956]URI == [957]propertyAttributeURIs,
[958]string-value == [959]anyString)
7.2.26 Production resourceAttr
attribute([960]URI == rdf:resource,
[961]string-value == [962]URI-reference)
7.2.27 Production datatypeAttr
attribute([963]URI == rdf:datatype,
[964]string-value == [965]URI-reference)
7.2.28 Production parseLiteral
attribute([966]URI == rdf:parseType,
[967]string-value == "Literal")
7.2.29 Production parseResource
attribute([968]URI == rdf:parseType,
[969]string-value == "Resource")
7.2.30 Production parseCollection
attribute([970]URI == rdf:parseType,
[971]string-value == "Collection")
7.2.31 Production parseOther
attribute([972]URI == rdf:parseType,
[973]string-value == [974]anyString - ("Resource" | "Literal" | "Collection")
)
7.2.32 Production URI-reference
An [975]RDF URI reference.
7.2.33 Production literal
Any XML element content that is allowed according to [976][XML] definition
Content of Elements Rule [43] [977]content. in section [978]3.1 Start-Tags,
End-Tags, and Empty-Element Tags
The string-value for the resulting event is discussed in [979]section 7.2.17.
7.2.34 Production rdf-id
An attribute [980]·string-value· matching any legal [981][XML-NS] token
[982]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.[983]string-value s .
r.[984]string-value p .
r.[985]string-value o .
r.[986]string-value
.
7.4 List Expansion Rules
For the given element e, create a new [987]RDF URI reference u :=
concat("http://www.w3.org/1999/02/22-rdf-syntax-ns#_", e.[988]li-counter),
increment the e.[989]li-counter property by 1 and return u.
8 Serializing an RDF Graph to RDF/XML
There are some [990]RDF Graphs as defined in [991]RDF Concepts and Abstract
Syntax that 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 ([992]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-[993]NCName character, ensuring that the first character of
the name is a [994]Letter or '_'. If the URI ends in a non-[995]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 the [996]syntaxTerms
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 in [997]RDF in HTML: Approaches [998][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
element in the element of the HTML/HTML to point at a separate
RDF/XML document. This approach has been used for several years by the
[999]Dublin Core Metadata Initiative (DCMI) on its Web site.
To use this technique, the 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 for RDF/XML, see [1000]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 [1001]RFC 2731 -- Encoding Dublin Core Metadata in
HTML[1002][RFC-2731] however rel="alternate" may also be appropriate. See
[1003]HTML 4.01 link types, [1004]XHTML Modularization -- LinkTypes and
[1005]XHTML 2.0 -- LinkTypes for further information on the values that may be
appropriate for the different versions of HTML.
[1006]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
([1007]example21.html linking to [1008]example21.rdf)
My 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 [1009]Section 21 Metadata of the [1010]Scalable Vector Graphics (SVG) 1.0
Specification [1011][SVG] and [1012]Section 21 Metadata of the [1013]Scalable
Vector Graphics (SVG) 1.1 Specification [1014][SVG11].
This document contains two example graphs in SVG with such embedded RDF/XML
inside the metadata element: [1015]figure 1 and [1016]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).
12 References
Normative References
[RDF-MS]
[1017]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 [1018]latest version of RDF M&S is available at
http://www.w3.org/TR/REC-rdf-syntax.
[XML]
[1019]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. [1020]latest version of XML is
available at http://www.w3.org/TR/REC-xml.
[XML-NS]
[1021]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 [1022]latest version
of Namespaces in XML is available at http://www.w3.org/TR/REC-xml-names.
[INFOSET]
[1023]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 [1024]latest
version of XML Information set is available at
http://www.w3.org/TR/xml-infoset.
[URIS]
[1025]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]
[1026]Resource Description Framework (RDF): Concepts and Abstract Syntax,
Klyne G., Carroll J. (Editors), W3C Recommendation, 10 February 2004.
[1027]This version is http://www.w3.org/TR/2004/REC-rdf-primer-20040210/.
The [1028]latest version is http://www.w3.org/TR/rdf-concepts/.
[RDF-TESTS]
[1029]RDF Test Cases, Grant J., Beckett D. (Editors), W3C Recommendation,
10 February 2004. [1030]This version is
http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/. The [1031]latest
version is http://www.w3.org/TR/rdf-testcases/.
[KEYWORDS]
[1032]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]
[1033]RFC 3023 -- 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]
[1034]MIME Media Types, The Internet Assigned Numbers Authority (IANA).
This document is http://www.iana.org/assignments/media-types/ . The
[1035]registration for application/rdf+xml is archived at
http://www.w3.org/2001/sw/RDFCore/mediatype-registration .
[XML-BASE]
[1036]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 [1037]latest version
of XML Base is at http://www.w3.org/TR/xmlbase.
[XML-XC14N]
[1038]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 [1039]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
[1040]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]
[1041]Unicode Normalization Forms, Unicode Standard Annex #15, Mark Davis,
Martin Dürst. (See [1042]http://www.unicode.org/unicode/reports/tr15/ for
the latest version).
Informational References
[CHARMOD]
[1043]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
[1044]latest version of the Character Model is at
http://www.w3.org/TR/charmod.
[RDF-SEMANTICS]
[1045]RDF Semantics, Hayes P. (Editor), W3C Recommendation, 10 February
2004. [1046]This version is
http://www.w3.org/TR/2004/REC-rdf-mt-20040210/. The [1047]latest version
is http://www.w3.org/TR/rdf-mt/.
[RDF-PRIMER]
[1048]RDF Primer, F. Manola, E. Miller, Editors, W3C Recommendation, 10
February 2004. [1049]This version is
http://www.w3.org/TR/2004/REC-rdf-primer-20040210/. The [1050]latest
version is at http://www.w3.org/TR/rdf-primer/.
[RDF-VOCABULARY]
[1051]RDF Vocabulary Description Language 1.0: RDF Schema, Brickley D.,
Guha R.V. (Editors), W3C Recommendation, 10 February 2004. [1052]This
version is http://www.w3.org/TR/2004/REC-rdf-schema-20040210/. The
[1053]latest version is http://www.w3.org/TR/rdf-schema/.
[STRIPEDRDF]
[1054]RDF: Understanding the Striped RDF/XML Syntax, D. Brickley, W3C,
2001. This document is http://www.w3.org/2001/10/stripes/.
[SVG]
[1055]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 [1056]latest version of
SVG is at http://www.w3.org/TR/SVG.
[SVG11]
[1057]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
[1058]latest version of SVG is at http://www.w3.org/TR/SVG11.
[XPATH]
[1059]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 [1060]latest
version of XPath is at http://www.w3.org/TR/xpath.
[SAX2]
[1061]SAX Simple API for XML, version 2, D. Megginson, SourceForge, 5 May
2000. This document is http://sax.sourceforge.net/.
[UNPARSING]
[1062]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]
[1063]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
[1064]latest version of the RELAX NG Specification is at
http://www.oasis-open.org/committees/relax-ng/spec.html.
[RELAXNG-COMPACT]
[1065]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]
[1066]RDF in HTML: Approaches, Sean B. Palmer, 2002
[RFC-2731]
[1067]RFC 2731 -- Encoding Dublin Core Metadata in HTML, John Kunze, DCMI,
December 1999.
[XML-SCHEMA1]
[1068]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 [1069]latest
version of XML Schema Part 1: Structures is at
http://www.w3.org/TR/xmlschema-1.
[XML-SCHEMA2]
[1070]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 [1071]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 [1072]RELAX NG XML version. These formats are
described in [1073]RELAX NG ([1074][RELAXNG]) and [1075]RELAX NG Compact
([1076][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.
[1077]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:node
ID | 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*, propertyEltL
ist
}
# 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 [1078]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 [1079]Example 8 in section [1080]2.7 after the
[1081]comment by Benjamin Nowack
No property attributes on rdf:parseType="Resource"
[1082]2.5 Update to reflect the syntax definition that property attributes
cannot be used with rdf:parseType="Resource" as pointed out by
[1083]comment by Sabadello 2003-10-30
URI Encoding
[1084]6.1.6, [1085]6.1.8, [1086]6.1.9 after [1087]proposal by Jeremy
Carroll
[1088]6.1.2, [1089]6.1.4 Added element/attribute URI-string-value
accessors
[1090]7.2.11, [1091]7.2.21 Added use of new uri event for the rdf:type
cases
[1092]7.2.11 ( and ), [1093]7.2.15 () [1094]7.2.16
() [1095]7.2.17 () [1096]7.2.18 () [1097]7.2.19
( twice) [1098]7.2.21 ( twice, once) changed from
X.URI to X.URI-string-value (anywhere "" appeared in the grammar
action without a hardcoded URI reference)
[1099]7.2.32 Replace action wording with "An RDF URI reference"
All changed as outlined in [1100]proposal 2003-10-06 after [1101]comment
by Patel-Schneider 2003-10-29
Appendix B.3: Issues requiring no document revisions
None
____________________________________________________________________________
[1102]RDF/XML Metadata
References
Visible links:
1. https://www.w3.org/
2. https://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/
3. https://www.w3.org/TR/rdf10-xml/
4. https://www.w3.org/TR/2003/PR-rdf-syntax-grammar-20031215/
5. http://purl.org/net/dajobe/
6. http://www-uk.hpl.hp.com/people/bwm/
7. https://www.w3.org/2001/sw/RDFCore/errata#rdf-syntax-grammar
8. https://www.w3.org/2001/sw/RDFCore/translation/rdf-syntax-grammar
9. https://www.w3.org/Consortium/Legal/ipr-notice#Copyright
10. https://www.w3.org/
11. http://www.csail.mit.edu/
12. http://www.ercim.org/
13. http://www.keio.ac.jp/
14. https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer
15. https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks
16. https://www.w3.org/Consortium/Legal/copyright-documents
17. https://www.w3.org/Consortium/Legal/copyright-software
18. https://www.w3.org/TR/2000/REC-xml-20001006
19. https://www.w3.org/TR/1999/REC-xml-names-19990114/
20. https://www.w3.org/TR/2001/REC-xml-infoset-20011024/
21. https://www.w3.org/TR/2001/REC-xmlbase-20010627/
22. https://www.w3.org/TR/REC-rdf-syntax/#section-Infoset-Grammar
23. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph
24. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
25. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
26. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/
27. https://www.w3.org/2003/06/Process-20030618/tr.html#RecsW3C
28. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Introduction
29. https://www.w3.org/TR/2004/REC-rdf-primer-20040210/
30. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
31. https://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/
32. https://www.w3.org/TR/2004/REC-rdf-mt-20040210/
33. https://www.w3.org/TR/2004/REC-rdf-schema-20040210/
34. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/
35. https://www.w3.org/TR/1999/REC-rdf-syntax-19990222/
36. https://www.w3.org/TR/2000/CR-rdf-schema-20000327/
37. https://www.w3.org/2001/sw/RDFCore/
38. https://www.w3.org/2001/sw/
39. https://www.w3.org/2001/sw/Activity
40. https://www.w3.org/2002/11/swv2/charters/RDFCoreWGCharter
41. https://www.w3.org/TR/2003/PR-rdf-syntax-grammar-20031215/
42. https://www.w3.org/TR/REC-rdf-syntax/#changes
43. mailto:www-rdf-comments@w3.org
44. http://lists.w3.org/Archives/Public/www-rdf-comments/
45. mailto:www-rdf-interest@w3.org
46. http://lists.w3.org/Archives/Public/www-rdf-interest/
47. https://www.w3.org/2001/sw/RDFCore/impls
48. https://www.w3.org/2001/sw/RDFCore/ipr-statements
49. https://www.w3.org/TR/
50. https://www.w3.org/TR/REC-rdf-syntax/#section-Introduction
51. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax
52. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-intro
53. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-node-property-elements
54. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-multiple-property-elements
55. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-empty-property-elements
56. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-property-attributes
57. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-complete-document
58. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-languages
59. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-XML-literals
60. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-datatyped-literals
61. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-blank-nodes
62. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-parsetype-resource
63. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-property-attributes-on-property-element
64. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-typed-nodes
65. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-ID-xml-base
66. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-list-elements
67. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-parsetype-Collection
68. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-reifying
69. https://www.w3.org/TR/REC-rdf-syntax/#section-Terminology
70. https://www.w3.org/TR/REC-rdf-syntax/#section-MIME-Type
71. https://www.w3.org/TR/REC-rdf-syntax/#section-Global
72. https://www.w3.org/TR/REC-rdf-syntax/#section-Namespace
73. https://www.w3.org/TR/REC-rdf-syntax/#section-Identifiers
74. https://www.w3.org/TR/REC-rdf-syntax/#section-baseURIs
75. https://www.w3.org/TR/REC-rdf-syntax/#section-constraints
76. https://www.w3.org/TR/REC-rdf-syntax/#section-conformance
77. https://www.w3.org/TR/REC-rdf-syntax/#section-Data-Model
78. https://www.w3.org/TR/REC-rdf-syntax/#section-Nodes
79. https://www.w3.org/TR/REC-rdf-syntax/#section-Infoset-Mapping
80. https://www.w3.org/TR/REC-rdf-syntax/#section-Infoset-Grammar-Notation
81. https://www.w3.org/TR/REC-rdf-syntax/#section-Infoset-Grammar
82. https://www.w3.org/TR/REC-rdf-syntax/#section-grammar-summary
83. https://www.w3.org/TR/REC-rdf-syntax/#section-grammar-productions
84. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
85. https://www.w3.org/TR/REC-rdf-syntax/#section-List-Expand
86. https://www.w3.org/TR/REC-rdf-syntax/#section-Serialising
87. https://www.w3.org/TR/REC-rdf-syntax/#section-rdf-in-HTML
88. https://www.w3.org/TR/REC-rdf-syntax/#section-rdf-in-SVG
89. https://www.w3.org/TR/REC-rdf-syntax/#section-Acknowledgments
90. https://www.w3.org/TR/REC-rdf-syntax/#section-References
91. https://www.w3.org/TR/REC-rdf-syntax/#section-Schemas
92. https://www.w3.org/TR/REC-rdf-syntax/#section-RELAXNG-Schema
93. https://www.w3.org/TR/REC-rdf-syntax/#section-Changes
94. https://www.w3.org/TR/2000/REC-xml-20001006
95. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml
96. https://www.w3.org/TR/1999/REC-rdf-syntax-19990222/
97. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdfms
98. https://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#grammar
99. https://www.w3.org/TR/2001/REC-xml-infoset-20011024/
100. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-infoset
101. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
102. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/
103. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-tests
104. https://www.w3.org/TR/2004/REC-rdf-mt-20040210/
105. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-semantics
106. https://www.w3.org/TR/2004/REC-rdf-primer-20040210/
107. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-primer
108. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
109. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-concepts
110. https://www.w3.org/TR/2004/REC-rdf-mt-20040210/
111. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-semantics
112. https://www.w3.org/TR/2004/REC-rdf-schema-20040210/
113. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-vocabulary
114. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/
115. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-tests
116. https://www.w3.org/2001/10/stripes/
117. https://www.w3.org/TR/REC-rdf-syntax/#ref-stripedrdf
118. https://www.w3.org/TR/REC-rdf-syntax/#section-Data-Model
119. https://www.w3.org/TR/REC-rdf-syntax/#section-Infoset-Grammar
120. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
121. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-concepts
122. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-data-model
123. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-syntax
124. https://www.w3.org/TR/2004/REC-rdf-mt-20040210/
125. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-semantics
126. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-node
127. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-triple
128. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
129. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-literal
130. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node
131. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
132. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
133. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
134. https://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-QName
135. https://www.w3.org/TR/1999/REC-xml-names-19990114/
136. https://www.w3.org/TR/REC-rdf-syntax/#ref-namespaces
137. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
138. https://www.w3.org/TR/1999/REC-xml-names-19990114/#dt-NSName
139. https://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-LocalPart
140. https://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-Prefix
141. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
142. https://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-LocalPart
143. https://www.w3.org/TR/1999/REC-xml-names-19990114/#dt-NSName
144. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
145. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
146. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-literal
147. https://www.w3.org/TR/REC-rdf-syntax/#example7
148. https://www.w3.org/TR/REC-rdf-syntax/figure1.svg
149. https://www.w3.org/TR/REC-rdf-syntax/#figure1
150. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
151. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
152. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-plain-literal
153. https://www.w3.org/TR/REC-rdf-syntax/#figure2
154. https://www.w3.org/TR/REC-rdf-syntax/figure2.svg
155. https://www.w3.org/TR/REC-rdf-syntax/#figure2
156. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
157. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
158. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
159. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
160. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
161. https://www.w3.org/TR/REC-rdf-syntax/#figure2
162. https://www.w3.org/TR/REC-rdf-syntax/#example1
163. https://www.w3.org/TR/REC-rdf-syntax/#figure2
164. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
165. https://www.w3.org/TR/REC-rdf-syntax/#example2
166. https://www.w3.org/TR/REC-rdf-syntax/#figure1
167. https://www.w3.org/TR/REC-rdf-syntax/#example2
168. https://www.w3.org/TR/REC-rdf-syntax/#example3
169. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-blank-nodes
170. https://www.w3.org/TR/REC-rdf-syntax/#example3
171. https://www.w3.org/TR/REC-rdf-syntax/#example4
172. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
173. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
174. https://www.w3.org/TR/REC-rdf-syntax/#example5
175. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-languages
176. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
177. https://www.w3.org/TR/REC-rdf-syntax/#example5
178. https://www.w3.org/TR/REC-rdf-syntax/#example6
179. https://www.w3.org/TR/REC-rdf-syntax/#example4
180. https://www.w3.org/TR/REC-rdf-syntax/#example6
181. https://www.w3.org/TR/REC-rdf-syntax/#figure1
182. https://www.w3.org/TR/REC-rdf-syntax/#example7
183. https://www.w3.org/TR/REC-rdf-syntax/example07.rdf
184. https://www.w3.org/TR/REC-rdf-syntax/example07.nt
185. https://www.w3.org/TR/REC-rdf-syntax/#example7
186. https://www.w3.org/TR/REC-xml#sec-lang-tag
187. https://www.w3.org/TR/2000/REC-xml-20001006
188. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml
189. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-datatyped-literals
190. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-XML-literals
191. https://www.w3.org/TR/REC-rdf-syntax/#example8
192. https://www.w3.org/TR/REC-rdf-syntax/example08.rdf
193. https://www.w3.org/TR/REC-rdf-syntax/example08.nt
194. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral
195. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-concepts
196. https://www.w3.org/TR/REC-rdf-syntax/#example9
197. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
198. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
199. https://www.w3.org/TR/REC-rdf-syntax/example09.rdf
200. https://www.w3.org/TR/REC-rdf-syntax/example09.nt
201. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-typed-literal
202. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
203. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
204. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-typed-literal
205. https://www.w3.org/TR/REC-rdf-syntax/#example10
206. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
207. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
208. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-typed-literal
209. https://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
210. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-schema2
211. https://www.w3.org/TR/REC-rdf-syntax/example10.rdf
212. https://www.w3.org/TR/REC-rdf-syntax/example10.nt
213. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node
214. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
215. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node
216. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
217. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node
218. https://www.w3.org/TR/xml-infoset/#infoitem.document
219. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
220. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
221. https://www.w3.org/TR/REC-rdf-syntax/#example7
222. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
223. https://www.w3.org/TR/REC-rdf-syntax/#example11
224. https://www.w3.org/TR/REC-rdf-syntax/example11.rdf
225. https://www.w3.org/TR/REC-rdf-syntax/example11.nt
226. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node
227. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
228. https://www.w3.org/TR/REC-rdf-syntax/#example7
229. https://www.w3.org/TR/REC-rdf-syntax/#example12
230. https://www.w3.org/TR/REC-rdf-syntax/example12.rdf
231. https://www.w3.org/TR/REC-rdf-syntax/example12.nt
232. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
233. https://www.w3.org/TR/REC-rdf-syntax/#example5
234. https://www.w3.org/TR/REC-rdf-syntax/#example13
235. https://www.w3.org/TR/REC-rdf-syntax/example13.rdf
236. https://www.w3.org/TR/REC-rdf-syntax/example13.nt
237. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
238. https://www.w3.org/TR/REC-rdf-syntax/#section-Namespace
239. https://www.w3.org/TR/REC-rdf-syntax/#example14
240. https://www.w3.org/TR/REC-rdf-syntax/#example15
241. https://www.w3.org/TR/REC-rdf-syntax/example14.rdf
242. https://www.w3.org/TR/REC-rdf-syntax/example14.nt
243. https://www.w3.org/TR/REC-rdf-syntax/example15.rdf
244. https://www.w3.org/TR/REC-rdf-syntax/example15.nt
245. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
246. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
247. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
248. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
249. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
250. https://www.w3.org/TR/REC-rdf-syntax/#example16
251. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
252. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
253. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
254. https://www.w3.org/TR/REC-rdf-syntax/example16.rdf
255. https://www.w3.org/TR/REC-rdf-syntax/example16.nt
256. https://www.w3.org/TR/REC-rdf-syntax/#example17
257. https://www.w3.org/TR/REC-rdf-syntax/#section-List-Expand
258. https://www.w3.org/TR/REC-rdf-syntax/#example17
259. https://www.w3.org/TR/REC-rdf-syntax/#example18
260. https://www.w3.org/TR/REC-rdf-syntax/example17.rdf
261. https://www.w3.org/TR/REC-rdf-syntax/example17.nt
262. https://www.w3.org/TR/REC-rdf-syntax/example18.rdf
263. https://www.w3.org/TR/REC-rdf-syntax/example18.nt
264. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeCollectionPropertyElt
265. https://www.w3.org/TR/REC-rdf-syntax/#example19
266. https://www.w3.org/TR/REC-rdf-syntax/example19.rdf
267. https://www.w3.org/TR/REC-rdf-syntax/example19.nt
268. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
269. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
270. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
271. https://www.w3.org/TR/REC-rdf-syntax/#constraint-id
272. https://www.w3.org/TR/REC-rdf-syntax/#example20
273. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
274. https://www.w3.org/TR/REC-rdf-syntax/example20.rdf
275. https://www.w3.org/TR/REC-rdf-syntax/example20.nt
276. http://www.ietf.org/rfc/rfc2119.txt
277. https://www.w3.org/TR/REC-rdf-syntax/#ref-keywords
278. https://www.w3.org/TR/REC-rdf-syntax/#ref-unicode
279. https://www.w3.org/TR/REC-rdf-syntax/#ref-charmod
280. https://www.w3.org/TR/2003/WD-charmod-20030822/#sec-Strings
281. http://www.ietf.org/rfc/rfc3023.txt
282. https://www.w3.org/TR/REC-rdf-syntax/#ref-rfc3023
283. http://www.iana.org/assignments/media-types/
284. https://www.w3.org/TR/REC-rdf-syntax/#ref-iana-media-types
285. https://www.w3.org/2000/03/rdf-tracking/#rdfms-abouteach
286. https://www.w3.org/2000/03/rdf-tracking/#rdfms-abouteachprefix
287. https://www.w3.org/2000/03/rdf-tracking/#rdfms-seq-representation
288. https://www.w3.org/2000/03/rdf-tracking/#rdfms-syntax-incomplete
289. https://www.w3.org/2000/03/rdf-tracking/
290. https://www.w3.org/TR/REC-rdf-syntax/#rdf-ns-uri
291. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
292. https://www.w3.org/TR/REC-rdf-syntax/#rdf-ns-uri
293. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
294. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph
295. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
296. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
297. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
298. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
299. https://www.w3.org/TR/REC-rdf-syntax/#section-baseURIs
300. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
301. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
302. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
303. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
304. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
305. https://www.w3.org/TR/REC-rdf-syntax/#section-baseURIs
306. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-literal
307. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
308. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-plain-literal
309. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-typed-literal
310. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral
311. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node
312. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
313. https://www.w3.org/TR/REC-rdf-syntax/#nodeIdAttr
314. https://www.w3.org/TR/xml-infoset/#infoitem.document
315. https://www.w3.org/TR/REC-rdf-syntax/#section-Infoset-Grammar-Action
316. https://www.w3.org/TR/2001/REC-xmlbase-20010627/
317. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-base
318. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-base-uri
319. https://www.w3.org/TR/REC-rdf-syntax/#section-root-node
320. https://www.w3.org/TR/REC-rdf-syntax/#section-element-node
321. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
322. https://www.w3.org/TR/2001/REC-xmlbase-20010627/
323. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-base
324. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
325. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
326. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
327. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test001.rdf
328. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test001.nt
329. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test004.rdf
330. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test004.nt
331. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test008.rdf
332. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test008.nt
333. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test013.rdf
334. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test013.nt
335. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test016.rdf
336. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test016.nt
337. http://www.isi.edu/in-notes/rfc2396.txt
338. https://www.w3.org/TR/REC-rdf-syntax/#ref-uri
339. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test013.rdf
340. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test013.nt
341. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test011.rdf
342. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test011.nt
343. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
344. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
345. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-base-uri
346. https://www.w3.org/TR/REC-rdf-syntax/#rdf-id
347. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test014.rdf
348. https://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test014.nt
349. https://www.w3.org/TR/rdf-concepts/#dfn-rdf-graph
350. https://www.w3.org/TR/REC-rdf-syntax/#dfn-rdf-document
351. https://www.w3.org/TR/REC-rdf-syntax/#dfn-rdf-xml-document
352. https://www.w3.org/TR/REC-rdf-syntax/#ref-xpath
353. https://www.w3.org/TR/xpath#infoset
354. https://www.w3.org/TR/REC-rdf-syntax/#section-Infoset-Mapping
355. https://www.w3.org/TR/REC-rdf-syntax/#ref-sax
356. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
357. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph
358. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph
359. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#implementation-note
360. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-concepts
361. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
362. https://www.w3.org/TR/REC-rdf-syntax/#ref-xpath
363. https://www.w3.org/TR/REC-rdf-syntax/#ref-sax
364. https://www.w3.org/TR/1999/REC-xml-names-19990114/
365. https://www.w3.org/TR/REC-rdf-syntax/#ref-namespaces
366. https://www.w3.org/TR/2001/REC-xmlbase-20010627/
367. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-base
368. https://www.w3.org/TR/REC-rdf-syntax/#section-baseURIs
369. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-infoset
370. https://www.w3.org/TR/xml-infoset/#infoitem.document
371. https://www.w3.org/TR/xml-infoset/#infoitem.element
372. https://www.w3.org/TR/xml-infoset/#infoitem.attribute
373. https://www.w3.org/TR/xml-infoset/#infoitem.character
374. https://www.w3.org/TR/xml-infoset/#infoitem.pi
375. https://www.w3.org/TR/xml-infoset/#infoitem.rse
376. https://www.w3.org/TR/xml-infoset/#infoitem.comment
377. https://www.w3.org/TR/xml-infoset/#infoitem.doctype
378. https://www.w3.org/TR/xml-infoset/#infoitem.entity.unparsed
379. https://www.w3.org/TR/xml-infoset/#infoitem.notation
380. https://www.w3.org/TR/xml-infoset/#infoitem.namespace
381. https://www.w3.org/TR/2000/REC-xml-20001006#dt-name
382. https://www.w3.org/TR/2000/REC-xml-20001006
383. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
384. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral
385. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
386. https://www.w3.org/TR/xml-infoset/#conformance
387. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-infoset
388. https://www.w3.org/TR/REC-rdf-syntax/#section-identifier-node
389. https://www.w3.org/TR/REC-rdf-syntax/#section-blank-nodeid-event
390. https://www.w3.org/TR/REC-rdf-syntax/#section-literal-node
391. https://www.w3.org/TR/REC-rdf-syntax/#section-typed-literal-node
392. https://www.w3.org/TR/xml-infoset/#infoitem.document
393. https://www.w3.org/TR/xml-infoset/#infoitem.element
394. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-language
395. https://www.w3.org/TR/2000/REC-xml-20001006#dt-name
396. https://www.w3.org/TR/2000/REC-xml-20001006
397. https://www.w3.org/TR/REC-rdf-syntax/#section-attribute-node
398. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
399. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
400. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
401. https://www.w3.org/TR/REC-rdf-syntax/#section-root-node
402. https://www.w3.org/TR/REC-rdf-syntax/#section-element-node
403. https://www.w3.org/TR/REC-rdf-syntax/#section-identifier-node
404. https://www.w3.org/TR/xml-infoset/#infoitem.attribute
405. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml
406. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-namespace-name
407. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-namespace-name
408. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-local-name
409. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-local-name
410. https://www.w3.org/TR/REC-rdf-syntax/#rdf-ns-uri
411. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-local-name
412. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-local-name
413. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdfms
414. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
415. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
416. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
417. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
418. https://www.w3.org/TR/xml-infoset/#infoitem.character
419. https://www.w3.org/TR/xml-infoset/#infoitem.character
420. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
421. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
422. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
423. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
424. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
425. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#sec-uri-encoding
426. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
427. https://www.w3.org/TR/REC-rdf-syntax/#section-Identifiers
428. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
429. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-blanknodeid-identifier
430. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
431. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#nodeID
432. https://www.w3.org/TR/REC-rdf-syntax/#section-Identifiers
433. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-blanknodeid-identifier
434. https://www.w3.org/TR/REC-rdf-syntax/#section-Identifiers
435. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-plain-literal
436. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-language-identifier
437. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-language
438. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
439. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
440. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-language
441. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
442. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
443. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntrip_strings
444. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
445. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-language
446. https://www.w3.org/TR/REC-rdf-syntax/#ref-charmod
447. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-typed-literal
448. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
449. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-value
450. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-datatype
451. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-value
452. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
453. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntrip_strings
454. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-datatype
455. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
456. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#sec-uri-encoding
457. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-value
458. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-datatype
459. https://www.w3.org/TR/REC-rdf-syntax/#ref-charmod
460. https://www.w3.org/TR/2001/REC-xmlschema-1-20010502/
461. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-schema1
462. https://www.w3.org/TR/2001/REC-xmlschema-1-20010502/#section-White-Space-Normalization-during-Validation
463. https://www.w3.org/TR/REC-rdf-syntax/#section-element-node
464. https://www.w3.org/TR/xml-infoset/#infoitem.element
465. https://www.w3.org/TR/REC-rdf-syntax/#section-end-element-node
466. https://www.w3.org/TR/REC-rdf-syntax/#section-Data-Model
467. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
468. https://www.w3.org/TR/REC-rdf-syntax/#section-Nodes
469. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples
470. https://www.w3.org/TR/REC-rdf-syntax/#section-Namespace
471. https://www.w3.org/TR/REC-rdf-syntax/#section-root-node
472. https://www.w3.org/TR/REC-rdf-syntax/#section-element-node
473. https://www.w3.org/TR/REC-rdf-syntax/#section-end-element-node
474. https://www.w3.org/TR/REC-rdf-syntax/#section-attribute-node
475. https://www.w3.org/TR/REC-rdf-syntax/#section-text-node
476. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-base-uri
477. https://www.w3.org/TR/REC-rdf-syntax/#section-baseURIs
478. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
479. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-blank-node-id
480. https://www.w3.org/TR/REC-rdf-syntax/#section-Identifiers
481. https://www.w3.org/TR/REC-rdf-syntax/#section-identifier-node
482. https://www.w3.org/TR/REC-rdf-syntax/#section-blank-nodeid-event
483. https://www.w3.org/TR/REC-rdf-syntax/#section-Identifiers
484. https://www.w3.org/TR/REC-rdf-syntax/#section-literal-node
485. https://www.w3.org/TR/REC-rdf-syntax/#section-typed-literal-node
486. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
487. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
488. https://www.w3.org/TR/REC-rdf-syntax/#syntaxTerms
489. https://www.w3.org/TR/REC-rdf-syntax/#syntaxTerms
490. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
491. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
492. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
493. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementURIs
494. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementURIs
495. https://www.w3.org/TR/REC-rdf-syntax/#anyURI
496. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
497. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
498. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
499. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
500. https://www.w3.org/TR/REC-rdf-syntax/#anyURI
501. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
502. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
503. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttributeURIs
504. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttributeURIs
505. https://www.w3.org/TR/REC-rdf-syntax/#anyURI
506. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
507. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
508. https://www.w3.org/TR/REC-rdf-syntax/#doc
509. https://www.w3.org/TR/REC-rdf-syntax/#doc
510. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-root-document-element
511. https://www.w3.org/TR/REC-rdf-syntax/#RDF
512. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-root-children
513. https://www.w3.org/TR/REC-rdf-syntax/#RDF
514. https://www.w3.org/TR/REC-rdf-syntax/#RDF
515. https://www.w3.org/TR/REC-rdf-syntax/#RDF
516. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
517. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
518. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
519. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
520. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
521. https://www.w3.org/TR/REC-rdf-syntax/#ws
522. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
523. https://www.w3.org/TR/REC-rdf-syntax/#ws
524. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
525. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
526. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
527. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementURIs
528. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
529. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
530. https://www.w3.org/TR/REC-rdf-syntax/#nodeIdAttr
531. https://www.w3.org/TR/REC-rdf-syntax/#aboutAttr
532. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
533. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
534. https://www.w3.org/TR/REC-rdf-syntax/#ws
535. https://www.w3.org/TR/REC-rdf-syntax/#ws
536. https://www.w3.org/TR/REC-rdf-syntax/#section-text-node
537. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml
538. https://www.w3.org/TR/2000/REC-xml-20001006#NT-S
539. https://www.w3.org/TR/2000/REC-xml-20001006#sec-common-syn
540. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
541. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
542. https://www.w3.org/TR/REC-rdf-syntax/#ws
543. https://www.w3.org/TR/REC-rdf-syntax/#propertyElt
544. https://www.w3.org/TR/REC-rdf-syntax/#ws
545. https://www.w3.org/TR/REC-rdf-syntax/#propertyElt
546. https://www.w3.org/TR/REC-rdf-syntax/#propertyElt
547. https://www.w3.org/TR/REC-rdf-syntax/#resourcePropertyElt
548. https://www.w3.org/TR/REC-rdf-syntax/#literalPropertyElt
549. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
550. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeResourcePropertyElt
551. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeCollectionPropertyElt
552. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeOtherPropertyElt
553. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
554. https://www.w3.org/TR/REC-rdf-syntax/#resourcePropertyElt
555. https://www.w3.org/TR/REC-rdf-syntax/#resourcePropertyElt
556. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
557. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
558. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
559. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
560. https://www.w3.org/TR/REC-rdf-syntax/#ws
561. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
562. https://www.w3.org/TR/REC-rdf-syntax/#ws
563. https://www.w3.org/TR/REC-rdf-syntax/#literalPropertyElt
564. https://www.w3.org/TR/REC-rdf-syntax/#literalPropertyElt
565. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
566. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
567. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
568. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
569. https://www.w3.org/TR/REC-rdf-syntax/#datatypeAttr
570. https://www.w3.org/TR/REC-rdf-syntax/#section-text-node
571. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
572. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
573. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
574. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
575. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
576. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
577. https://www.w3.org/TR/REC-rdf-syntax/#parseLiteral
578. https://www.w3.org/TR/REC-rdf-syntax/#literal
579. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeResourcePropertyElt
580. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeResourcePropertyElt
581. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
582. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
583. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
584. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
585. https://www.w3.org/TR/REC-rdf-syntax/#parseResource
586. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
587. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeCollectionPropertyElt
588. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeCollectionPropertyElt
589. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
590. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
591. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
592. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
593. https://www.w3.org/TR/REC-rdf-syntax/#parseCollection
594. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
595. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeOtherPropertyElt
596. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeOtherPropertyElt
597. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
598. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
599. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
600. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
601. https://www.w3.org/TR/REC-rdf-syntax/#parseOther
602. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
603. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
604. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
605. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
606. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
607. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
608. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
609. https://www.w3.org/TR/REC-rdf-syntax/#resourceAttr
610. https://www.w3.org/TR/REC-rdf-syntax/#nodeIdAttr
611. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
612. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
613. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
614. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
615. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
616. https://www.w3.org/TR/REC-rdf-syntax/#rdf-id
617. https://www.w3.org/TR/REC-rdf-syntax/#nodeIdAttr
618. https://www.w3.org/TR/REC-rdf-syntax/#nodeIdAttr
619. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
620. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
621. https://www.w3.org/TR/REC-rdf-syntax/#rdf-id
622. https://www.w3.org/TR/REC-rdf-syntax/#aboutAttr
623. https://www.w3.org/TR/REC-rdf-syntax/#aboutAttr
624. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
625. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
626. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
627. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
628. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
629. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
630. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttributeURIs
631. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
632. https://www.w3.org/TR/REC-rdf-syntax/#anyString
633. https://www.w3.org/TR/REC-rdf-syntax/#resourceAttr
634. https://www.w3.org/TR/REC-rdf-syntax/#resourceAttr
635. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
636. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
637. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
638. https://www.w3.org/TR/REC-rdf-syntax/#datatypeAttr
639. https://www.w3.org/TR/REC-rdf-syntax/#datatypeAttr
640. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
641. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
642. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
643. https://www.w3.org/TR/REC-rdf-syntax/#parseLiteral
644. https://www.w3.org/TR/REC-rdf-syntax/#parseLiteral
645. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
646. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
647. https://www.w3.org/TR/REC-rdf-syntax/#parseResource
648. https://www.w3.org/TR/REC-rdf-syntax/#parseResource
649. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
650. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
651. https://www.w3.org/TR/REC-rdf-syntax/#parseCollection
652. https://www.w3.org/TR/REC-rdf-syntax/#parseCollection
653. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
654. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
655. https://www.w3.org/TR/REC-rdf-syntax/#parseOther
656. https://www.w3.org/TR/REC-rdf-syntax/#parseOther
657. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
658. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
659. https://www.w3.org/TR/REC-rdf-syntax/#anyString
660. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
661. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
662. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
663. https://www.w3.org/TR/REC-rdf-syntax/#literal
664. https://www.w3.org/TR/REC-rdf-syntax/#literal
665. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml
666. https://www.w3.org/TR/2000/REC-xml-20001006#NT-content
667. https://www.w3.org/TR/2000/REC-xml-20001006#sec-starttags
668. https://www.w3.org/TR/REC-rdf-syntax/#rdf-id
669. https://www.w3.org/TR/REC-rdf-syntax/#rdf-id
670. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
671. https://www.w3.org/TR/REC-rdf-syntax/#ref-namespaces
672. https://www.w3.org/TR/REC-xml-names/#NT-NCName
673. https://www.w3.org/TR/REC-rdf-syntax/#section-MIME-Type
674. https://www.w3.org/TR/REC-rdf-syntax/#doc
675. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
676. https://www.w3.org/TR/REC-rdf-syntax/#section-element-node
677. https://www.w3.org/TR/REC-rdf-syntax/#RDF
678. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
679. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-base-uri
680. https://www.w3.org/TR/REC-rdf-syntax/#section-root-node
681. https://www.w3.org/TR/REC-rdf-syntax/#section-Namespace
682. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
683. https://www.w3.org/TR/REC-rdf-syntax/#section-Namespace
684. https://www.w3.org/TR/REC-rdf-syntax/#section-Namespace
685. https://www.w3.org/2000/03/rdf-tracking/#rdfms-aboutEach-on-object
686. https://www.w3.org/2000/03/rdf-tracking/#rdfms-abouteachprefix
687. https://www.w3.org/2001/sw/RDFCore/20030123-issues/#timbl-01
688. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-abouteach/error001.rdf
689. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-abouteach/error002.rdf
690. https://www.w3.org/TR/REC-rdf-syntax/#anyURI
691. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
692. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
693. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
694. https://www.w3.org/TR/REC-rdf-syntax/#anyURI
695. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
696. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
697. https://www.w3.org/TR/REC-rdf-syntax/#anyURI
698. https://www.w3.org/TR/REC-rdf-syntax/#coreSyntaxTerms
699. https://www.w3.org/TR/REC-rdf-syntax/#oldTerms
700. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
701. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-root-document-element
702. https://www.w3.org/TR/REC-rdf-syntax/#RDF
703. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-root-children
704. https://www.w3.org/TR/REC-rdf-syntax/#RDF
705. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
706. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
707. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
708. https://www.w3.org/TR/REC-rdf-syntax/#ws
709. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
710. https://www.w3.org/TR/REC-rdf-syntax/#ws
711. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
712. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementURIs
713. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
714. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
715. https://www.w3.org/TR/REC-rdf-syntax/#nodeIdAttr
716. https://www.w3.org/TR/REC-rdf-syntax/#aboutAttr
717. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
718. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
719. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
720. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
721. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
722. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
723. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
724. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
725. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
726. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
727. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
728. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
729. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
730. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
731. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
732. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
733. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
734. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
735. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
736. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
737. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
738. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
739. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
740. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
741. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
742. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
743. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
744. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
745. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
746. https://www.w3.org/TR/REC-rdf-syntax/#ref-nfc
747. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
748. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
749. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-language
750. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-language
751. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
752. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
753. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI-string-value
754. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-string-value
755. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
756. https://www.w3.org/TR/REC-rdf-syntax/#section-text-node
757. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml
758. https://www.w3.org/TR/2000/REC-xml-20001006#NT-S
759. https://www.w3.org/TR/2000/REC-xml-20001006#sec-common-syn
760. https://www.w3.org/TR/REC-rdf-syntax/#ws
761. https://www.w3.org/TR/REC-rdf-syntax/#propertyElt
762. https://www.w3.org/TR/REC-rdf-syntax/#ws
763. https://www.w3.org/TR/REC-rdf-syntax/#resourcePropertyElt
764. https://www.w3.org/TR/REC-rdf-syntax/#literalPropertyElt
765. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
766. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeResourcePropertyElt
767. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeCollectionPropertyElt
768. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeOtherPropertyElt
769. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
770. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
771. https://www.w3.org/TR/REC-rdf-syntax/#section-List-Expand
772. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
773. https://www.w3.org/TR/REC-rdf-syntax/#resourcePropertyElt
774. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
775. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
776. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
777. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
778. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
779. https://www.w3.org/TR/REC-rdf-syntax/#ws
780. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
781. https://www.w3.org/TR/REC-rdf-syntax/#ws
782. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
783. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
784. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
785. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
786. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
787. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
788. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
789. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
790. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
791. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
792. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
793. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
794. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
795. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
796. https://www.w3.org/TR/REC-rdf-syntax/#datatypeAttr
797. https://www.w3.org/TR/REC-rdf-syntax/#section-text-node
798. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
799. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-text-string-value
800. https://www.w3.org/TR/REC-rdf-syntax/#ref-nfc
801. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-value
802. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-text-string-value
803. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-datatype
804. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
805. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
806. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-text-string-value
807. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-language
808. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-language
809. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
810. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
811. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
812. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-string-value
813. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
814. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
815. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
816. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
817. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
818. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
819. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
820. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
821. https://www.w3.org/TR/REC-rdf-syntax/#parseLiteral
822. https://www.w3.org/TR/REC-rdf-syntax/#literal
823. https://www.w3.org/TR/REC-rdf-syntax/#section-Data-Model
824. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral
825. https://www.w3.org/TR/REC-rdf-syntax/#ref-xpath
826. https://www.w3.org/TR/1999/REC-xpath-19991116#infoset
827. https://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-document-subset
828. https://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/
829. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml-xc14n
830. https://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces-PrefixList
831. https://www.w3.org/TR/REC-rdf-syntax/#ref-nfc
832. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-value
833. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-literal-datatype
834. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
835. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
836. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
837. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-typedliteral-string-value
838. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test009.rdf
839. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test009.nt
840. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
841. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
842. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
843. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
844. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
845. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
846. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
847. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
848. https://www.w3.org/TR/REC-rdf-syntax/#parseResource
849. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
850. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
851. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
852. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
853. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
854. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
855. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test004.rdf
856. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test004.nt
857. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
858. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
859. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
860. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
861. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
862. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
863. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
864. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
865. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
866. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
867. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
868. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
869. https://www.w3.org/TR/REC-rdf-syntax/#parseCollection
870. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
871. https://www.w3.org/TR/REC-rdf-syntax/#nodeElementList
872. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
873. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
874. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
875. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
876. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
877. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
878. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
879. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
880. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
881. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
882. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
883. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
884. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
885. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
886. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
887. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
888. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
889. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
890. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
891. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
892. https://www.w3.org/TR/REC-rdf-syntax/#parseOther
893. https://www.w3.org/TR/REC-rdf-syntax/#propertyEltList
894. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
895. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI
896. https://www.w3.org/TR/REC-rdf-syntax/#propertyElementURIs
897. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-attributes
898. https://www.w3.org/TR/REC-rdf-syntax/#idAttr
899. https://www.w3.org/TR/REC-rdf-syntax/#resourceAttr
900. https://www.w3.org/TR/REC-rdf-syntax/#nodeIdAttr
901. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
902. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
903. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-language
904. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-language
905. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
906. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
907. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
908. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-string-value
909. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
910. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
911. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
912. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test002.rdf
913. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test002.nt
914. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test005.rdf
915. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test005.nt
916. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
917. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
918. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
919. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
920. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
921. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttr
922. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
923. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
924. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
925. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
926. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
927. https://www.w3.org/TR/REC-rdf-syntax/#ref-nfc
928. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-value
929. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
930. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-literal-language
931. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-language
932. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
933. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI-string-value
934. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-literal-string-value
935. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test013.rdf
936. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test013.nt
937. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test014.rdf
938. https://www.w3.org/2000/10/rdf-tests/rdfcore/rdfms-empty-property-elements/test014.nt
939. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-subject
940. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
941. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-URI-string-value
942. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
943. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-identifier
944. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
945. https://www.w3.org/TR/REC-rdf-syntax/#section-Reification
946. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
947. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
948. https://www.w3.org/TR/REC-rdf-syntax/#rdf-id
949. https://www.w3.org/TR/REC-rdf-syntax/#constraint-id
950. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
951. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
952. https://www.w3.org/TR/REC-rdf-syntax/#rdf-id
953. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
954. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
955. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
956. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
957. https://www.w3.org/TR/REC-rdf-syntax/#propertyAttributeURIs
958. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
959. https://www.w3.org/TR/REC-rdf-syntax/#anyString
960. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
961. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
962. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
963. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
964. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
965. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
966. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
967. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
968. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
969. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
970. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
971. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
972. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-URI
973. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
974. https://www.w3.org/TR/REC-rdf-syntax/#anyString
975. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
976. https://www.w3.org/TR/REC-rdf-syntax/#ref-xml
977. https://www.w3.org/TR/2000/REC-xml-20001006#NT-content
978. https://www.w3.org/TR/2000/REC-xml-20001006#sec-starttags
979. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
980. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-attribute-string-value
981. https://www.w3.org/TR/REC-rdf-syntax/#ref-namespaces
982. https://www.w3.org/TR/REC-xml-names/#NT-NCName
983. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
984. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
985. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
986. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-identifier-string-value
987. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-URI-reference
988. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-liCounter
989. https://www.w3.org/TR/REC-rdf-syntax/#eventterm-element-liCounter
990. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-graph
991. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
992. https://www.w3.org/TR/REC-xml-names/#dt-qname
993. https://www.w3.org/TR/REC-xml-names/#NT-NCName
994. https://www.w3.org/TR/REC-xml#NT-Letter
995. https://www.w3.org/TR/REC-xml-names/#NT-NCName
996. https://www.w3.org/TR/REC-rdf-syntax/#syntaxTerms
997. http://infomesh.net/2002/rdfinhtml/
998. https://www.w3.org/TR/REC-rdf-syntax/#ref-rdf-in-xhtml
999. http://www.dublincore.org/
1000. https://www.w3.org/TR/REC-rdf-syntax/#section-MIME-Type
1001. http://www.ietf.org/rfc/rfc2731.txt
1002. https://www.w3.org/TR/REC-rdf-syntax/#ref-rfc2731
1003. https://www.w3.org/TR/html401/types.html#type-links
1004. https://www.w3.org/TR/xhtml-modularization/abstraction.html#dt_LinkTypes
1005. https://www.w3.org/TR/xhtml2/abstraction.html#dt_LinkTypes
1006. https://www.w3.org/TR/REC-rdf-syntax/#example21
1007. https://www.w3.org/TR/REC-rdf-syntax/example21.html
1008. https://www.w3.org/TR/REC-rdf-syntax/example21.rdf
1009. https://www.w3.org/TR/SVG/metadata.html
1010. https://www.w3.org/TR/2001/REC-SVG-20010904/
1011. https://www.w3.org/TR/REC-rdf-syntax/#ref-svg
1012. https://www.w3.org/TR/SVG11/metadata.html
1013. https://www.w3.org/TR/2003/REC-SVG11-20030114/
1014. https://www.w3.org/TR/REC-rdf-syntax/#ref-svg11
1015. https://www.w3.org/TR/rdf-syntax-grammar/figure1.svg
1016. https://www.w3.org/TR/rdf-syntax-grammar/figure2.svg
1017. https://www.w3.org/TR/1999/REC-rdf-syntax-19990222/
1018. https://www.w3.org/TR/REC-rdf-syntax/
1019. https://www.w3.org/TR/2000/REC-xml-20001006
1020. https://www.w3.org/TR/REC-xml
1021. https://www.w3.org/TR/1999/REC-xml-names-19990114/
1022. https://www.w3.org/TR/REC-xml-names/
1023. https://www.w3.org/TR/2001/REC-xml-infoset-20011024/
1024. https://www.w3.org/TR/xml-infoset/
1025. http://www.isi.edu/in-notes/rfc2396.txt
1026. https://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
1027. https://www.w3.org/TR/2004/REC-rdf-primer-20040210/
1028. https://www.w3.org/TR/rdf-concepts/
1029. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/
1030. https://www.w3.org/TR/2004/REC-rdf-testcases-20040210/
1031. https://www.w3.org/TR/rdf-testcases/
1032. http://www.ietf.org/rfc/rfc2119.txt
1033. http://www.ietf.org/rfc/rfc3023.txt
1034. http://www.iana.org/assignments/media-types/
1035. https://www.w3.org/2001/sw/RDFCore/mediatype-registration
1036. https://www.w3.org/TR/2001/REC-xmlbase-20010627/
1037. https://www.w3.org/TR/xmlbase/
1038. https://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/
1039. https://www.w3.org/TR/xml-exc-c14n/
1040. http://www.unicode.org/unicode/standard/versions/
1041. http://www.unicode.org/unicode/reports/tr15/
1042. http://www.unicode.org/unicode/reports/tr15/
1043. https://www.w3.org/TR/2002/WD-charmod-20020220/
1044. https://www.w3.org/TR/charmod/
1045. https://www.w3.org/TR/2004/REC-rdf-mt-20040210/
1046. https://www.w3.org/TR/2004/REC-rdf-mt-20040210/
1047. https://www.w3.org/TR/rdf-mt/
1048. https://www.w3.org/TR/2004/REC-rdf-primer-20040210/
1049. https://www.w3.org/TR/2004/REC-rdf-primer-20040210/
1050. https://www.w3.org/TR/rdf-primer/
1051. https://www.w3.org/TR/2004/REC-rdf-schema-20040210/
1052. https://www.w3.org/TR/2004/REC-rdf-schema-20040210/
1053. https://www.w3.org/TR/rdf-schema/
1054. https://www.w3.org/2001/10/stripes/
1055. https://www.w3.org/TR/2001/REC-SVG-20010904/
1056. https://www.w3.org/TR/SVG/
1057. https://www.w3.org/TR/2003/REC-SVG11-20030114/
1058. https://www.w3.org/TR/SVG11/
1059. https://www.w3.org/TR/1999/REC-xpath-19991116
1060. https://www.w3.org/TR/xpath
1061. http://sax.sourceforge.net/
1062. http://www.hpl.hp.com/techreports/2001/HPL-2001-294.html
1063. http://www.oasis-open.org/committees/relax-ng/spec-20011203.html
1064. http://www.oasis-open.org/committees/relax-ng/spec.html
1065. http://www.oasis-open.org/committees/relax-ng/compact-20021121.html
1066. http://infomesh.net/2002/rdfinhtml/
1067. http://www.ietf.org/rfc/rfc2731.txt
1068. https://www.w3.org/TR/2001/REC-xmlschema-1-20010502/
1069. https://www.w3.org/TR/xmlschema-1/
1070. https://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
1071. https://www.w3.org/TR/xmlschema-2/
1072. https://www.w3.org/TR/REC-rdf-syntax/rdfxml.rng
1073. http://www.oasis-open.org/committees/relax-ng/spec-20011203.html
1074. https://www.w3.org/TR/REC-rdf-syntax/#ref-relaxng
1075. http://www.thaiopensource.com/relaxng/compact/
1076. https://www.w3.org/TR/REC-rdf-syntax/#ref-relaxng-nx
1077. https://www.w3.org/TR/REC-rdf-syntax/rdfxml.rnc
1078. https://www.w3.org/TR/2003/WD-rdf-syntax-grammar-20031010/
1079. https://www.w3.org/TR/REC-rdf-syntax/#example8
1080. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-languages
1081. http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0215.html
1082. https://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-property-attributes
1083. http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0074.html
1084. https://www.w3.org/TR/REC-rdf-syntax/#section-identifier-node
1085. https://www.w3.org/TR/REC-rdf-syntax/#section-literal-node
1086. https://www.w3.org/TR/REC-rdf-syntax/#section-typed-literal-node
1087. http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Nov/0006.html
1088. https://www.w3.org/TR/REC-rdf-syntax/#section-element-node
1089. https://www.w3.org/TR/REC-rdf-syntax/#section-attribute-node
1090. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
1091. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
1092. https://www.w3.org/TR/REC-rdf-syntax/#nodeElement
1093. https://www.w3.org/TR/REC-rdf-syntax/#resourcePropertyElt
1094. https://www.w3.org/TR/REC-rdf-syntax/#literalPropertyElt
1095. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeLiteralPropertyElt
1096. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeResourcePropertyElt
1097. https://www.w3.org/TR/REC-rdf-syntax/#parseTypeCollectionPropertyElt
1098. https://www.w3.org/TR/REC-rdf-syntax/#emptyPropertyElt
1099. https://www.w3.org/TR/REC-rdf-syntax/#URI-reference
1100. http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0100.html
1101. http://lists.w3.org/Archives/Public/www-rdf-comments/2003OctDec/0068.html
1102. https://www.w3.org/TR/REC-rdf-syntax/metadata.rdf
Hidden links:
1104. https://www.w3.org/TR/REC-rdf-syntax/#section-element-node
Usage: http://www.kk-software.de/kklynxview/get/URL
e.g. http://www.kk-software.de/kklynxview/get/http://www.kk-software.de
Errormessages are in German, sorry ;-)