- From: <noah_mendelsohn@us.ibm.com>
- Date: Wed, 6 Aug 2008 10:29:30 -0400
- To: John Bradley <john.bradley@wingaa.com>
- Cc: "Booth, David (HP Software - Boston)" <dbooth@hp.com>, "Henry S. Thompson" <ht@inf.ed.ac.uk>, Julian Reschke <julian.reschke@gmx.de>, www-tag@w3.org
John Bradley writes:
> The definition of "anyURI" changes slightly to include the
> mapping of http: IRI according to RFC3987 This allows for the
> ireg-name component to be mapped via RFC3490 for schemes using
> domain names.
OK, good.
> In XML schema 1.1 that is almost done [http://www.w3.
> org/TR/xmlschema11-2/]
> [...] allows almost all http: scheme IRI to work as "anyURI",
> relative and null IRI are excluded so it is still a sub set,
> though a much larger one than before.
Hmm, I don't see where relative or "null" are excluded. The
specification for that datatype says [1]:
"[Definition:] anyURI represents an Internationalized Resource
Identifier Reference (IRI). An anyURI value can be absolute >>or
relative<<, and may have an optional fragment identifier (i.e., it may be
an IRI Reference)."
Was there something else you meant when you said that "relative [is]
excluded"? I read this as explicitly allowing relative. As to "null"
IRIs, the word null does not appear in RFC 3987 [1] or in RFC 3986 [2] for
that matter, but RFC 3987 includes the following grammar:
IRI-reference = IRI / irelative-ref
irelative-ref = irelative-part [ "?" iquery ] [ "#" ifragment ]
irelative-part = "//" iauthority ipath-abempty
/ ipath-absolute
/ ipath-noscheme
/ ipath-empty
ipath-empty = 0<ipchar>
This seems to me to indicate that an IRI Reference, as required by XML
Schema 1.1, can indeed be an ipath-empty, I.e. the null string. Am I
still missing something?
Noah
[1] http://www.ietf.org/rfc/rfc3987.txt
[2] http://www.ietf.org/rfc/rfc3986.txt
--------------------------------------
Noah Mendelsohn
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
Received on Wednesday, 6 August 2008 14:28:56 UTC