W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > April 2003

RE: tex-01 new proposal

From: <Patrick.Stickler@nokia.com>
Date: Mon, 7 Apr 2003 16:31:16 +0300
Message-ID: <A03E60B17132A84F9B4BB5EEDE57957B01B90C8E@trebe006.europe.nokia.com>
To: <GK@NineByNine.org>, <jjc@hplb.hpl.hp.com>, <dave.beckett@bristol.ac.uk>
Cc: <w3c-rdfcore-wg@w3.org>



> -----Original Message-----
> From: ext Graham Klyne [mailto:GK@NineByNine.org]
> Sent: 07 April, 2003 11:18
> To: Jeremy Carroll; dave.beckett@bristol.ac.uk
> Cc: w3c-rdfcore-wg@w3.org
> Subject: RE: tex-01 new proposal 
> 
> 
> 
> At 15:33 04/04/2003 +0200, Jeremy Carroll wrote:
> > > On this one, I don't see any harm in having parsers transpose lang
> > > tags to lowercase and NTriples only having lowercase lang tags.
> > >
> >I do not like NTriples being changed in this way, that seems 
> to make things
> >worse from the point of view of tex's comment.
> 
> I note that the role of (RDF/XML) parsers is to create an 
> abstract syntax 
> graph from RDF/XML input, not N-triples.  I think *requiring* 
> parsers to 
> case-normalize is over-specification, and I think the 
> case-agnostic view 
> for the abstract syntax proposed by Jeremy is about right. [**]
> 
> But adopting a convention for N-triples, which is a concrete 
> representation 
> of an abstract syntax graph, that case-insensitive values are 
> presented as 
> lower case seems to address the other concerns I have heard.

This sounds like an excellent middle ground.

Patrick


> #g
> --
> 
> [**]  Note: this doesn't mean that parsers MUST NOT 
> case-normalize where 
> appropriate:  that is an implementation decision.
> 
> 
> -------------------
> Graham Klyne
> <GK@NineByNine.org>
> PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E
> 
> 
Received on Monday, 7 April 2003 09:31:32 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:56:53 EDT