W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2004

3rd try on versioning question

From: <dean@xsoftware.biz>
Date: Sat, 16 Oct 2004 11:30:55 -0700 (PDT)
Message-ID: <59494.>
To: www-xml-schema-comments@w3.org

I have asked a few times, and have not quite given up just yet.  I am
looking for an industry standard on how to do versioning and
extensibility.  It would be great if there was a standard way of doing
this.  I have used some standards that kind of messed up and we couldn't
extend it.

Something new in the xsd like below would help greatly in this
area.....(maybe there is a final keyword to prevent use of super also)

Say you have xml
The next standard comes out and is
<CarVersion2 super=”CarVersion1”>….<CarVersion2>  where they have added
subelements to the standard
And another
<CarVersion3 super=”CarVersion2:CarVersion1”>….<CarVersion3>
Last one decides it is not compatible with version 1 anymore(only stays
compatible with last 2 releases
<CarVersion4 super=”CarVersion3:CarVersion2”>….<CarVersion4>

Typically you only stay compatible 3 releases back(well, if you can even
do that as without some strategy like above in w3c specs, it is really
hard to do such a think).

Now, if I have a server that sends back CarVersion3 events, a client who
only knows version 1 can understand the event as he will ignore all the
fields in the sort of a subclass kind of thing.

Instead, all companies I know of implement a version 3 spec and send back
version 1, version 2, version 3 events resulting in 3 times the code. 
This is not pretty.  Is there a cleaner way I am not aware of?

This also solves the extensibility problem allowing companyX to create
<CompanyXCar super="CarVersion2:CarVersion1">...

Notice that the parser can look at CompanyXCar and if it only knows the
version 1 spec, will automatically know that this is CarVersion1.  The
super is a list of elements that this xml packet also happens to be.

This also helps with SOAP alot because objects can be subclassed and I can
passback a subclass which will marshal to CarVersion3 instead of the
superclass CarVersion 1.  unmarshalling back will depend on the version of
the client.
thanks for any info,
Received on Saturday, 16 October 2004 18:30:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:02 UTC