Next message: jamsden@us.ibm.com: "Re: Why do we need working resource ids ?"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568EF.004CA88C.00@d54mta02.raleigh.ibm.com>
Date: Tue, 30 May 2000 09:57:17 -0400
Subject: Re: workspaces as collections
Geoff,
I don't think this changes the Target-Selector. We don't want users to have
to use server generated URLs. We want them to use versioned resource URLs
and the Target-Selector header. So I think the versioned-resource and
working-resource-id case are still needed. Simpliciy comes from
uniformity.
Versioned Resource
- can be accessed by server generated URL
- can be accessed with a versioned resource URL and a Target-Selector:
versioned-resource
Revision
- can be accessed by a server generated revision URL
- can be accessed with a versioned resource URL and a Target-Selector:
revision-id <revision-id>
- can be accessed with a versioned resource URL and a Target-Selector:
label <label>
Working Resource
- can be accessed by a server generated working resource URL
- can be accessed with a versioned resource URL and a Target-Selector:
working-resource-id <working-resource-id>
Clients will almost always use the second form. The Target-Selector is
always ignored for the first form.
If it would mean the same thing, why would we introduce a
"workspace" clause in the Target-Selector header when the
user could get the same effect by either using a Workspace
header or by just prepending the workspace URL to the request-URL?
The Target-Selector header is currently a bag of special cases,
but the good news is that it looks like we can get rid of both
the "versioned-resource" case (now that we have history-URL's),
and the "working-resource-id" case (now that we have working resource
URL's).
So that leaves a Target-Selector as just taking either a label
or a revision-id, which is much simpler. (And if we took your
earlier suggestion, and put revision-id's and labels in the same
namespace, it would be *even* simpler ... :-).
Cheers,
Geoff
From: jamsden@us.ibm.com
Date: Mon, 29 May 2000 23:17:29 -0400
It would mean the same thing.
What would it mean to put a workspace URL in a Target-Selector header?
Either it means the same thing as a prefix to the URL (in which case
it is redundant with using it in a Workspace header), or it means
something
different, which just would be confusing.
Cheers,
Geoff