Re: Review of Turtle doc (part 2)

On Mon, Apr 9, 2012 at 2:02 PM, Zhe Wu <alan.wu@oracle.com> wrote:
> Hi Andy,
>
> On 4/9/2012 9:08 AM, Andy Seaborne wrote:
>>
>> ...
>>
>>
>> == 12.1 Media Type and Content Encoding
>>
>> Why is is "application/ntriples" and not "application/n-triples" given the
>> language is called "N-triples"?  It would avoid confusion to make it
>> "n-triples".
>>
>> "The content encoding of N-Triples is always UTF-8."
>>  Not true - if its "text/plain" then it's ASCII.
>
>
> According to a local Unicode expert, US-ASCII is a binary subset of UTF-8 so
> it is UTF-8.

Correct. You can serve application/ntriples that contains no bytes
outside of the US-ASCII range. However a conforming
'application/ntriples' parser should not barf on characters that are
outside the US-ASCII range.

--Gavin

>
> Thanks,
>
> Zhe
>
>
>>
>> "As N-Triples is a subset of Turtle it may also be provided as
>> text/turtle. "
>>  please remove.
>> If using "text/turtle;charset=utf-8" then it's Turtle, not N-triples.
>>
>> Maybe less formal:  "note that when parsed by a Turtle parser, data in the
>> N-Triples format will produce exactly the same triples as the restricted
>> N-triples language".
>>
>> == 12.3
>>
>> needed?
>>
>> == 12.4
>>
>> Make the same style as Turtle.
>>
>> Use full names, not "subj", "pred" etc.
>>
>> remove @terminals
>>
>> Numbering.
>>
>> BLANK_NODE_LABEL is not PN_LOCAL from Turtle anymore.
>> PN_CHARS_U
>> PN_CHARS are also not from Turtle anymore.
>>
>> Use of "\\" when "\" is meant.
>>
>> Remove @pass.
>>
>> == Section 13
>>
>> Not reviewed.
>>
>> == Section A (Turtle Media Type)
>>
>> Puts charset under "optional" - isn't it required?
>>
>> Change control: needs updating.
>>
>> == Section B (N-Triples media type)
>>
>> charset not mentioned under parameters.
>>
>>
>>
>>
>
>

Received on Monday, 9 April 2012 21:20:19 UTC