- From: <telarson@stanford.edu>
- Date: Mon, 7 Jun 2004 10:16:09 -0700
- To: mhk@mhk.me.uk
- Cc: xmlschema-dev@w3.org
- Message-ID: <OF82408BBE.28AD1411-ON86256EAC.005E50E3-88256EAC.005EDCBB@LocalDomain>
Michael,
You were right. Thanks for your help. One last question. How do you use
Xerces to validate schemas? Is there a simple code snippet you could
provide?
Thanks,
Tait
"Michael Kay" <mhk@mhk.me.uk>
06/04/2004 03:37 PM
To
Tait E Larson/Burlingame/IBM@IBMUS
cc
<xmlschema-dev@w3.org>
Subject
RE: Problem with types derived from mixed complex types
> -----Original Message-----
> From: Tait E Larson [mailto:telarson@us.ibm.com]
> Sent: 04 June 2004 19:42
> To: Michael Kay
> Cc: xmlschema-dev@w3.org
> Subject: RE: Problem with types derived from mixed complex types
>
>
>
>
>
> Michael,
>
> I'm not 100% sure your example works in this case. In the
> case described
> in the link below the base type is complex (i.e. contains
> other elements).
> In your example I believe "xsl:generic-element-type" is simple.
No, it's complex.
This is covered by rule 2 in section 3.4.3:
2 If the <simpleContent> alternative is chosen, all of the following must
be
true:
2.1 The type definition ·resolved· to by the ·actual value· of the base
[attribute] must be one of the following:
2.1.1 [...]
2.1.2 only if the <restriction> alternative is also chosen, a complex type
definition whose {content type} is mixed and a particle which is
·emptiable·, as defined in Particle Emptiable (§3.9.6);
2.1.3 [...]
2.2 If clause 2.1.2 above is satisfied, then there must be a <simpleType>
among the [children] of <restriction>.
This validates OK in Xerces.
Michael Kay
Received on Monday, 7 June 2004 15:47:01 UTC