Tango.info event: Difference between revisions

Revision as of 2013-07-15T03:51:24

Notes about the implementation of the Event Component (RFC 5545 3.6.1) in tango.info.

If an element name is the same as a field name in tango.info iCal, then its possible values are restricted by the iCal definition.

Name	RFC5545 section	Values	Usage in tango.info
categories	3.8.1.2	milonga,festival,lesson ...	active
class	3.8.1.3	PUBLIC, PRIVATE, CONFIDENTIAL	considered
comment	3.8.1.4	varchar(500)	active
description	3.8.1.5	RFC: can have language tag	considered as standalone, currently for festivals this value is generated
geo	3.8.1.6		derived from location?
location	3.8.1.7		split into several fields, e.g. country
status	3.8.1.11	confirmed,cancelled	active
summary	3.8.1.12	varchar(255) // -> tango.info event name, RFC: can have language tag	active
attendee	3.8.4.1		table: event_attendee contains artists
partstat	3.8.4.1 ATTENDEE	accepted, declined, tentative	considered
contact	3.8.4.2	<text>	considered
organizer	3.8.4.3		considered
recurrence-id	3.8.4.4		considered, mark summer breaks and modifications?
related-to	3.8.4.5		considered
url	3.8.4.6	RFC: does not attempt to standardize the form of the URI, nor the format of the resource pointed	considered
uid	3.8.4.7		considered
exdate	3.8.5.1		active
rdate	3.8.5.2		considered
freq	3.8.5.3 RRULE	YEARLY, MONTHLY, WEEKLY	active
interval	3.8.5.3 RRULE	if interval=1, then empty. Only other value in tango.info currently: 2	active
byday	3.8.5.3 RRULE	MO,TU,WE,TH,FR,SA,SU, 1MO,1TU,..,2MO,..,3MO,..,4MO, 5MO, -1MO,..,-1SU	active
until	3.8.5.3 RRULE		considered

@@ Line 5: / Line 5: @@
 [[Template:Event]]
-Notes about the implementation of the Event Component [http://tools.ietf.org/html/rfc5545#section-3.6.1 RFC 5545 3.6.1] in tango.info.
+Notes about the implementation of the Event Component ([http://tools.ietf.org/html/rfc5545#section-3.6.1 RFC 5545 3.6.1]) in tango.info.
 ==Elements==