|
XML Technical Committee
updated April 22 2011
Charter
TC-XML will develop the following specifications:
- A specification for a two-way reference mapping of iCalendar to XML.
- A core abstract calendaring API, and concrete web services bindings 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.
The main audience for the specifications will be software developers.
The TC will consider prior art wherever possible, and the TC will work with other
CalConnect TCs as necessary to produce this work.
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.
- Deliver calendaring web service specifications for REST and SOAP
frameworks.
Non-goals for WS-Calendar work
- Provide a mechanism for discovery of endpoints that support WS-Calendar
- Describe 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)
Harmonization of WS-Calendar work (Cal-WS) and OASIS WS CALENDAR
The TC XML work in this area will be published as a CalConnect Proposal: Cal-WS. This work will be formally contributed to and be included within the body of the WS-Calendar specification being developed by OASIS. It is the goal of CalConnect and OASIS to maintain harmonization between the Cal-WS specification and WS CALENDAR. To this end, the two bodies will coordinate and agree upon any proposed changes to Cal-WS, which will be made by TC XML. Upon publication of the new revision of Cal-WS, it will be re-contributed to OASIS to allow a revision of WS CALENDAR incorporating the new revision of Cal-WS.
Begin and End Dates
|
Begin: |
February 2008 |
|
End: |
TBD |
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:
- November 2009: Updated specification based on feedback and WS-Calendar requirements.
- March 2010: Final specification including support for resource linking.
- April 2011: xCal (iCalendar in XML) Last Call initiated in IETF.
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:
- March 2010:Initial core abstract API specification
and WS-Calendar specification meeting.
- May 2010: Deliver V1.0 of core abstract API specification and
Cal-WS RESTful specification.
- October 2010: Deliver final specification.
TC-XML Reflector Mailing List
tc-xml-l
You must be an employee of a Consortium member to be subscribed to this mailing list.
You must be subscribed to the TC-XML mailing list to post messages to this mailing list.
Chair
Mike Douglass, Rensselaer Polytechnic Institute:
Please contact the Chairs for more information or to join this
Technical Committee. You must be an employee of a Consortium member to participate in a Technical Committee.
|
