ISSUE-73: Security and Privacy Implications for PIM APIs

contacts-security

Security and Privacy Implications for PIM APIs

State:

CLOSED

Product:

APIs — General

Raised by:

Robin Berjon

Opened on:

2010-02-03

Description:

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.

Related Actions Items:

No related actions

Related emails:

1. Draft Minutes 2010-03-10 (from frederick.hirsch@nokia.com on 2010-03-10)
2. regrets (from marco.marengo@telecomitalia.it on 2010-03-09)
3. Agenda - Distributed Meeting 2010-03-10 (from frederick.hirsch@nokia.com on 2010-03-08)
4. Re: A comment on Security and Privacy Implications for Contact APIs (from noah_mendelsohn@us.ibm.com on 2010-02-03)
5. RE: ISSUE-73 (contacts-security): Security and Privacy Implications for PIM APIs [APIs - General] (from richard.tibbett@orange-ftgroup.com on 2010-02-03)
6. Re: A comment on Security and Privacy Implications for Contact APIs (from robin@berjon.com on 2010-02-03)
7. ISSUE-73 (contacts-security): Security and Privacy Implications for PIM APIs [APIs — General] (from sysbot+tracker@w3.org on 2010-02-03)

Related notes:

Display change log