ISSUE-68: The AC4CSR spec and "webarch"
ac4csr-webarch
The AC4CSR spec and "webarch"
- State:
- CLOSED
- Product:
- HISTORICAL: CORS [this spec uses Bugzilla for Bug/Issue tracking http://tinyurl.com/Bugz-CORS]
- Raised by:
- Arthur Barstow
- Opened on:
- 2008-01-28
- Description:
- 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/> - Related Actions Items:
- No related actions
- Related emails:
- No related emails
Related notes:
(sent on Feb 6th)
Tyler,
I'm pleased to inform you that the WAF working group believes it has resolved an issue you raised. You raised an issue in [1] that we identified as issue #22 [2]. Subsequently, a proposal was put forward to the Working Group and incorporated into the latest editors draft [3]. In a sentence, it adds the ability for a server to grant access to paths in addition to the existing protocols, names, ports and http method specification capabilities. We hope this satisfies your request, and please let us know if it does not.
Cheers,
Dave Orchard, on behalf of the Web Application Format WG
[1] http://lists.w3.org/Archives/Public/public-appformats/2008Jan/0298.html
[2] http://www.w3.org/2005/06/tracker/waf/issues/22
[3] http://dev.w3.org/2006/waf/access-control/
Display change log
