- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Nov 2010 18:50:24 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6089
Henry S. Thompson <ht@inf.ed.ac.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ht@inf.ed.ac.uk
--- Comment #9 from Henry S. Thompson <ht@inf.ed.ac.uk> 2010-11-14 18:50:23 UTC ---
The WG asked me to write explaining our position, which is against applying any
real constraint to the value space of anyURI. Before doing so, however, I
wonder if the WG has misunderstood the Murata's original request. He cites the
following phrase (from 1.0 2nd edition)
. . . the value fulfills the role of a URI as defined
by [RFC 2396], as amended by [RFC 2732].
But the relevant section now reads
[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). This type
should be used when the value fulfills the role of an IRI, as defined in [RFC
3987] or its successor(s) in the IETF Standards Track.
Note: IRIs may be used to locate resources or simply to identify them. In the
case where they are used to locate resources using a URI, applications should
use the mapping from anyURI values to URIs given by the reference escaping
procedure defined in [LEIRI] and in Section 3.1 Mapping of IRIs to URIs of
[RFC 3987] or its successor(s) in the IETF Standards Track. This means that
a wide range of internationalized resource identifiers can be specified when
an anyURI is called for, and still be understood as URIs per [RFC 3986] and
its successor(s).
It seems to me that this wording addresses Murata's concerns -- Murata, is that
in fact the case?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 14 November 2010 18:50:26 UTC