Required XML element with no data to populate it - it might not be a problem! Here's why ...
Roger L Costello <[email protected]>
| Newsgroups | gmane.text.xml.devel |
|---|---|
| Message-ID | <SA9PR09MB5952D9B0C72DAA9B69238745C8809@SA9PR09MB5952.namprd09.prod.outlook.com> |
Hi Folks, Suppose you are using data from System A to populate an XML instance document. An element in the instance is required (per the XSD) but there is no System A data to populate it. With regard to creating an instance from System A data, that is a problem (or minimally, a highly undesirable situation). Suppose the element's parent is optional, now is it a problem? Suppose the element's parent is required but the element's grand-parent is optional, now is it a problem? How far up the tree should you look to find an optional ancestor? Fascinating problem! Comments? /Roger _______________________________________________________________________ XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting. [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Or unsubscribe: [email protected] subscribe: [email protected] List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php