<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.webdav">
    <title>gmane.ietf.webdav</title>
    <link>http://blog.gmane.org/gmane.ietf.webdav</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7352"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7349"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7345"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7343"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7338"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7336"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7330"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7311"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7301"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7299"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7298"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7297"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7293"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7286"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7285"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7254"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7251"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7250"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7241"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.webdav/7225"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7352">
    <title>LOCKing an unmapped URL</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7352</link>
    <description>&lt;pre&gt;If a write lock is successfully created on an unmapped URL, should an 
ETag (with associated Location header) be returned for the empty 
resource in the 201 response?

&lt;/pre&gt;</description>
    <dc:creator>Ken Murchison</dc:creator>
    <dc:date>2013-01-03T20:59:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7349">
    <title>If header field and conditional precedence</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7349</link>
    <description>&lt;pre&gt;Happy Holidays to All!

I'm trying to figure out where the If header field fits in the 
precedence order outlined in:
http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-21#section-5

I assume that the If header field should be evaluated in a step 0, but 
my question is what should happen when the If header is present and 
evaluates to true?  Should processing continue to step 3 or step 1?  In 
other words, does If completely supersede If-Match, where a client 
wishing to submit both a state token and an ETag MUST only use If, or is 
a client allowed to submit a state token with If AND submit an ETag with 
If-Match?

In text, the two options might look something like this:

    0.  When If is present, evaluate it:

        *  if true, continue to step 3

        *  if false, respond 412 (Precondition Failed)

    1.  When If is not present and If-Match is present,
        evaluate it:

    ...


OR


    0.  When If is present, evaluate it:

        *  if true, continue to step 1

        *  if fals&lt;/pre&gt;</description>
    <dc:creator>Ken Murchison</dc:creator>
    <dc:date>2012-12-23T21:00:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7345">
    <title>Ambiguous example for COPY in RFC 4918</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7345</link>
    <description>&lt;pre&gt;Dear all,

this is my first post to this list so, if this is not the correct
mailing list to discuss the topic, please, just tell me and I'll forward
it to a more appropriate forum.

We're working at a C# implementation of RFC 4918 and while most parts of
it are quite clear we found one example that, if taken with the text
preceding it, is quite puzzling. About a COPY operation with infinite
Depth and Overwrite:T the RFC says:

    9.8.4 COPY and Overwriting Destination Resources

    [...]
    When a collection is overwritten, the membership of the destination
    collection after the successful COPY request must be the same
    membership as the source collection immediately before the COPY.
    Thus, merging the membership of the source and destination
    collections together in the destination is not a compliant behavior.
    [...]

But the example "9.8.8 Example - COPY of a Collection" says that
"[...]Because there was an error copying R2, none of R2's members were
copied.[...]". Our understanding is t&lt;/pre&gt;</description>
    <dc:creator>Federico Di Gregorio</dc:creator>
    <dc:date>2012-08-29T10:29:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7343">
    <title>Microsoft Mini-Redirector Bug with respect to handling DAV:href</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7343</link>
    <description>&lt;pre&gt;Hi there,

reporting here so it get's archived:

Version: Microsoft-WebDAV-MiniRedir/6.1.7601

Problem: client is doing a PROPFIND request without payload, thus 
defaulting to DAV:allprop.

Server returns a custom property than *contains* a DAV:href child 
element, like that:

