RE: Fwd: [xml-dev] Data versioning strategy: address semantic, relations

[Len Bullard <len.bullard@uai.com>]

The problem then is may be multi-variate:  a change breaks one system but
not another.  As in does not break the processing application but does break
the help description of the running system.  It isn't just *identifying* the
change; it is capturing the real and non-real time effects.

That is the difference between *a* version (identifying the resource) and
version control (identifying and executing the process).  Not a new topic
here or elsewhere.

len

-----Original Message-----
From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn@us.ibm.com] 
Sent: Thursday, December 13, 2007 3:49 PM
To: Greg Hunt
Cc: xml-dev@lists.xml.org
Subject: Re: Fwd: [xml-dev] Data versioning strategy: address semantic,
relationship, and syntactic changes?

Greg Hunt writes:

> The real question is how do we identify breaking and non-breaking 
changes?

Exactly.  Furthermore, breaking/non-breaking is a function of at least: a) 
the verison of the specification the author had in mind when authoring a 
document b) the version of the specification the receiver had in mind when 
interpreting the document and crucially c) the particular purpose for 
which the document is being read
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.