W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2006

[Bug 50] Property teminology inconsistent with RFC3253

From: <bugzilla@soe.ucsc.edu>
Date: Sun, 1 Jan 2006 04:18:01 -0800
Message-Id: <200601011218.k01CI1EV002965@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=50

julian.reschke@greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From julian.reschke@greenbytes.de  2006-01-01 04:18 -------
The changes look good to me, except that I would prefer to use some other
property than DAV:getcontentlength as example for "protected" (because that one
is even computed). Such as:

Section 14., para. 2:
OLD:

    A protected property is one which cannot be changed with a PROPPATCH
    request.  There may be other requests which would result in a change
    to a protected property (as when a PUT request to an existing
    resource causes DAV:contentlength to change to a new value).  Note
    that a given property could be protected on one type of resource, but
    not protected on another type of resource.

NEW:

    A protected property is one which cannot be changed with a PROPPATCH
    request.  There may be other requests which would result in a change
    to a protected property (as when a LOCK request affects the value of
    DAV:lockdiscovery).  Note that a given property could be protected on
    one type of resource, but not protected on another type of resource.




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Received on Sunday, 1 January 2006 12:18:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:12 GMT