Privacy/TPWG/Proposals on elements for 1and3 party use

From W3C Wiki
< Privacy‎ | TPWG
Revision as of 20:48, 22 January 2014 by Ninja (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This discussion aims at agreeing whether and if yes in what form we should retain the 1 and 3 signals in the current TPE spec. Please refer to ISSUE-241 for more information and related emails.

Elements for 1st and 3rd party in the TPE

Last Public Working Draft

5.2.3 First Party (1)
A tracking status value of 1 means that the origin server claims that the designated resource is designed for use only within a first-party context and conforms to the requirements on a first party. If the designated resource is operated by an outsourced service provider, the service provider claims that it conforms to the requirements on a third party acting as a first party.
For the site-wide tracking status and Tk header field, the tracking status values 1 and 3 indicate how the designated resource is designed to conform, not the nature of the request. Hence, if a user agent is making a request in what appears to be a third-party context and the tracking status value indicates that the designated resource is designed only for first-party conformance, then either the context has been misunderstood (both are actually the same party) or the resource has been referenced incorrectly.
For the request-specific tracking status resource, an indication of first or third party as the status value describes how the resource conformed to that specific request, and thus indicates the applicable set of requirements to which the origin server claims to conform.
5.2.4 Third Party (3)
A tracking status value of 3 means that the origin server claims that the designated resource conforms to the requirements on a third party.

Current Editors' draft

In the current Editors' draft this section does no longer exist. Compliance with a potential 1st or 3rd party rule set would be implied by additional qualifiers.

5.5.4 Qualifiers Property
An origin server may send a property named qualifiers with a string value containing a sequence of case sensitive characters corresponding to explanations or limitations on the extent of tracking. Multiple qualifiers indicate that multiple explanations or forms of tracking might apply for the designated resource. The meaning of each qualifier is presumed to be defined by one or more of the regimes listed in compliance.
qualifiers = %x22 "qualifiers" %x22
qualifiers-v = %x22 *qualifier %x22
qualifier = id-char