Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Defining recursive elements?

From: "Pete Cordell" <petexmldev@--------------.--->
To: "Boris Kolpackov" <boris@-------------.--->, <xmlschema-dev@--.--->
Date: 5/17/2007 11:50:00 PM
----- Original Message From: "Boris Kolpackov" <...>


> Hi,
>
> Andrew Welch <andrew.j.welch@g...> writes:
>
>> Well it's a matter of taste, but if you use the venetian blind style
>> of schema then you wouldn't use element ref="" much, but @type
>> instead, eg:
>>
>> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
>>
>>  <xs:element name="part" type="part"/>
>>
>>  <xs:complexType name="part">
>>    <xs:sequence>
>>      <xs:element name="part" type="part" minOccurs="0"
>>      maxOccurs="unbounded"/>
>>    </xs:sequence>
>>    <xs:attribute name="serial" type="xs:string"/>
>>  </xs:complexType>
>>
>> </xs:schema>
>
> Note that this change will result in a different schema if there
> was a target namespace involved. In the original example, both
> elements are qualified while in this schema the global one would
> be qualified while the local one wouldn't.


Although, just to clarify for those that are a bit fuzzy about namespaces in 
schema, commonly if people define a schema that specifies a target 
namespace, 9 times out of 10 they will also make 
elementFormDefault="qualified".  Hence all elements will end up qualified 
and the same result can be achieved.

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware Ltd
for XML Schema to C++ data binding visit
 http://www.tech-know-ware.com/lmx/
 http://www.codalogic.com/lmx/
=============================================



From petexmldev@t... Thu May 17 22:07:29 2007
Received: from lisa.w3.org ([12


transparent
Print
Mail
Like It
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