ISSUE-109: What's the consequence of a literal being ill-typed?

ill-typed-so-what

What's the consequence of a literal being ill-typed?

State:
CLOSED
Product:
RDF Semantics
Raised by:
Richard Cyganiak
Opened on:
2012-11-09
Description:
(Raising and issue on this for referencing in the upcoming new Concepts WD)

What's the relevance of the distinction between “graphs containing ill-typed literals” and “inconsistent graphs” in the Semantics?

The text stresses that the presence of an ill-typed literals does not constitute an inconsistency. But why does the distinction matter? Is there any reason anybody needs to know about this distinction who isn't interested in the arcana of the model theory?

From the perspective of someone who authors RDF data, or works with RDF data, they both seem like belonging to the same class of problem, and I'm a bit at a loss as to how to explain the difference.

What should an implementation do? Should authors avoid generating such graphs? Should consumers reject it? Is an implementation that rejects ill-formed xsd:dates conforming?
Related Actions Items:
No related actions
Related emails:
  1. proposal for ISSUE-109 ill-typed literals (from pfpschneider@gmail.com on 2013-04-17)
  2. Re: Agenda for 17 April 2013 (from david@3roundstones.com on 2013-04-15)
  3. Re: Agenda for 17 April 2013 (from pfpschneider@gmail.com on 2013-04-15)
  4. ISSUE-109 Re: Agenda 10 Apr telecon (from pfpschneider@gmail.com on 2013-04-10)
  5. Re: how to make ill-typed literals inconsistent - ISSUE 109 (from richard@cyganiak.de on 2013-01-16)
  6. Intent to close ISSUE-109 (from markus.lanthaler@gmx.net on 2012-12-18)
  7. JSON-LD Telecon Minutes for 2012-12-18 (from msporny@digitalbazaar.com on 2012-12-18)
  8. Re: Agenda: JSON-LD Telecon - Tuesday, December 18th 2012 (from francois@joshfire.com on 2012-12-18)
  9. Re: Agenda: JSON-LD Telecon - Tuesday, December 18th 2012 (from gregg@greggkellogg.net on 2012-12-17)
  10. Agenda: JSON-LD Telecon - Tuesday, December 18th 2012 (from msporny@digitalbazaar.com on 2012-12-17)
  11. RDF Concepts draft ready; overview of open issues (from richard@cyganiak.de on 2012-11-21)
  12. Re: [All] Agenda for 21 Nov (from alexhall@revelytix.com on 2012-11-20)
  13. Re: [All] Agenda for 21 Nov (from david@3roundstones.com on 2012-11-20)
  14. Re: [All] Agenda for 21 Nov (from phayes@ihmc.us on 2012-11-17)
  15. Re: [All] Agenda for 21 Nov (from richard@cyganiak.de on 2012-11-17)
  16. Re: [All] Agenda for 21 Nov (from phayes@ihmc.us on 2012-11-16)
  17. Re: [All] Agenda for 21 Nov (from richard@cyganiak.de on 2012-11-16)
  18. Re: Ill-typed vs. inconsistent? (from phayes@ihmc.us on 2012-11-13)
  19. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from antoine.zimmermann@emse.fr on 2012-11-13)
  20. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from richard@cyganiak.de on 2012-11-13)
  21. Re: Ill-typed vs. inconsistent? (from richard@cyganiak.de on 2012-11-13)
  22. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from phayes@ihmc.us on 2012-11-13)
  23. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from phayes@ihmc.us on 2012-11-13)
  24. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from antoine.zimmermann@emse.fr on 2012-11-13)
  25. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from phayes@ihmc.us on 2012-11-13)
  26. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from richard@cyganiak.de on 2012-11-12)
  27. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from pierre-antoine.champin@liris.cnrs.fr on 2012-11-12)
  28. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from richard@cyganiak.de on 2012-11-12)
  29. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from pierre-antoine.champin@liris.cnrs.fr on 2012-11-11)
  30. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from richard@cyganiak.de on 2012-11-11)
  31. Re: RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from pierre-antoine.champin@liris.cnrs.fr on 2012-11-11)
  32. RDF-ISSUE-109 (ill-typed-so-what): What's the consequence of a literal being ill-typed? [RDF Concepts] (from sysbot+tracker@w3.org on 2012-11-09)

Related notes:

Re-assigning the issue to RDF Semantics, as consensus seems to be forming around addressing this by a change in the semantics.

Richard Cyganiak, 16 Jan 2013, 17:56:25

RESOLVED: Close ISSUE-109 by making ill-typed literals not denote and requiring that RDF implementations accept ill-typed literals and produce RDF graphs from them, possibly producing a warning. http://lists.w3.org/Archives/Public/public-rdf-wg/2013Apr/0117.html
https://www.w3.org/2013/meeting/rdf-wg/2013-04-24#resolution_3

David Wood, 7 May 2013, 14:18:28

Display change log ATOM feed


Guus Schreiber <guus.schreiber@vu.nl>, Chair, Ivan Herman <ivan@w3.org>, Sandro Hawke <sandro@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 109.html,v 1.1 2014-07-09 12:17:54 carine Exp $