This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1350 - please change URILiteral to IRILiteral
Summary: please change URILiteral to IRILiteral
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Don Chamberlin
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard: grammar
Keywords:
Depends on: 1354
Blocks: 1341
  Show dependency treegraph
 
Reported: 2005-05-11 04:39 UTC by Felix Sasaki
Modified: 2005-06-29 16:04 UTC (History)
0 users

See Also:


Attachments

Description Felix Sasaki 2005-05-11 04:39:19 UTC
http://www.w3.org/International/2005/02/xquery-review.html Comment ID: 5
Comment 1 Felix Sasaki 2005-05-18 19:07:38 UTC
(In reply to comment #0)
> http://www.w3.org/International/2005/02/xquery-review.html Comment ID: 5
For collations, namespaces, schemas, and so on, the production 141 "URILiteral
(app. A. 1) is used, which refers to a "StringLiteral". "URILiteral" should be
changed to "IRILiteral", and the reference section should contain an entry to
the IRI specification RFC3987. There should also be a clear indication how XML
Base affects collations, namespaces etc. Btw, you don't need to change the
underlying type system, but the name of the production 141.
Comment 2 Felix Sasaki 2005-05-30 08:28:53 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > http://www.w3.org/International/2005/02/xquery-review.html Comment ID: 5
> For collations, namespaces, schemas, and so on, the production 141 "URILiteral
> (app. A. 1) is used, which refers to a "StringLiteral". "URILiteral" should be
> changed to "IRILiteral", and the reference section should contain an entry to
> the IRI specification RFC3987. There should also be a clear indication how XML
> Base affects collations, namespaces etc. Btw, you don't need to change the
> underlying type system, but the name of the production 141.
> 

consensus of the i18n-core-wg, telecon 27 may 2005: IRI is now an official RFC,
please refer to it.
Comment 3 Don Chamberlin 2005-06-11 04:20:05 UTC
Felix,
In meetings on May 19 and June 7, the Query and XSLT working groups considered 
this comment. The working groups feel that it is undesirable to globally change 
all occurrences of "URI" to "IRI" because many terms such as "base URI" are in 
common use throughout the family of XML-related specifications. However, the 
working groups agreed to make the following changes:

(1) In the XPath and XQuery specifications, replace references to RFC 2396 with 
references to RFC 3986 and 3987.

(2) In the XPath and XQuery specifications, Section 2 (Basics), add the 
following paragraph: "Within this specification, the term URI refers to a 
Universal Resource Identifier as defined in RFC 3896 and extended in RFC 3897 
with the new name IRI. The term URI has been retained in preference to IRI to 
avoid introducing new names for concepts such as 'Base URI' that are defined or 
referenced across the whole family of XML specifications."

(3) In the XQuery specification, Section 2.4.5 (URI Literals), add the 
following note: "The xs:anyURI type is designed to anticipate the introduction 
of Internationalized Resource Identifiers (IRI's) as defined in [RFC 3987]."

We hope that these changes will address your concerns. Please let us know 
whether you find these changes to be an acceptable response to your comment.

Regards,
Don Chamberlin (for the Query and XSLT working groups)
Comment 4 Felix Sasaki 2005-06-22 08:36:51 UTC
(In reply to comment #3)
> Felix,
> In meetings on May 19 and June 7, the Query and XSLT working groups considered 
> this comment. The working groups feel that it is undesirable to globally 
change 
> all occurrences of "URI" to "IRI" because many terms such as "base URI" are in 
> common use throughout the family of XML-related specifications. However, the 
> working groups agreed to make the following changes:
> 
> (1) In the XPath and XQuery specifications, replace references to RFC 2396 
with 
> references to RFC 3986 and 3987.
> 
> (2) In the XPath and XQuery specifications, Section 2 (Basics), add the 
> following paragraph: "Within this specification, the term URI refers to a 
> Universal Resource Identifier as defined in RFC 3896 and extended in RFC 3897 
> with the new name IRI. The term URI has been retained in preference to IRI to 
> avoid introducing new names for concepts such as 'Base URI' that are defined 
or 
> referenced across the whole family of XML specifications."
> 
> (3) In the XQuery specification, Section 2.4.5 (URI Literals), add the 
> following note: "The xs:anyURI type is designed to anticipate the introduction 
> of Internationalized Resource Identifiers (IRI's) as defined in [RFC 3987]."
> 
> We hope that these changes will address your concerns. Please let us know 
> whether you find these changes to be an acceptable response to your comment.
> 
> Regards,
> Don Chamberlin (for the Query and XSLT working groups)
> 

consenus of the i18n-core-wg (telecon 21 May 2005):
The working group is VERY HAPPY about your changes! We thank you very much and 
regared the bug as closed.
Regards,
Felix Sasaki
Comment 5 Paul Cotton 2005-06-24 23:57:29 UTC
See 1508:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1508

for the discussion of the following sub-point of this original comment:

"There should also be a clear indication how XML
Base affects collations, namespaces etc."

/paulc