I am not sure how you would handle this in the spreadsheets but W3C
schema is capable of modeling this situation:
<xsd:sequence>
<xsd:choice minOccurs="1">
<xsd:element ref="BuyersID"/>
<xsd:element ref="SellersID"/>
</xsd:choice>
<xsd:element ref="CopyIndicatory"/>
. . .
</xsd:sequence>
If the choice is optional, i.e., no BuyersID or SellersID, then the
"minOccurs" attribute would be set to 0.
Betty
On Thu, 11 Aug 2005, Tim McGrath wrote:
this comes from trying to implement a rule that goes along the lines of...
"all documents must have an ID. However with some documents (eg Order)
it may be either the BuyersID and/or the SellersID"
unfortunately we dont have schema (or spreadsheet) syntax for "either
are optional but one must be used" - which is actually a common rule in
the real world. What we have don is the best we can.
Anne Hendry wrote:
We notice that some documents contain an 'ID' element. The 'ID'
elements seem to be mandatory. The documents that don't have 'ID'
seem to have 'BuyersID' and 'SellersID', but those are optional.
Is this an intended modeling aspect that assumes in the documents that
don't have 'ID' the users would implement either a BuyersID or
SellersID, even though they are both optional? Do we want to
duplicate this model for new documents? When do you determine you
want a mandatory ID vs. two optional Buyers|Sellers IDs?
Thanks,
Anne
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php