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 1441 - [XQX] complex type derivation vs substitution group
Summary: [XQX] complex type derivation vs substitution group
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQueryX 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-13 23:34 UTC by Michael Rys
Modified: 2005-08-08 23:16 UTC (History)
0 users

See Also:


Attachments

Description Michael Rys 2005-05-13 23:34:22 UTC
During the review, we discussed whether we prefer one or the other. It quickly 
showed, that there are use cases and needs for both. E.g., complex type 
derivation is easier to map with popular type to object model mappers while 
substitution provides for better XPath discoverability of the information.

We propose (after talking to one of the editors) that the spec should provide 
both approaches with some guidelines on when one may be preferable over the 
other and provide a transform between them (as it was available in previous 
internal drafts)
Comment 1 Jim Melton 2005-06-27 00:38:17 UTC
The Query WG has considered your comment and has determined that two approaches
are unnecessary and undesirable, but agrees that a substitution group approach
is preferred.  A new XQueryX schema has been developed that replaces the former
complex type derivation approach with a substitution group approach.  When a new
edition of the XQueryX spec is published, we hope that you will review it and,
if, you find the changes satisfactory, mark this comment as CLOSED. 

We appreciate your feedback on the XML Query specifications. Please let us know
if this response is satisfactory. If not, please respond to this message,
explaining your concerns.

Jim Melton
On behalf of the XML Query Working Group