Tango.info iCal: Difference between revisions

From tango.info wiki
Jump to navigation Jump to search
Line 46: Line 46:


{| class="wikitable"
{| class="wikitable"
! iCal
! iCal section
! iCal name
! Example
! Example
! Note
! Note
! Tango.info
! Tango.info
|-
| 3.2.3.  Calendar User Type
| CUTYPE
| ATTENDEE;CUTYPE=GROUP:mailto:ietf-calsch@example.org
| seems to identify people and resources; INDIVIDUAL, ,GROUP, ROOM ....
|
|-
| 3.2.10. Language
| LANGUAGE
|
* SUMMARY;LANGUAGE=en-US:Company Holiday Party
* LOCATION;LANGUAGE=en:Germany
| language tag per RFC5646
|-
|-
| 3.2.15.  Relationship Type
| RELTYPE
|
| PARENT, CHILD, SIBLING
|
|-
| 3.2.19.  Time Zone Identifier
| TZID
| America/New_York
|
| derive from "region"?
|-
| 3.3.12.  Time ???
| DTSTART
| DTSTART
|  
|  
Line 57: Line 84:
|     
|     
|-
|-
| 3.3.12.  Time ???
| DTEND
| DTEND
|
|
|-
|-
| 3.3.12.  Time ???
| RRULE
| RRULE
| RRULE:FREQ=WEEKLY;UNTIL=19971224T000000Z
| RRULE:FREQ=WEEKLY;UNTIL=19971224T000000Z
Line 65: Line 94:
|
|
|-
|-
| TZID
| 3.8.1.12. Summary
| America/New_York
|
| derive from "region"
|-
| LANGUAGE
|
* SUMMARY;LANGUAGE=en-US:Company Holiday Party
* LOCATION;LANGUAGE=en:Germany
| language tag per RFC5646
|-
| SUMMARY
| SUMMARY
| SUMMARY:Department Party
| SUMMARY:Department Party
Line 81: Line 100:
| 64 char
| 64 char
|-
|-
| 3.8.4.3.  Organizer
| ORGANIZER
| ORGANIZER
|  
|  
Line 89: Line 109:
|
|
|
|
|-
| CUTYPE
| ATTENDEE;CUTYPE=GROUP:mailto:ietf-calsch@example.org
| Calendar User Type, seems to identify people and resources; INDIVIDUAL, ,GROUP, ROOM ....
|
|-
|-
| 3.8.4.5.  Related To
| RELATED-TO
| RELATED-TO
|
|
*RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@example.com
*RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@example.com
|-
|-
| RELTYPE
| 3.8.1.2.  Categories
|
|
|
| use for event types?
|-
| 3.8.1.4.  Comment
|
|
| try not to use - free text can be problematic
|-
| 3.8.1.5.  Description
|
|
| to be generated?
|-
| 3.8.1.6.  Geographic Position
| GEO
|
|
| PARENT, CHILD, SIBLING
* GEO:37.386013;-122.082932
|
|
| optional
|-
|-
| 3.8.1.7.
| LOCATION
| LOCATION
|  
|  

Revision as of 2012-04-12T16:50:59


example file for one festival

BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
PRODID:-//tango info//tango info cal//EN
BEGIN:VEVENT
UID:tango.info/2010DEBERA
URL:http://www.tango.info/2010DEBERA
DTSTART:20100601T140000Z
DTEND:20100605T040000Z
SUMMARY:Festival Berlin 2010
DESCRIPTION:Festival Berlin 2010\n\nMariana Montes, Sebastián Arce
LOCATION:Berlin, Germany
GEO:52.520895,13.409672
CLASS:PUBLIC
CATEGORIES;LANGUAGE=en:tango,festival
DTSTAMP:20090101T010101
END:VEVENT
END:VCALENDAR
  • RELATED-TO;RELTYPE=SIBLING|PARENT|CHILD:tango.info/2010DEBERA

Fields

Seperators

  • 3.1.1. List and Field Separators
    • COMMA - Values in a list of values MUST be separated by a COMMA character.
    • SEMICOLON
      • Some property values are defined in terms of multiple parts. These structured property values MUST have their value parts separated by a SEMICOLON character.
      • Some properties allow a list of parameters. Each property parameter in a list of property parameters MUST be separated by a SEMICOLON character.
    • COLON ?

Example:

iCal section iCal name Example Note Tango.info
3.2.3. Calendar User Type CUTYPE ATTENDEE;CUTYPE=GROUP:mailto:ietf-calsch@example.org seems to identify people and resources; INDIVIDUAL, ,GROUP, ROOM ....
3.2.10. Language LANGUAGE
  • SUMMARY;LANGUAGE=en-US:Company Holiday Party
  • LOCATION;LANGUAGE=en:Germany
language tag per RFC5646
3.2.15. Relationship Type RELTYPE PARENT, CHILD, SIBLING
3.2.19. Time Zone Identifier TZID America/New_York derive from "region"?
3.3.12. Time ??? DTSTART
  • DTSTART;TZID=America/New_York:19980101T090000
3.3.12. Time ??? DTEND
3.3.12. Time ??? RRULE RRULE:FREQ=WEEKLY;UNTIL=19971224T000000Z UNTIL-time in UTC!
3.8.1.12. Summary SUMMARY SUMMARY:Department Party 64 char
3.8.4.3. Organizer ORGANIZER
CN
3.8.4.5. Related To RELATED-TO
  • RELATED-TO;RELTYPE=SIBLING:19960401-080045-4000F192713@example.com
3.8.1.2. Categories use for event types?
3.8.1.4. Comment try not to use - free text can be problematic
3.8.1.5. Description to be generated?
3.8.1.6. Geographic Position GEO optional
3.8.1.7. LOCATION deberwl001 (TI-location identifier, composed of country, city, venue code and running number: DE BER WL 001)

Validator