OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Optional elements and restrictions

[ Lists Home | Date Index | Thread Index ]
  • To: <xml-dev@lists.xml.org>
  • Subject: Optional elements and restrictions
  • From: "Lawson, Marc" <mlawson@relico.com>
  • Date: Thu, 10 Nov 2005 12:47:55 -0500
  • Thread-index: AcXmHuF9Oybpa6ZHQIWEjFPYBcStWg==
  • Thread-topic: Optional elements and restrictions



In my schema, I have an “optional” element that looks like this:


<xs:element name="DESTINATION_SYSTEM_ID" minOccurs=”0”>


<xs:restriction base="xs:string">

<xs:enumeration value="TRUST_PROD"/>

<xs:enumeration value="TRUST_TEST"/>

<xs:enumeration value="PENSION_PROD"/>

<xs:enumeration value="PENSION_TEST"/>






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 omitted altogether.


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!

Marc Lawson



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS