W3C home > Mailing lists > Public > www-tag@w3.org > March 2007

Versioning Finding Updated

From: David Orchard <dorchard@bea.com>
Date: Fri, 23 Mar 2007 16:16:35 -0700
Message-ID: <E16EB59B8AEDF445B644617E3C1B3C9C036ECD1D@repbex01.amer.bea.com>
To: <www-tag@w3.org>
Cc: <public-xml-versioning@w3.org>

I've updated the 2 part versioning finding for review at our Apr 2nd
meeting. 

http://www.w3.org/2001/tag/doc/versioning-20070326.html
 
The major differences from
http://www.w3.org/2001/tag/doc/versioning-20060929.html that we reviewed
are:
- Moved all xml material (section xml terminology in section 1, plus all
of 8,9) into the versioning-xml finding (and changed versioning-part2 to
versioning-xml)
- shuffled first section on why/how/why extend
- added a section on application versioning that Noah wrote
- added some text on trade-offs between extensibility and
interoperability
- Inserted new section 2 "Versioning Strategies" that has versioning
designs from big bang to forwards compatible to backwards compatible and
includes replacement and side by side deployment
- Added summary section to requirements section and design question (for
use in case studies section)
- Added version #s to identifying and extending languages section (now
section 5)
- Added Case Stuides

http://www.w3.org/2001/tag/doc/versioning-xml-20070326.html

The major differences for the xml (nee part 2) from 2004 Nov that were
never reviewed are
- insertions from Part 1
- inserted section 2 version identification technologies
- added only 1 namespace + version # as identification strategy
- refined section 4 on indicating compatibility of extensions
- Added section 5 explaining schema 1.0
- added section 8 case studies of xml versioning
- Updated Other technologies section 10
- Added notes on Redefine

Sadly to report, there are very little cutbacks in size.
Cheers,
Dave

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Received on Friday, 23 March 2007 23:16:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:51 UTC