Lists Home |
Date Index |
Thanks, Pete. This is very helpful.
From: Pete Cordell [mailto:email@example.com]
Sent: Thursday, November 10, 2005 1:30 PM
To: Lawson, Marc; firstname.lastname@example.org
Subject: Re: [xml-dev] Optional elements and restrictions
The behaviour you describe is correct. As you know,
<DESTINATION_SYSTEM_ID/> is equivalent to
<DESTINATION_SYSTEM_ID></DESTINATION_SYSTEM_ID> and none of the
enumerations match "".
I personally don't see how an "empty element" can be considered
to an "omitted element", (e.g. consider <br /> in (early) (X)HTML), so
changing the data source seems the correct thing. If reality does not
that, you could add an additional enumeration of the form:
But that would probably require additional application layer processing
fix it up!
for XML to C++ data binding visit
----- Original Message -----
From: "Lawson, Marc" <email@example.com>
Sent: Thursday, November 10, 2005 5:47 PM
Subject: [xml-dev] Optional elements and restrictions
In my schema, I have an "optional" element that looks like this:
<xs:element name="DESTINATION_SYSTEM_ID" minOccurs="0">
My instance document will fail validation if the element is provided
without any data, as in...
However, the instance document will pass validation if the element is
I am hearing that it is best practice to allow both scenarios - the
"empty element" and the "omitted element" - in documents that are
provided. Do I need to tell the company that is sending the file to
omit the element if it doesn't have data, or can I restructure the
schema to only validate elements that have data?
Any input is appreciated!