ISSUE-58: PlainLiteral and TypedLiteral value for strings

plain/typed literal encoding

PlainLiteral and TypedLiteral value for strings

State:
CLOSED
Product:
RDFa 1.1 API
Raised by:
Nathan Rixham
Opened on:
2010-10-28
Description:
We need to define what the `value` + toString() of TypedLiteral and PlainLiteral should be, especially PlainLiteral.

If somebody implements an N-Triples parser, then the value of Plain Literals will be ascii safe, likewise with Turtle and unicode + special chars (\n etc) in single quoted values. We need to clarify if the value held by plain literal will be converted to UTF8 and essentially decoded to a native string, or whether it will remain in it's encoded form.
Related Actions Items:
No related actions
Related emails:
  1. PROPOSAL to close ISSUE-58: PlainLiteral and TypedLiteral value for strings (from msporny@digitalbazaar.com on 2010-11-10)
  2. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from nathan@webr3.org on 2010-10-29)
  3. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from msporny@digitalbazaar.com on 2010-10-29)
  4. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from msporny@digitalbazaar.com on 2010-10-28)
  5. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from shane@aptest.com on 2010-10-28)
  6. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from nathan@webr3.org on 2010-10-28)
  7. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from nathan@webr3.org on 2010-10-28)
  8. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from shane@aptest.com on 2010-10-28)
  9. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from nathan@webr3.org on 2010-10-28)
  10. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from tai@g5n.co.uk on 2010-10-28)
  11. RDFa WG telecon minutes for 2010-10-28 (from msporny@digitalbazaar.com on 2010-10-28)
  12. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from nathan@webr3.org on 2010-10-28)
  13. Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from tai@g5n.co.uk on 2010-10-28)
  14. RDFa API new Issues - summary (from nathan@webr3.org on 2010-10-28)
  15. ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API] (from sysbot+tracker@w3.org on 2010-10-28)

Related notes:

Not an issue

For the triple:
<#nbsp> <http://example.com/lit> "Hello \n\tWorld."

object.value will hold the true value:

"Hello
World."

not an encoded value.

Nathan Rixham, 28 Oct 2010, 16:23:28

The Note mentioning that this is not an issue is incorrect. A proposal and public review period is required to close the issue.

Manu Sporny, 29 Oct 2010, 12:35:41

Closed after time allotted in the PROPOSAL to close the issue and no objections to the PROPOSAL.

Manu Sporny, 2 Dec 2010, 14:43:30

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 58.html,v 1.1 2015/03/27 14:12:25 vivien Exp $