[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CAP (Hierarchial calendars) - latest intem draft



In section 1.3


I propose we remove:

>   Hierarchical Calendars
>
>    A CS feature where a calendar has a hierarchical relationship
>    with another calendar in the CS.  The top-most calendars in the
>    hierarchical relationship have the CS as their parent.  There
>    may be multiple top-most calendars in a given CS.  Within a
>    given hierarchical relationship, all sub-calendars have a
>    calendar with a "parent" relationship.  In addition, sub-
>    calendars may have a relationship with another calendar that
>    has a "child" relationship.  The hierarchical calendar feature
>    is not a storage relationship of the calendars within the CS.
>    Instead it is a feature that relates access control rights to
>    calendar content between different calendars in the CS.  The
>    hierarchical relationship of a calendar is specified in the
>    "PARENT" and "CHILD" calendar properties.

And replace it with something like:

     Related Calendars

     A CS feature where a calendar has a relationship with another
     calendar. The relationship is specified in the calendar with
     the RELATED-TO calendar property. This relationship has no
     predefined meaning to CAP. It is a convince for the CUA, CU,
     or CS administrator so that calendars may be organized and
     marked as relating to each other as specified in the
     implementation or administrative configuration of the CS or
     CUA. Any CUA with sufficient access permission may view these
     RELATED-TO properties.
begin:vcard 
n:Royer;Doug
tel;cell:208-520-4044
tel;fax:208-552-1179
tel;work:208-520-4044
x-mozilla-html:FALSE
url:http://Royer.com/People/Doug
org:INET-Consulting LLC <http://INET-Consulting.com
adr:;;1795 W. Broadway #266;Idaho Falls;ID;83402;
version:2.1
email;internet:Doug@xxxxxxxxx
title:Chief Executive Manager
x-mozilla-cpt:;9152
fn:Doug Royer
end:vcard