head	1.2;
access;
symbols
	V0_1:1.1.1.1 ICAL_INIT:1.1.1;
locks; strict;
comment	@# @;


1.2
date	2000.07.20.21.30.24;	author jeffp;	state Exp;
branches;
next	1.1;

1.1
date	2000.07.18.04.27.48;	author jeffp;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	2000.07.18.04.27.48;	author jeffp;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Added a first cut of the VFreeBusy object. Some other minor clean up.
@
text
@This is a list of things that need to be done in the iCalendar implementation.

HIGH PRIORITY

1. DB Persistence for the Attendee Property. (90%)

   A. Add delete functionality 
   B. More Testing

2. DB Persistence for the Categories Property. (60%)
   A. Add Update functionality
   B. Add delete functionality
   C. Load the Language parameter automatically
   D. Deal with the case where we need more than one Category property
          As far as this implementation we will have one Category per language
          value.
   E. Automatically delete a category entry when removing them from the
          object.

3. DB Persistence for the Comment Property. (70%)

4. DB Persistence for the Contact Property. (70%)

5. DB Persistence for the ExDate Property. (70%)

6. DB Persistence for the ExRule Property. (70%)

7. DB Persistence for the RStatus Property. (70%)

8. DB Persistence for the Related Property. (70%)

9. DB Persistence for the Resources Property (60%)
    A. Add Update functionality
    B. Add delete functionality
    C. Load the Language and Alternate Representation Parameters automatically
    D. Deal with the case where we need more than one Resource per Language 
           Value.

10. DB Persistence for the RDate Property (70%)

11. DB Persistence for the RRule Property (70%)

12. DB Persistence for the X-Prop Property (70%)

13. DB Persistence for the Delegatee Parameter

14. DB Persistence for the Delegator Parameter

15. DB Persistence for the Member Parameter

16. Work with integrating the iCalendar objects with Turbine Users and
       permissions.

17. Work with tying in related objects (ie this category goes with this event)
       as in joining or a set of select statements.

18. Fix bug somewhere in Turbine or Village where the database id does not
exist a record where it should.

19. Define an object to store common database information object where the
 database id, parent id, parent table name etc can live.

20. Set the database id on an insert in saveToDB(). 

21. Add support for rfc1766 on the language parameter.

22. Add support for rfc822 on the UID property.

23. Add support for rfc1738 for the calendar address types.

24. Split out the exception and recur dates from the dtend and dtstart dates
because exception and recur dates can have multiple values.
@


1.1
log
@Initial revision
@
text
@d71 2
a72 1

@


1.1.1.1
log
@iCalendar 0.1 pre-release
@
text
@@
