- From: <bugzilla@jessica.w3.org>
- Date: Mon, 10 Oct 2011 19:18:23 +0000
- To: public-xml-schema-testsuite@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13760
Sandy Gao <sandygao@ca.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #4 from Sandy Gao <sandygao@ca.ibm.com> 2011-10-10 19:18:21 UTC ---
> open032 has been modified to test the intended condition in a different way.
Trying to understand what constraint is violated by open032. It now has
<xs:openContent mode="interleave">
<xs:any notNamespace="http://open.com/"/>
</xs:openContent>
which will be merged with the base open content
<xs:openContent mode="interleave">
<xs:any namespace="http://open.com/" processContents="lax"/>
</xs:openContent>
to form an "interleave" open content that allows all namespaces. This satisfies
the relevant bullets in
http://www.w3.org/TR/xmlschema11-1/#cos-ct-extends
1.4.3.2.2.3 One or more of the following is true:
1.4.3.2.2.3.1 B.{content type}.{open content} (call it BOT) is ·absent·.
1.4.3.2.2.3.2 T.{content type}.{open content} (call it EOT) has {mode}
interleave.
1.4.3.2.2.3.3 Both BOT and EOT have {mode} suffix.
1.4.3.2.2.4 If neither BOT nor EOT is ·absent·, then BOT.{wildcard}.{namespace
constraint} is a subset of EOT.{wildcard}.{namespace constraint}, as defined by
Wildcard Subset (§3.10.6.2).
Changing the derived "interleave" to "suffix" would make the schema invalid.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 10 October 2011 19:18:26 UTC