This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4684 - Can sml:keyref refer to an xs:key/unique?
Summary: Can sml:keyref refer to an xs:key/unique?
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P1 normal
Target Milestone: LC
Assignee: Kirk Wilson
QA Contact: SML Working Group discussion list
Depends on: 4995 5130
  Show dependency treegraph
Reported: 2007-06-21 17:26 UTC by Sandy Gao
Modified: 2007-10-16 20:56 UTC (History)
0 users

See Also:


Description Sandy Gao 2007-06-21 17:26:58 UTC
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">
   <sml:keyref name="myRef refer="tns:myKey">

 <xs:key name="myKey">
Comment 1 Valentina Popescu 2007-08-28 13:48:15 UTC
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
Comment 2 Valentina Popescu 2007-08-28 14:50:17 UTC
there are too many unknowns about this one; move target to LC
Comment 3 Kirk Wilson 2007-09-12 12:37:55 UTC
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 for complete proposal
Comment 4 Kirk Wilson 2007-10-04 17:22:51 UTC
Or does the resolution of 5130 depend on how we choose to resolve this issue?  
Comment 5 Kirk Wilson 2007-10-12 14:59:00 UTC
Revised proposal for discussion at second Redmond F2F
Comment 6 Kumar Pandit 2007-10-16 20:46:21 UTC
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.