From 7a778e5661a8866357ed5dfdc11df3d5860e4047 Mon Sep 17 00:00:00 2001 From: Gregg Kellogg Date: Sun, 5 Feb 2023 16:17:22 -0800 Subject: [PATCH 1/7] Update SOTD on section refs --- spec/index.html | 102 ++++++++++++++++++++++-------------------------- 1 file changed, 47 insertions(+), 55 deletions(-) diff --git a/spec/index.html b/spec/index.html index eacbd18..ef43c49 100644 --- a/spec/index.html +++ b/spec/index.html @@ -73,23 +73,14 @@
-

This document is an edited version of the 2004 RDF XML Syntax - Specification Recommendation. The purpose of this revision is - to make this - document available as part of the RDF 1.2 document set. Changes are - limited to revised references, terminology updates, and adaptations to - the introduction. - The technical content of the document is unchanged, except for - the fact that the datatype XMLLiiteral is marked as - non-normative in RDF 1.2. The (non-normative) algorithm for - parsing XMLLiteral - (Sec. 7.2.17) - has been updated to be in line with - the current state of XML technology. Details of the changes - are listed in the Changes - section. Since the edits to this document do not invalidate - previous implementations the Director decided no new implementation report was required.

- +

This document is a part of the RDF 1.2 document suite. The + document defines the RDF XML syntax, + a concrete syntax for RDF [[RDF12-CONCEPTS]].

+ +

There have been no substantive changes to this document since [[RDF11-XML]]. + Minor editorial changes, if any, are + detailed in .

+
@@ -139,9 +130,9 @@

An XML Syntax for RDF

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 - 6 Syntax Data Model and - 7 RDF/XML Grammar, the - latter two sections take precedence. + and + , + the latter two sections take precedence.

@@ -296,8 +287,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.

 
@@ -523,8 +514,8 @@ 
Languages: xml:lang

     to allow the identification of content language.
     The xml:lang attribute can be used on any node element or property element
     to indicate that the included content is in the given language.
-    Typed literals
-    which includes XML literals
+    
+    which includes 
     are not affected by this attribute.
     The most specific in-scope language present
     (if any) is applied to property element string literal content or
@@ -950,7 +941,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 +1002,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 +1044,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 +1225,7 @@ 
Identifiers