W3C home > Mailing lists > Public > public-cwm-talk@w3.org > July to September 2009

N3 spec. probable error

From: Barclay, Daniel <daniel@fgm.com>
Date: Wed, 5 Aug 2009 12:06:02 -0400
Message-ID: <4A79ADEA.7010706@fgm.com>
To: <public-cwm-talk@w3.org>
Regarding the N3 specification currently at

In the Grammar section, it says:

     The fragment identifier part of a URI where the rest of
     the URI is that of an information resource which has a
     representation in N3 is used to identify any thing
     whatever, abstract or concrete.

Note that the current wording (unintentionally) says that it is just
the fragment identifier part of URI that identifies some thing, when
in reality is it the _whole_ URI that identifies it.

Additionally, the restriction to having an information resource (let
alone the restriction to having one with an N3 representation) seems
excessively restrictive.  Why can't a URI used in an N3 document
refer to a resource described in an RDF/XML document?

(Plain text sometimes corrupted to HTML "courtesy" of Microsoft Exchange.) [F]
Received on Wednesday, 5 August 2009 16:06:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:06 UTC