Re: CAP (Hierarchial calendars) - latest intem draft

["John Stracke" <jstracke@xxxxxxxxxxxxxxxxxxxx>]

>        This document specifies how a Calendar User Agent (CUA)
>interacts with a Calendar Store (CS) to manage calendar
>information. In particular, it specifies how to query, create,
>modify, and delete iCalendar components (e.g., events, to-dos, or
>daily journal entries). It further specifies how to search for
>available busy time information.
[...]
>The 1st paragraph expressly includes 2445 components but NOT the ones
>in this draft (ie: VAGENDAs).

I don't see that at all.  2445 is not the only document that will ever 
define iCalendar components.  If CAP defines VAGENDA, then that's an 
iCalendar component.  Or are you pointing to the fact that only 2445 
components are listed? That list is not exhaustive, because it starts with 
"e.g.".

/=======================================================\
|John Stracke                   |Principal Engineer     |
|jstracke@xxxxxxxxxxxxxxxxxxxx  |Incentive Systems, Inc.|
|http://www.incentivesystems.com|My opinions are my own.|
|=======================================================|
|I'm not a bibliophile, I'm a bibliophiliac. Put me in a|
|bookstore, & my wallet bleeds.                         |
\=======================================================/