Relationship between BIND and RFC 3253

• From: Werner Donn? <werner.donne@re.be>
• Date: Mon, 11 Aug 2008 14:00:47 +0200
• To: w3c-dist-auth@w3.org
• Message-Id: <F7FF49A9-5C47-445A-B8C0-1E6383DCDDB0@re.be>

Hi,
I wonder if the BIND spec could include an informal discussion about
the relationship with RFC 3253. There are two cases I see at the moment
that are worth mentioning.
1) When supporting version controlled collections, bindings may be
  introduced in a server without actually issuing the BIND method.
  When a MOVE is performed of a resource from one collection to
  another, both collections should be checked out. An additional binding
  would be the result if one collection would be subsequently checked  
in,
  while the check-out of the other is undone. The resulting situation
  is meaningless if the binding model is not supported.
2) RFC 3253 proposes the version-history feature. It can provide access
  to the version history of a resource, "even after all version- 
controlled
  resources for that version history have been deleted". In terms of the
  binding model this means "when all bindings to it in any collection
  version have been deleted". RFC 3253 doesn't propose a way to  
reinstate
  a version history in the URI namespace of a server. With the BIND  
method
  there is a possibility by using a resource-id as the value of the href
  element. In practice, this is a way for an end-user to recover an
  accidentally deleted version-controlled resource.
Best regards,
Werner.
--
Werner Donn?  --  Re                                     https://www.pincette.biz
Engelbeekstraat 8                                               https://www.re.be
BE-3300 Tienen
tel: (+32) 486 425803	e-mail: werner.donne@re.be

Received on Monday, 11 August 2008 12:01:25 UTC