-
- Graph for RDF/XML Example (SVG version)
+
+
+ Graph for RDF/XML Example
An RDF graph is given in Figure 1
@@ -227,8 +221,16 @@
Node Elements and Property Elements
graph shown in Figure 2:
-
- One Path Through the Graph (SVG version)
+
+
+ One Path Through the Graph
The left hand side of the Figure 2
@@ -296,8 +298,8 @@
Node Elements and Property Elements
Example 2
gives the result in Example 3
(this example fails to show that the blank node is
- shared between the two paths, see
- 2.10):
+ shared between the two paths,
+ see ):
Property Attributes
only if the property element name is not repeated
(required by XML — attribute names are unique on an XML element)
and any in-scope xml:lang on the
- property element's string literal (if any) are the same (see
- Section 2.7)
+ property element's string literal (if any) are the same
+ (see )
This abbreviation is known as a Property Attribute
and can be applied to any node element.
@@ -950,7 +952,7 @@
Container Membership Property Elements: rdf:li and rdf:_<
Example 17. There is an rdf:li
special property element that is equivalent to
rdf:_1, rdf:_2 in order,
- explained in detail in section 7.4.
+ explained in detail in .
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.
@@ -1011,7 +1013,7 @@
Collections: rdf:parseType="Collection"
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
- 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
@@ -1053,7 +1055,7 @@
Reifying Statements: rdf:ID
The rdf:ID attribute can be used on a property
element to reify the triple that it generates (See
- section 7.3 Reification Rules for the
+ for the
full details).
The identifier for the triple should be constructed as a
IRI
@@ -1234,7 +1236,7 @@
Identifiers
given as XML attribute values interpreted as relative
IRIs that are resolved against the in-scope base URI
- as described in section 5.3
+ as described in
to give absolute IRIs
transformed from XML namespace-qualified element and attribute names
(QNames)
@@ -1258,7 +1260,7 @@
Identifiers
IRIs
by appending the attribute value to the result of appending
"#" to the in-scope base URI which is defined in
- Section 5.3 Resolving IRIs
+
Literal
@@ -1413,7 +1415,7 @@
Syntax Data Model
Information Set Mapping.
A sequence of events is normally derived from an XML document, in
which case they are in document order as defined below in
- Section 6.2 Information Set Mapping.
+ .
The sequence these events form are intended to be similar to the sequence
of events produced by the [[SAX]] XML API from
the same XML document. Sequences of events may be checked against
@@ -1801,7 +1803,7 @@
IRI Event
For further information on identifiers in the RDF graph, see
- section 5.2.
+ .
@@ -1837,7 +1839,7 @@
Blank Node Identifier Event
For further information on identifiers in the RDF graph, see
- section 5.2.
+ .
@@ -2022,7 +2024,7 @@
Information Set Mapping
Grammar Notation
The following notation is used to describe matching the sequence
- of data model events as given in Section 6
+ of data model events as given in
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:
@@ -2045,7 +2047,7 @@
Grammar Notation
where the event-content is an expression matching
- event-types (as defined in Section 6.1),
+ event-types (as defined in ),
using notation given in the following sections.
The number is used for reference purposes.
The grammar action may include generating
@@ -2072,7 +2074,7 @@
A string created by interpreting string s as a relative IRI to the
- ·base-uri· accessor of e
- as defined in Section 5.3 Resolving URIs.
+ ·base-uri· accessor of e
+ as defined in .
The resulting string represents an
IRI.
@@ -2196,7 +2198,7 @@
Grammar Action Notation
generated-blank-node-id()
A string value for a new distinct generated
blank node identifier
- as defined in section 5.2 Identifiers.
+ as defined in .
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 section 6 Syntax Data Model)
+ (as noted in section )
but remains an XML Infoset of XML Information items.
l is transformed into the lexical form of an
@@ -2875,7 +2878,7 @@
and then if i is given, the above statement is reified with
uri(identifier := resolve(e, concat("#", i.string-value)))
using the reification rules in
- section 7.3.
+ .
Test:
Indicated by
@@ -3147,7 +3150,7 @@
Production emptyPropertyElt
reified with
uri(identifier := resolve(e, concat("#", i.string-value)))
using the reification rules in
- section 7.3.
+ .
@@ -3296,7 +3299,7 @@
Production literal
The string-value for the resulting event is discussed in
- section 7.2.17.
+ .
@@ -3526,8 +3529,8 @@
Changes for RDF 1.1 Recommendation
Updated link to QName definition in XML-NAMES
Added diff with 2004 Recommendation
Sections concerning rdf:XMLLiteral
- (Sec. 2.8
- and Sec. 7.2.17)
+ (
+ and )
marked as non-normative.