 |
|
|
On Wed, Apr 22, 2009 at 3:17 PM, Chuck Bearden <cbearden@r...> wrote:
> [...]
> The decision was made (a) to add a version attribute to the root element,
> and (b) not to change the namespace URI (which was already unversioned).
> Did the maintainers of EgXML make the right choice?
What happens when a message needs to be constructed, exchanged, and
validated, which contains content defined by both v1 and v2? A
majority of schema-validating XML parsers support only a single schema
for a given namespace on a particular validation pass.
What happens when a message is constructed that only uses content from
v1 or v2, without using the designated root element? How does the
receiver determine the appropriate schema when the version is not
explicitly referenced?
Webb Roberts
_______________________________________________________________________
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: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
