![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - RE: Problem with types derived from mixed complex types [Thread Next] RE: Problem with types derived from mixed complex typesTo: "'Tait E Larson'" <telarson@--.---.---> Date: 6/5/2004 12:38:00 AM
> -----Original Message-----
> From: Tait E Larson [mailto:telarson@u...]
> Sent: 04 June 2004 19:42
> To: Michael Kay
> Cc: xmlschema-dev@w...
> 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 =B7resolved=B7 to by the =B7actual value=B7 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
=B7emptiable=B7, as defined in Particle Emptiable (=A73.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
From rschloss@u... Sat Jun 5 05:08:15 2004
Return-Path: <rschloss@us. | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
