W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2008

RE: TAG finding on "Associating Resources with Namespaces"

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Wed, 25 Jun 2008 11:43:32 -0700
To: "Phillips, Addison" <addison@amazon.com>, "www-tag@w3.org" <www-tag@w3.org>
CC: "chairs@w3.org" <chairs@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <4D66CCFC0B64BA4BBD79D55F6EBC22575343724261@NA-EXMSG-C103.redmond.corp.microsoft.com>
> the finding uses the term "URI" throughout where it appears to mean an IRI reference.

Other W3C specifications have had to deal with this kind of problem.  For example the “XQuery 1.0 and XPath 2.0 Functions and Operators” Recommendation [1] includes the following clarifying definitions:

[Definition] URI and URI reference

Within this specification, the term "URI" refers to Universal Resource Identifiers as defined in [RFC 3986]<http://www.w3.org/TR/2007/REC-xpath-functions-20070123/#rfc3986> and extended in [RFC 3987]<http://www.w3.org/TR/2007/REC-xpath-functions-20070123/#rfc3987> with a new name "IRI". The term "URI Reference", unless otherwise stated, refers to a string in the lexical space of the xs:anyURI datatype as defined in [XML Schema Part 2: Datatypes Second Edition]<http://www.w3.org/TR/2007/REC-xpath-functions-20070123/#xmlschema-2>. Note that this means, in practice, that where this specification requires a "URI Reference", an IRI as defined in [RFC 3987]<http://www.w3.org/TR/2007/REC-xpath-functions-20070123/#rfc3987> will be accepted, provided that other relevant specifications also permit an 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. Note also that the definition of xs:anyURI is a wider definition than the definition in [RFC 3987]<http://www.w3.org/TR/2007/REC-xpath-functions-20070123/#rfc3987>; for example it does not require non-ASCII characters to be escaped.


[1] http://www.w3.org/TR/2007/REC-xpath-functions-20070123/

Paul Cotton, Microsoft Canada

17 Eleanor Drive, Ottawa, Ontario K2E 6A3

Tel: (425) 705-9596 Fax: (425) 936-7329

-----Original Message-----
From: chairs-request@w3.org [mailto:chairs-request@w3.org] On Behalf Of Phillips, Addison
Sent: Wednesday, June 25, 2008 2:34 PM
To: www-tag@w3.org
Cc: chairs@w3.org; public-i18n-core@w3.org
Subject: RE: TAG finding on "Associating Resources with Namespaces"

(personal comment)


Although the underlying references (GRRDL, RDDL) either directly reference IRI or do so via XML Base, etc., the finding uses the term "URI" throughout where it appears to mean an IRI reference. It might be useful to note this somewhere, avoiding the seemingly unavoidable question of whether the "nature key URI" is, in fact, an instance of (LE?)IRI.

Best Regards,


Addison Phillips

Globalization Architect -- Lab126

Chair -- W3C Internationalization WG

Internationalization is not a feature.

It is an architecture.

> -----Original Message-----

> From: chairs-request@w3.org [mailto:chairs-request@w3.org] On

> Behalf Of Williams, Stuart (HP Labs, Bristol)

> Sent: Wednesday, June 25, 2008 8:54 AM

> To: www-tag@w3.org

> Subject: TAG finding on "Associating Resources with Namespaces"



> The TAG has approved the publication of "Associating Resources with

> Namespaces" as a TAG finding.


> The document is available at:


>   http://www.w3.org/2001/tag/doc/nsDocuments/


> It is edited by Henry S. Thompson and Norman Walsh.  The abstract

> reads as follows:


>  This Finding addresses the question of how ancillary information

>  (schemas, stylesheets, documentation, etc.) can be associated with

> a

>  namespace.


> Other TAG findings can be found at:


>   http://www.w3.org/2001/tag/findings


> Stuart Williams,

> TAG co-chair

> --

> Hewlett-Packard Limited registered Office: Cain Road, Bracknell,

> Berks RG12 1HN

> Registered No: 690597 England


> [Tracker: ISSUE-8]


Received on Wednesday, 25 June 2008 18:44:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:03 UTC