- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Jan 2013 17:54:51 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20634 --- Comment #3 from Michael Kay <mike@saxonica.com> --- Some further observations: (a) we say in 4.11: [Definition: A schema import imports the element declarations, attribute declarations, and type definitions from a schema into the in-scope schema definitions. For each user-defined generalized atomic type in the schema, schema import also adds a corresponding constructor function. ]. So it seems that at least in the case where there is an "import schema" declaration, we already import the type xs:error (because it is present in every schema), and we also add a corresponding constructor function xs:error() whose behaviour is rather similar to fn:error(). If there is no "import schema" declaration, the status quo is less clear. (b) since xs:error is an empty union, and since a user-defined XSD 1.1 schema can include an empty union type, there are no new semantic problems - there is no doubt that a query can import an empty union type and that its semantics must be well-defined, the only question is whether it imports the particular empty union type called xs:error. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 22 January 2013 17:54:52 UTC