- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Wed, 23 Jul 2014 17:45:26 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv27036/drafts
Modified Files:
tracking-compliance.html tracking-dnt.html
Log Message:
tracking-ISSUE-247: update HTTP references to newly published RFCs; update other RFC references for consistency
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/07/23 02:54:16 1.120
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/07/23 17:45:26 1.121
@@ -89,7 +89,7 @@
The term <dfn>user agent</dfn> refers to any of the
various client programs capable of initiating HTTP requests,
including but not limited to browsers, spiders (web-based robots),
- command-line tools, native applications, and mobile apps [[!HTTP11]].
+ command-line tools, native applications, and mobile apps [[!RFC7230]].
</p>
<p class="issue" data-number="227" title="User Agent requirements in UA Compliance vs. Scope section">
There is a proposal to move a sentence about user agents from the Introduction/Scope section to this section. We might also include a reference here to the conformance requirements on user agents in the companion TPE recommendation.
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/04/15 00:36:38 1.270
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/07/23 17:45:26 1.271
@@ -8,9 +8,9 @@
var respecConfig = {
specStatus: "ED",
shortName: "tracking-dnt",
- // publishDate: "2014-03-13",
- previousPublishDate: "2014-01-28",
- previousMaturity: "WD",
+ // publishDate: "2014-07-23",
+ previousPublishDate: "2014-04-24",
+ previousMaturity: "LCWD",
edDraftURI: "http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html",
editors: [
{ name: "Roy T. Fielding", url: "http://roy.gbiv.com/",
@@ -31,40 +31,8 @@
"status" : "ED",
"href" : "http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html",
"title" : "Tracking Compliance and Scope",
- "date" : "08 April 2014",
+ "date" : "08 May 2014",
"publisher" : "W3C"
- },
- "HTTP" : {
- "title" : "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing",
- "authors": ["Roy T. Fielding", "Julian Reschke"],
- "status" : "Internet-Draft",
- "date" : "6 February 2014",
- "publisher" : "IETF",
- "href" : "http://datatracker.ietf.org/doc/draft-ietf-httpbis-p1-messaging/"
- },
- "HTTP-semantics" : {
- "title" : "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content",
- "authors": ["Roy T. Fielding", "Julian Reschke"],
- "status" : "Internet-Draft",
- "date" : "6 February 2014",
- "publisher" : "IETF",
- "href" : "http://datatracker.ietf.org/doc/draft-ietf-httpbis-p2-semantics/"
- },
- "HTTP-cache" : {
- "title" : "Hypertext Transfer Protocol (HTTP/1.1): Caching",
- "authors": ["Roy T. Fielding", "Mark Nottingham", "Julian Reschke"],
- "status" : "Internet-Draft",
- "date" : "6 February 2014",
- "publisher" : "IETF",
- "href" : "http://datatracker.ietf.org/doc/draft-ietf-httpbis-p6-cache/"
- },
- "RFC7159" : {
- "title" : "The JavaScript Object Notation (JSON) Data Interchange Format",
- "authors": ["Tim Bray, Ed."],
- "status" : "Internet RFC 7159",
- "date" : "March 2014",
- "publisher" : "IETF",
- "href" : "http://www.rfc-editor.org/rfc/rfc7159.txt"
}
},
noIDLSectionTitle: true
@@ -157,9 +125,9 @@
informed choice.
</p>
<p>
- This specification defines Hypertext Transfer Protocol [[!HTTP]]
- elements for communicating the user's tracking preference (if any)
- and communicating the server's tracking behavior (if any).
+ This specification extends Hypertext Transfer Protocol (HTTP)
+ semantics [[!RFC7231]] to communicate a user's tracking preference,
+ if any, and an origin server's tracking behavior.
The <a>DNT</a> request header field is defined for communicating the
user's tracking preference for the request target. A well-known URI
for a <a href="#status-resource">tracking status resource</a> and the
@@ -196,9 +164,9 @@
</p>
<p>
A <dfn>user agent</dfn> is any of the various client programs
- capable of initiating HTTP requests [[!HTTP]], including (but not
+ capable of initiating HTTP requests, including (but not
limited to) browsers, spiders (web-based robots), command-line
- tools, custom applications, and mobile apps.
+ tools, custom applications, and mobile apps [[!RFC7230]].
</p>
<p>
A <dfn>network interaction</dfn> is a single HTTP request and its
@@ -283,9 +251,11 @@
<section id='notation'>
<h3>Formal Syntax</h3>
<p>
- This specification uses Augmented Backus-Naur Form [[!ABNF]]
- to define network protocol syntax and WebIDL [[!WEBIDL]] for
- defining scripting APIs.
+ This specification uses the Augmented Backus-Naur Form (ABNF)
+ notation of [[!RFC5234]] to define network protocol syntax and
+ WebIDL [[!WEBIDL]] to define scripting APIs.
+ Conformance criteria and considerations regarding error handling are
+ defined in Section 2.5 of [RFC7230].
</p>
</section>
</section>
@@ -453,7 +423,7 @@
<p>
The <dfn>DNT</dfn> header field is a mechanism for expressing the
- user's tracking preference in an HTTP request [[!HTTP]].
+ user's tracking preference in an HTTP request ([[!RFC7230]]).
</p>
<pre class="abnf">
<dfn>DNT-field-name</dfn> = "DNT"
@@ -519,7 +489,7 @@
JSON string without further encoding
(<a href="#status-representation" class="sectionRef"></a>).
At most one DNT header field can be present in a valid
- request [[!HTTP]].
+ request [[!RFC7230]].
</p>
</section>
@@ -904,7 +874,7 @@
</p>
<p>
A <dfn>tracking status resource space</dfn> is defined by the
- following URI Template [[URI-TEMPLATE]]:
+ following URI Template [[RFC6570]]:
</p>
<pre>/.well-known/dnt/{+status-id}</pre>
<p>
@@ -928,7 +898,7 @@
<h4>Status Checks are Not Tracked</h4>
<p>
When sending a request for the tracking status, a user agent
- SHOULD include any cookie data [[COOKIES]] (set prior to the
+ SHOULD include any cookie data [[RFC6265]] (set prior to the
request) that would be sent in a normal request to that origin
server, since that data might be needed by the server to determine
the current tracking status. For example, the cookie data might
@@ -957,7 +927,7 @@
If the tracking status is applicable to all users, regardless of
the received <a>DNT-field-value</a> or other data received via the
request, then the origin server SHOULD mark the response as
- cacheable [[!HTTP-cache]] and assign a time-to-live (expiration or
+ cacheable [[!RFC7234]] and assign a time-to-live (expiration or
max-use) that is sufficient to enable shared caching but not
greater than the earliest point at which the service's tracking
behavior might increase.
@@ -1307,7 +1277,7 @@
then the origin server SHOULD send a 409 (Conflict) response with a
message payload that describes why the request has been refused and
how one might supply the required consent or exception to avoid this
- conflict [[!HTTP-semantics]].
+ conflict [[!RFC7231]].
</p>
<p>
The 409 response ought to include a user authentication mechanism in
@@ -1703,7 +1673,7 @@
</p>
<p>If the document-origin would not be able to set a cookie on the
- <code>domain</code> following the cookie domain rules [[!COOKIES]]
+ <code>domain</code> following the cookie domain rules [[!RFC6265]]
(e.g. <code>domain</code> is not a right-hand match or is a TLD)
then the duplet MUST NOT be entered into the database and
a SYNTAX_ERR exception SHOULD be thrown.
Received on Wednesday, 23 July 2014 17:45:28 UTC