![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - XSD versioning ... [Thread Next] Re: XSD versioning ...To: Dragon Fly <dragon-fly999@-------.---> Date: 7/11/2008 8:36:00 PM Hi, Let your customer choose the version he wants. If he did not yet upgraded to version 2 then he should receive version 1 documents that do not contain the new element. When he is ready to process version 2 documents then he should be able to choose version 2 and receive further version 2 documents. Hope that helps, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger www.---.com Dragon Fly wrote: > 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 > not 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. Check out the i=92m Ta= lkathon. > <http://www.imtalkathon.com/?source=EML_WLH_Talkathon_JustTalk> From gkholman@C... Fri Jul 11 14:51:11 2008 Received: fro | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
