ISSUE-80: Instead of responding with a Link: header URI, does it make sense to use a well-known location for this policy?

Instead of responding with a Link: header URI, does it make sense to use a well-known location for this policy?

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Opened on:
2011-09-22
Description:
Related Actions Items:
No related actions
Related emails:
  1. RE: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from kevsmith@adobe.com on 2012-03-05)
  2. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from npdoty@w3.org on 2012-03-05)
  3. RE: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from kevsmith@adobe.com on 2012-03-05)
  4. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from npdoty@w3.org on 2012-03-05)
  5. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from npdoty@w3.org on 2012-03-05)
  6. Re: ACTION-115: Write up counter-proposal to header with well-known URI (from fielding@gbiv.com on 2012-02-13)
  7. diff of TPE editing since the FPWD (from fielding@gbiv.com on 2012-01-10)
  8. RE: Proposed Agenda for 2011-11-30 TPWG call (from wileys@yahoo-inc.com on 2011-11-30)
  9. RE: Proposed Agenda for 2011-11-30 TPWG call (from wileys@yahoo-inc.com on 2011-11-30)
  10. Proposed Agenda for 2011-11-30 TPWG call (from mts@zurich.ibm.com on 2011-11-30)
  11. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from karld@opera.com on 2011-10-28)
  12. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from singer@apple.com on 2011-10-28)
  13. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from ronansan@gmail.com on 2011-10-28)
  14. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from rigo@w3.org on 2011-10-28)
  15. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from ronansan@gmail.com on 2011-10-27)
  16. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from singer@apple.com on 2011-10-27)
  17. RE: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from wileys@yahoo-inc.com on 2011-10-27)
  18. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from fielding@gbiv.com on 2011-10-27)
  19. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from mts@zurich.ibm.com on 2011-10-27)
  20. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from rigo@w3.org on 2011-10-26)
  21. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from mts@zurich.ibm.com on 2011-10-26)
  22. Re: Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from karld@opera.com on 2011-10-21)
  23. Re: Agenda for 2011-10-12 DNT Workgroup Meeting (from npdoty@w3.org on 2011-10-13)
  24. Well-known URI vs response headers? [ISSUE-81, ISSUE-47, ISSUE-80] (from mts@zurich.ibm.com on 2011-10-13)
  25. Re: Agenda for 2011-10-12 DNT Workgroup Meeting (from nmarnau@datenschutzzentrum.de on 2011-10-11)
  26. Agenda for 2011-10-12 DNT Workgroup Meeting (from mts@zurich.ibm.com on 2011-10-11)
  27. Re: Agenda for 2011-10-05 TPWG call (from npdoty@w3.org on 2011-10-09)
  28. Agenda for 2011-10-04 TPWG call (from aleecia@aleecia.com on 2011-10-04)
  29. Response Headers [ISSUE-47,ISSUE-48,ISSUE-51,ISSUE-76,ISSUE-79,ISSUE-80,ISSUE-81,ISSUE-87] (from mts@zurich.ibm.com on 2011-10-04)
  30. ISSUE-80: Instead of responding with a Link: header URI, does it make sense to use a well-known location for this policy? (from sysbot+tracker@w3.org on 2011-09-22)

Related notes:

Yes: As long as we do not find use cases that mandate a response header, I'd like to default to a well-known URL to communicate the server's preference.

Matthias Schunter, 27 Oct 2011, 15:02:40

Superseded by a revision of ISSUE-47 that discusses responses that indicate a policy (either as header or well-known URI)

Matthias Schunter, 19 Jan 2012, 16:46:02

Display change log ATOM feed


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, 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: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $