Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XSD versioning ...

From: "Pete Cordell" <petexmldev@---------.--->
To: "Dragon Fly" <dragon-fly999@-------.--->, <xmlschema-dev@--.--->
Date: 7/11/2008 5:23:00 PM
You can design your XSD schema so that it accommodates versioning.  This =
is 
mainly done using xs:any, but, especially in XSD 1.0, there are gotchas 
involved in this.  There's a good article on this at:

http://www.xml.com/pub/a/2004/10/27/extend.html

The story for XSD 1.1 should hopefully be a lot better.

One thing such versioning strategies miss is the ability to declare that 
certain version 2 concepts are required to be understood by a parser, 
otherwise the message should be rejected in some way.  This procedure has=
 to 
be defined when version 1 is specified.  The method I like best is using =
an 
attribute called something like "Requires" in the top level element which=
 
contains a number of tokens that the receiving parser must understand in 
order to fully understand the message.  This to me keeps all the 
compatibility assessment in one place and allows for an easy go/no go 
decision quite early.

Just as an example, it might look like:

    <MySchema Requires="foo bar">...

That's said, your versioning strategy does depend on things like whether =
you 
have one way or two way communication, or there's an archival aspect to i=
t 
etc.

HTH,

Pete Cordell
Codalogic
For XML C++ data binding visit http://www.codalogic.com/lmx/

----- Original Message ----- 
From: "Dragon Fly" <dragon-fly999@h...>
To: <xmlschema-dev@w...>
Sent: Friday, July 11, 2008 3:24 PM
Subject: XSD versioning ...


What is the best way to handle XSD versioning? Let's say I have the 
following scenario ...

- Version 1 of the XSD is given to a customer.
- The customer writes a parsing program (that performs validation against=
 
V1).

3 months later ...

- A new element is added to version 2 of the XSD.
- The new XML files sent to the customer have the new element.
- The new XML files fail validations because version 1 of the XSD does no=
t 
have the new element.

Is there anything that I can do to plan for this? Thank you.

_________________________________________________________________
It=92s a talkathon =96 but it=92s not just talk.
http://www.imtalkathon.com/?source=EML_WLH_Talkathon_JustTalk 



From dragon-fly999@h... Fri Jul 11 20:53:37 2008
Received: from maggie.w3.org ([193.51.208.68])
	by frink


transparent
Print
Mail
Digg
delicious
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