Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


xsts-2002-01-16 - msxsdtest - complexType - errors

From: Kasimier Buchcik <kbuchcik@---------.-->
To: public-xml-schema-testsuite <public-xml-schema-testsuite@--.--->, XML-SCHEMA <xmlschema-dev@--.--->
Date: 6/6/2005 7:08:00 PM
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

From K.Buchcik@4... Tue Jun 07 09:51:05 2005
Received: from maggie.w3.org (


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent