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

PROPOSED to RESOLVE ISSUE-127 with Canonical N-Triples

From: Gavin Carothers <gavin@carothers.name>
Date: Fri, 5 Jul 2013 11:26:32 -0700
Message-ID: <CAPqY83yAp-b=Or1uQnSqX_6cpS+_mYwi7hPq+yu7h5S7L+W0Ag@mail.gmail.com>
To: RDF-WG WG <public-rdf-wg@w3.org>, Gregory Williams <greg@evilfunhouse.com>, "public-rdf-comments@w3.org" <public-rdf-comments@w3.org>
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:26:59 UTC

This archive was generated by hypermail 2.3.1 : Friday, 5 July 2013 18:27:00 UTC