W3C home > Mailing lists > Public > public-appformats@w3.org > January 2008

ISSUE-22 (ac4csr-webarch): The AC4CSR spec and "webarch" [Access Control]

From: Web Application Formats Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 28 Jan 2008 02:05:32 +0000 (GMT)
To: public-appformats@w3.org
Message-Id: <20080128020532.57D3DBEEC@nelson.w3.org>

ISSUE-22 (ac4csr-webarch): The AC4CSR spec and "webarch" [Access Control]

http://www.w3.org/2005/06/tracker/waf/issues/

Raised by: Arthur Barstow
On product: Access Control

Tyler Close asserts the AC4CSR spec is "counter to what webarch tries to encourage" regarding:
[[
 Good practice: Identify with URIs
 <http://www.w3.org/TR/webarch/#pr-use-uris>
]]

Tyler raised this issue via:
[1] <http://www.w3.org/mid/C7B67062D31B9E459128006BAAD0DC3D074F480422@G6W0269.americas.hpqcorp.net>
[2] <http://www.w3.org/mid/C7B67062D31B9E459128006BAAD0DC3D074F4F6D7B@G6W0269.americas.hpqcorp.net>

[1] was in response to Mark Nottinham's email that "per-resource OPTIONS requests are too chatty":
 <http://www.w3.org/mid/8A6373E7-7211-4606-ABF5-F028416CACEE@yahoo-inc.com>
[2] was in response to Ian Hickson's e-mail:
 <http://www.w3.org/mid/Pine.LNX.4.62.0801252158560.20219@hixie.dreamhostps.com>

One additional factor to consider when discussing this issue is that the webarch/AWWW document is purely non-Normative:

 <http://www.w3.org/TR/webarch/>
Received on Monday, 28 January 2008 02:05:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:56:21 UTC