Warning:
This wiki has been archived and is now read-only.

RDF 1.1 New Features and Migration Note

From RDF Working Group Wiki

Jump to: navigation, search

This page is an informal collection of notes for a possible WG Note.

Its purpose is to collect information on changes from RDF 1.0 to RDF 1.1.

See Sandro's slides at http://www.w3.org/2013/Talks/0603-rdf11/

1 Concepts and Abstract Syntax
2 Semantics
3 JSON-LD 1.0
4 JSON-LD 1.0 API
5 Turtle
6 TriG
7 N-Triples
8 N-Quads
9 RDF Schema

Concepts and Abstract Syntax

See http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/#change-log

Semantics

Most of the changes between RDF and RDF 1.1 do not have any effect on implementations of entailment, but there are a few minor changes.

The sequence in which the versions of entailment are defined has changed. Datatype entailment is now defined on top of simple entailment, and then RDF and RDFS entailment are defined. Datatype entailment formally refers to a set of 'recognized' datatypes, replacing the old datatype maps, but this does not have any effect on implementation.

RDF entailment has two required datatypes xsd:string and rdf:langString which must be recognized, but this doesn't appreciably add to RDF entailment as these two datatypes replace plain literals.

Literals formerly described as plain literals are now divided into xsd:string literals, for plain literals without language tags, and rdf:langString literals, for plain literals with language tags. Thus all literals have a type and there is no need for an implementation to have separate data structures for plain literals and datatyped literals, although rdf:langString is a special datatype as it has a language tag in addition to a lexical form and thus it requires special treatment. Implementations that have a special internal data structure for plain literals might not need to appreciably change. The zero Unicode character is not a valid element in xsd:string values, but was allowed in plain literals, so there is a minor change here.

One change that does affect entailment is that graphs containing invalid literals (e.g., "a"^^xsd:integer) are immediately inconsistent for recognized datatypes, even in sub-RDFS entailment regimes.

There is a list of XML Schema datatypes that are deemed suitable for use within RDF. They are all optional except for xsd:string.

The rdf:XMLLiteral datatype is now optional. rdf:HTML is a new optional datatype; implementation experience and illustrative tests are requested. (Note also that rdf:HTML has at-risk aspects concerning DOM4 normalization.) rdf:PlainLiteral is a newish optional datatype; implementation experience and illustrative tests are requested.

RDF 1.1 includes RDF Datasets. However, the semantics of RDF Datasets in RDF 1.1 is minimal and entailment per se is only defined on RDF graphs so there are no changes here.