[Ietf-caldav] Some questions with respect to the CalDAV specification draft 6

[Kai Pan]

Hi,
I am reading the CalDAV specification draft 6 and have some questions about it.

1.  In Section 8.3.1, Page 26, there is an example for the calendar-query REPORT method. In this example, the calendar-data element is like this
     <C:calendar-data>
       <C:comp name="VCALENDAR">
         <C:allprop/>
         <C:comp name="VEVENT">
           <C:prop name="X-ABC-GUID"/>
           <C:prop name="UID"/>
           ......
     
     As shown above, the <C:allprop/> element comes before the <C:comp name="VEVENT"> element, but the XML definition for the comp element in Section 10.2.1, Page 45 says that the allprop element should be behind the comp element at the same level as it:
  <!ELEMENT comp ((allcomp, (allprop | prop*)) |
                    (comp*, (allprop | prop*)))>

So, I am a bit confused here. Did I understand wrong or something?

2. In Section 10.1, Page 44, the calendar-query element is defined as below:
   <!ELEMENT calendar-query (DAV:allprop | DAV:propname | DAV:prop)?
                            calendar-data? filter>

I just wonder whether it is a sequence and there is order among (DAV:allprop | DAV:propname | DAV:prop)?, calendar-data?, and filter. Should there be commas among them and a pair of parenthesis that enclose them?

3. The calendar-data element is defined as
   <!ELEMENT calendar-data ((comp?, expand-recurrence-set?) |
                 #PCDATA)?>
   But, when calendar-data elements appear in the REPORT response, can I assume that the calendar-data element can only be PCDATA, but comp or expand-recurrence-set?

Thanks.

Kai Pan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/ietf-caldav/attachments/20050718/d9972f59/attachment.htm