[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Changing Namespaces Between Specification Versions

• From: Webb Roberts <strebor@g...>
• To: xml-dev@l...
• Date: Wed, 22 Apr 2009 21:54:41 -0400

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

• Follow-Ups:
  • Re: Changing Namespaces Between Specification Versions
    • From: "G. Ken Holman" <gkholman@C...>

• References:
  • Changing Namespaces Between Specification Versions (was: XIN: XML implicit namespace definitions)
    • From: "Paul Spencer" <xml-dev-list@b...>
  • RE: Changing Namespaces Between Specification Versions (was: XIN: XML implicit namespace definitions)
    • From: "Michael Kay" <mike@s...>
  • Re: Changing Namespaces Between Specification Versions (was: XIN: XML implicit namespace definitions)
    • From: "Pete Cordell" <petexmldev@c...>
  • RE: Changing Namespaces Between Specification Versions (was: XIN: XML implicit namespace definitions)
    • From: "Michael Kay" <mike@s...>
  • Re: Changing Namespaces Between Specification Versions (was: XIN: XML implicit namespace definitions)
    • From: Andrew Welch <andrew.j.welch@g...>
  • Re: Changing Namespaces Between Specification Versions (was: XIN: XML implicit namespace definitions)
    • From: "Pete Cordell" <petexmldev@c...>
  • Re: Changing Namespaces Between Specification Versions
    • From: Chuck Bearden <cbearden@r...>