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

Re: Minor fix to DAP homepage

From: Frederick Hirsch <Frederick.Hirsch@nokia.com>
Date: Tue, 3 Nov 2009 17:52:32 -0500
Cc: Frederick Hirsch <Frederick.Hirsch@nokia.com>, Robin Berjon <robin@robineko.com>, W3C Device APIs and Policy WG <public-device-apis@w3.org>
Message-Id: <82FDF005-990C-417E-88C0-8C1E26612E75@nokia.com>
To: ext David Rogers <david.rogers@omtp.org>

I've updated the DAP home page [1] to address this concern, listing  
BONDI 1.01 as contribution and moving the reference to the security  
specification to the recommended reading page [2].

Does this address the concern?

regards, Frederick

Frederick Hirsch

[1] http://www.w3.org/2009/dap/

[2] http://www.w3.org/2009/dap/rec-reading.html

On Oct 29, 2009, at 6:43 AM, ext David Rogers wrote:

> Hi there,
> I just looked at the DAP homepage and noticed an issue. The link to  
> the A&S specs from BONDI only refer to one pdf:http://bondi.omtp.org/1.01/security/BONDI_Architecture_and_Security_v1_01.pdf 
>  (for example). Please could you refer to the complete document set  
> as that was the intent of our submission?
> From http://bondi.omtp.org/1.01/ :
> Architecture and Security
> The Architecture and Security work stream defines the architectural  
> components to deliver API extensibility and the security framework  
> required to protect an end user from the risks associated with the  
> opening up of sensitive APIs. It includes the precise definition of  
> a flexible security mechanism. The exposure of these interfaces is  
> essential to enable great services. However, a security framework is  
> essential to protect the user from the abuse of these interfaces by  
> malicious web applications or widgets.
> Document
> Description
> Architecture and Security
> UPDATED - Primary specification document for the architecture and  
> security workstream
> Architecture and Security Appendices
> UPDATED - Appendices to complement the above document
> Application Lifecycle and Events
> Defines requirements of application lifecycle
> XML definition of Security Policy (RelaxNG)
> The precise syntactic definition of the XML security policy
> XML definition of Digital Signatures (RelaxNG)
> File on which the security policy definition is dependent
> Thanks,
> David.
> David Rogers
> OMTP Director of External Relations
Received on Tuesday, 3 November 2009 22:53:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:13 UTC