This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In bug 6010, John Arwe wrote: 3.10.1 The Wildcard Schema Component "The keywords defined and sibling allow a kind of wildcard which matches only elements not declared in the current schema ..." Given that "schema" is, according to 2.1 which has the closest thing I could find to a formal definition of this word, just a set of schema components, I'm not sure what the actual boundary for 'defined' is nor how interoperable its definition really is. A schema processor is allowed to put almost literally anything (extra, i.e. unused) into the schema (set of components) used for assessment, no? If there was some concept of a "minimal schema", at say schema document granularity, it might be clearer...of course then if someone re-factors the documents, ymmv. Conceptually I have no objection, I'm just not sure right now how wide its net casts. 3.10.1 The Wildcard Schema Component "The keywords defined and sibling allow a kind of wildcard which matches only elements not declared in the current schema ..." Similar question for sibling. This is somewhat better defined than schema, but the language seems loose. {ns constraint} clause 6 talks about the containing type decl; here, I wonder if that should read very literally, or to include all of what look like sibling elements in an instance but are attributed to {base type definition} items, transitively. Each of these paragraphs indicates a need for clarification. Editors to draft suitable clarifications.
As part of this exercise I wonder if the ##defined keyword should be renamed to something like ##definedGlobally as at the moment just looking at the keywords suggests that ##definedSibling is a sub-set of ##defined which I don't believe it is.
In August and September 2009 the XML Schema working group performed triage on the remaining open issues in a WBS poll [1], whose results are summarized at [2] and accepted formally at [3]. In the course of that triage we decided to close this issue without further action. Since this is a WG issue, not an external one, I'm going both to mark it resolved and to close it. [1] http://www.w3.org/2002/09/wbs/19482/200908CRissues/ [2] http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2009Sep/0005.html [3] http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2009Sep/att-0005/2009-09-11telcon.html#item04 (all links member-only)