W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2012

RE: ISSUE-126: Should DAP review and take advantage of SysApps security models

From: Suresh Chitturi <schitturi@rim.com>
Date: Fri, 30 Nov 2012 17:36:31 +0000
To: "SULLIVAN, BRYAN L" <bs3131@att.com>, Arthur Barstow <art.barstow@nokia.com>, Device APIs Working Group <public-device-apis@w3.org>
Message-ID: <8B118C943801754098C9B36B567EABA3AE9A29@XMB103ADS.rim.net>
>DAP and SysApps APIs are likely to take different approaches to similar needs,
>but we should promote synergy where possible. For example in the object
>model for data related to APIs, where possible (e.g. a contact object), we
>should work toward common interface definitions. The way in which the APIs
>are invoked, and the related security/privacy approaches may end up being
>very different, but at least the actual data definition itself should be reusable?

+1 to having coming object model definitions between DAP and SysApps where possible. Contacts is a very good example for this!
DAP has spent significant time on some of these aspects and rehashing them again in SysApps makes little or no sense.


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 Friday, 30 November 2012 17:40:08 UTC

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