Edit comment LC-2264 for Web Applications Working Group

Quick access to LC-2258 LC-2259 LC-2260 LC-2261 LC-2262 LC-2263 LC-2264

Comment LC-2264

Comment Shortname:

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

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeWidgets 1.0: Access Requests Policy /**/ <!--... W3C Working Draft 4 August 2009 Abstract Status of this Document Table of Contents 1 Introduction 1.1 Definitions access request grant access widget execution scopes deny access network resource feature-enabled API widget execution scope web execution scope 1.2 The Widget Family of Specifications Widgets 1.0 family of specifications 1.3 Design Goals and Requirements Security model Restricted access to remote web resources Security Current development practice or industry best- practice Interoperability 2 Policy 3 The access Element Attributes uri URI attribute special value supported subdomains boolean attribute Usage example 4 Processing model access-request list ifragment ipath iuser info iquery in error ignore rule for getting a single attribute value valid URI iuser info in error ignore rule for getting a single attribute value valid boolean value in error ignore ifragment ipath iquery unsupported in error ignore ToASCII Rule for Granting Access to a URI identifiable Resources Acknowledgements Normative References [RFC3987] [URI] [RFC3490] [Widgets-PC] Informative References [Widgets-Reqs] [Widgets-DigSig] [Widgets-Updates] [Widgets-APIs] [HTML5] [HTTP] [HTTPS]
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

Comment:

Hi,

The attribute "uri" on the <access> element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
suggest renaming it in "urlpattern" or just "pattern" (unless there are
already many implementations that rely on that attribute name).

There may be lessons to be taken in designing these patterns from POWDER
http://www.w3.org/TR/2009/REC-powder-dr-20090901/ - although I suspect
the POWDER expressivity needs are much greater than what is needed here.

Dom

Related issues: (space separated ids)

WG Notes:

Resolution:

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