Re: Selecting a subset of texts for preparing ISSUE-5 for a call for objection

On Oct 25, 2013, at 9:46 AM, Matthias Schunter (Intel Corporation) wrote:

> Hi Team,
> for preparation of next week's call, I would like to assemble a shortlist of
> proposals that we use for the call for objections:
> I took the liberty and added the text discussed in last week's telco (revised Proposal 1) as a first initial candidate since I perceived support from several members of the group.
> If you cannot live with any of the proposals currently shortlisted,
> please nominate an extra one to shortlist while explaining
>    - What is the shortcoming of the currently shortlisted proposals
>    - How does the newly added proposal mitigate this shortcoming
> This will enable me to compile a list of (hopefully) less than 7 alternatives
> to then use as the set of alternatives on our call for objection.

I have renamed the shortlisted proposals to "candidates" and modified
my proposal to reflect the comments received, as follows:

Candidate (A): Tracking across multiple distinct contexts

email October 16; discussed on 2013-10-23 teleconference. Amended by Roy in response to comments received.


Tracking is the collection of data regarding a particular user's activity across multiple distinct contexts and the retention, use, or sharing of data derived from that activity outside the context in which it occurred.


The above definition depends on collection, retention, use, and sharing being defined along the lines of the editors' draft or as clarified by Vinay's proposals.

The above definition also depends on there being a definition of context that bounds a scope of user activity, though it is not dependent on any particular definition of that term. For example, something along the lines of: For the purpose of this definition, a context is a set of resources that share the same data controller, same privacy policy, and a common branding, such that a user would expect that data collected by one of those resources is available to all other resources within the same context.

The above definition also assumes that an explanation of permitted tracking will occur as well, presumably in the introduction along with the definition of tracking, so that a reader won't be misled about the user's expressed preference being the same as compliance. For example, something along the lines of: Some servers might perform tracking regardless of the user's expressed preference; for example, a service might have obtained prior consent that allows them to track the user, or a service might limit its tracking to specific purposes that are allowed under a given compliance regime (see Section XX).




Received on Friday, 25 October 2013 22:32:57 UTC