W3C home > Mailing lists > Public > public-rdf-comments@w3.org > July 2013

Re: PROPOSED to RESOLVE ISSUE-127 with Canonical N-Triples

From: David Booth <david@dbooth.org>
Date: Fri, 05 Jul 2013 14:47:35 -0400
Message-ID: <51D714C7.1020109@dbooth.org>
To: Gavin Carothers <gavin@carothers.name>
CC: RDF-WG WG <public-rdf-wg@w3.org>, Gregory Williams <greg@evilfunhouse.com>, "public-rdf-comments@w3.org" <public-rdf-comments@w3.org>
Gavin,

Don't you mean "MUST" instead of "SHOULD" in all of the below, in order 
to be considered *canonical*?

David

On 07/05/2013 02:26 PM, Gavin Carothers wrote:
> https://www.w3.org/2011/rdf-wg/track/issues/127 states that the new
> N-Triples specification doesn't provide for the old functionality of a
> given triple having one and only one way to write it down. The current
> draft of N-Triples has added a Canonical N-Triples definition to the
> conformance section.
>
> A *canonical N-Triple document* is a *N-Triple document* with additional
> constraints:
>
>   * Space between terms (|WS+|) /SHOULD/ be a single space, (|U+0020|).
>   * Space after or before terms (|WS*|) /SHOULD/ be empty.
>   * |HEX| /SHOULD/ use only uppercase letters (|[A-F]|).
>   * Characters not allowed directly in STRING_LITERAL_QUOTE (|U+0022|,
>     |U+005C|, |U+000A|, |U+000D|) /SHOULD/ use |ECHAR| not |UCHAR|.
>   * Characters /SHOULD/ be represented directly and not by |UCHAR|.
>
> This is NOT the same as the current definition in RDF Test Cases as it
> prefers the direct representation of characters over the use of escape
> sequences. It also specifies the white space rules.
>
>
> --Gavin
>
>
Received on Friday, 5 July 2013 18:48:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:57 UTC