ACTION-258: Propose 'should' for same-party and why

Propose 'should' for same-party and why

State:
closed
Person:
Rigo Wenning
Due on:
December 12, 2012
Created on:
September 19, 2012
Associated Issue:
ISSUE-164
Related emails:
  1. Re: ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-04-26)
  2. Re: ACTION-258: Propose 'should' for same-party and why (from derhoermi@gmx.net on 2013-04-26)
  3. Re: ACTION-258: Propose 'should' for same-party and why (from fielding@gbiv.com on 2013-04-25)
  4. Re: ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-04-25)
  5. Re: ACTION-258: Propose 'should' for same-party and why (from fielding@gbiv.com on 2013-04-23)
  6. RE: ACTION-258: Propose 'should' for same-party and why (from michael.oneill@baycloud.com on 2013-04-23)
  7. Re: ACTION-258: Propose 'should' for same-party and why (from ronansan@gmail.com on 2013-04-23)
  8. Re: ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-04-23)
  9. RE: ACTION-258: Propose 'should' for same-party and why (from adrianba@microsoft.com on 2013-04-23)
  10. Re: ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-04-23)
  11. Re: ACTION-258: Propose 'should' for same-party and why (from fielding@gbiv.com on 2013-04-23)
  12. Re: RE: Approach to ISSUE-167: Multiple site exception (from rigo@w3.org on 2013-03-22)
  13. Re: ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-03-21)
  14. Re: ACTION-258: Propose 'should' for same-party and why (from fielding@gbiv.com on 2013-03-21)
  15. Re: RE: RE: ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-03-20)
  16. Re: RE: ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-03-20)
  17. RE: ACTION-258: Propose 'should' for same-party and why (from adrianba@microsoft.com on 2013-03-20)
  18. Re: DNT: Agenda for March 20 call (revised) (from peter@peterswire.net on 2013-03-19)
  19. Re: DNT: Agenda for March 20 call (from jmayer@stanford.edu on 2013-03-19)
  20. DNT: Agenda for March 20 call (from peter@peterswire.net on 2013-03-19)
  21. ACTION-258: Propose 'should' for same-party and why (from rigo@w3.org on 2013-01-22)
  22. Re: today's (24 October 2012) call: canceled (from ifette@google.com on 2012-10-24)
  23. Re: today's (24 October 2012) call: canceled (from david@networkadvertising.org on 2012-10-24)
  24. today's (24 October 2012) call: canceled (from aleecia@aleecia.com on 2012-10-24)
  25. Re: Agenda for 16 October 2012 call (from tlr@w3.org on 2012-10-17)
  26. Re: Agenda for 16 October 2012 call (from bszoka@techfreedom.org on 2012-10-17)
  27. Re: Agenda for 16 October 2012 call (from jmayer@stanford.edu on 2012-10-16)
  28. Agenda for 16 October 2012 call (from aleecia@aleecia.com on 2012-10-16)
  29. Agenda for 16 October 2012 call (from aleecia@aleecia.com on 2012-10-16)

Related notes:

Rigo: If two domains on a site want 1st party privileges (intended for 1st party use), both should be declared in the same party attribute.

Matthias Schunter, 5 Dec 2012, 17:12:22

Roy Fielding as best explained this issue in
http://lists.w3.org/Archives/Public/public-tracking/2013Jan/0083.html

At the end, in possibilities (y) and (z), Roy's email perfectly describes the issue and the benefit of having a first origin describing other first parties or service providers in the Tracking Status Report as "same party".
It is therefore suggested to use the following wording:
Old wording:
An optional member named same-party may be provided with an array value containing a list of domain names that the origin server claims are the same party, to the extent they are referenced by the designated resource, since all data collected via those references share the same data controller as the designated resource.

New wording:
An optional member named same-party SHOULD be provided with an array value containing a list of domain names that the origin server claims are the same party, to the extent they are referenced by the designated resource, since all data collected via those references share the same data controller as the designated resource.

Rigo Wenning, 22 Jan 2013, 20:27:45

Display change log.

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 258.html,v 1.1 2019/02/01 09:32:01 vivien Exp $