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

Re: Review of Turtle doc (part 2)

From: Eric Prud'hommeaux <eric@w3.org>
Date: Mon, 9 Apr 2012 23:12:01 -0400
To: Zhe Wu <alan.wu@oracle.com>
Cc: public-rdf-wg@w3.org
Message-ID: <20120410031200.GA26827@w3.org>
* Zhe Wu <alan.wu@oracle.com> [2012-04-09 14:02-0700]
> 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.

I'm a strong advocate of single media type; encoding flexibility makes XML parsers very complex. That said, there may be use cases which motivate labeling
  <http://a.example/\u6587\u4EF6> <http://a.example/\u5A92\u9AD4\u985E\u578B> "application/n-triples;charset=us-ascii" .
as 7-bit safe and
  <http://a.example/\u6587\u4EF6> <http://a.example/媒體類型> "application/n-triples;charset=utf-8" .
as full UTF-8. A statement like "The content encoding of N-Triples is either UTF-8 or us-ascii" combined with an RFC2119 statement like "N-Triples parsers MUST parse UTF-8 documents" would accomplish this. Are there motivating use cases for this minor complexity? Does their value exceed the cost of possible divergence in N-Triples processors?


> 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.
> >
> >
> >
> >
> 
> 

-- 
-ericP
Received on Tuesday, 10 April 2012 03:12:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:04 UTC