- From: Mounir Lamouri <mounir@lamouri.fr>
- Date: Mon, 04 Mar 2013 01:05:16 +0100
- To: Suresh Chitturi <schitturi@blackberry.com>
- CC: EDUARDO FULLEA CARRERA <efc@tid.es>, Wonsuk Lee <wonsuk73@gmail.com>, "wonsuk11.lee@samsung.com" <wonsuk11.lee@samsung.com>, Adam Barth <w3c@adambarth.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>, "Christophe Dumez - SISA (ch.dumez@sisa.samsung.com)" <ch.dumez@sisa.samsung.com>
On 01/03/13 22:05, Suresh Chitturi wrote: > On March 01, 2013 3:50 AM, EDUARDO FULLEA CARRERA wrote: >> I propose the editors collaborate to reach this alignment. In any case >> the changes are mainly about naming or grouping of attributes, so IMO >> nothing so meaningful that should prevent the SysApps Contacts API draft to >> go to FPWD. >> > > Our main concern is that FPWD is an important milestone so getting the alignment done prior would signal a good message to the community that we are indeed aligning between the two groups. And maybe even calling this out in the draft on the approach and alignment would help. I am not sure that there is a pressing need in synchronising between DAP and SysApps on that matter and making sure that this happen before FPWD doesn't seem that important given that the Contacts API will very unlikely get frozen after FPWD. As I see it, "Pick Contacts Intent" should have an API surface that looks like Contacts API to keep a certain level of consistency within the Web Platform. Actually, the dependency of "Pick Contacts Intent" on "Contacts API" is so strong that the ideal solution would be to merge "Pick Contacts Intent" inside "Contacts API". However, given the current status of Web Intent, it is probably better to keep this as a separate work for the moment. -- Mounir
Received on Monday, 4 March 2013 00:05:55 UTC