draft-ietf-iri-3987bis-11.txt   draft-ietf-iri-3987bis-12.txt 
Internationalized Resource Identifiers M. Duerst Internationalized Resource Identifiers M. Duerst
(iri) Aoyama Gakuin University (iri) Aoyama Gakuin University
Internet-Draft M. Suignard Internet-Draft M. Suignard
Obsoletes: 3987 (if approved) Unicode Consortium Obsoletes: 3987 (if approved) Unicode Consortium
Intended status: Standards Track L. Masinter Intended status: Standards Track L. Masinter
Expires: September 13, 2012 Adobe Expires: January 17, 2013 Adobe
March 12, 2012 July 16, 2012
Internationalized Resource Identifiers (IRIs) Internationalized Resource Identifiers (IRIs)
draft-ietf-iri-3987bis-11 draft-ietf-iri-3987bis-12
Abstract Abstract
This document defines the Internationalized Resource Identifier (IRI) This document defines the Internationalized Resource Identifier (IRI)
protocol element, as an extension of the Uniform Resource Identifier protocol element, as an extension of the Uniform Resource Identifier
(URI). An IRI is a sequence of characters from the Universal (URI). An IRI is a sequence of characters from the Universal
Character Set (Unicode/ISO 10646). Grammar and processing rules are Character Set (Unicode/ISO 10646). Grammar and processing rules are
given for IRIs and related syntactic forms. given for IRIs and related syntactic forms.
Defining IRI as a new protocol element (rather than updating or Defining IRI as a new protocol element (rather than updating or
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Guidelines are provided for the use and deployment of IRIs and Guidelines are provided for the use and deployment of IRIs and
related protocol elements when revising protocols, formats, and related protocol elements when revising protocols, formats, and
software components that currently deal only with URIs. software components that currently deal only with URIs.
This document is part of a set of documents intended to replace RFC This document is part of a set of documents intended to replace RFC
3987. 3987.
RFC Editor: Please remove the next paragraph before publication. RFC Editor: Please remove the next paragraph before publication.
This (and several companion documents) are intended to obsolete RFC This document, and several companion documents, are intended to
3987, and also move towards IETF Draft Standard. For discussion and obsolete RFC 3987. For discussion and comments on these drafts,
comments on these drafts, please join the IETF IRI WG by subscribing please join the IETF IRI WG by subscribing to the mailing list
to the mailing list public-iri@w3.org, archives at public-iri@w3.org, archives at
http://lists.w3.org/archives/public/public-iri/. For a list of open http://lists.w3.org/archives/public/public-iri/. For a list of open
issues, please see the issue tracker of the WG at issues, please see the issue tracker of the WG at
http://trac.tools.ietf.org/wg/iri/trac/report/1. For a list of http://trac.tools.ietf.org/wg/iri/trac/report/1. For a list of
individual edits, please see the change history at individual edits, please see the change history at
http://trac.tools.ietf.org/wg/iri/trac/log/draft-ietf-iri-3987bis. http://trac.tools.ietf.org/wg/iri/trac/log/draft-ietf-iri-3987bis.
This document is available in (line-printer ready) plaintext ASCII
and PDF. It is also available in HTML from
http://www.sw.it.aoyama.ac.jp/2012/pub/
draft-ietf-iri-3987bis-12.html, and in UTF-8 plaintext from http://
www.sw.it.aoyama.ac.jp/2012/pub/draft-ietf-iri-3987bis-12.utf8.txt.
While all these versions are identical in their technical content,
the HTML, PDF, and UTF-8 plaintext versions show non-Unicode
characters directly. This often makes it easier to understand
examples, and readers are therefore advised to consult these versions
in preference or as a supplement to the ASCII version.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 13, 2012. This Internet-Draft will expire on January 17, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 8, line 52 skipping to change at page 8, line 52
1.4. Notation 1.4. Notation
RFCs and Internet Drafts currently do not allow any characters RFCs and Internet Drafts currently do not allow any characters
outside the US-ASCII repertoire. Therefore, this document uses outside the US-ASCII repertoire. Therefore, this document uses
various special notations for such characters in examples. various special notations for such characters in examples.
In text, characters outside US-ASCII are sometimes referenced by In text, characters outside US-ASCII are sometimes referenced by
using a prefix of 'U+', followed by four to six hexadecimal digits. using a prefix of 'U+', followed by four to six hexadecimal digits.
To represent characters outside US-ASCII in examples, this document To represent characters outside US-ASCII in a document format that is
uses 'XML Notation'. limited to US-ASCII, this document uses 'XML Notation'. XML Notation
uses a leading '&#x', a trailing ';', and the hexadecimal number of
XML Notation uses a leading '&#x', a trailing ';', and the the character in the UCS in between. For example, Я stands for
hexadecimal number of the character in the UCS in between. For CYRILLIC CAPITAL LETTER YA. In this notation, an actual '&' is
example, я stands for CYRILLIC CAPITAL LETTER YA. In this denoted by '&'. This notation is only used in the ASCII
notation, an actual '&' is denoted by '&'. version(s) of this document, because in the other versions, non-ASCII
characters are used directly.
To denote actual octets in examples (as opposed to percent-encoded To denote actual octets in examples (as opposed to percent-encoded
octets), the two hex digits denoting the octet are enclosed in "<" octets), the two hex digits denoting the octet are enclosed in "<"
and ">". For example, the octet often denoted as 0xc9 is denoted and ">". For example, the octet often denoted as 0xc9 is denoted
here as <c9>. here as <c9>.
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in [RFC2119]. and "OPTIONAL" are to be interpreted as described in [RFC2119].
skipping to change at page 14, line 20 skipping to change at page 14, line 20
removed some characters, and the interpretation of reserved removed some characters, and the interpretation of reserved
characters will have already been done (with the syntactic reserved characters will have already been done (with the syntactic reserved
characters outside of the IRI component). This mapping is defined characters outside of the IRI component). This mapping is defined
for all sequences of Unicode characters, whether or not they are for all sequences of Unicode characters, whether or not they are
valid for the component in question. valid for the component in question.
For each character which is not allowed anywhere in a valid URI apply For each character which is not allowed anywhere in a valid URI apply
the following steps. the following steps.
Convert to UTF-8: Convert the character to a sequence of one or more Convert to UTF-8: Convert the character to a sequence of one or more
octets using UTF-8 [RFC3629]. octets using UTF-8 [STD63].
Percent encode: Convert each octet of this sequence to %HH, where HH Percent encode: Convert each octet of this sequence to %HH, where HH
is the hexadecimal notation of the octet value. The hexadecimal is the hexadecimal notation of the octet value. The hexadecimal
notation SHOULD use uppercase letters. (This is the general URI notation SHOULD use uppercase letters. (This is the general URI
percent-encoding mechanism in Section 2.1 of [RFC3986].) percent-encoding mechanism in Section 2.1 of [RFC3986].)
Note that the mapping is an identity transformation for parsed URI Note that the mapping is an identity transformation for parsed URI
components of valid URIs, and is idempotent: applying the mapping a components of valid URIs, and is idempotent: applying the mapping a
second time will not change anything. second time will not change anything.
skipping to change at page 15, line 46 skipping to change at page 15, line 46
3.4.3. Additional Considerations 3.4.3. Additional Considerations
Note: Domain Names may appear in parts of an IRI other than the Note: Domain Names may appear in parts of an IRI other than the
ireg-name part. It is the responsibility of scheme-specific ireg-name part. It is the responsibility of scheme-specific
implementations (if the Internationalized Domain Name is part of implementations (if the Internationalized Domain Name is part of
the scheme syntax) or of server-side implementations (if the the scheme syntax) or of server-side implementations (if the
Internationalized Domain Name is part of 'iquery') to apply the Internationalized Domain Name is part of 'iquery') to apply the
necessary conversions at the appropriate point. Example: Trying necessary conversions at the appropriate point. Example: Trying
to validate the Web page at to validate the Web page at
http://r&#xE9;sum&#xE9;.example.org would lead to an IRI of http://r&#xE9;sum&#xE9;.example.org would lead to an IRI of
http://validator.w3.org/check?uri=http%3A%2F%2Fr&#xE9;sum&#xE9;. http://validator.w3.org/check?uri=http%3A%2F%2Fr&#xE9;sum&#xE9;
example.org, which would convert to a URI of .example.org, which would convert to a URI of
http://validator.w3.org/check?uri=http%3A%2F%2Fr%C3%A9sum%C3%A9. http://validator.w3.org/check?uri=http%3A%2F%2Fr%C3%A9sum%C3%A9.
example.org. The server-side implementation is responsible for example.org. The server-side implementation is responsible for
making the necessary conversions to be able to retrieve the Web making the necessary conversions to be able to retrieve the Web
page. page.
Note: In this process, characters allowed in URI references and Note: In this process, characters allowed in URI references and
existing percent-encoded sequences are not encoded further. (This existing percent-encoded sequences are not encoded further. (This
mapping is similar to, but different from, the encoding applied mapping is similar to, but different from, the encoding applied
when arbitrary content is included in some part of a URI.) For when arbitrary content is included in some part of a URI.) For
example, an IRI of example, an IRI of
"http://www.example.org/red%09ros&#xE9;#red" (in XML notation) is "http://www.example.org/red%09ros&#xE9;#red" (in XML notation) is
converted to converted to
"http://www.example.org/red%09ros%C3%A9#red", not to something "http://www.example.org/red%09ros%C3%A9#red", not to something
like like
"http%3A%2F%2Fwww.example.org%2Fred%2509ros%C3%A9%23red". "http%3A%2F%2Fwww.example.org%2Fred%2509ros%C3%A9%23red".
3.5. Mapping query components 3.5. Mapping query components
For compatibility with existing deployed HTTP infrastructure, the For compatibility with existing deployed HTTP infrastructure, the
following special case applies for schemes "http" and "https" and following special case applies for the schemes "http" and "https"
IRIs whose origin has a document charset other than one which is UCS- when an IRI is found in a document whose charset is not based on UCS
based (e.g., UTF-8 or UTF-16). In such a case, the "query" component (e.g., not UTF-8 or UTF-16). In such a case, the "query" component
of an IRI is mapped into a URI by using the document charset rather of an IRI is mapped into a URI by using the document charset rather
than UTF-8 as the binary representation before pct-encoding. This than UTF-8 as the binary representation before pct-encoding. This
mapping is not applied for any other scheme or component. mapping is not applied for any other scheme or component.
3.6. Mapping IRIs to URIs 3.6. Mapping IRIs to URIs
The mapping from an IRI to URI is accomplished by applying the The mapping from an IRI to URI is accomplished by applying the
mapping above (from IRI to URI components) and then reassembling a mapping above (from IRI to URI components) and then reassembling a
URI from the parsed URI components using the original punctuation URI from the parsed URI components using the original punctuation
that delimited the IRI components. that delimited the IRI components.
skipping to change at page 19, line 15 skipping to change at page 19, line 15
4. http://www.example.org/D%FCrst 4. http://www.example.org/D%FCrst
5. http://www.example.org/D%FCrst 5. http://www.example.org/D%FCrst
6. http://www.example.org/D%FCrst 6. http://www.example.org/D%FCrst
The following example contains "%e2%80%ae", which is the percent- The following example contains "%e2%80%ae", which is the percent-
encoded encoded
UTF-8 character encoding of U+202E, RIGHT-TO-LEFT OVERRIDE. The UTF-8 character encoding of U+202E, RIGHT-TO-LEFT OVERRIDE. The
direct use of this character is forbiddin in an IRI. Therefore, the direct use of this character is forbidden in an IRI. Therefore, the
corresponding octets are re-percent-encoded in step 4. This example corresponding octets are re-percent-encoded in step 4. This example
shows that the case (upper- or lowercase) of letters used in percent- shows that the case (upper- or lowercase) of letters used in percent-
encodings may not be preserved. The example also contains a encodings may not be preserved. The example also contains a
punycode-encoded domain name label (xn--99zt52a), which is not punycode-encoded domain name label (xn--99zt52a), which is not
converted. converted.
1. http://xn--99zt52a.example.org/%e2%80%ae 1. http://xn--99zt52a.example.org/%e2%80%ae
2. http://xn--99zt52a.example.org/<e2><80><ae> 2. http://xn--99zt52a.example.org/<e2><80><ae>
skipping to change at page 36, line 48 skipping to change at page 36, line 48
PubliclyAvailableStandards/ PubliclyAvailableStandards/
c051273_ISO_IEC_10646_2011(E).zip>. c051273_ISO_IEC_10646_2011(E).zip>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3491] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep [RFC3491] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep
Profile for Internationalized Domain Names (IDN)", Profile for Internationalized Domain Names (IDN)",
RFC 3491, March 2003. RFC 3491, March 2003.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005. RFC 3986, January 2005.
[RFC5890] Klensin, J., "Internationalized Domain Names for [RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document Framework",
RFC 5890, August 2010. RFC 5890, August 2010.
[RFC5891] Klensin, J., "Internationalized Domain Names in [RFC5891] Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", RFC 5891, August 2010. Applications (IDNA): Protocol", RFC 5891, August 2010.
[RFC5892] Faltstrom, P., "The Unicode Code Points and [RFC5892] Faltstrom, P., "The Unicode Code Points and
Internationalized Domain Names for Applications (IDNA)", Internationalized Domain Names for Applications (IDNA)",
RFC 5892, August 2010. RFC 5892, August 2010.
[STD63] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[STD68] Crocker, D. and P. Overell, "Augmented BNF for Syntax [STD68] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[UNIV6] The Unicode Consortium, "The Unicode Standard, Version [UNIV6] The Unicode Consortium, "The Unicode Standard, Version
6.0.0 (Mountain View, CA, The Unicode Consortium, 2011, 6.1.0 (Mountain View, CA, The Unicode Consortium, 2012,
ISBN 978-1-936213-01-6)", October 2010. ISBN 978-1-936213-02-3)", 2012.
[UTR15] Davis, M. and M. Duerst, "Unicode Normalization Forms", [UTR15] Davis, M. and M. Duerst, "Unicode Normalization Forms",
Unicode Standard Annex #15, March 2008, Unicode Standard Annex #15, March 2008,
<http://www.unicode.org/unicode/reports/tr15/ <http://www.unicode.org/unicode/reports/tr15/
tr15-23.html>. tr15-23.html>.
12.2. Informative References 12.2. Informative References
[Bidi] Duerst, M., Masinter, L., and A. Allawi, "Guidelines for [Bidi] Duerst, M., Masinter, L., and A. Allawi, "Guidelines for
Internationalized Resource Identifiers with Bi-directional Internationalized Resource Identifiers with Bi-directional
Characters (Bidi IRIs)", draft-ietf-iri-bidi-guidelines-02 Characters (Bidi IRIs)", draft-ietf-iri-bidi-guidelines-02
(work in progress), March 2012. (work in progress), March 2012.
[CharMod] Duerst, M., Yergeau, F., Ishida, R., Wolf, M., and T. [CharMod] Duerst, M., Yergeau, F., Ishida, R., Wolf, M., and T.
Texin, "Character Model for the World Wide Web: Resource Texin, "Character Model for the World Wide Web 1.0:
Identifiers", World Wide Web Consortium Candidate Resource Identifiers", W3C Candidate Recommendation CR-
Recommendation, November 2004, charmod-resid-20041122, November 2004,
<http://www.w3.org/TR/charmod-resid>. <http://www.w3.org/TR/2004/CR-charmod-resid/>.
[Duerst97] [Duerst97]
Duerst, M., "The Properties and Promises of UTF-8", Proc. Duerst, M., "The Properties and Promises of UTF-8", Proc.
11th International Unicode Conference, San Jose , 11th International Unicode Conference, San Jose ,
September 1997, <http://www.ifi.unizh.ch/mml/mduerst/ September 1997, <http://www.ifi.unizh.ch/mml/mduerst/
papers/PDF/IUC11-UTF-8.pdf>. papers/PDF/IUC11-UTF-8.pdf>.
[Equivalence] [Equivalence]
Masinter, L. and M. Duerst, "Equivalence and Masinter, L. and M. Duerst, "Equivalence and
Canonicalization of Internationalized Resource Identifiers Canonicalization of Internationalized Resource Identifiers
(IRIs)", draft-ietf-iri-comparison-01 (work in progress), (IRIs)", draft-ietf-iri-comparison-01 (work in progress),
March 2012. March 2012.
[Gettys] Gettys, J., "URI Model Consequences", [Gettys] Gettys, J., "URI Model Consequences",
<http://www.w3.org/DesignIssues/ModelConsequences>. <http://www.w3.org/DesignIssues/ModelConsequences>.
[HTML4] Raggett, D., Le Hors, A., and I. Jacobs, "HTML 4.01 [HTML4] Raggett, D., Le Hors, A., and I. Jacobs, "HTML 4.01
Specification", World Wide Web Consortium Recommendation, Specification", W3C Recommendation REC-html401-19991224,
December 1999, December 1999, <http://www.w3.org/TR/1999/REC-html401>.
<http://www.w3.org/TR/html401/appendix/notes.html#h-B.2>.
[RFC2130] Weider, C., Preston, C., Simonsen, K., Alvestrand, H., [RFC2130] Weider, C., Preston, C., Simonsen, K., Alvestrand, H.,
Atkinson, R., Crispin, M., and P. Svanberg, "The Report of Atkinson, R., Crispin, M., and P. Svanberg, "The Report of
the IAB Character Set Workshop held 29 February - 1 March, the IAB Character Set Workshop held 29 February - 1 March,
1996", RFC 2130, April 1997. 1996", RFC 2130, April 1997.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2192] Newman, C., "IMAP URL Scheme", RFC 2192, September 1997. [RFC2192] Newman, C., "IMAP URL Scheme", RFC 2192, September 1997.
skipping to change at page 38, line 49 skipping to change at page 38, line 48
[RFC2640] Curtin, B., "Internationalization of the File Transfer [RFC2640] Curtin, B., "Internationalization of the File Transfer
Protocol", RFC 2640, July 1999. Protocol", RFC 2640, July 1999.
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", RFC 3987, January 2005. Identifiers (IRIs)", RFC 3987, January 2005.
[RFC4395bis] [RFC4395bis]
Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
Registration Procedures for New URI/IRI Schemes", Registration Procedures for New URI/IRI Schemes",
draft-ietf-iri-4395bis-irireg-03 (work in progress), draft-ietf-iri-4395bis-irireg-04 (work in progress),
July 2011. December 2011.
[RFC5122] Saint-Andre, P., "Internationalized Resource Identifiers [RFC5122] Saint-Andre, P., "Internationalized Resource Identifiers
(IRIs) and Uniform Resource Identifiers (URIs) for the (IRIs) and Uniform Resource Identifiers (URIs) for the
Extensible Messaging and Presence Protocol (XMPP)", Extensible Messaging and Presence Protocol (XMPP)",
RFC 5122, February 2008. RFC 5122, February 2008.
[RFC6055] Thaler, D., Klensin, J., and S. Cheshire, "IAB Thoughts on [RFC6055] Thaler, D., Klensin, J., and S. Cheshire, "IAB Thoughts on
Encodings for Internationalized Domain Names", RFC 6055, Encodings for Internationalized Domain Names", RFC 6055,
February 2011. February 2011.
skipping to change at page 39, line 26 skipping to change at page 39, line 24
[UNIXML] Duerst, M. and A. Freytag, "Unicode in XML and other [UNIXML] Duerst, M. and A. Freytag, "Unicode in XML and other
Markup Languages", Unicode Technical Report #20, World Markup Languages", Unicode Technical Report #20, World
Wide Web Consortium Note, June 2003, Wide Web Consortium Note, June 2003,
<http://www.w3.org/TR/unicode-xml/>. <http://www.w3.org/TR/unicode-xml/>.
[UTR36] Davis, M. and M. Suignard, "Unicode Security [UTR36] Davis, M. and M. Suignard, "Unicode Security
Considerations", Unicode Technical Report #36, Considerations", Unicode Technical Report #36,
August 2010, <http://unicode.org/reports/tr36/>. August 2010, <http://unicode.org/reports/tr36/>.
[XLink] DeRose, S., Maler, E., and D. Orchard, "XML Linking [XLink] DeRose, S., Maler, E., Orchard, D., and N. Walsh, "XML
Language (XLink) Version 1.0", World Wide Web Linking Language (XLink) Version 1.1", W3C
Consortium REC-xlink-20010627, June 2001, Recommendation REC-xlink11-20100506, May 2010,
<http://www.w3.org/TR/xlink/#link-locators>. <http://www.w3.org/TR/xlink11/#link-locators>.
[XML1] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and [XML1] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium REC-xml-20081116, Edition)", W3C Recommendation REC-xml-20081126,
November 2008, <http://www.w3.org/TR/REC-xml>. November 2008, <http://www.w3.org/TR/2008/REC-xml/>.
[XMLSchema] [XMLSchema]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes", Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
World Wide Web Consortium REC-xmlschema-2-20041028, Second Edition", W3C Recommendation REC-xmlschema-2-
May 2001, <http://www.w3.org/TR/xmlschema-2/#anyURI>. 20041028, October 2004,
<http://www.w3.org/TR/xmlschema-2/#anyURI>.
[XPointer] [XPointer]
Grosso, P., Maler, E., Marsh, J., and N. Walsh, "XPointer Grosso, P., Maler, E., Marsh, J., and N. Walsh, "XPointer
Framework", World Wide Web Consortium REC-xptr-framework- Framework", W3C Recommendation REC-xptr-framework-
20030325, March 2003, 20030325, March 2003,
<http://www.w3.org/TR/xptr-framework/#escaping>. <http://www.w3.org/TR/xptr-framework/#escaping>.
Authors' Addresses Authors' Addresses
Martin Duerst (Note: Please write "Duerst" with u-umlaut wherever Martin J. Duerst (Note: Please write "Duerst" with u-umlaut wherever
possible, for example as "D&#252;rst" in XML and HTML) possible, for example as "D&#252;rst" in XML and HTML.)
Aoyama Gakuin University Aoyama Gakuin University
5-10-1 Fuchinobe 5-10-1 Fuchinobe
Sagamihara, Kanagawa 229-8558 Chuo-ku
Sagamihara, Kanagawa 252-5258
Japan Japan
Phone: +81 42 759 6329 Phone: +81 42 759 6329
Fax: +81 42 759 6495 Fax: +81 42 759 6495
Email: duerst@it.aoyama.ac.jp Email: duerst@it.aoyama.ac.jp
URI: http://www.sw.it.aoyama.ac.jp/D%C3%BCrst/ URI: http://www.sw.it.aoyama.ac.jp/D%C3%BCrst/
(Note: This is the percent-encoded form of an IRI) (Note: This is the percent-encoded form of an IRI)
Michel Suignard Michel Suignard
Unicode Consortium Unicode Consortium
 End of changes. 22 change blocks. 
49 lines changed or deleted 62 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/