W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > January 2006

Re: Agenda for XML Core WG telcon of 2006 January 18

From: François Yergeau <francois@yergeau.com>
Date: Wed, 18 Jan 2006 09:28:05 -0800
Cc: public-xml-core-wg@w3.org
Message-id: <43CE7AA5.4030906@yergeau.com>

François Yergeau a écrit :
> ===========================================================
> XML 1.0, 4.2.2 
> [http://www.w3.org/TR/2004/REC-xml-20040204/#sec-external-ent]
> XML 1.1, 4.2.2 
> [http://www.w3.org/TR/2004/REC-xml11-20040204/#sec-external-ent]
> ===========================================================
> 
> System identifiers (and other XML strings meant to be used as URI 
> references)

That sentence is an editing leftover, please ignore it.  The rest of the 
messag is my proposal.

> 
> [Definition: *XML resource identifiers* are XML string meant to be used 
> as IRI references or URI references].  System identifers are XML 
> resource identifiers.  An XML resource identifier may contain characters 
> that, according to [IETF RFC 3897] and [IETF RFC 3986], must be escaped 
> before the string can be used to retrieve the referenced resource. To 
> convert an XML resource identifier to an IRI reference, the following 
> characters must be escaped:
> 
>     * the control characters #x0 to #x1F and #x7F (most of which cannot 
> appear in XML)
>     * space #x20
> 
>       Note:
> 
>       Authors are advised to avoid unescaped spaces, as XML Schema has 
> identified them as an interoperability risk.
> 
>     * the delimiters < #x3C, > #x3E and " #x22
>     * the unwise characters { #x7B, } #x7D, | #x7C, \ #x5C, ^ #x5E and ` 
> #x60
> 
> These characters are escaped by applying to them steps 2.1 to 2.3 of 
> Section 3.1 of [IETF RFC 3987].
> 
> If necessary for the implementation, an IRI reference is converted to a 
> URI reference by following the prescriptions of Section 3.1 of [IETF RFC 
> 3987]. This conversion MUST be performed only when absolutely necessary 
> and as late as possible in a processing chain. In particular, neither 
> the process of converting a relative IRI to an absolute one nor the 
> process of passing a IRI reference to a process or software component 
> responsible for dereferencing it SHOULD trigger escaping.
> 
> 
> ===========================================================
> XLink 1.1, 5.4 
> [http://www.w3.org/TR/2005/WD-xlink11-20050707/#link-locators]
> ===========================================================
> 
> The value of the href attribute is an XML resource identifer as defined 
> in [XML 1.1], which must be an IRI reference as defined in [IETF RFC 
> 3987] or must result in an IRI reference after the escaping procedure 
> described in [XML 1.1] is applied.  If necessary for the implementation, 
> the value may be further converted to a URI reference as described in 
> [XML 1.1].
> 
> 
> ===========================================================
> XML Base 1.0, 3 [http://www.w3.org/TR/2001/REC-xmlbase-20010627/#syntax]
> ===========================================================
> 
> The value of this attribute is an XML resource identifer as defined in 
> [XML 1.1], which is interpreted as an IRI Reference as defined in RFC 
> 3987 [IETF RFC 3987], after the escaping procedure described in [XML 
> 1.1] is applied.  If necessary for the implementation, the value may be 
> further converted to a URI reference as described in [XML 1.1].
> 
> 
> ===========================================================
> XInclude 1.0, 4.1.1 [http://www.w3.org/TR/2004/REC-xinclude-20041220/#IRIs]
> ===========================================================
> 
> The value of this attribute is an XML resource identifer as defined in 
> [XML 1.1], which is interpreted as an IRI Reference as defined in RFC 
> 3987 [IETF RFC 3987], after the escaping procedure described in [XML 
> 1.1] is applied.  If necessary for the implementation, the value may be 
> further converted to a URI reference as described in [XML 1.1].
> 
> 
> 
> 
> 
> 
Received on Wednesday, 18 January 2006 17:28:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:33 GMT