Return-Path: 
 <dev-return-95449-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 91553 invoked from network); 2 Jul 2007 17:42:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 2 Jul 2007 17:42:24 -0000
Received: (qmail 52626 invoked by uid 500); 2 Jul 2007 17:42:25 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 52368 invoked by uid 500); 2 Jul 2007 17:42:24 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 52353 invoked by uid 99); 2 Jul 2007 17:42:24 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jul 2007 10:42:24 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS
X-Spam-Check-By: apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jul 2007 10:42:20 -0700
Received: from [192.168.0.129] (unknown [80.240.191.89])
	by smtp.mxes.net (Postfix) with ESMTP id 0652F519AD
	for <dev@cocoon.apache.org>; Mon,  2 Jul 2007 13:41:58 -0400 (EDT)
Message-ID: <468938E4.5080807@apache.org>
Date: Mon, 02 Jul 2007 19:41:56 +0200
From: Grzegorz Kossakowski <gkossakowski@apache.org>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Versioning XML Schemas
References: <4687B023.1000707@tuffmail.com> <4687BC1B.8010103@gmx.de>
 <4687C5DD.7030608@apache.org> <46880851.9080603@gmx.de>
 <46892266.4050604@apache.org> <loom.20070702T181124-780@post.gmane.org>
In-Reply-To: <loom.20070702T181124-780@post.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Joerg Heinicke pisze:
> Grzegorz Kossakowski <gkossakowski <at> apache.org> writes:
> 
>> I wonder what will be broken if someone sticks to 2.2.3 version of schema?
> 
> It's actually not so easy to stick to a particular version.
> Quoting myself from the last mail:
> 
>>> With increasing the version number of the schema you have to adapt all your 
>>> references to the new version just to get your app working again. Or you'd
>>> need to hold all versions probably in use in your local XML catalogue or
>>> access them remotely.
> 
> Since this approach does not scale the problem increases with each new schema
> version. I'd have no problem with somebody being forced to update the reference
> if he wants to use a new feature (the additional attribute). But the approach
> breaks drop-in replacement. You would at least need to update the XML catalogue.
> I don't consider remote access a serious alternative.

Thanks for repeating your message. Now I understand it completely and agree with your view.

-- 
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/