BIND issue "binding properties", was: I-D ACTION:draft-ietf-webdav-bind-07.txt

See 
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JanMar/0154.html> 
and 
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JanMar/0146.html>.

As far as I understand, this issue is about the BIND spec being 
incompatible with servers that vary the value of a property based on the 
request-URI to which a PROPFIND request was applied.

The authors feel that properties are part of the state of the resource, 
and all the BIND spec defines are additional access paths to the same 
resource. Thus, property values should not vary based on the request-URI.

If a particular server (such as the Microsoft servers mentioned in 
Lisa's mail) behave differently, they'll have to make changes if they 
*also* want to support the BIND protocol (as far as I can tell, there 
are no plans to do that, so I don't think we should worry about that).

In the discussion thread 
(<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004JanMar/thread.html#154>), 
I see three people agreeing (Geoff, Jason and myself) and nobody 
supporting Lisa's point of view, so, as far as I can tell, there was a 
rough consensus that this isn't a problem at *that* point of time.

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

Received on Friday, 15 October 2004 18:59:53 UTC