Re: Activity, Workspace, Configuration

jamsden@us.ibm.com
Wed, 8 Dec 1999 13:56:00 -0500 

From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256841.00680411.00@d54mta03.raleigh.ibm.com>
Date: Wed, 8 Dec 1999 13:56:00 -0500
Subject: Re: Activity, Workspace, Configuration

--0__=jlOPwCsycbjP9VsMStvNnRIOL865FeceCd889cOJ8Wua1LZcWNYh37Fv
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline








Budi Surjanto <surjanto@informatik.uni-kl.de> on 12/08/99 10:45:35 AM

To:   "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>, Jim
      Amsden/Raleigh/IBM@IBMUS
cc:

Subject:  Re: Activity, Workspace, Configuration



Thank you very much  for your response.
If you don't mind I would like to continue my questions :)

As explained, a collection and a configuration contains
a set of versioned resources resp. revisions of versioned resources.
What is exactly the semantic of the containment relationship?
Is it the aggregation?
<jra>
Collections contain member URL segments, not resources or versioned
resources. These segments represent bindings to some resource.
Configurations contain members that are bindings to a particular revision
of a versioned resource. So the containment relationship is to the
bindings, not the resources themselves which could be stored somewhere
else, or in some other collection.
</jra>

It is assumed that revisions within a configuration
(or versioned resources within a collections) are
"related" in some way. Can this relationship explicitly
be specified in DAV or the definition of a relationship
(with its semantic) should be handled by the corresponding applications?
<jra>
The meaning of membership in a collection or configuration is up to the
application. WebDAV defines a set of structural semantics with respect to
collections and configurations, but not their meaning. You can use WebDAV
properties to capture meta-data about such relationships though that
applications and search engines may be able to make use of.
</jra>

Is it correct that one can build collection resp. configuration
hierarchically?
For example:
A, B, C are versioned resources and {a1}, {b1}, and {c1} the corresponding
revisions of each of them.
CL1 and CL2 are collections whereas CL1 contains {A, CL2} and
CL2 contains {B, C}.
CO1 and CO2 are configurations whereas CO1 contains {a1, CO2}
and CO2 contains {b1, c1}.

In the latter case, if a revision c2 of c1 was made, does it effect
some kind of "revision propagation" of the other revisions contained
in the configuration hierarchy (CO1 and CO2), since they are
related to each other in a some way?
<jra>
Configurations can't contain configurations. This is to keep revision
selection simpler.
</jra>

Thank you in advance.

Kindly regards,
Budi


--0__=jlOPwCsycbjP9VsMStvNnRIOL865FeceCd889cOJ8Wua1LZcWNYh37Fv
Content-type: application/octet-stream; 
	name="surjanto.vcf"
Content-Disposition: attachment; filename="surjanto.vcf"
Content-transfer-encoding: base64

YmVnaW46dmNhcmQgDQpuOlN1cmphbnRvO0J1ZGkNCnRlbDtmYXg6KCs0OS02MzEpIDIwNS0zMjk5
DQp0ZWw7d29yazooKzQ5LTYzMSkgMjA1LTMyNzENCngtbW96aWxsYS1odG1sOkZBTFNFDQp1cmw6
aHR0cDovL3d3dy51bmkta2wuZGUvQUctSGFlcmRlci9TdXJqYW50by8NCm9yZzpVbml2ZXJzaXR5
IG9mIEthaXNlcnNsYXV0ZXJuO0NvbXB1dGVyIFNjaWVuY2UgRGVwYXJ0bWVudA0KdmVyc2lvbjoy
LjENCmVtYWlsO2ludGVybmV0OnN1cmphbnRvQGluZm9ybWF0aWsudW5pLWtsLmRlDQphZHI7cXVv
dGVkLXByaW50YWJsZTo7O0FHIERCSVM9MEQ9MEFQLk8uIEJveCAzMDQ5O0thaXNlcnNsYXV0ZXJu
Ozs2NzY1MztHZXJtYW55DQp4LW1vemlsbGEtY3B0OjstODg5Ng0KZm46QnVkaSBTdXJqYW50bw0K
ZW5kOnZjYXJkDQoNCg==

--0__=jlOPwCsycbjP9VsMStvNnRIOL865FeceCd889cOJ8Wua1LZcWNYh37Fv--