- From: Suresh Chitturi <schitturi@blackberry.com>
- Date: Mon, 4 Mar 2013 20:02:36 +0000
- To: Wonsuk Lee <wonsuk11.lee@samsung.com>, 'EDUARDO FULLEA CARRERA' <efc@tid.es>, 'Wonsuk Lee' <wonsuk73@gmail.com>
- CC: 'Adam Barth' <w3c@adambarth.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>, 'Christophe Dumez - SISA' <ch.dumez@sisa.samsung.com>, "cpgs@samsung.com" <cpgs@samsung.com>
>From: Wonsuk Lee [mailto:wonsuk11.lee@samsung.com] >Hi. Eduardo and Suresh. > >> > Suresh>> Not being a member of Sys Apps group, I would let the >> > Suresh>> editors >> > comment first, but generally there is a strong interest/support on >> > the DAP side for harmonization of the contact formats and semantics. >> > The current contact format in DAP (independent of intents or >> > non-intents >> > approach) is the outcome of many prior discussions and viewed to be >> > the best way forward without creating a dependency on a specific >> > underlying formats but instead taking a "minimum subset' approach >> > that can be implemented on top of underlying implementations (of >> > course with >> an extensible mechanism). >> > Contact formats in general is a moving target and therefore basing >> > the APIs on a single format might be risky path! >> > >> >> I agree we should aim at aligning the contact's data model between DAP >> and SysApps specs. Actually the differences are not that big, so it >> should not be a problem. 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. > >I agreed with this. Based on the consensus for aligning the contact's data >model between DAP and SysApps specs, I would like to bring current proposal >to CfC in the group. Sounds good to me! Regards, Suresh --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Monday, 4 March 2013 20:03:05 UTC