- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 30 Jan 2007 15:44:24 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4174 jonathan.robie@datadirect.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Comment #1 from jonathan.robie@datadirect.com 2007-01-30 15:44 ------- Hi John, On behalf of the XML Query Working Group, I'd like to thank you for this comment, which generated a rather long and interesting discussion. In the end, we decided to make no change for the following reasons: - If we keep the original type of the element then we encounter some difficult corner cases; for instance, do we keep that type if the element is renamed? - Local types are not designed for use in root level elements. Arguably, the schema itself identifies which types should be allowed at the root level. - There is an easy workaround. Although you can not do a transform in strict mode to create elements with local types at the top level, you can certainly do this in other validation modes, and you can certainly validate the result as long as the query result places all locally declared types in a context where they are allowed to exist in a validated document. So we do not feel this needs to be fixed.
Received on Tuesday, 30 January 2007 15:44:32 UTC