[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: xs:choice question...


xs choice

Actually remove the <xs:sequence></xs:sequence> from the second <xs:element name="RequestedDeliveryDateTime" /> it should not be there.. sorry

Cheers,
brian




Brian J Gentry/NA/TNT/TPG

01/16/2006 01:47 PM

To
"Priscilla Walmsley" <pwalmsley-lists@d...>
cc
"'Brian J Gentry'" <Brian.j.Gentry@t...>, xml-dev@l...
Subject
RE: xs:choice question...Link






That works in a vaccuum, im sorry i didnt fully elaborate the need in the first message.  I have a structure that looks like this:


<
xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.url/to/schema/namespace/OrderManagement/V1" elementFormDefault="qualified" attributeFormDefault="unqualified">
       
<xs:complexType name="OrderHeader">
               
<xs:sequence>
                       
<xs:element name="Comments"  minOccurs="0"/>
                       
<xs:element name="OrderWeight"  minOccurs="0"/>
                       
<xs:element name="OrderPieces"  minOccurs="0"/>
                       
<xs:element name="OrderVolume"  minOccurs="0"/>
                       
<xs:choice>
                               
<xs:sequence>
                                       
<xs:element name="RequestedShipDateTime" />
                                       
<xs:element name="RequestedDeliveryDateTime"  minOccurs="0"/>
                               
</xs:sequence>
                               
<xs:sequence>
                                       
<xs:element name="RequestedDeliveryDateTime" />
                               
</xs:sequence>
                       
</xs:choice>
                       
<xs:element name="RequestedShipDateTime"  minOccurs="0"/>
                       
<xs:element name="RequestedDeliveryDateTime"  minOccurs="0"/>
                       
<xs:element name="OrderDates"  minOccurs="0" maxOccurs="unbounded"/>
                       
<xs:element name="ShipFromParty" />
                       
<xs:element name="ShipToParty" />
                       
<xs:element name="OrderParty"  minOccurs="0" maxOccurs="unbounded"/>
                       
<xs:element name="OrderReference"  minOccurs="0" maxOccurs="unbounded"/>
                       
<xs:element name="OrderMonetary"  minOccurs="0" maxOccurs="unbounded"/>
               
</xs:sequence>
       
</xs:complexType>
</
xs:schema>

I still get the "non-deterministic" message when i apply your pattern.  


Cheers,

brian


"Priscilla Walmsley" <pwalmsley-lists@d...>

01/16/2006 12:44 PM


To
"'Brian J Gentry'" <Brian.j.Gentry@t...>, <xml-dev@l...>
cc
Subject
RE: xs:choice question...







Why not just:

 

                       
<xs:choice>
                       
 <xs:sequence>
                                     
<xs:element name="A" minOccurs="1"/>
                                     
<xs:element name="B" minOccurs="0"/>
                         
</xs:sequence>
                       
 <xs:element name="B" minOccurs="1"/>
                     
</xs:choice>

Hope that helps,

Priscilla

 

-----------------------------------------------------------------
Priscilla Walmsley                
http://www.datypic.com/
Author, Definitive XML Schema     (Prentice Hall PTR)
          Definitive XQuery (coming in 2006)

-----------------------------------------------------------------

 


From: Brian J Gentry [mailto:Brian.j.Gentry@t...]
Sent:
Monday, January 16, 2006 12:36 PM
To:
xml-dev@l...
Subject:
xs:choice question...



Hello,

       I have a schema that needs to require 1 of 2 elements, but also allow for both of them. So if the elements are A & B, then A alone is valid, B alone is valid, A & B are valid, but ~A & ~B is invalid.


I tried the following..


                     
<xs:choice>
                       
<xs:sequence>
                                     
<xs:element name="A" minOccurs="1"/>
                                     
<xs:element name="B" minOccurs="0"/>
                       
</xs:sequence>
                       
<xs:sequence>
                                     
<xs:element name="A" minOccurs="0"/>
                                     
<xs:element name="B" minOccurs="1"/>
                       
</xs:sequence>
                     
</xs:choice>

But this is not working as it makes the model non-deterministic.  Is there a way to solve this?


Thanks for your time and kind regards,

Brian Gentry


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.