diff --git a/spec/index.html b/spec/index.html index 120c201..0950956 100644 --- a/spec/index.html +++ b/spec/index.html @@ -134,7 +134,7 @@

Introduction

This example introduces many of features of the Turtle language: - @base and Relative IRIs, + @base and Relative IRI references, @prefix and prefixed names, predicate lists separated by ';', object lists separated by ',', @@ -250,7 +250,7 @@

IRIs

may contain numeric escape sequences (described below). For example <http://example.org/#green-goblin>.

-

Relative IRIs like <#green-goblin> +

Relative IRI references like <#green-goblin> are resolved relative to the current base IRI. A new base IRI can be defined using the '@base' or 'BASE' directive. Specifics of this operation are defined in @@ -331,10 +331,10 @@

IRIs

. @base . - . # relative IRIs, e.g. http://one.example/subject2 + . # relative IRI references, e.g. http://one.example/subject2 BASE - . # relative IRIs, e.g. http://one.example/subject2 + . # relative IRI references, e.g. http://one.example/subject2 @prefix p: . p:subject3 p:predicate3 p:object3 . # prefixed name, e.g. http://two.example/subject3 @@ -398,7 +398,7 @@

Quoted Literals

(U+005E U+005E). The datatype IRI in Turtle may be written using either an absolute IRI, - a relative IRI, + a relative IRI reference, or prefixed name. If there is no datatype IRI and no language tag, the datatype is xsd:string. @@ -866,12 +866,12 @@

Comments

IRI References

- Relative IRIs are resolved with base IRIs as per [[[RFC3986]]] [[RFC3986]] using only the basic algorithm in section 5.2. + Relative IRI references are resolved with base IRIs as per [[[RFC3986]]] [[RFC3986]] using only the basic algorithm in section 5.2. Neither Syntax-Based Normalization nor Scheme-Based Normalization (described in sections 6.2.2 and 6.2.3 of RFC3986) are performed. Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of [[[RFC3987]]] [[RFC3987]].

- The @base or BASE directive defines the Base IRI used to resolve relative IRIs + The @base or BASE directive defines the Base IRI used to resolve relative IRI references per [[RFC3986]] section 5.1.1, "Base URI Embedded in Content". Section 5.1.2, "Base URI from the Encapsulating Entity" defines how the In-Scope Base IRI may come from an encapsulating document, @@ -1216,7 +1216,7 @@

RDF Term Constructors

production type procedure - IRIREF IRI The characters between "<" and ">" are taken, with the numeric escape sequences unescaped, to form the unicode string of the IRI. Relative IRI resolution is performed per Section 6.3. + IRIREF IRI The characters between "<" and ">" are taken, with the numeric escape sequences unescaped, to form the unicode string of the IRI. Relative IRI reference resolution is performed per Section 6.3. PNAME_NS prefix When used in a prefixID or sparqlPrefix production, the prefix is the potentially empty unicode string matching the first argument of the rule is a key into the namespaces map. IRI When used in a PrefixedName production, the iri is the value in the namespaces map corresponding to the first argument of the rule. PNAME_LN IRI A potentially empty prefix is identified by the first sequence, PNAME_NS. The namespaces map MUST have a corresponding namespace. The unicode string of the IRI is formed by unescaping the reserved characters in the second argument, PN_LOCAL, and concatenating this onto the namespace. @@ -1505,7 +1505,7 @@

Internet Media Type, File Extension and Macintosh File Type

".ttl"
Base URI:
-
The Turtle '@base <IRIref>' or 'BASE <IRIref>' term can change the current base URI for relative IRIrefs in the query language that are used sequentially later in the document.
+
The Turtle '@base <IRIref>' or 'BASE <IRIref>' term can change the current base URI for relative IRI references in the query language that are used sequentially later in the document.
Macintosh file type code(s):
"TEXT"
Person & email address to contact for further information: