[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: What does an empty element denote?
I've few things to say on the original post as well illustrated by Roger. Few of my comments are inline,
On 2 June 2015 at 17:45, Costello, Roger L. <costello@mitre.org> wrote:
From what I had read in the XSD 1.0 specification (and those facts haven't changed in XSD 1.1), this example doesn't define a content model at all for element "Test1". A content model of an element ("Test1" in this case), ought to specify 0-1 child elements. In this case, an XML element instance "Test1" can have one of the simpleType value from the set {0, 1, …, 9}.
I cannot dispute MSM's logic as explained by Roger. It seems correct to me.
As is mentioned in these example, I was tempted to explain the difference between Test2 and Test3's content as I seem to understand from the XSD 1.0 / 1.1 specifications. The element declaration's Test2 and Test3 at a low level will validate the same content which is empty in both the cases for Test2 and Test3. The presence of <xs:sequence/> in Test2 and <xs:choice> in Test3 are essentially equivalent from the validation perspective, although an XSD validator can adopt different means to understand the syntax of xs:sequence and xs:choice. -- Regards,
Mukul Gandhi
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|