W3C home > Mailing lists > Public > public-ietf-w3c@w3.org > January 2010

RE: Coordination issue: vCard, iCalendar vs JavaScript contact and calendaring APIs

From: Larry Masinter <masinter@adobe.com>
Date: Wed, 27 Jan 2010 10:48:46 -0800
To: Thomas Roessler <tlr@w3.org>, Mark Nottingham <mnot@mnot.net>
CC: Dominique HazaŽl-Massieux <dom@w3.org>, public-ietf-w3c <public-ietf-w3c@w3.org>, Frederick Hirsch <Frederick.Hirsch@nokia.com>, Robin Berjon <robin@berjon.com>, "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D5FE884@nambxv01a.corp.adobe.com>
(cc www-tag with respect to "architecture for web applications"
issue).


> I'd like to check in on how to best coordinate with whatever 
> IETF efforts are going on in the space.


There have been a number of drafts, RFCs, and documents published
around network access to calendars, address books.

I'd think the best way to coordinate would be to first evaluate the 
compatibility of the new APIs with the existing network protocol
standards both as written and  as deployed, and evaluate the
compatibility issues. If there are strong reasons why W3C groups
need an incompatible data model, representation, namespace, or
method of interoperably accessing calendar or address information
than that chosen by the IETF, then those incompatibilities would
then drive the wider community review and venue.

Working through some of the use cases (e.g., show how the
JavaScript APIs could be implemented using icalendar or
ldap directory access, and showing how icalendar and ldap
use cases can be exposed via JavaScript APIs) would be
a good first technical step.

Larry
--
http://larry.masinter.net


-----Original Message-----
From: public-ietf-w3c-request@w3.org [mailto:public-ietf-w3c-request@w3.org] On Behalf Of Thomas Roessler
Sent: Wednesday, January 27, 2010 8:01 AM
To: Mark Nottingham
Cc: Thomas Roessler; Dominique HazaŽl-Massieux; public-ietf-w3c; Frederick Hirsch; Robin Berjon
Subject: Coordination issue: vCard, iCalendar vs JavaScript contact and calendaring APIs

The Device API and Policy Working Group is drafting APIs to manipulate contact and calendar data.  I'd like to check in on how to best coordinate with whatever IETF efforts are going on in the space.

An FPWD for the contacts API has already been published:
   http://www.w3.org/TR/2010/WD-contacts-api-20100121/

I'll follow up with a pointer to the Calendaring API draft when it becomes available.

Thanks,
--
Thomas Roessler, W3C  <tlr@w3.org>
Received on Wednesday, 27 January 2010 18:49:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 January 2010 18:49:46 GMT