RE: Addendum to XLink 1.1 appendix C

I have a concern.

If we are going to add this, why shouldn't we add
a note on how to use XLink in SVG?  Or how to do
something else using XLink?

This sounds like something the I18N group should
put in some Note or document of theirs, not in
the XLink spec.  I fear this opens us up to requests 
to add all other sorts of "here's how you would do X
using XLink" examples to the base XLink spec.  Doing
this wasn't in our XLink 1.1 requirements document.

So while I don't have anything in particular against
the details of I18N's request, I'm not sure it's really
wise to start down this path at all at the going-to-CR
stage.

Am I over-reacting, or do others share my concern?

paul

> -----Original Message-----
> From: public-xml-core-wg-request@w3.org 
> [mailto:public-xml-core-wg-request@w3.org] On Behalf Of Norman Walsh
> Sent: Wednesday, 2006 January 18 15:22
> To: public-xml-core-wg@w3.org
> Cc: Henry Thompson
> Subject: Addendum to XLink 1.1 appendix C
> 
> Henry,
> 
> The I18N folks would like this addition to XLink 1.1 Appendix C.
> Does it look OK to you? (To everyone else?)
> 
> <div2 id="sample-ruby">
> <head>Sample XML Schema with Ruby</head>
> 
> <p>The following <bibref ref="xmlschema-1"/> demonstrates how the
> XLink 1.1 schema could be extended to support <bibref ref="ruby"/>
> in XLink title elements in an extended link.</p>
> 
> <p>It is provided only as a convenience for application developers; it
> has no normative status.</p>
> 
> <eg><![CDATA[<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"/>
> 
> <xs:element name="myExtendedLink">
>  <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">
>             <!-- Define the content of your ruby element here -->
>           </xs:element>		
>          </xs:sequence>
>         </xs:restriction>
>        </xs:complexContent>
>       </xs:complexType>
>      </xs:element>
>     </xs:sequence>		
>    </xs:extension>
>   </xs:complexContent>
>  </xs:complexType>
> </xs:element>
> </xs:schema>]]></eg>
> 
> </div2>
> 
> 
>                                         Be seeing you,
>                                           norm
> 
> -- 
> Norman.Walsh@Sun.COM / XML Standards Architect / Sun 
> Microsystems, Inc.
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution is 
> prohibited.
> If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
>

Received on Thursday, 19 January 2006 15:46:41 UTC