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

RE: Minor fix to DAP homepage

From: David Rogers <david.rogers@omtp.org>
Date: Thu, 29 Oct 2009 14:13:34 -0000
Message-ID: <4C83800CE03F754ABA6BA928A6D94A0601E5F19E@exch-be14.exchange.local>
To: "Frederick Hirsch" <Frederick.Hirsch@nokia.com>
Cc: "Robin Berjon" <robin@robineko.com>, "W3C Device APIs and Policy WG" <public-device-apis@w3.org>
Hi,

Whatever is necessary to avoid people reading that document in isolation
for A&S I think.

Thanks!


David.

-----Original Message-----
From: Frederick Hirsch [mailto:Frederick.Hirsch@nokia.com] 
Sent: 29 October 2009 14:08
To: David Rogers
Cc: Frederick Hirsch; Robin Berjon; W3C Device APIs and Policy WG
Subject: Re: Minor fix to DAP homepage

David

The home page already has a link to the BONDI1.01 page on the INPUTS  
section, thus linking to the complete document set:

"(and also BONDI 1.0 specifications and 1.01 specifications)"

I called out that one document but could move it to the Recommended  
reading page below. Would that take care of it?

regards, Frederick

Frederick Hirsch
Nokia



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 Thursday, 29 October 2009 14:14:15 UTC

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