locked
iCal endpoint RRS feed

Answers

  • Hi Steven,

     

    We're working to put together a more detailed whitepaper on the iCal endpoint, but this information should help you get started (this is based on our .NET Micro Framework implementation):

    It is based on this iCal document: http://www.ietf.org/rfc/rfc2445.txt

    The endpoint processes a subset of the full standard. It recognizes the components VCALENDAR, VEVENT and VALARM. Each content item sent to the endpoint must be a VCALENDAR component containing a single VEVENT. The VEVENT component can contain VALARM components. If there are multiple VALARMs, the endpoint uses the earliest one.  Recurring appointments must be broken up into individual VEVENT items, each in a separate content ID.

    The endpoint processes the following properties:

     

    Code Snippet

    For Calendar:
                VERSION                  (must be “2.0”)
                CALSCALE                (must be “GREGORIAN”)

    For Event:
                ATTENDEE
                DESCRIPTION
                LOCATION
                ORGANIZER
                DTSTART
                DTEND

    For Alarm:
                TRIGGER

     

    Hope that helps,

    Dan

    Thursday, June 28, 2007 3:50 PM
    Moderator

All replies

  • Hi Steven,

     

    We're working to put together a more detailed whitepaper on the iCal endpoint, but this information should help you get started (this is based on our .NET Micro Framework implementation):

    It is based on this iCal document: http://www.ietf.org/rfc/rfc2445.txt

    The endpoint processes a subset of the full standard. It recognizes the components VCALENDAR, VEVENT and VALARM. Each content item sent to the endpoint must be a VCALENDAR component containing a single VEVENT. The VEVENT component can contain VALARM components. If there are multiple VALARMs, the endpoint uses the earliest one.  Recurring appointments must be broken up into individual VEVENT items, each in a separate content ID.

    The endpoint processes the following properties:

     

    Code Snippet

    For Calendar:
                VERSION                  (must be “2.0”)
                CALSCALE                (must be “GREGORIAN”)

    For Event:
                ATTENDEE
                DESCRIPTION
                LOCATION
                ORGANIZER
                DTSTART
                DTEND

    For Alarm:
                TRIGGER

     

    Hope that helps,

    Dan

    Thursday, June 28, 2007 3:50 PM
    Moderator
  • Here's a little more information about the Calendar endpoint:

     

    Functionality

     

    The SideShow Calendar endpoint displays daily schedules and event details. When first entered, the endpoint displays a page with the current day’s schedule in the form of a list. The current or next meeting item is highlighted. The user can page forward or backward to see the next or previous day’s schedule, respectively.

     

    Pressing the Select button navigates to a details page for the currently selected event. While viewing a details page, the user can page forward or backward to see the next or previous event’s details, respectively. Pressing the Back button takes the user to the daily schedule that contains the currently viewed event.

     

    On the SideShow home page the Calendar endpoint display the time of the last update from the PC and the time, place and subject of the next meeting.

     

    The endpoint displays pop-up reminder alerts for events that have a reminder time associated with them.

     

    Content Format

     

    The endpoint accepts content from a PC gadget in iCalendar format. Each content item contains a VCALENDAR object which contains a single VEVENT component. The VEVENT component can optionally contain a VALARM component.

     

    The endpoint processes a subset of the full iCalendar property set for each component.  The following table defines which properties are handled:

     

    Component

    Property

    Comment

    VCALENDAR

    VERSION

    Must be “2.0”

     

    CALSCALE

    If present, must be “GREGORIAN”

    VEVENT

    ATTENDEE

    Displays common name attribute

    Truncates to first three attendees

     

    DESCRIPTION

    Truncates to first 1000 characters

     

    LOCATION

     

     

    ORGANIZER

    Displays common name attribute

     

    DTSTART

    Local or universal time

     

    DTEND

    Local or universal time

     

    SUMMARY

     

    VALARM

    TRIGGER

    Uses earliest trigger that precedes the event

     

    ICalendar components, properties and attributes that are not listed in the table are skipped over.

     

    The time range of events that the endpoint will display is one week in the past to three weeks in the future. Events outside of this range are ignored.

     

    The DSTART and DEND times may be specified in local or universal time. If universal time is specified the endpoint converts the times to local time for display based on the device’s assigned time zone.

     

    All content must use UTF-8 encoding.

     

    Here is an example of a valid content item for the Calendar endpoint:

     

    BEGIN:VCALENDAR

    VERSION:2.0

    BEGIN:VEVENT

    DESCRIPTION:Go through all projects\, update status.\nExamine my role.\n

        Go through all deliverables.\nWorry about me as a big person\; big picture.

    DTEND:20071007T020000

    DTSTART:20070928T030000

    ATTENDEE;CN="John Smith"

    ATTENDEE;CN="Jane Doe"

    ORGANIZER;CN="Joe Public"

    SUMMARYStick out tongueroject Planning 3

    BEGIN:VALARM

    TRIGGER:-PT15M

    ACTIONBig SmileISPLAY

    END:VALARM

    END:VEVENT

    END:VCALENDAR

     

     

    The full iCalendar format specification can be found at: http://www.ietf.org/rfc/rfc2445.txt.

     

    Friday, September 21, 2007 2:35 AM