&amp;lt;D:response&amp;gt;
   &amp;lt;D:href&amp;gt;/foo/bar.txt&amp;lt;/D:href&amp;gt;
   &amp;lt;D:propstat&amp;gt;
     &amp;lt;D:prop&amp;gt;
       &amp;lt;D:displayname&amp;gt;bar.txt&amp;lt;/D:displayname&amp;gt;
       &amp;lt;D:creationdate&amp;gt;2012-06-01T12:52:57Z&amp;lt;/D:creationdate&amp;gt;
       &amp;lt;D:resourcetype/&amp;gt;
       &amp;lt;D:lockdiscovery/&amp;gt;
       &amp;lt;D:getcontenttype&amp;gt;text/plain; charset=UTF-8&amp;lt;/D:getcontenttype&amp;gt;
       &amp;lt;C:linked-from xmlns:C="http://example.com/ns"&amp;gt;
         &amp;lt;D:href&amp;gt;/qux&amp;lt;/D:href&amp;gt;
       &amp;lt;/C:linked-from&amp;gt;
       &amp;lt;D:getetag&amp;gt;"7248-1338555179558"&amp;lt;/D:getetag&amp;gt;
       &amp;lt;D:getlastmodified&amp;gt;Fri, 01 Jun 2012 12:52:59 GMT&amp;lt;/D:getlastmodified&amp;gt;
       &amp;lt;D:supportedlock&amp;gt;
         &amp;lt;D:lockentry&amp;gt;
           &amp;lt;D:lockscope&amp;gt;&amp;lt;D:exclusive/&amp;gt;&amp;lt;/D:lockscope&amp;gt;
           &amp;lt;D:locktype&amp;gt;&amp;lt;D:write/&amp;gt;&amp;lt;/D:locktype&amp;gt;
         &amp;lt;/D:lockentry&amp;gt;
       &amp;lt;/D:supportedlock&amp;gt;
      &lt;/pre&gt;</description>
    <dc:creator>Julian Reschke</dc:creator>
    <dc:date>2012-06-02T09:38:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7338">
    <title>webDAV apple open source</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7338</link>
    <description>&lt;pre&gt;I am having a hard time compiling the webDAV apple open source codes.  I am
missing NetFS/NetFSPrivate.h header files.  Anyone has access to that file?

Thanks.
&lt;/pre&gt;</description>
    <dc:creator>Syl-J CALIMPUSAN</dc:creator>
    <dc:date>2012-02-09T01:40:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7336">
    <title>New Version Notification for draft-daboo-webdav-sync-07.txt (fwd)</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7336</link>
    <description>&lt;pre&gt;Hi folks,
FYI We have posted a new -07 version of the sync report draft that 
addresses the last call, IESG review etc comments. Please take a look at 
the changes and make sure these are OK.

------------ Forwarded Message -----------
Date: January 19, 2012 8:18:19 AM -0800
From: internet-drafts&amp;lt; at &amp;gt;ietf.org
To: cyrus&amp;lt; at &amp;gt;daboo.name
cc: cyrus&amp;lt; at &amp;gt;daboo.name, arnaud.quillaud&amp;lt; at &amp;gt;oracle.com
Subject: New Version Notification for draft-daboo-webdav-sync-07.txt

A new version of I-D, draft-daboo-webdav-sync-07.txt has been successfully
submitted by Cyrus Daboo and posted to the IETF repository.

Filename: draft-daboo-webdav-sync
Revision: 07
Title: Collection Synchronization for WebDAV
Creation date: 2012-01-19
WG ID: Individual Submission
Number of pages: 32

Abstract:
   This specification defines an extension to Web Distributed Authoring
   and Versioning (WebDAV) that allows efficient synchronization of the
   contents of a WebDAV collection.

Editorial Note (To be removed by RFC Editor before publication)

   Please&lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2012-01-19T16:21:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7330">
    <title>About COPY Overwrite:T Depth:0</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7330</link>
    <description>&lt;pre&gt;RFC 4918 section 9.8.4 defines overwrite with Depth:infinity (When a
collection is overwritten, the membership of the destination collection after
the successful COPY request MUST be the  same membership as the source
collection immediately before the COPY), but the exact meaning of an overwrite
copy with Depth:0 is not defined.

I would like to know what is the expected behavior of a COPY with Overwrite:T
and Depth:0? i.e. whether /dst/bar exists or not, after the following methods
are executed in order:

MKCOL /src
MKCOL /src/foo
MKCOL /dst
MKCOL /dst/bar
COPY /src to /dst with Depth:0 and Overwrite:F


collection and its properties, but not resources identified by its internal
member URLs, are to be copied.

