DAP Rechartering
DAP WG F2F
15 March 2011
Dominique Hazaël-Massieux
<dom@w3.org>
@dontcallmedom
Chartering process
new charter
draft (
Feb 2
)
current charter expiring June 2011
needs final draft early May at the latest
New charter proposal
policy framework removal
tightening up scope of APIs
clarification on security model
diff to previous charter
Policy Framework
rough consensus on removing it
some concerns from Deutsch Telekom, AT&T
keep permissions API
Security Model
concerns on too close linking to "browser-model" from RIM, AT&T, DT (at least)
mention widgets or not?
Privacy
Best Practices?
"Do Not Track"?
Privacy Rulesets?
Existing APIs: removal?
Communication Log (AT&T want to keep)
Gallery (AT&T, FT)
Existing APIs: reshape
User interaction into “vibration, beeps, menus”
Application launcher into "intent-based" approach?
SysInfo into specific sensors (network, bluetooth?, NFC?)
... and generic sensor API too?
New APIs
home media connectivity? mDNS? DLNA?
audio volume read?
<device>
?
Success Criteria:
add implementation on real constrained device
make sure TV can be one of these
