Altova Mailing List Archives


Re: [xml-dev]Changing Namespaces Between Specification Versions

From: Andrew Welch <andrew.j.welch@-----.--->
To: "G. Ken Holman" <gkholman@----------------.--->
Date: 4/23/2009 3:46:00 PM
>> How does the
>> receiver determine the appropriate schema when the version is not
>> explicitly referenced?
>
> Why not "try one and if it fails try the other"?

There is a problem with this - the document is a v2 doc but fails for
some reason, so validation falls back to the v1 schema, which also
fails... which error message gets presented to the user?

You want the v2 failure message, but the system can't confidently give you that.




-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

_______________________________________________________________________

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

Disclaimer

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.