'Scope' change proposal

• From: David Singer <singer@apple.com>
• Date: Tue, 02 Jul 2013 17:13:49 -0700
• To: "public-tracking@w3.org List" <public-tracking@w3.org>
• Message-id: <5743E796-2866-4A39-82DA-CDA4EDABCF1F@apple.com>

http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Scope

Problem:

The scope sentence sets the general scope of the specification, and the proposed alternatives imply no rules for anything other than 3rd parties, which is misleading.

Solution:

no change.  we think the current sentence sets the general scope well.


Question:

do we need formal 'no change' proposals for everything, or (if we fail to agree on a proposal) is that always implicitly there?


David Singer
Multimedia and Software Standards, Apple Inc.

Received on Wednesday, 3 July 2013 00:14:18 UTC