- From: Rich Tibbett <richt@opera.com>
- Date: Thu, 09 Sep 2010 11:31:39 +0200
- To: Thomas Roessler <tlr@w3.org>
- CC: Renato Iannella <renato@iannella.it>, public-device-apis@w3.org
Thomas Roessler wrote: > On 9 Sep 2010, at 09:45, Rich Tibbett wrote: > >> On top of that, the vCard standard does not provide a JSON mapping for its properties at present. It doesn't translate well to communication over the web at large. > > So, that argument says nothing about what to use as the basis for an API -- it isn't *at* *all* clear that just because there isn't a native JSON format vcard isn't suitable for "the web at large". > That's not what I was trying to say. Short of writing a JSON mapping ourselves it will be difficult to include in our WebIDL-based specs. We could write that JSON mapping ourselves...but then Portable Contacts has already done that. The current concern is that we also get OpenSocial attributes from Portable Contacts which we have not integrated in to the specification yet. To integrate these fields in to the spec perhaps an extension mechanism is the way to go...and then the spec starts to look a great deal like the vCard standard anyways... >> The DAP WG is defining WebIDL based APIs with the objective of being able to apply these definitions to REST-based API interactions in the future. >> >> Finally, we have also specified the format based on real-world implementations around this concept, most notably the Mozilla Contacts project [3]. >
Received on Thursday, 9 September 2010 09:32:27 UTC