Re: Adding to configs
jamsden@us.ibm.com
Tue, 21 Dec 1999 16:56:40 -0500
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <8525684E.007E23DD.00@d54mta03.raleigh.ibm.com>
Date: Tue, 21 Dec 1999 16:56:40 -0500
Subject: Re: Adding to configs
We talked about having a new method for this at DC. Want to consider that
solution?
Tim_Ellison@oti.com (Tim Ellison OTT)@w3.org on 12/21/99 03:46:43 PM
Sent by: ietf-dav-versioning-request@w3.org
To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
cc:
Subject: Adding to configs
When adding a (versioned resource -> revision) to a configuration is the
corrrect protocol:
BIND <versioned resource URI>
Target-Selector: <something to pick a revision of the versioned resource>
Destination: <config URI>/<versioned resource ID>
That doesn't seem right since I can't say where the config working resource
is.
How about:
BIND <config URI>/<versioned resource ID>
Target-Selector: <a workspace to pick a working config>
Destination: <stable revision URI>
Now that seems the wrong way around? and it means I _have_ to use a stable
revision URI.
What do you think it should be?
Tim
p.s. it sure would be good to get rid of the <versioned resource ID>, but
that would create a problem for removing it with DELETE.