Re: Notes from 5/3/99 Versioning TeleConf
jamsden@us.ibm.com
Wed, 5 May 1999 09:57:23 -0400
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256768.004CA5D7.00@d54mta03.raleigh.ibm.com>
Date: Wed, 5 May 1999 09:57:23 -0400
Subject: Re: Notes from 5/3/99 Versioning TeleConf
Geoff says:
>>
Certainly defining specializations of collection is a sensible approach.
My point was just that if there is more than one collection that defines
the state of a snapshot, then you need to make these be *subcollections*
of a snapshot. In particular, there is the collection of versioned
resources that define the "scope" of the snapshot (let's call that the
"scope collection", and then the collection of revisions that is
created when you "checkin" the snapshot (let's call that the
"selection collection").
<<
This might be the source of our disconnect. I see the configuration as a single
collection whose members are URL references of versioned resources the creator
of the configuration is interested in. The specialization of this collection
provides additional data that associates each URL member with a specific
revision. This isn't another collection, but additional data in the same
collection.