Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Data versioning strategy: address semantic, relationship, and syntactic changes?

From: "Stephen Green" <stephengreenubl@-----.--->
To: "Costello, Roger L." <costello@-----.--->
Date: 12/9/2007 10:49:00 AM
On 07/12/2007, Costello, Roger L. <costello@m...> wrote:

> QUESTIONS
>
> a. Do you agree with the three categories of change?
>
> b. Do these categories represent all types of change?
>
> c. Do you agree that a versioning strategy must address semantic,
> relationship, and syntactic changes?
>
> /Roger
>


These are three categories which are acceptable in certain situations.
There are situations where these are not acceptable. If the semantics
were, say, legally binding (as with legally binding documents) it might
not be acceptable to change them. On the other hand there may be other
categories of change which are acceptable in other situations. So I
think there is always a problem with versioning - that it is a subject
where one size doesn't fit all. When we have looked at versioning for
XML business documents we have found that the requirements are so
strict and rigorous in comparison to other domains that the accepted
wisdom didn't really apply. This can be quite disheartening and baffling
but is largely due, I think, to over-simplification. It's not so much a
tutorial matter as a doctorate thesis matter. However, maybe these
three categories cover a certain area of requirements which can be quite
simply described so that they aren't seen as the whole picture and so
that folk using XML in areas out of scope to these categories don't
seriously underestimate the task they might have in hand. Given that, I
think they are a good fit for the average, innocuous, internal use of XML.

-- 
Stephen Green

Partner
SystML, http://www.systml.co.uk
Tel: +44 (0) 117 9541606

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice


transparent
Print
Mail
Like It
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