W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2009

ISSUE-32 (paddy): Features, Device Capabilities, their identification, and their role in policy. [Security Policy Framework — General]

From: Device APIs and Policy Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 14 Oct 2009 10:32:23 +0000 (GMT)
To: public-device-apis@w3.org
Message-Id: <20091014103223.3E6CCBFC6@nelson.w3.org>

ISSUE-32 (paddy): Features, Device Capabilities, their identification, and their role in policy. [Security Policy Framework — General]

http://www.w3.org/2009/dap/track/issues/32

Raised by: Paddy Byers
On product: Security Policy Framework — General

This issue concerns how a security policy refers to resources under its control.

Specifically, there needs to be a definition of what those resources are, or what device functionality they represent, and how they are identified.

Various of the input documents have definitions and naming schemes for these as part of their policy framework and for DAP it is necessary to arrive at a common set of concepts and definitions.
Received on Wednesday, 14 October 2009 10:32:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:01 GMT