This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
For example, is the following allowed? Or should sml:keyref only be able to refer to sml:key/unique? <xs:element name="e" type="t"> <xs:annotation> <xs:appinfo> <sml:keyref name="myRef refer="tns:myKey"> ... </sml:keyref> </xs:appinfo> </xs:annotation> <xs:key name="myKey"> ... </xs:key> </xs:element>
A good scenario for reusing xs:key/unique is in legacy documents; you may want to reuse an existing schema key/unique and refer to it from another document using the sml:keyref element
there are too many unknowns about this one; move target to LC
Recommendation has been proposed to add an optional scope attribute to sml:keyref that implicit contains a deref() and refers to the element in which the xs:key/xs:unique is defined. See http://lists.w3.org/Archives/Public/public-sml/2007Sep/0077.html for complete proposal
Or does the resolution of 5130 depend on how we choose to resolve this issue?
Revised proposal for discussion at second Redmond F2F http://lists.w3.org/Archives/Public/public-sml/2007Oct/0083.html
decision at redmond f2f: We decided to keep SML and XSD id constratints separate. Bug 5130 will marked editorial so that this can be clarified in the spec.