W3C home > Mailing lists > Public > public-rdf-wg@w3.org > March 2012

Re: review comments of N-Triples in the Turtle document

From: Zhe Wu <alan.wu@oracle.com>
Date: Tue, 20 Mar 2012 11:05:49 -0700
Message-ID: <4F68C6FD.7020607@oracle.com>
To: public-rdf-wg@w3.org
Hi Gavin,

Please see my comments inline.

>> - Replace
>>           "N-Triples may also be provided as text/plain. When used in this
>> way N-Triples must
>>           use the escaped form of any character outside US-ASCII"
>>    with
>>           "When encoded using US-ASCII as specified in section 3 [REF1],
>> N-Triples should
>>            be provided as text/plain."
> This isn't exactly true. There is nothing wrong with encoding an
> N-Triples file using US-ASCII and serving as application/ntriples. The
> relationship goes the other direction. If you want to provide
> text/plain N-Triples you MUST use US-ASCII. If you want to provide
> US-ASCII you can use either text/plain, text/turtle, or
> application/ntriples.

I guess my question really is what do we gain from encoding using US-ASCII and serving
as application/ntriples?

>> - Add the following to the end of "See N-Triples Media Type for the media
>> type registration form."
>>    For maximum backward compatibility, users or applications may want to
>> choose US-ASCII
>>    encoding to serialize N-Triples.
> I don't think we should recommend providing any format in US-ASCII over UTF-8.

I don't think that sentence truly recommends US-ASCII over UTF-8.  It is important, in my opinion,
for us to point out non-trivial consequences caused by the changes we propose.

Assume a user serializes using UTF-8 encoding for non ASCII characters and the
new \ encoding for ', \b, and \f. Such a serialization will not work
with some of the existing tools, rapper 2-1.9.0 for example.

The proposed new sentence simply makes clear one important consequence.

>> - The language in [REF1] does not cover [A-Z] while the new grammar supports
>> upper case.
>>     Is this necessary?
> Yes. All script tag parts are mixed case and regions are uppercase.
> Some text explaining normalization for the test case format vs. dump
> format could be used, or we can simply reference the older N-Triples
> for test cases document.
> az-Latn-IR


>> - For some specific characters (within ASCII range), [REF1] uses the
>> following encoding:
>>    \t   \n   \r   \"   \\
>>     The new grammar seems to cover more. In particular,  \b  \f  \'  are
>> added.
>>     A consequence of this change is that a previously illegal syntax, like
>> the
>>     triple below, is now legal.
>>     <urn:s>  <http://abc.com/p>  "aa\'b" .
>>    It is important to have some text clearly explaining this new behavior.
> Sure.



>> [REF1] http://www.w3.org/TR/rdf-testcases/#ntriples
Received on Tuesday, 20 March 2012 18:06:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:12 UTC