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

Re: XML Schema

From: <noah_mendelsohn@us.ibm.com>
Date: Wed, 9 Nov 2005 12:20:50 -0500
To: "Udo Ende" <u.ende@mid.de>
Cc: "Xmlschema-Dev-Request" <xmlschema-dev@w3.org>
Message-ID: <OFE3F5167F.52F7A776-ON852570B4.0056B186-852570B4.005F4B26@lotus.com>
Re: XML Schema

I can't offhand think of a way to do this in XML Schema, but I should 
point out that many in the XML community consider the example you describe 
to be a suboptimal use of XML markup.  Very often when you have rules 
like:

Some of the inner elements are only optional, others are included more 
than one time (therefore I can not use "all" for the complexType).

There is some implied structure that the markup is not capturing.  It's 
hard to be sure without seeing some details, but very often adding levels 
of markup in the instance makes the XML more self-describing, and at the 
same time makes it more suitable for Schema validation.   Among the reaons 
that schema does not support more elaborate pattern specifications for 
content models is that they are so often (though admittedly not always) a 
questionnable approach.

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------








"Udo Ende" <u.ende@mid.de>
Sent by: xmlschema-dev-request@w3.org
11/08/2005 10:41 AM
 
        To:     "Xmlschema-Dev-Request" <xmlschema-dev@w3.org>
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        XML Schema



Hi,

I do not find a solution for my following problem:

The root elements of my XML data contain many different inner elements.
Therefore I chose a complexType definition for the root elements.

Some of the inner elements are only optional, others are included more 
than
one time (therefore I can not use "all" for the complexType).

I can not tell in which order the inner elements will appear. Therefore I
can not use "sequence" for the complexType.

I decided to use "choice" - with the attribute "maxOccurs" "unbounded" not
only allowing one element under the root elements.

But with that it seems I lose a validation opportunity to tell if an inner
element must appear or is only optional (minOccurs 1 for the inner 
elements
does not show a difference within validation).

Any idea how I could handle this situation?

Regards,
Udo
Received on Wednesday, 9 November 2005 17:21:03 GMT

Subscribe to the Stylus Scoop newsletter for helpful XML tips and tutorials.
Email
First Name
Last Name
Company

Download Stylus Studio 6 XML Enterprise Edition

Subscribe in XML format
RSS 2.0
Atom 0.3
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-2007 All Rights Reserved.