[Bug 5289] "##defined" in wildcards

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5289





------- Comment #4 from sandygao@ca.ibm.com  2007-12-10 15:01 -------
In the bug description:

> Arguably the "effect at a distance" of "##defined" is not new, it already
> exists for processContents="strict". However, I believe that the type
> subsumption rules for processContents="strict" do not take into account the
> actual set of element declarations that a wildcard is capable of matching,
> because they do not affect local validity of an element against the wildcard.

The subsumption rules do take into account "strict", in a nontrivial way. If
base has a strict wildcard, and the derived has a local element without a
matching global, then the restriction is invalid; when you add a matching
global, the restriction may become valid.

The reason the restriction (without a global) is invalid is because base
requires xsi:type and derived doesn't.

Received on Monday, 10 December 2007 15:01:37 UTC