Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Versioning of XML Schema and namespaces

From: Eliot Kimber <ekimber@---------------.--->
To: Dan Vint <dvint@-----.--->
Date: 5/10/2005 5:22:00 AM
Dan Vint wrote:
> I agree with the idea that namespaces could provide this functionality, 
> except that most folks recommend not versioning the namespace. I believe 
> you or someone in this thread suggested using the version attribute for 
> this function. Well that might work if the parsers actually did 
> something with the version attribute. The only mechanism that I can be 
> sure will be caught by the parser is to use the namespace with a version 
> to indicate that the document conforms to a different version of the 
> standard than someone else might be using.

If you're depending on *parsers* to bind instances to schemas then you 
should be using schemaLocation= because clearly you have control over 
that part of the system (the parsers you're using). Put the version 
information in the URI of the XSD instance. I don't see that you can do 
anything other that that.

Putting a version in the namespace is definitely not the right thing to do.

Both Mike Kay and I have have recommended using a separate version 
attribute to indicate the schema version to use. This presumes that you 
have the ability to implement the mechanism that binds documents to 
schemas, which you may not have.



-- 
W. Eliot Kimber
Professional Services
Innodata Isogen
9390 Research Blvd, #410
Austin, TX 78759
(512) 372-8155

ekimber@i...
www.innodata-isogen.com


From John.Hockaday@g... Wed May 11 02:29:02 2005
Received: from maggie.w3


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent