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

RE: [admin] Relationship of DAP and SysApps deliverables

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Thu, 7 Feb 2013 15:50:01 +0000
To: "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: <59A39E87EA9F964A836299497B686C351096DF49@WABOTH9MSGUSR8D.ITServices.sbc.com>
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
Received on Thursday, 7 February 2013 15:51:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:58 UTC