Altova Mailing List Archives

Re: Mixed contents and group in schema definition

From: "Dave Carlson" <dcarlson@----------.--->
To: <xml-dev@---.--->
Date: 7/7/2000 8:17:00 AM
You say that "the mixed content is not recognized."  Not recognized by what?
It it's not recognized by XML Authority, then this is due to limitations of
current schema support in XA.  I'm also struggling with evaluating whether
my schema design ideas are correct/valid.  I just downloaded XMLSpy">XMLSpy
yesterday to evaluate its compliance, compared to the current limitations of


----- Original Message -----
From: Pierre Attar <patt@t...>
For being able to have declarations like :

         <element name = "AUTHOR">
                 <complexType content = "elementOnly">
                                 <element name= "FIRST" type="textType"/>
                                 <element name= "LAST" type="textType"/>

This does not work because the mixed content is not recognize and I a no
more able to have mixed contents : <FIRST>Here is a <B>real</B> test

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at


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 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.