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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Thomas Roessler
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  <[hidden email]>








Reply | Threaded
Open this post in threaded view
|

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

masinter
(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: [hidden email] [mailto:[hidden email]] 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  <[hidden email]>









Reply | Threaded
Open this post in threaded view
|

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

Harry Halpin
2010/1/27 Larry Masinter <[hidden email]>:
> (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.
>
I might add there is the non-IETF but quite popular PortableContacts
(part of OpenSocial) that is quite close to vCard, and FOAF [2]. If
people want, I'm happy to devote W3C Social Web XG conference call
time/irc chat (16:00-18:00 UTC) for people to co-ordinate and discuss
this, as well as our list-serv [3]. We really need to make sure all
these efforts line up so people don't go crazy...

[1]http://code.google.com/apis/contacts/docs/poco/1.0/developers_guide.html
[2]http://xmlns.com/foaf/spec/
[3]http://www.w3.org/2005/Incubator/socialweb/

>
> 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: [hidden email] [mailto:[hidden email]] 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  <[hidden email]>
>
>
>
>
>
>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

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

Mark Nottingham-2
In reply to this post by Thomas Roessler
Thomas,

I've CC'ed the chairs of the relevant WGs:
  * <vcarddav http://www.ietf.org/dyn/wg/charter/vcarddav-charter.html>
  * <calsify http://www.ietf.org/dyn/wg/charter/calsify-charter.html>

Cheers,


Begin forwarded message:

> From: Thomas Roessler <[hidden email]>
> Date: 28 January 2010 3:00:37 AM AEDT
> To: Mark Nottingham <[hidden email]>
> Cc: Thomas Roessler <[hidden email]>, Dominique Hazaël-Massieux <[hidden email]>, public-ietf-w3c <[hidden email]>, Frederick Hirsch <[hidden email]>, Robin Berjon <[hidden email]>
> 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  <[hidden email]>
>
>
>
>
>
>
>


--
Mark Nottingham     http://www.mnot.net/


Reply | Threaded
Open this post in threaded view
|

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

Thomas Roessler
Thanks, Mark.

I'd be particularly interested in hearing more about the relevant WGs' attitudes toward subsetting of the data formats defined.

I'll also note that the Device API WG's specifications will describe both APIs to manipulate calendaring and contact data, an a mapping of the vCard and iCalendar data models into JavaScript objects.  The latter might potentially turn into a canonical JSON mapping for these objects.

Regards,
--
Thomas Roessler, W3C  <[hidden email]>







On 28 Jan 2010, at 04:02, Mark Nottingham wrote:

> Thomas,
>
> I've CC'ed the chairs of the relevant WGs:
>  * <vcarddav http://www.ietf.org/dyn/wg/charter/vcarddav-charter.html>
>  * <calsify http://www.ietf.org/dyn/wg/charter/calsify-charter.html>
>
> Cheers,
>
>
> Begin forwarded message:
>
>> From: Thomas Roessler <[hidden email]>
>> Date: 28 January 2010 3:00:37 AM AEDT
>> To: Mark Nottingham <[hidden email]>
>> Cc: Thomas Roessler <[hidden email]>, Dominique Hazaël-Massieux <[hidden email]>, public-ietf-w3c <[hidden email]>, Frederick Hirsch <[hidden email]>, Robin Berjon <[hidden email]>
>> 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  <[hidden email]>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Mark Nottingham     http://www.mnot.net/
>
>