Subject: DEFAULT_VCAR

From: Doug Royer <[email-masked]>
Date: Sun, 27 Feb 2000 15:36:02 -0800

The DEFAULT_VCAR Calendar Property (12.2) only allows for one
VCAR.

Unless there are objects, I'll change it be multi value. As it
can be impossible to specify a single VCAR for all needs.

I am going to change the name from DEFAULT_VAR to DEFAULT_VCARS.

I have also added what I think are the minimum VCARs needed (CAR-MIN):

Predefined calendar access CARIDs that MUST be implemented (CAR-MIN) are
below. What they contain is up to an implementation or administrator.

CARID:READBUSYTIMEINFO - Specifies rights for reading VFREEBUSY components
by anonymous and known users. Suggested VCAR to allow all users to read
VFREEBUSY components:

	BEGIN:VCAR
	CARID:READBUSYTIMEINFO
	GRANT:UPN=*;ACTION=READ;OBJECTS=VFREEBUSY;VALUE=*
	END:VCAR

CARID:REQUESTONLY - Specifies rights for creating new event invitations
(REQUEST), 
to-do assignments and journal entries by users other than the owner of the
calendar.
Suggested VCAR to allow access by nonowners to submit REQUESTs:

	BEGIN:VCAR
	CARID:REQUESTONLY
	GRANT:UPN=NONOWNER;ACTION=CREATE;OBJECT=*
	 ;OBJECT=METHOD;VALUE=REQUEST
	END:VCAR

CARID:UPDATEPARTSTATUS - Specifies rights for a user to modify their
participation
status in a calendar they do not own. Suggested VCAR to allow users to update
their
own participation status:

	BEGIN:VCAR
	CARID:UPDATEPARTSTATUS
	GRANT:UPN=*;ACTION=MODIFY
	 ;OBECT=PARTSTAT:VALUE=*
	 ;OBJECT=ATTENDEE;VALUE=SELF
	END:VCAR

CARID:DEFAULTOWNER - Specifies the default access for
any owner of a calendar.
Suggested VCAR to all owners access to their own calendars:

	BEGIN:VCAR
	CARID:DEFAULTOWNER
	GRANT:UPN=OWNER;ACTION=*;OBJECT=*;VALUE=*;
	END:VCAR