W3C home > Mailing lists > Public > www-rdf-comments@w3.org > January to March 2002

Re: Proposed NTriples changes for literal notation

From: Dave Beckett <dave.beckett@bristol.ac.uk>
Date: Thu, 14 Mar 2002 08:16:49 +0000
To: Tim Berners-Lee <timbl@w3.org>
cc: www-rdf-comments <www-rdf-comments@w3.org>, w3c-rdfcore-wg <w3c-rdfcore-wg@w3.org>
Message-ID: <11048.1016093809@tatooine.ilrt.bris.ac.uk>
>>>Tim Berners-Lee said:
> It has been very convenient that NTriples have been a subset of N3.
> These proposals mark a significant parting of the ways as they stand.
> 
> The "-" character in N3 I had intended to use in the future as an operator.
> 
> The "." character is often used immedaitely after the last token in a
> statement.
> 
> Therefore,  "foo"en would be much preferable to "foo"-en  which looks
> certianly to me like a subtraction.

However, the language codes can have '-' in them such as en-us, en-uk
and so on.  How do you suggest we get round that if we changed to
  "foo"en-us
?

Maybe something more awkward:
  "foo"X"en-us"
where X is another character?

Or a bracketing pair?: "foo"("en-us")

Or a function/predicate-like thing: literal("foo", "en-us")

Lots of choices; but compatibility with N3 remains *very* useful, so
that's why I tried to ask N3 developers before we changed this.


> And insisting on a space before "." is both messy, and error prone, as well
> as not current practice.

That can be fixed as I proposed, by specifying the allowed set of
chars in a language string rather than just specifying a terminating
condition (next space).  Unless we go to other delimiters as above.

<snip/>

Dave
Received on Thursday, 14 March 2002 03:16:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 September 2012 14:16:30 GMT