Tango.info event

From tango.info wiki
Jump to navigation Jump to search

Template:Event

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

Elements

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.

Type Name RFC5545 section Values Usage in tango.info
property categories 3.8.1.2 milonga,festival,lesson ... active
property class 3.8.1.3 PUBLIC, PRIVATE, CONFIDENTIAL considered
property comment 3.8.1.4 varchar(500) active
property description 3.8.1.5 RFC: can have language tag considered as standalone, currently for festivals this value is generated
property geo 3.8.1.6 derived from location?
property location 3.8.1.7 split into several fields, e.g. country
property status 3.8.1.11 confirmed,cancelled active
property summary 3.8.1.12 varchar(255) // -> tango.info event name, RFC: can have language tag active
property attendee 3.8.4.1 table: event_attendee contains artists
parameter partstat 3.8.4.1 ATTENDEE, 3.2.12 ACCEPTED, DECLINED, TENTATIVE considered
property contact 3.8.4.2 <text> considered
property organizer 3.8.4.3 considered
property recurrence-id 3.8.4.4 considered, mark summer breaks and modifications?
property related-to 3.8.4.5 considered
property url 3.8.4.6 RFC: does not attempt to standardize the form of the URI, nor the format of the resource pointed considered
property uid 3.8.4.7 considered
property exdate 3.8.5.1 active
property rdate 3.8.5.2 considered
property rrule 3.8.5.3 active
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
property created 3.8.7.1 active
property dtstamp 3.8.7.2 Note: RFC says has to be present urgent
property last-modified 3.8.7.3 RFC: can be present active