Next message: jamsden@us.ibm.com: "Re: Questions on activities"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568C8.0064158E.00@d54mta03.raleigh.ibm.com>
Date: Fri, 21 Apr 2000 14:13:06 -0400
Subject: Re: Initializing a new workspace using an RSR
No, but I just don't think of it that way. That is, I don't think of the
workspace as just a bunch of revisions, but rather versioned resource and
some revision of those resources. Either could change independently of the
other. I can see that your approach would work too, its just that it might
be useful to retain the knowledge about which versioned resources you are
interested in separately so you can change the revision without changing
the versioned resource. For example, you might want to just change the
label, activity, or configuration, and not have to change the versioned
resource too to select a different revision.
|------------------------+------------------------>
| | "Geoffrey M. Clemm" |
| | <geoffrey.clemm@ratio|
| | nal.com> |
| | Sent by: |
| | ietf-dav-versioning-r|
| | equest@w3.org |
| | |
| | 04/20/2000 10:58 PM |
| | |
|------------------------+------------------------>
>------------------------|
| |
| To: |
| ietf-dav-versioning@w|
| 3.org |
| cc: |
| Subject: |
| Re: Initializing a |
| new workspace using |
| an RSR |
>------------------------|
From: jamsden@us.ibm.com
I think we need two concepts for a workspace - the versioned
resources that specify its scope or members, and the RSR which
picks the revision.
If a workspace tracks the revisions it selects in a DAV:revision-set
property, is there any need for a set of versioned resources
to define its scope (since the revisions effectively define the
set of versioned resources)?
Cheers,
Geoff