- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 Jun 2012 15:52:37 +0000
- To: public-xml-schema-testsuite@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17607
Summary: test "s3_4_2_4ii08s" of set "defaultAttributesApply"
invalid
Product: XML Schema Test Suite
Version: 2006-11-06
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: IBM tests
AssignedTo: cmsmcq@blackmesatech.com
ReportedBy: xml.dev@altova.com
QAContact: public-xml-schema-testsuite@w3.org
In my opinion test "s3_4_2_4ii08s" and "s3_4_2_4ii10s" of set
"defaultAttributesApply" should be invalid (or their second ts:schemaDocument
element should be removed).
Both of them have two ts:schemaDocument elements. The schema referenced by the
second one is overridden by an xs:override in the first one. So listing both of
them as ts:schemaDocument in the ts:schemaTest element causes duplicate
components in the resulting schema (the overridden component clashes with the
original "imported" by the ts:schemaDocument element).
See the last note in http://www.w3.org/TR/xmlschema11-1/#src-override:
"Note: It is a consequence of the semantics of inclusion, as defined in
Inclusion Constraints and Semantics (§4.2.3) (in particular clause 3.1.2 and
clause 3.2.2); redefinition, as defined in Including modified component
definitions (<redefine>) (§4.2.4); import, as defined in References to schema
components across namespaces (<import>) (§4.2.6); and overriding, as defined in
this section, that if the same schema document is both (a) included, imported,
or redefined, and (b) non-vacuously overridden, or if the same schema document
overridden twice in different ways, then the resulting schema will have
duplicate and conflicting versions of some components and will not be
conforming, just as if two different schema documents had been included, with
different declarations for the same ·named· components."
Best regards,
Andreas Meissl
--
Configure bugmail: https://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 Tuesday, 26 June 2012 15:52:49 UTC