2823 2006-02-11 00:35:30 +0000 RQ-146 needs clarification re. wildcards (ElementDeclarationsConsistent) 2006-06-12 16:32:49 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only Other All RESOLVED DUPLICATE 2544 needsDrafting P1 normal --- 1 cmsmcq ht www-xml-schema-comments oldest_to_newest 8188 0 cmsmcq 2006-02-11 00:35:30 +0000 This issue was originally reported by David Bau. Consider the following "tricky" indirect case involving a wildcard referencing a global element: <element name="a" type="string"/> <complexType name="example-2"> <sequence> <element name="a" type="int"/> <element name="whatever"/> <any namespace="##targetNamespace" processContents="lax"/> </sequence> </complexType> Clearly the local <a> and the indirect reference to the global <a> are "inconsistent" with each other within the content model of the above example but I'm not sure if the "directly, indirectly, or implicitly" language in the EDC rule captures this case. See mail from: David Bau. (http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003OctDec/0029.html) See reply from: from Henry Thompson. (http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003OctDec/0030.html) Proposals to discharge this requirement also cover RQ-17. (#restrictn-rules) This item was classified as Req in the meeting of 2004-03-12 (http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Mar/0033.html). This item was discussed in the meeting of 2004-04-09 (http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Apr/0178.html), in connection with RQ-17.. Various proposals to resolve this issue have been discussed, most recently in Toronto (November 2005); in Toronto the WG instructed the editors to prepare a proposal reflecting the agreement reached there. 9968 1 sandygao 2006-06-12 16:32:49 +0000 *** This bug has been marked as a duplicate of bug 2544 ***