Re: Notes from 5/3/99 Versioning TeleConf
jamsden@us.ibm.com
Thu, 6 May 1999 09:40:46 -0400
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256769.004B3C98.00@d54mta03.raleigh.ibm.com>
Date: Thu, 6 May 1999 09:40:46 -0400
Subject: Re: Notes from 5/3/99 Versioning TeleConf
I mean additional state that is only visible through its inpact on the use of
the configuration in the context of a Workspace RSR. We may want additional
configuration behavior simply to report what revisions are selected by the URL
so users can see what's in a configuration before putting it in their workspace.
This would also allow configurations to be used when publishing sites.
"Geoffrey M. Clemm" <gclemm@tantalum.atria.com> on 05/05/99 11:05:29 PM
To: Jim Amsden/Raleigh/IBM@IBMUS
cc: ietf-dav-versioning@w3.org
Subject: Re: Notes from 5/3/99 Versioning TeleConf
From: jamsden@us.ibm.com
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.
If by "additional data" you mean additional state that is only visible
through its impact on the revisions selected when a workspace uses it
in its RSR, then I'm happy. If by additional data you mean additional
members of that collection, then I'll object for the reasons mentioned
in my preceding message to Sankar.
Cheers,
Geoff