Hi all,
I'm looking at 3.4.2.3.3 Mapping Rules for Content Type Property of
Complex Content.
The branch under 6.1 is the only case that allows the type being defined
to pick up the openContent of the base type. However, whenever 5.2
applies (the wildcard element is based on the schema's
defaultOpenContent), 6.1 does not apply. So, if I have a
defaultOpenContent, then in many cases of complex type extension, the
new type will not inherit the openContent of its base type. Am I
reading that right? Is that the intention? I would think that the
openContent of the base type should take precedence over the default.
If the default open content is more restrictive than the base open
content, then one would be forced to put an acceptable explicit
openContent into the derived type; otherwise, the rules in "Derivation
Valid (extension)" will be violated.
It looks like the behavior for restrictions is similar, except that in
that case, 6.1 would have caused the derived type to have openContent of
"absent", while 5.2 may again prevent this by supplying the default
openContent.
Regards,
Kevin
