XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange

>
> I assert that a data versioning strategy should be decoupled from a
> data validation strategy.  Versioning should be driven by business
> requirements, not technology limitations.

I think this is something everyone can agree on as long as one
understands that there are such things as real limits to technological
possibilities, and that Business requirements cannot break through
those limits if only a technological solution is wanted. This is
obvious, but lots of business types don't realize it, so I am hesitant
to affirm completely a description that would seem to validate (pun
not resisted) their preconceptions.

Cheers,
Bryan Rasmussen


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS