I18n comments on XLink 1.1

You describe Attribute value defaulting only in terms of XML DTDs. Please add a note on attribute value defaulting with XML Schema and with RELAX NG (in DTD compatibility mode).

About the title-type element: You mention internationalization and localization as a motivation to use the title-type element, and give the examples of bidirectional contexts or East Asian languages. This is very good! Could you add a pointer to examples of such elements, e.g. the W3C ruby specification, the dir attribute in html or language identification via xml:lang?

You reference RFC 3987 and its escaping procedure. This is very good!

In this section you do not refer to the escaping procedure from RFC 3987 which you mentioned in sec. 5.4. Is there a reason for this?

Your reference to the superseded version of XPointer, and not to the XPointer Framework. Is there a reason for this?

Editorial: In the reference to IETF I-D XMT, you provide the name of the editors, in other IETF references you don't.

Editorial: Please refer to the Unicode standard as described in Character Model for the World Wide Web, i.e. with a generic reference to the Unicode standard:
The Unicode Consortium, The Unicode Standard, Version 4.1, ISBN 0-321-18578-1, as updated from time to time by the publication of new versions. (See http://www.unicode.org/unicode/standard/versions for the latest version and additional information on versions of the standard and of the Unicode Character Database).

Editorial: There is an entry for XLinkToRDF in the bibliography. It is not used in the main text.

In the appendix, you provide an XML DTD, an XML Schema and an RELAX NG schema for XLink 1.1. Nevertheless, the examples in the main text make use only of XML DTDs. It would be good if you (a) would provide examples for RELAX NG and XML Schema in the text as well, or (b) if that is too much effort, than at least provide an example for each schema language in Appendix C. Especially for the use case of Internationalization and Localization for the title-type element (sec. 5.1.4), this would be very helpful. An example does not need to, but could look like this:

<xs:schema
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:my="http://example.com/myns"
targetNamespace="http://example.com/myns"
elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:import namespace="http://www.w3.org/1999/xlink"
 schemaLocation="xlink1-1.xsd"/>
<!- This imports the XML Schema for XLink you provided in appendix C -->
<xs:element name="myDoc">
 <xs:complexType>
  <xs:complexContent>
   <xs:extension base="xlink:extended">
    <xs:sequence>
     <xs:element name="myTitle">
      <xs:complexType mixed="true">
       <xs:complexContent>
        <xs:restriction base="xlink:titleEltType">
         <xs:sequence>
          <xs:element name="ruby" minOccurs="0" maxOccurs="unbounded">
<!-- Here we have the ruby definition -->
          </xs:element>		
         </xs:sequence>
        </xs:restriction>
       </xs:complexContent>
      </xs:complexType>
     </xs:element>
    </xs:sequence>		
   </xs:extension>
  </xs:complexContent>
 </xs:complexType>
</xs:element>
</xs:schema>
				  

The hrefTypein the XML Schema and the href.att pattern in the RELAX NG schema are defined in terms of xs:anyURI. Please add a note that anyURI in its current version does not support the escaping rules of RFC 3987.