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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
[xml-dev]Changing Namespaces Between Specification Versions

On Wed, Apr 22, 2009 at 3:17 PM, Chuck Bearden <cbearden@rice.edu> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

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

Copyright 1993-2007 XML.org. This site is hosted by OASIS