- From: Kasimier Buchcik <kbuchcik@4commerce.de>
- Date: Mon, 06 Jun 2005 17:07:30 +0200
- To: public-xml-schema-testsuite <public-xml-schema-testsuite@w3.org>, XML-SCHEMA <xmlschema-dev@w3.org>
Hi, potential errors in the TS xsts-2002-01-16 - msxsdtest: Section: complexType ctA014, ctA015, ctA023, ctA024 (all schemata) expected: invalid result : valid reason : duplicate values in the attributes 'block' and 'final' are not ruled out ctA029, ctC003, ctF003 (all schemata) expected: invalid result : valid reason : Duplicate IDs in separated schema documents are not violating the ID constraint. ctF006 (schema) expected: valid result : invalid reason : violates derivation-ok-restriction (5.4.1.2); "complex type 'fooType': If the content type is 'mixed', then the content type of the base type must also be 'mixed'." Would be happy to see those removed or fixed. A question about ctL021.v: I currently use the first <schemaTest> information of each <testGroup> to get hold of the main schema document for the instances; i.e. I _avoid_ using xsi-driven schema assembling. The instance document of "ctL021.v" specifies 2 schema documents via xsi, the second not being mentioned in the testGroup "ctL021", so there's seems no way around xsi here. Is this intended? I would be nice to have the opportunity to _not_ need xsi-driven schema assembling. The best (for me) would be to <import> the second schema in the first one, so that there's always only one main schema. Could we go this way? Regards, Kasimier
Received on Monday, 6 June 2005 15:07:33 UTC