Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XSD 1.1 Proposal: Naming wildcard extension sites

From: Boris Kolpackov <boris@---------.--->
To: Pete Cordell <petexmldev@--------------.--->
Date: 3/12/2007 1:08:00 AM
Hi Pete,

Pete Cordell <petexmldev@t...> writes:

>    <xs:element name="Element1">
>        <xs:complexType>
>            <xs:sequence>
>                <xs:element name="Child1" type="xs:int"/>
>                <xs:any namespace="##other" maxOccurs="unbounded"
>                        processContents="lax" socket="Element1"/>
>            </xs:sequence>
>        </xs:complexType>
>    </xs:element>
>
>    <xs:element name="Element2">
>        <xs:complexType>
>            <xs:sequence>
>                <xs:element name="Child2" type="xs:int"/>
>                <xs:any namespace="##other" maxOccurs="unbounded"
>                        processContents="lax" socket="Element2"/>
>            </xs:sequence>
>        </xs:complexType>
>    </xs:element>
>
>
> ...
>
>
>    <xs:plugin socket="core:Element1">
>        <xs:element name="ExtensionElement" type="xs:int"
>                maxOccurs="unbounded"/>
>    </xs:plugin>

You can already do pretty much the same thing with substitution
groups. The only difference is that you will need to decide
whether your extension is going to be of simple or complex type.
But that can be easily overcome by providing two "extension points":
one with anyType and the other with anySimpleType.


-boris


--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding


transparent
Print
Mail
Digg
delicious
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