Re: introduction to the TPE

On Apr 9, 2014, at 3:20 PM, David Wainberg wrote:

> Apologies for having to drop in the middle of this discussion today, but I was late for another meeting. As we discussed, the Introduction should be pared down to remove unneeded and inappropriate text, and to better reflect what is in the document. The last para is most all that's required. I propose the following version as the complete intro:
> 
> 1. Introduction
> This specification defines protocol elements for use within the Hypertext Transfer Protocol [HTTP] which allow a user to express a tracking preference, via the DNT request header field, and allow a server to describe their tracking behavior via a well-known tracking status resource and the Tk response header field. In addition, JavaScript APIs are defined for enabling scripts to determine DNT status and to register a user-granted exception. This specification does not stand on its own, but rather is intended to couple with a compliance specification that will define what recipients must do in response to the DNT request header field.

As an editorial matter, this suggestion is rejected since it
does not explain the motivation for the protocol and the nature
of the Web that makes such motivation apparent.  That's why we
have introductions.

I have revised the introduction to remove the one paragraph that
did express an opinion, and added a paragraph to explain that
compliance is not included in the protocol. The TPE specification
does stand on its own: the protocol is effective without any
compliance regime and has no normative dependencies on any
compliance regime.


....Roy

Received on Thursday, 10 April 2014 04:15:48 UTC