W3C home > Mailing lists > Public > www-tag@w3.org > November 2011

Re: Identifying Application State

From: ashok malhotra <ashok.malhotra@oracle.com>
Date: Wed, 23 Nov 2011 09:55:18 -0800
Message-ID: <4ECD3386.6070400@oracle.com>
To: Jonathan Rees <jar@creativecommons.org>
CC: "www-tag@w3.org" <www-tag@w3.org>
A new version of Identifying Application State is available at:
This contains changes in response to your comments in:

Here is how your comments have been addressed:

Need explanations or references [] for abbreviations used to improve
the reach and durability of the document:
[AM] Added reference to RFC 3987 and 3987bis
[AM] Added reference to XML Schema where this is defined
[AM] Replaced the abbreviation by Content Deleviry Networks
[AM] Added reference to XMLHttpRequest2

Re "not defined by the HTML specification"  -- architecturally the #
practice would have to derive from the media type registration, not
the HTML spec. The distinction would be academic if the registration
defined fragid semantics by reference to the spec, or if the spec
*was* the registration, but from a FYN perspective it's the
registration that has responsibility. You could just change
"specification" to "media type registration".
[AM] Done

Editorial nit, there should be no hyphen in "information on the
client-side" (non-adjectival compound).  All the other "client-side"s
are adjectival and therefore correct, so don't change those.
[AM] Done

Please let us know if this is satisfactory.


All the best, Ashok
Received on Wednesday, 23 November 2011 17:55:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:41 UTC