W3C home > Mailing lists > Public > public-device-apis@w3.org > February 2013

RE: [admin] Relationship of DAP and SysApps deliverables

From: Suresh Chitturi <schitturi@rim.com>
Date: Thu, 7 Feb 2013 16:00:40 +0000
To: "SULLIVAN, BRYAN L" <bs3131@att.com>, "Frederick.Hirsch@nokia.com" <Frederick.Hirsch@nokia.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
CC: "wonsuk11.lee@samsung.com" <wonsuk11.lee@samsung.com>, "w3c@adambarth.com" <w3c@adambarth.com>, "dsr@w3.org" <dsr@w3.org>, "dom@w3.org" <dom@w3.org>
Message-ID: <8B118C943801754098C9B36B567EABA3B02B5A@XMB103ADS.rim.net>
We support this position very much as well.
It doesn't make much sense to create deviating core specs unless a there is a strong reason. It sends a very wrong message to the web community!

More specifically, in the case of contacts, the work from DAP related to Contact object/properties [1] should be re- used in SysApps.
The definition consists of a common set of properties across multiple standards (e.g. vCard, CAB, PoCo) and extensible mechanism for vendor specific extensions. 

[1] http://www.w3.org/TR/2011/WD-contacts-api-20110616/#contact-interface


Regards,
Suresh


>-----Original Message-----
>From: SULLIVAN, BRYAN L [mailto:bs3131@att.com]
>Sent: Thursday, February 07, 2013 9:50 AM
>To: Frederick.Hirsch@nokia.com; public-device-apis@w3.org
>Cc: wonsuk11.lee@samsung.com; w3c@adambarth.com; dsr@w3.org;
>dom@w3.org
>Subject: RE: [admin] Relationship of DAP and SysApps deliverables
>
>Very useful overview, Frederick.
>
>+1 to the goal of alignment and reuse of common API design elements. I have
>mentioned this as a goal several times.
>
>Thanks,
>Bryan Sullivan
>
>-----Original Message-----
>From: Frederick.Hirsch@nokia.com [mailto:Frederick.Hirsch@nokia.com]
>Sent: Thursday, February 07, 2013 6:58 AM
>
>[snip]
>
>-----
>Conclusion
>
>I think it would be helpful to share use cases and requirements and also
>consider the implications of overlap work items.
>
>In particular, regarding Contacts, we may want to
>
>(a) make sure that the data formats and meaning are consistent (for
>interoperability)
>
>(b)  ask whether similar APIs across two groups should share a common API
>style  and practices [5] and maybe even details apart from optional
>parameters or intentionally be different (whether it is better to enable
>commonality or make clear distinctions)
>
>Thoughts? I hope this is helpful.
>
>regards, Frederick
>
>Frederick Hirsch, Nokia
>Chair, W3C DAP Working Group
>
>[1] http://www.w3.org/2009/dap/
>
>[2] http://www.w3.org/2012/sysapps/
>
>[3] http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0026.html
>
>[4] http://www.w3.org/2012/webcrypto/
>
>[5] API checklist,  http://www.w3.org/2009/dap/wiki/ApiCheckList
>
>Web API Design Cookbook, http://darobin.github.com/api-design-cookbook/
>
>For tracker, complete ACTION-612
>
>
>


---------------------------------------------------------------------
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 Thursday, 7 February 2013 16:01:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 February 2013 16:01:10 GMT