[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Caution using XML Schema backward- or forward-compatibilit

• From: David Carver <d_a_carver@y...>
• To: Fraser Goffin <goffinf@g...>
• Date: Thu, 27 Dec 2007 09:42:02 -0500

Fraser Goffin wrote:
> Roger,
>
> I think in an earlier thread David Orchard contributed some comments.
> I can't remember whether he included EXTENSIBILITY as a [special] type
> of versioning. In particular the ideas around who 'owns' the
> vocabulary and who can make changes. One of the things that I find
> very difficult is where there is only central ownership and no ability
> for distributed extensibility. Central ownership has very many plus
> points, but at least one significant negative, namely, the speed of
> change. In particualr information items that are [at least initially]
> part of a private relationship between two (or more) trading partners,
> but where the vast majority of the exchange is fulfilled by a
> 'standard' schema. IMO extensibility (for the vocabulary user) is
> essential and hels to reduce versioning 'churn' and more importantly
> ensures that the core vocabulary does not constrain the business
> operating model of those that want to use it.
>   
That reason for extensibility is only necessary if the central authority 
can't or won't respond quicker.  Some of it has to do with the way 
vocabularies are designed and distributed to the members of those 
organizations.   I wrote about this back in December of 2006.   
Basically the central authority needs to adapt faster to their members 
chaning needs:

Agile Schema Development.
http://www.starstandard.org/index.php?n=STAR.XML2006

We've been doing this for 3 years now, and it works extremely well.

It definitely helps with backward and forward compatibility testing as 
well, at least from a structure stand point.

• Follow-Ups:
  • RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Michael Kay" <mike@s...>
  • Re: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Fraser Goffin" <goffinf@g...>
  • Re: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Stephen Green" <stephengreenubl@g...>

• References:
  • Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Costello, Roger L." <costello@m...>
  • Re: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Stephen Green" <stephengreenubl@g...>
  • RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Michael Kay" <mike@s...>
  • RE: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Costello, Roger L." <costello@m...>
  • Re: Caution using XML Schema backward- or forward-compatibility as a versioning strategy for data exchange
    • From: "Fraser Goffin" <goffinf@g...>