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

RE: NTriples changes for URI-refs - rdf-charmod-uri

From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Date: Fri, 26 Apr 2002 12:00:55 +0100
To: "Dave Beckett" <dave.beckett@bristol.ac.uk>
Cc: "w3c-rdfcore-wg" <w3c-rdfcore-wg@w3.org>
Message-ID: <JAEBJCLMIFLKLOJGMELDCENNCDAA.jjc@hplb.hpl.hp.com>
Dave:
>
> old text:
>
>   absoluteURI  ::=  character+ with escapes as defined in
> section URI References
>   -- http://www.w3.org/2001/08/rdf-test/#absoluteURI
>
>   3.3 URI References
>
>   URI references are defined and encoded using the rules defined in
>   [Charmod] section Character Encoding in URI References.  That is,
>   disallowed characters are represented in UTF-8 and then encoded
>   using the %HH format, where HH is the byte value expressed using
>   hexadecimal notation.
>   -- http://www.w3.org/2001/08/rdf-test/#sec-uri-encoding
>
>
> might be changed to:
>   -----------------------------------------------------------------------
>   absoluteURI  ::=  character+ with escapes as defined in
> section URI References
>   -- http://www.w3.org/2001/08/rdf-test/#absoluteURI
>
>   3.3 URI References
>
>   URI references are sequences of US-ASCII character productions
>   encoding Unicode characters that form an Internationalized
>   Resource Identifier (IRI) [IRIs].
>
>   Disallowed IRI characters (see [IRIs] 2.3 part B) are represented in
>   UTF-8 and then encoded using the %HH format, where HH is the byte
>   value expressed using hexadecimal notation.
>
>   Characters above the US-ASCII range are made available by the \u or
>   \U escapes as described in section Strings for ranges [#x80-#xFFFF]
>   and [#x10000-#x10FFFF] respectively.
>
>   Characters [#x0-#x1F] and #x7F are forbidden in URI references.
>
>   -- http://www.w3.org/2001/08/rdf-test/#sec-uri-encoding
>   -----------------------------------------------------------------------
>
>
> along with a new reference
>
>   -----------------------------------------------------------------------
>   [IRIs]
>      Duerst and Suignard, Internationalized Resource Identifiers (IRI)
>      IETF Internet Draft (work in progress), April 17 2002,
>        http://www.ietf.org/internet-drafts/draft-duerst-iri-00.txt
>
>   -- in section http://www.w3.org/2001/08/rdf-test/#ref_normative
>
>   -----------------------------------------------------------------------
>
> but I'm sure Jeremy could write something better :)
>

I am looking at
http://www.w3.org/TR/xlink/#link-locators

[[[

3.3 URIRefs



The uriref production expands to a string which must be a URI reference as
defined in [IETF RFC 2396], or must result in a URI reference after the
standard escaping procedure is applied. The procedure is applied when
passing the URI reference to a URI resolver. The standard escaping
procedure is described in [IETF RFC 2396] using UTF-8 as the character
encoding.

>
>   Characters above the US-ASCII range are made available by the \u or
>   \U escapes as described in section Strings for ranges [#x80-#xFFFF]
>   and [#x10000-#x10FFFF] respectively.
>
>   Characters [#x0-#x1F] and #x7F are forbidden in URI references.
>

]]]

We could add a non-normative link to xlink for the full procedure, we could
just copy-paste from xlink, there is also the rfc 2732 issue that my text
doesn't deal with.

I am hoping we will have time to consider the choice at the telecon today.
I am fairly easy as to whether to have the link to IRI or not ...

I believe Dave's proposed text and my proposed text differ in their
treatment of bidi IRIs!
(not that I've read that bit of Martin Dürst's draft).

Jeremy
Received on Friday, 26 April 2002 07:01:46 EDT

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