W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2002

binding-names of members of working-collection

From: B H, Girish <g.b.h@sap.com>
Date: Wed, 19 Jun 2002 20:05:27 +0200
Message-ID: <67B8CED503F3D511BB9F0008C75DAD6601297D6B@dbwdfx17.wdf.sap-ag.de>
To: ietf-dav-versioning@w3.org

Working-collections contain binding to version-histories. But what is not
clear, is the binding-name of such bindings. 

To illustrate, take a collection hierarchy:
     +- /a
     +- /b
     +- /c

The binding-names in the version-controlled-collection "coll" would be "a",
"b" and "c".
Assume that the version-history of /coll/a is at URL /vh/vh20. Since the
version-history is a DAV resource, it can have the name "vh20". Similar
version-histories for /coll/b and /coll/c are at /vh/vh21 and /vh/22.

When we CHECKOUT "coll", we get the working-collection "/wr/wr123". 
What should the PROPFIND on /wr/wr123 return?
a) /wr/wr123/vh20 (binding-name is the 'name' of the version-history),
/wr/wr123/vh21 and /wr/wr123/vh22
b) /wr/wr123/a (binding-name is still the same as the binding-name in the
version-controlled-collection), /wr/wr123/b and /wr/wr123/c

Certainly the latter is more convenient. However, is this specifically
mentioned in the spec?

Received on Wednesday, 19 June 2002 14:06:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:48 UTC