W3C home > Mailing lists > Public > public-privacy@w3.org > January to March 2012

Re: Privacy by Design in APIs

From: Hannes Tschofenig <hannes.tschofenig@nsn.com>
Date: Thu, 29 Mar 2012 17:35:34 +0200
To: Robin Berjon <robin@berjon.com>, "public-privacy (W3C mailing list)" <public-privacy@w3.org>
Message-ID: <CB9A4DE6.A478%hannes.tschofenig@nsn.com>
Hey Robin, 

Have you had a chance to look at this privacy consideration document:

You may find some of the content relevant.

There are really basic things you need to think about first. For example,
think about the scope of your document. Who is the target audience? A
resulting document will look very different if you are addressing the
protocol developers in the W3C (as compared to someone who deploys a
complete solution).

You also do not reference any terminology, which leads to endless confusion.
For this purpose you may want to look at this document:

I have plenty of additional comments but I want to get these high-level
things discussed first.


On 3/29/12 4:21 PM, "Robin Berjon" <robin@berjon.com> wrote:

> Hi all,
> this is a heads up that I've started work on a TAG draft finding for "Privacy
> by Design in APIs". It is intended to provide some strategies for API
> designers to be as privacy-friendly as possible.
> You can find my draft at:
>    http://darobin.github.com/api-design-privacy/api-design-privacy.html
> And can fork and make pull requests at (note that it's in the gh-pages
> branch):
>    https://github.com/darobin/api-design-privacy/tree/gh-pages
> It's a first draft and still has a number of rough edges. Feedback is very
> welcome on pretty much any aspect ‹ share and enjoy!
Received on Thursday, 29 March 2012 14:36:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:23:53 UTC