diff --git a/spec/index.html b/spec/index.html index 6089b90..fa3e8d7 100644 --- a/spec/index.html +++ b/spec/index.html @@ -3,7 +3,7 @@ - RDF 1.2 Concepts and Abstract Syntax + RDF 1.2 Concepts and Abstract Data Model @@ -77,9 +77,9 @@

The Resource Description Framework (RDF) is a framework for representing information on the Web. - This document defines an abstract syntax (a data model) + This document defines an abstract data model which serves to link all RDF-based languages and specifications. - The abstract syntax has two key data structures:

+ The abstract model has two key data structures:

-

Graph-based Data Model

+

Graph-based Abstract Data Model

-

The core structure of the abstract syntax is a set of +

The core structure of the abstract model is a set of triples, each consisting of a subject, a predicate and an object. A set of such triples is called an RDF graph. An RDF graph can be visualized as a node and @@ -155,8 +155,8 @@

Graph-based Data Model

There can be four kinds of nodes in an RDF graph: IRIs, literals, blank nodes, and triple terms.

- -

There is a mixture of "Abstract Syntax" and "Data Model". We should have a consistent way to say "Abstract Syntax" vs "Data Model". One way is to use "Abstract Syntax" as the basis of semantics and usually say "Data Model" in Concepts otherwise.

+
@@ -255,7 +255,7 @@

The Referent of an IRI

unique identifiers in a graph data model that describes resources. However, those interactions are critical to the concept of [[[LINKED-DATA]]], [[LINKED-DATA]], - which makes use of the RDF data model and serialization formats.

+ which uses the RDF abstract syntax and serialization formats.

@@ -305,7 +305,7 @@

RDF Vocabularies and Namespace IRIs

would be abbreviated as rdf:XMLLiteral. Note however that such abbreviations are not meant to be processed directly as IRIs, and are not to be used in syntactic contexts where IRIs are expected. - Note also that [=namespace IRIs=] and [=namespace prefixes=] are not a formal part of the RDF data model. + Note also that [=namespace IRIs=] and [=namespace prefixes=] are not a formal part of the RDF abstract model. They are merely a syntactic convenience for abbreviating IRIs; for processing, the actual IRIs are reconstructed by replacing each namespace prefix with the corresponding namespace IRI.

@@ -400,7 +400,7 @@

Triple Terms and Reification

RDF and Change over Time

-

The RDF data model is atemporal: RDF graphs +

The RDF abstract model is atemporal: RDF graphs are static snapshots of information.

However, RDF graphs can express information @@ -595,13 +595,13 @@

RDF Version Announcement

-

This specification, RDF 1.2 Concepts and Abstract Syntax, - defines a data model and related terminology for use in +

This specification, RDF 1.2 Concepts and Abstract Model, + defines an abstract model and related vocabulary for use in other specifications, such as concrete RDF syntaxes, API specifications, and query languages. Implementations cannot directly conform to - RDF 1.2 Concepts and Abstract Syntax, + RDF 1.2 Concepts and Abstract Model, but can conform to such other specifications that normatively reference terms defined here.

@@ -847,7 +847,8 @@

IRIs

is a string that conforms to the syntax defined in RFC 3987 [[!RFC3987]].

-

An IRI in the RDF abstract syntax +

An IRI in the RDF abstract model + MUST be resolved per [[RFC3986]] and MUST NOT be a relative reference. An IRI MAY contain a fragment identifier. @@ -859,7 +860,7 @@

IRIs

Unicode code points, as in Simple String Comparison in section 5.3.1 of [[!RFC3987]]. - (This is done in the abstract syntax, so the IRIs are resolved + (This is done in the abstract model, so the IRIs are resolved IRIs with no escaping or encoding.) Further normalization MUST NOT be performed before this comparison.

@@ -877,7 +878,7 @@

IRIs

An IRI reference is common usage of an Internationalized Resource Identifier. An IRI reference refers to either a resolved IRI or relative IRI reference, as described by the IRI-reference production in . - The abstract syntax uses only fully resolved IRIs. + The abstract model uses only fully resolved IRIs. When IRIs are used in operations that are only defined for URIs, they must first be converted according to the mapping defined in @@ -1008,7 +1009,7 @@

Representation of Literals

Some concrete syntaxes MAY support simple literals consisting of only a lexical form without any datatype IRI, language tag, or base direction. - Simple literals are syntactic sugar for abstract syntax + Simple literals are syntactic sugar for data model literals with the datatype IRI http://www.w3.org/2001/XMLSchema#string @@ -1037,7 +1038,7 @@

Representation of Literals

In RDF 1.1, `"chat"@fr` and `"chat"@FR` represent two distinct terms, but implementations may replace either with the other via some form of normalization. In RDF 1.2, they represent the exact same literal, - i.e., the case difference in the concrete syntax does not propagate into the abstract syntax. + i.e., the case difference in the concrete syntax does not propagate into the abstract model. Since many RDF 1.1 implementations do normalize language tags internally, they will not be impacted by this change. @@ -1145,7 +1146,7 @@

Blank Nodes

They are always locally scoped to the file or RDF store, and are not persistent or portable identifiers for blank nodes. Blank node identifiers are not - part of the RDF abstract syntax, but are entirely dependent + part of the RDF abstract model, but are entirely dependent on the concrete syntax or implementation. The syntactic restrictions on blank node identifiers, if any, therefore also depend on the concrete RDF syntax or implementation. Implementations that handle blank node @@ -1943,7 +1944,7 @@

The rdf:JSON Datatype

Replacing Blank Nodes with IRIs

-

Blank nodes do not have identifiers in the RDF abstract syntax. The +

Blank nodes do not have identifiers in the RDF abstract model. The blank node identifiers introduced by some concrete syntaxes have only local scope and are purely an artifact of the serialization.

@@ -1999,7 +2000,7 @@

Privacy Considerations

Security Considerations

-

The RDF Abstract Syntax is not used directly for conveying information, +

The RDF Abstract Model is not used directly for conveying information, although concrete serialization forms are specifically intended to do so.

Applications MAY evaluate given data to infer more assertions or to dereference IRIs, @@ -2215,7 +2216,7 @@

Changes between RDF 1.1 and RDF 1.2

  • Improved the use of IRI terminology, and added . This improves the language using relative IRI references - and clarifies that, in the abstract syntax, IRIs are resolved, + and clarifies that, in the abstract model, IRIs are resolved, avoiding the incorrect use of "absolute IRI".
  • Changed reference from DOM4, which was not a recommendation at the time, to [[DOM]], making the definitions of rdf:HTML and rdf:XMLLiteral datatypes normative.