The Litmus test suite (v0.13) does not check this behavior. There is a fork of
Litmus that expects the resource to exists after the Depth:0 copy (test
depth_zero_copy in http://github.com/tolsen/litmus/), but the test suite of
PerlDAV v0.45 takes the opposite approach (test 6_dav_copy_move.t). What is&lt;/pre&gt;</description>
    <dc:creator>Javier Godoy</dc:creator>
    <dc:date>2011-12-15T00:17:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7311">
    <title>WebDAV sync report client support</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7311</link>
    <description>&lt;pre&gt;Does anybody know which clients support sync-collection?  I know that 
Lightning does, and the version of iCal that I have (4.0.4) doesn't 
appear to.

&lt;/pre&gt;</description>
    <dc:creator>Ken Murchison</dc:creator>
    <dc:date>2011-11-22T21:40:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7301">
    <title>WebDAV sync report w/invalid sync token</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7301</link>
    <description>&lt;pre&gt;Folks,

What is the proper response code for a sync-collection report if the 
sync-token is either invalid or out of date?  The I-D doesn't seem to 
specify, so looking at RFC 3253 section 1.6 it appears that 403 and 409 
are the two options for a precondition failure, with 409 presumably 
being the correct choice in this case.  Am I missing something?

Thanks,
Ken

&lt;/pre&gt;</description>
    <dc:creator>Ken Murchison</dc:creator>
    <dc:date>2011-11-15T13:32:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7299">
    <title>If Header interaction with If-Match, etc</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7299</link>
    <description>&lt;pre&gt;What, if any, interaction does the If header have with the other 
conditional headers?  HTTPbis part 4 
(http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional) 
specifically states which headers can't/shouldn't be used together.

I assume that If-Match and If-None-Match shouldn't be used with If, but 
what about If-[un]modified-Since and If?  Should an implementation just 
look for and use If when specified and ignore all other conditionals?

&lt;/pre&gt;</description>
    <dc:creator>Ken Murchison</dc:creator>
    <dc:date>2011-11-10T23:58:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7298">
    <title>WebDAV sync last call</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7298</link>
    <description>&lt;pre&gt;Hi folks,
The authors believe the WebDAv Sync document 
(&amp;lt;https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/&amp;gt;) is ready to 
go to the IESG for consideration of publishing as an RFC. We'd like to get 
final reviews from this list along with a list of existing or planned 
implementations of this draft to include as supporting documentation for 
the IESG. Please review and provide feedback, thanks.

&lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2011-08-30T13:38:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7297">
    <title>DAV ACL question</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7297</link>
    <description>&lt;pre&gt;Folks,

Still a relative DAV newbie and trying to wrap my head around RFC 3744. 
  If I have an implementation where DAV:read-current-user-privilege-set 
can not be split from DAV:read, and DAV:read-acl, DAV:write-acl, 
DAV:unlock can not be separated from one another, is the response below 
correct?

I have DAV:read-current-user-privilege-set as abstract under DAV:read, 
and I have DAV:read-acl, DAV:write-acl, DAV:unlock all as abstract under 
a private aggregate right CYRUS:admin.

Actually, looking at this again, since all of the member privileges 
contained in the DAV:write aggregate have been granted to the current 
user, should DAV:write also be listed?


&amp;lt;?xml version="1.0" encoding="utf-8"?&amp;gt;
&amp;lt;D:multistatus xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"
       xmlns:CY="http://cyrusimap.org/ns/"&amp;gt;
   &amp;lt;D:response&amp;gt;
     &amp;lt;D:href&amp;gt;/calendars/user/ken/events/&amp;lt;/D:href&amp;gt;
     &amp;lt;D:propstat&amp;gt;
       &amp;lt;D:status&amp;gt;HTTP/1.1 200 OK&amp;lt;/D:status&amp;gt;
       &amp;lt;D:prop&amp;gt;
         &amp;lt;D:supported-privilege-set&amp;gt;
           &amp;lt;D:supp&lt;/pre&gt;</description>
    <dc:creator>Ken Murchison</dc:creator>
    <dc:date>2011-08-25T16:04:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7293">
    <title>PROPFIND vs. Accept: vs. variants</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7293</link>
    <description>&lt;pre&gt;I've encountered some behavior that surprised me from Apache's mod_dav and I'm trying to figure out what the correct behavior is. Specifically, what is the interpretation of the Accept: header sent with a PROPFIND (or other DAV request other than GET)?

I have a server with mod_dav and MultiViews enabled, and files foo.txt and foo.png. As a result of this, Apache presents a resource at 'foo', whose content and content-type vary depending on the Accept: header sent in the GET request. This is as expected and as desired.

If I do a PROPFIND on that resource, I get information about either the txt or the png variant, depending on the Accept header sent in the PROPFIND request. If I supply 'Accept: application/xml', then the PROPFIND fails entirely with HTTP status 406. So clearly Apache is using the Accept: header to select the variant on which to run the PROPFIND. This is unexpected (to me), but makes a certain amount of sense. (The &amp;lt;href&amp;gt; in the PROPFIND result always returns the url with the appropriate exte&lt;/pre&gt;</description>
    <dc:creator>Wim Lewis</dc:creator>
    <dc:date>2011-04-20T21:07:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7286">
    <title>WebDAV sync informal last call</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7286</link>
    <description>&lt;pre&gt;Hi folks,
It is our intent to submit draft-daboo-webdav-sync-05 to the IETF. As such 
we would appreciate it if you could give this one final review and post 
comments back to this list (including "ok to go" comments) so we can show 
the ADs that review has been done by various WebDAV experts.

BTW there are already several client and server implementations of this 
draft now and I believe most implementors are happy with what we have done.

&lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2011-04-07T14:00:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7285">
    <title>1st CFP: IJCAI-11 Workshop on Discovering Meaning On the Go in Large  &amp; Heterogeneous Data (LHD-11)</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7285</link>
    <description>&lt;pre&gt;Apologies for cross-posting

------------------------------------------------------------------------------
Call for papers for LHD-11 workshop at IJCAI-11, July 2011, Barcelona:

Discovering Meaning On the Go in Large &amp;amp; Heterogeneous Data

http://dream.inf.ed.ac.uk/events/lhd-11/
------------------------------------------------------------------------------

An interdisciplinary approach is necessary to discover and match meaning
dynamically in a world of increasingly large data.  This workshop aims
to bring together practitioners from academia, industry and government
for interaction and discussion.  The workshop will feature:

*  A panel discussion representing industrial and governmental input,
entitled "Big Society meets Big Data: Industry and Government
Applications of Mapping Meaning".  Panel members will include:
 *  Peter Mika (Yahoo!)
 *  Alon Halevy (Google)
 *  Tom McCutcheon (Dstl)
 *  (tbc)
*  An invited talk from Fausto Giunchglia, discussing the relationship
between social computing and ontol&lt;/pre&gt;</description>
    <dc:creator>Michael Chan</dc:creator>
    <dc:date>2010-12-18T00:48:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7254">
    <title>Proposal for work on an efficient, browser-friendly, HTTP-based communication  protocol for fine-grained information exchange</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7254</link>
    <description>&lt;pre&gt;Proposal for work on an efficient, browser-friendly, HTTP-based 
communication protocol for fine-grained information exchange

HTTP/1.1 (RFC 2616) already contains a set of tools for modifying 
resources , namely the methods PUT, POST, and DELETE.

Many systems have been built on top of this, most of them in an ad-hoc 
manner (which is ok when client and server are controlled by the same 
developers).

We would like to cover some of the following use cases extending the 
resource oriented model.

(1) An simple javascript based browser application should be able to 
read fine-grained information (comparable to WebDAV properties) in a 
simple manner using a defined JSON format to be consumed in an intuitive 
fashion.

(2) A simple HTML Form should be able to write information in a patch 
oriented manner containing both binary (file) data and fine-grained, 
typed information using a multipart POST.

(3) A simple javascript application should be able to write information 
in a patch oriented fashion using a defi&lt;/pre&gt;</description>
    <dc:creator>Julian Reschke</dc:creator>
    <dc:date>2010-08-12T08:36:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7251">
    <title>status code 425</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7251</link>
    <description>&lt;pre&gt;Hi,

I just found in &amp;lt;http://www.iana.org/assignments/http-status-codes&amp;gt;:


RFC 2817 says 
(&amp;lt;http://greenbytes.de/tech/webdav/rfc2817.html#rfc.section.7.1&amp;gt;):

 &amp;gt; 3. WebDAV Advanced Collections [5] (Work in Progress) [defines 425]

where [5] is:


...which of course isn't *that* helpful (RFC Editor, you listening? :-)

Anyway, this seems to come from 
&amp;lt;http://tools.ietf.org/html/draft-ietf-webdav-collection-protocol-04#section-7.2&amp;gt; 
which says:


That draft was never finished, but RFC 3648 ("Web Distributed Authoring 
and Versioning (WebDAV) Ordered Collections Protocol") was. That uses 
the precondition name "DAV:collection-must-be-ordered" instead 
(&amp;lt;http://greenbytes.de/tech/webdav/rfc3648.html#rfc.section.6.1&amp;gt;).

I don't believe anybody has implemented status code 425.

Maybe we should un-reserve it in the IANA registry?

Best regards, Julian


&lt;/pre&gt;</description>
    <dc:creator>Julian Reschke</dc:creator>
    <dc:date>2010-07-20T17:11:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7250">
    <title>Could not access /webdav/</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7250</link>
    <description>&lt;pre&gt;Hi All,
     I followed the instruction given at link
http://www.howtoforge.com/how-to-set-up-webdav-with-apache2-on-opensuse-11.2 to
set up WebDav with Apache2 on OpenSuse-11.2. Later, as given on tha same
page, I used *cadaver *to test WebDav during which I am getting following
error.
*   *
*   Could not access /webdav/ (not WebDAV-enabled?):*
*   405 Method Not Allowed*
*   Connection to `www.example1.com' closed.*

Could someone please help me to resolve the issue ?

Thanks
Shyam
&lt;/pre&gt;</description>
    <dc:creator>Shyam Burkule</dc:creator>
    <dc:date>2010-07-08T09:40:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7241">
    <title>304 or 412 for If-Modified-Since?</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7241</link>
    <description>&lt;pre&gt;Hi folks,
RFC 2616 in Section 14.25 "If-Modified-Since" states that a 304 should be 
returned if the resource is not modified.

RFC 4918 in Section 12.1 "412 Precondition Failed" states that a 412 should 
be returned when a conditional header fails to hold.

So what should clients expect from WebDAV servers?

Second, does If-Modified-Since make sense for PROPFIND or REPORT requests?

&lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2010-06-30T01:29:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7225">
    <title>WebDAv collection sync: last issue</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7225</link>
    <description>&lt;pre&gt;Hi folks,
The latest WebDAV collection sync draft is here: 
&amp;lt;https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/&amp;gt;. We believe we 
are close to done with this and would like to submit to the IESG soon. 
However, there is one open issue that we need feedback from implementors on.

The question is whether collection resources that are immediate children of 
the collection being targeted for the REPORT should be reported as 
"modified" if any of their child resources (depth infinity) are modified.

Key points:

1) We have deliberately scoped the REPORT defined in this draft to be 
Depth:1 only - i.e. it will only report changes to immediate children. 
Depth:infinity change reporting was ruled out at this time (though 
eventually we would expect to see it defined if there is interest).

2) The first real implementations of this REPORT are being done for CalDAV 
and CardDAV servers where typically calendar/addressbook collections only 
have immediate child resources and not collections - so the draft as 
cur&lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2010-06-07T13:57:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.webdav/7224">
    <title>ACL: DAV:privilege element - multiple child elements?</title>
    <link>http://comments.gmane.org/gmane.ietf.webdav/7224</link>
    <description>&lt;pre&gt;Hi,
RFC3744 defines DAV:privilege as:

&amp;lt;!ELEMENT privilege ANY&amp;gt;

"ANY" technically implies one or more child elements. However, all examples 
in 3744 have just a single child. It has been my assumption that only one 
child is allowed. However, I recently came across a server that is 
returning multiple child elements. So what is, or is not, allowed here?

&lt;/pre&gt;</description>
    <dc:creator>Cyrus Daboo</dc:creator>
    <dc:date>2010-06-07T13:40:26</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.webdav">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.webdav</link>
  </textinput>
</rdf:RDF>
