Re: [Reefknot-users] parents and locking

[Eric B. <er...@so...>]

On Fri, 23 Mar 2001, srl wrote:

> The POD at the bottom of many of the N::I modules is left over from
> the version of Net::ICal that had bindings to libical. That
> documentation has been left lying around as memos for things we
> might want to do in the future. It's not gospel. Offhand, I can't

None of the old Net::ICal code or documentation was carried over. There
may be a few bits that aren't clear, but all of it was written for the new
Net::ICal OO interface. 

> think of what parent-child relationships between calendars might be
> useful for. 

CAP offers calendar hierarchies, in which getting components on a parent
calendar will also return components from a child calendar. Thus, you
could overlay your work, personal and baseball team calendars. You may not
have write access to the baseball calendar, and you may not be invited to
events on it ( they may be PUBLISHed events), but the events in the
baseball calendar could block out time on your personal calendar. 

See the latest CAP draft, section 1.3, definitions, "Hierarchical
Calendar", 2.4.5 Inheritance, and ( as yet unwritten) 9.2.3 Using Parent
and Children Properties.

eric.