[xsde-users] Multiple restrictions

[Boris Kolpackov]

Hi Pavel,

Pavel Fiala <pavel.fiala at cern.ch> writes:

>   <xs:complexType name="myArrayType1_base" abstract="true">
>     <xs:complexContent>
>       <xs:restriction base="my:type">
>         <xs:attribute name="id" type="xs:unsignedInt" use="required"/>
>         <xs:attribute name="dataType" type="my:basicDataType"
> fixed="64" use="required"/>
>       </xs:restriction>
>     </xs:complexContent>
>   </xs:complexType>
> 
> Now, it compiles without any error but the fixed value is ignored.
> The only restriction is the one from basicDataType. I guess it's the
> same limitation, isn't it?

Yes, normally fixed/default values are supported by XSD/e but not
in this case. Essentially, XSD/e uses information from the base
attribute.


> Also, I have to process large files (Xerces DOM takes ~1.7GB of memory)
> so I would probably go for XSD's C++/parser. Is there tha same limitation
> in the C++/parser?

Yes, C++/Parser in XSD and XSD/e use the same architecture.


> Otherwise I will have a look at the C++/tree streaming and performance
> examples.

Yes, the streaming example shows how you can handle very large documents
with C++/Tree.

Boris