proposed resolution for ill-typed literal issue (RDF Concepts issue 60)

PROPOSAL:  Change the requirements for handling ill-typed literals so that 
implementations may drop triples containing literals that are ill-typed for 
datatypes that they recognize.

The relevant wording is in RDF 1.2 Concepts and Syntax:

If the literal's datatype IRI is in the set of recognized datatype IRIs, let d 
be the referent of the datatype IRI.
If the literal's lexical form is in the lexical space of d, then the literal 
value is the result of applying the lexical-to-value mapping of d to the 
lexical form.
Otherwise, the literal is ill-typed and no literal value can be associated 
with the literal. Such a case produces a semantic inconsistency but is not 
syntactically ill-formed. Implementations MUST accept ill-typed literals and 
produce RDF graphs from them. Implementations MAY produce warnings when 
encountering ill-typed literals.

A possible change if the proposal is accepted is:

...
Otherwise, the literal is ill-typed and no literal value can be associated 
with the literal. Such a case produces a semantic inconsistency but is not 
syntactically ill-formed. Implementations MUST accept ill-typed literals from 
their recognized datatypes and produce RDF graphs for inputs that contain 
them.  Implementations MAY produce warnings when encountering ill-typed 
literals from their recognized datatypes.  Implementations MAY exclude triples 
that contain ill-typed literals from their recognized datatypes from the RDF 
graphs they produce and SHOULD produce warnings when this happens.
NOTE:  Implementations MUST accept all literals with datatypes that are not in 
their recognized datatypes.


See https://github.com/w3c/rdf-concepts/issues/60 for discussion of the topic.

Received on Thursday, 7 November 2024 19:27:49 UTC