Charter

1. A specification for a two-way reference mapping of iCalendar to XML.
2. A core abstract calendaring API, and a concrete web services binding for that API. The initial design goal for this set of specifications is based on the NIST Smart Grid requirements for a web services calendaring and scheduling API.

Goals for XML iCalendar Work

• Define a mapping of iCalendar so that the same iCalendar input always produces the same XML result.
• Define a mapping of XML to iCalendar so that the same XML input always products the same iCalendar result.
• Define a mapping so that both XML and iCalendar input can be round-tripped whenever possible without losing or changing content.
• Define a mapping which results in a destination representation which is just as concise as the source representation.
• Propose a MIME media type that can be used to transport the XML version of the iCalendar data.
• Submit the resulting specification to the IETF as an RFC.
• Inform and be informed by the current IETF work on vCard.

Non-goals for XML iCalendar Work

• Changing or improving the iCalendar specification.

Goals for WS-Calendar work

• Deliver a WS-Calendar specification that meets the needs of the NIST Smart Grid effort.
• Deliver a core abstract calendaring API that will serve as a base specification for future work, and support other protocol bindings in the future.

Non-goals for WS-Calendar work

• Provide a mechanism for discovery of endpoints that support WS-Calendar
• escribe end-to-end security mechanisms for using WS-Calendar
• Create a new abstract calendar data model (we'll use iCalendar via XML iCalendar as the abstract model)

Begin and End Dates

Milestones and Work Products

For XML iCalendar:

• Update the current XML iCalendar specification based on feedback received so far.
• Coordinate with the vCard XML format work in IETF to ensure reasonable consistency between the XML iCalendar format and the XML vCard format.
• Ensure that the XML iCalendar specification meets the needs of the WS-Calendar work.

Milestones:

• December 2009: Updated specification based on feedback received, and any WS-Calendar requirements.

For Calendar API:

• Base abstract calendaring API
• Create, retrieve, update, delete operations on the API
• Mapping of that API on to web services for WS-Calendar
• Associating the API with the iCal/xCal data models
• Demonstration of data model extensibility as needed by WS-Calendar

Milestones:

• December 2009: Deliver initial core abstract API specification and WS-Calendar specification meeting all of the requirements above.
• June 2010: Deliver final draft of core abstract API specification and WS-Calendar specification.

TC-XML Reflector Mailing List

Chair