|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Question on id constraints
1. It is not necessary for the pk to be defined earlier in the schema file according to an example from the W3C. In the example that they give they create a keyref that refers to another labeled "state" which doesn't occur until much later. <xs:keyref name="vehiclestate" refer="state">
.... <xs:element name="root">
<xs:key name="state">
I would assume that the reasoning for this is that the key must be defined within context that it is in and not within a special order. If there is a key with respect to an element then it must be defined with in that element definition. If the ordering mattered then that would limit the potency of xml. Say for example a element has a key reference to another key within another element and that element has a key reference to a key within the first element, then there would be no way to define this. 2. No it is not required for pk to be defined within the same element as the keyref. If you think of the element definition as a database table and the pk representing a primary key, then it wouldn't make sense for you to define a key reference to that key within the same table. Instead the more likely use of key references is to refer to a key within another table (or element within this case). I hope that this information helped,
"Anderson, John" wrote:
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








