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

RE: ISSUE-73 (contacts-security): Security and Privacy Implications for PIM APIs [APIs - General]

From: <richard.tibbett@orange-ftgroup.com>
Date: Wed, 3 Feb 2010 12:52:46 +0100
Message-ID: <6039_1265197964_4B69638C_6039_5857_1_355A518BC0575547B2A3D6773AAF8EEF8A3532@ftrdmel1>
To: <public-device-apis@w3.org>
Cc: <noah_mendelsohn@us.ibm.com>
Hi Robin,

Thanks for raising this issue. I was having account issues with raising
this on the tracker.

Here is the original request to create this issue:
http://lists.w3.org/Archives/Public/public-device-apis/2010Jan/0221.html

- Richard

> -----Original Message-----
> From: public-device-apis-request@w3.org 
> [mailto:public-device-apis-request@w3.org] On Behalf Of 
> Device APIs and Policy Working Group Issue Tracker
> Sent: 03 February 2010 11:48
> To: public-device-apis@w3.org
> Subject: ISSUE-73 (contacts-security): Security and Privacy 
> Implications for PIM APIs [APIs - General]
> 
> 
> ISSUE-73 (contacts-security): Security and Privacy 
> Implications for PIM APIs [APIs - General]
> 
> http://www.w3.org/2009/dap/track/issues/73
> 
> Raised by: Robin Berjon
> On product: APIs - General
> 
> This issue is raised to track the outcome from this thread:
> 
>   
> http://www.w3.org/mid/OFE390B98E.2E6FBE81-ON852576AB.00776921-
> 852576B8.0053B66F@lotus.com
> 
> PIM APIs are grouped together because they are likely to have 
> similar requirements; and because they are probably different 
> from for instance Geolocation.
> 
> Interesting point at 
> http://www.w3.org/mid/AEF2CA6D-D088-45BB-9654-BD383E3C521B@w3.
> org about how PIM APIs are similar in their security 
> requirements to FS APIs.
> 
> 
> 
> 

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************
Received on Wednesday, 3 February 2010 11:53:21 UTC

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