Device APIs Working Group
Issue Tracking
Summary
Issues:
Raised
Open
Pending Review
Closed
Postponed
All
Create
Actions:
Open
Overdue
Closed
Pending Review
Raise
Users
My
Tracker
Products
Agenda planning
Recent activity
Raised Issues
Apply the following changes to selected issues:
Mark as
No status change
Closed
Open
Raised
Pending Review
Postponed
Associate to product:
No change
APIs — General
Application Configuration API
Application Launcher API
Battery Status API
Calendar API
Capture API
Communication Log API
Contacts API
Device APIs Permissions
FileSystem API
Gallery API
HTML Media Capture
Local Media Capture API (getUserMe…
Messaging API
Network Information API
Organizational matters
Policy Framework
Policy Framework Requirements
Privacy
ReSpec
Security Policy Framework — Gene…
Sensor API
System Information and Events API
Tasks API
Testing
User Interaction API
Vibration API
There are 4 raised issues listed in the system.
↓
ID
↓
State
Title
Raised on
↓
Product
Open Actions
ISSUE-119
customErrorObjects
RAISED
Should we have different Error objects for each spec, or should we go the way that Exceptions are going and only have one object
2011-08-31
Contacts API
0
ISSUE-120
multipleSensors
RAISED
How to handle exposing single vs multiple sensors of the same type
2011-10-05
Sensor API
0
ISSUE-122
RAISED
Is low level data necessary for all sensor APIs, which ones have use cases and which not
2011-11-03
0
ISSUE-123
RAISED
Low level discovery API security and privacy issues
2011-11-04
0
Raise an issue
.
Frederick Hirsch <
frederick.hirsch@nokia.com
>, Robin Berjon <
robin@berjon.com
>, Chairs, Dominique Hazaël-Massieux <
dom@w3.org
>, Dave Raggett <
dsr@w3.org
>, Staff Contacts
Tracker:
documentation
, (
configuration for this group
), originally developed by
Dean Jackson
, is developed and maintained by the Systems Team <
w3t-sys@w3.org
>.
$Id: issues.php,v 1.12 2011/06/15 13:30:08 vivien Exp $