Edit comment LC-2374 for Web Applications Working Group

Quick access to LC-2374 LC-2375

Comment LC-2374

Comment Shortname:

Commenter: Dominique Hazael-Massieux <dom@w3.org>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeWidget Access Request Policy /**/ /*********************... Abstract This specification defines the security model cont... Status of This Document This section describes the status o... Table of Contents 1. Introduction 2. Definitions 3. Confor... 1. Introduction This section is non-normative. User agents... 2. Definitions An access request is a request made by an au... access request grant access deny access access request policy policy network resource feature-enabled API widget execution scope external execution scope 3. Conformance As well as sections marked as non-normative,... user agents 4. Policy A user agent enforces an access request policy. I... 5. The access Element The access element allows authors to... access 5.1 Attributes origin An IRI attribute that defines the sp... origin special value subdomains 5.2 Usage example This example contains multiple uses of th... 6. Processing access elements in the Configuration Document... access-request list access-request list 7. Rules for Granting Access to a Network Resources When mu... A. Design Goals and Requirements The design goals and requi... B. Acknowledgements The editor would like to thank (in no p... C. References C.1 Normative references [RFC2119] S. Bradn... C.1 Normative references [RFC2119] S. Bradner. Key words f... [RFC2119] [RFC3490] [RFC3987] [URI] [WIDGETS] C.2 Informative references [HTML5] Ian Hickson; David Hyat... [HTML5] [WIDGETS-APIS] [WIDGETS-REQS]
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

A quick comment after re-reading WARP at the invitation of Robin to DAP
[1]: I don’t think the notion of subdomain is well-defined; is w3.org a
subdomain of .org? is co a subdomain of co.uk? I assume they are in the
sense of the spec, but if that’s so, it doesn’t match the “street”
meaning of the word “subdomain”; this matters in particular in section 7
(rules for granting access), since this has an impact on how a user
agent decides to grant access to a network resource. Given that IP
addresses are allowed, the algorithm to determine if something is a
subdomain of another domain is as simple as looking to the last dot in
the authority component.

(kudos on the spec otherwise; I find it to be very crisp)

Dom

1.
http://www.w3.org/mid/4AEBCB34-9BF1-4C14-8E54-40E1EEE59F0B@robineko.com

Related issues: (space separated ids)

WG Notes: Response at: http://www.w3.org/mid/C202B2E7-CC40-4781-A2A2-982C067389B6@berjon.com

Resolution:

(Please make sure the resolution is adapted for public consumption)