Re: CAP 13: Bad CAL-QUERY example / description?

[email protected] wrote:

>
>
>        (d) Selects every property and every component
>            that is in any "VEVENT" component, with each "VEVENT"
>            component wrapped in a BEGIN/END VALARM tags. 

Fixed to say VEVENT tags. 

>
> which is later described as:
>
>        (e) Selects all properties and all contained
>            components in all "VEVENT" components that have a "VALARM"
>            component with a "TRIGGER" property value between
>            the provided dates and times, with each "VEVENT"
>            component wrapped in a BEGIN/END VALARM tags.

Fixed to say VEVENT tags. I left that in because in the past that was a 
question.
Should the properties be in the VREPLY, or inside of a VEVENT?  Inside the
VREPLY would make it difficult to parse separate vevent objects.

>
> Bruce
> PS: Why is the spacing skewed?  Isn't it supposed to be all left edge 
> aligned when indented like that?? 

Bug in XML->RFC. Those kinds of fixes will have to be hand edited in the 
final approved push to the IETF.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
[email protected]                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards