ISSUE-1 param-style |
CLOSED |
Pick parameter passing style (list or object) |
2009-07-29 |
APIs — General |
0 |
ISSUE-2 error-handling |
CLOSED |
Error handling style |
2009-08-25 |
APIs — General |
0 |
ISSUE-3 async-style |
CLOSED |
Asynchronous calls style |
2009-08-25 |
APIs — General |
0 |
ISSUE-4 api-versioning |
CLOSED |
API Versioning |
2009-08-25 |
APIs — General |
0 |
ISSUE-5 |
CLOSED |
Gathering requirements for Application Configuration API |
2009-08-25 |
Application Configuration API |
0 |
ISSUE-6 AppLaunchReq |
CLOSED |
Gathering requirements for Application Launcher API |
2009-08-25 |
Application Launcher API |
0 |
ISSUE-7 CalendarReq |
CLOSED |
Gathering requirements - calendar |
2009-08-25 |
Calendar API |
0 |
ISSUE-8 CameraReq |
CLOSED |
Gathering requirements for Camera API |
2009-08-25 |
Capture API |
0 |
ISSUE-9 CommLogReq |
CLOSED |
Gathering requirements for Communication Log API |
2009-08-25 |
Communication Log API |
0 |
ISSUE-10 ContactsReq |
CLOSED |
Gathering requirements for Contacts API |
2009-08-25 |
Contacts API |
0 |
ISSUE-11 FilesystemReq |
CLOSED |
Gathering requirements for FileSystem API |
2009-08-25 |
FileSystem API |
0 |
ISSUE-12 GalleryReq |
CLOSED |
Gathering requirements for Gallery API |
2009-08-25 |
Gallery API |
0 |
ISSUE-13 MessagingReq |
CLOSED |
Gathering requirements - messaging |
2009-08-25 |
Messaging API |
0 |
ISSUE-14 SysinfoReq |
CLOSED |
Gathering requirements for System Information and Events API |
2009-08-25 |
System Information and Events API |
0 |
ISSUE-15 TasksReq |
CLOSED |
Gathering requirements for Tasks API |
2009-08-25 |
Tasks API |
0 |
ISSUE-16 UserInteractionReq |
CLOSED |
Gathering requirements for User Interaction API |
2009-08-25 |
User Interaction API |
0 |
ISSUE-17 FilesystemSecurityReq |
CLOSED |
Summarize security issues and related requirements for file API |
2009-09-03 |
FileSystem API |
0 |
ISSUE-18 compareSecurityStartingPoints |
CLOSED |
Determine security policy starting points for review and comparison |
2009-09-21 |
Security Policy Framework — General |
0 |
ISSUE-19 html5SecurityModel |
CLOSED |
What are key HTML 5 security model considerations that impact DAP Policy language and framework |
2009-09-21 |
Security Policy Framework — General |
0 |
ISSUE-20 |
CLOSED |
What are essential requirements for DAP security and policy |
2009-09-21 |
Security Policy Framework — General |
0 |
ISSUE-21 FeaturesCapabilities |
CLOSED |
Is policy/access control on both features and device capabilities needed, do all submissions include both of these |
2009-09-23 |
Policy Framework Requirements |
0 |
ISSUE-22 ReqReq |
CLOSED |
Should we have an umbrella requirements document? |
2009-09-23 |
APIs — General |
0 |
ISSUE-23 defaultPolicy |
CLOSED |
Should policy framework support notion of default policy? |
2009-09-29 |
Security Policy Framework — General |
0 |
ISSUE-24 |
CLOSED |
Policy, need to define semantics of capabilities or not |
2009-09-30 |
Security Policy Framework — General |
0 |
ISSUE-25 x-module |
CLOSED |
Cross-module dependency and impact on policy |
2009-09-30 |
APIs — General |
0 |
ISSUE-26 apiIdentification |
CLOSED |
How to refer to API |
2009-10-06 |
Security Policy Framework — General |
0 |
ISSUE-27 |
CLOSED |
[Policy] Is revocation in scope |
2009-10-06 |
Security Policy Framework — General |
0 |
ISSUE-28 noModalPrompt |
CLOSED |
Requirement for NO security prompting |
2009-10-06 |
Policy Framework Requirements |
0 |
ISSUE-29 apiKeys |
CLOSED |
Should DAP APIs support "API Keys" |
2009-10-07 |
Policy Framework Requirements |
0 |
ISSUE-30 federatedIdentityReq |
CLOSED |
Is support/integration for federated identity required, e.g. OpenId, OpenAuth, SAML etc |
2009-10-07 |
Policy Framework Requirements |
0 |
ISSUE-31 callbackEventsPolicyReq |
CLOSED |
What are the special DAP policy requirements and issues elated to events and callbacks, if any |
2009-10-07 |
Policy Framework Requirements |
0 |
ISSUE-32 featuresCapabilitiesIdentification |
CLOSED |
Features, Device Capabilities, their identification, and their role in policy. |
2009-10-14 |
Security Policy Framework — General |
0 |
ISSUE-33 persistingState |
CLOSED |
Persisting state of user decisions |
2009-10-21 |
Policy Framework |
0 |
ISSUE-34 protectingDataOrApis |
CLOSED |
Protecting data versus protecting apis |
2009-10-21 |
APIs — General |
0 |
ISSUE-35 deadlockPolicy |
CLOSED |
How to handle malformed policies, policy validity and intentional abuse of policy? How is policy deadlock handled? e.g. Only dial +39 numbers + Never dial +39 numbers |
2009-11-02 |
Policy Framework |
0 |
ISSUE-36 domainBasedTrust |
CLOSED |
How far can we go with domain based trust model given constraints of HTML5 security model |
2009-11-02 |
Policy Framework Requirements |
0 |
ISSUE-37 domainSpoofing |
CLOSED |
Domain spoofing and trust in the network layer |
2009-11-02 |
Policy Framework Requirements |
0 |
ISSUE-38 securityUseCases |
CLOSED |
Use cases and threat model for security requirements |
2009-11-02 |
Policy Framework Requirements |
0 |
ISSUE-39 filesystemUseCases |
CLOSED |
Use cases for filesystem API |
2009-11-02 |
FileSystem API |
0 |
ISSUE-40 ridOfFilesystem |
CLOSED |
Is File API appropriate abstraction/interface |
2009-11-02 |
FileSystem API |
0 |
ISSUE-41 |
CLOSED |
Include MMI in DAP specification reviews, including APIs and security |
2009-11-02 |
|
0 |
ISSUE-42 |
CLOSED |
Able to use of MMI for user interactions |
2009-11-02 |
|
0 |
ISSUE-44 apiHanging |
CLOSED |
What do APIs hang off of? |
2009-11-12 |
APIs — General |
0 |
ISSUE-45 ReSpec-ToC-depth |
CLOSED |
Respec: customize table of content depth |
2009-11-24 |
APIs — General |
0 |
ISSUE-46 respec-opera |
CLOSED |
Opera doesn't render ReSpected issues |
2009-11-24 |
APIs — General |
0 |
ISSUE-47 respec-opera |
CLOSED |
Opera doesn't render ReSpected issues |
2009-11-25 |
APIs — General |
0 |
ISSUE-48 respec-wrap |
CLOSED |
Wrapping WebIDL definitions in the source doesn't work, it should |
2009-12-02 |
ReSpec |
0 |
ISSUE-49 respec-optional |
CLOSED |
ReSpec mis-parses "optional" as part of the type |
2009-12-02 |
ReSpec |
0 |
ISSUE-50 respec-indent |
CLOSED |
ReSpec should detect that examples are indented and remove the leading white space |
2009-12-02 |
ReSpec |
0 |
ISSUE-51 respec-nullable-types |
CLOSED |
ReSpec: no support for nullable types in IDL |
2009-12-02 |
ReSpec |
0 |
ISSUE-52 respec-optional |
CLOSED |
'optional' is not recognised by ReSpec |
2009-12-03 |
ReSpec |
0 |
ISSUE-53 respec-arrays |
CLOSED |
Respec doesn't support arrays |
2009-12-03 |
ReSpec |
0 |
ISSUE-54 messagingUriSchemes |
CLOSED |
What messaging use cases cannot be fulfilled by existing URI schemes (mailto, sms, mms)? |
2009-12-09 |
Messaging API |
0 |
ISSUE-55 objectParams |
CLOSED |
Should we use object literals in place of positional parameters and if so when? |
2009-12-16 |
APIs — General |
0 |
ISSUE-56 |
CLOSED |
Add custom copyright notice |
2009-12-16 |
ReSpec |
0 |
ISSUE-57 |
CLOSED |
Setting note with a title |
2009-12-16 |
ReSpec |
0 |
ISSUE-58 |
CLOSED |
Provide link to section of document producing text that includes section title and section number |
2009-12-17 |
ReSpec |
0 |
ISSUE-59 sysinfo-minmaxfrequency |
CLOSED |
SysInfo: make minFrequency and maxFrequency optional |
2009-12-21 |
System Information and Events API |
0 |
ISSUE-60 sysinfo-accelerometer |
CLOSED |
orientation, acceleration compass in System Information |
2009-12-21 |
System Information and Events API |
0 |
ISSUE-61 |
CLOSED |
Enable note regarding Reference versions |
2009-12-23 |
ReSpec |
0 |
ISSUE-62 respec-changemarkers |
CLOSED |
Add change markers to respec |
2010-01-06 |
ReSpec |
0 |
ISSUE-63 encryptedIsMagic |
CLOSED |
network API: "encrypted" property is meaningless |
2010-01-06 |
System Information and Events API |
0 |
ISSUE-64 hidingIsHard |
CLOSED |
"Generic" sensors may permit discovering sensitive information |
2010-01-06 |
System Information and Events API |
0 |
ISSUE-65 |
CLOSED |
ReSpec creating invalid HTML wth save as HTML source: link for stylesheet missing closing tag or slash, link for w3 image missing closing tag or slash |
2010-01-12 |
|
0 |
ISSUE-66 restfulAPIs |
CLOSED |
Investigation around Virtual Web Devices / REST-ful oriented APIs |
2010-01-13 |
APIs — General |
0 |
ISSUE-67 navigator.Stuff |
CLOSED |
In navigator.device, should "device" be "service" or something else? |
2010-01-13 |
APIs — General |
0 |
ISSUE-68 respec-idl-indent |
CLOSED |
confusing indentation of WebIDL blocks in ReSpec |
2010-01-18 |
ReSpec |
0 |
ISSUE-69 inline-css |
CLOSED |
ReSpec should always have inlineCSS true |
2010-01-20 |
ReSpec |
0 |
ISSUE-70 usecases-in-spec |
CLOSED |
Should we have use-cases in specifications |
2010-01-27 |
APIs — General |
0 |
ISSUE-71 dataModelDiff |
CLOSED |
Difference in data model between Contacts/Calendar APIs and vCard/vCalendar |
2010-01-27 |
Calendar API |
0 |
ISSUE-72 uriSchemesInContacts |
CLOSED |
Usage of URIs for sms, tel:, etc in PIM APIs |
2010-01-27 |
Contacts API |
0 |
ISSUE-73 contacts-security |
CLOSED |
Security and Privacy Implications for PIM APIs |
2010-02-03 |
APIs — General |
0 |
ISSUE-74 respec-multi-prev |
CLOSED |
ReSpec should support multiple previous versions (e.g. for merged documents) |
2010-02-08 |
ReSpec |
0 |
ISSUE-75 respec-non-rectrack |
CLOSED |
ReSpec should support non-RecTrack override |
2010-02-08 |
ReSpec |
0 |
ISSUE-76 sysinfo-availableNetworks |
CLOSED |
Available/Preferred Networks in sysinfo |
2010-03-01 |
System Information and Events API |
0 |
ISSUE-78 exifPrivacy |
CLOSED |
Capture has a minimisation problem with EXIF data (e.g. it could be Geotagged) |
2010-03-16 |
Capture API |
0 |
ISSUE-79 fingerprintingSysinfo |
CLOSED |
Fingerprinting privacy issue related to sysinfo, need for feedback on privacy risk |
2010-03-16 |
System Information and Events API |
0 |
ISSUE-80 lunasolarCalendar |
CLOSED |
Can we support lunasolar calendars in the calendar API? |
2010-03-17 |
Calendar API |
0 |
ISSUE-81 timezonedDate |
CLOSED |
How to represent dates? ES has Date but with no TZ information; using strings is less than ideal; do we have to create a Web Dates specification? |
2010-03-17 |
Calendar API |
0 |
ISSUE-82 commMessaging |
CLOSED |
Should Communication Logs be part of the messaging API or part of a telephony API? |
2010-03-18 |
Communication Log API |
0 |
ISSUE-83 warp |
CLOSED |
Note relationship of WARP to DAP policy work |
2010-04-28 |
Policy Framework |
0 |
ISSUE-84 messagingHeaders |
CLOSED |
Which headers to support setting/getting in Messaging API? |
2010-04-28 |
Messaging API |
0 |
ISSUE-85 codecs |
CLOSED |
No provisions for audio/x-speex, video/x-webm, audio/ogg, or video/ogg |
2010-06-09 |
Capture API |
0 |
ISSUE-86 contactsSharing |
CLOSED |
Privacy issue about sharing other users contact information from own address book |
2010-07-13 |
Contacts API |
0 |
ISSUE-87 rulesetGranluarity |
CLOSED |
Degree of ruleset transmission with API calls, how often, which |
2010-07-13 |
Privacy |
0 |
ISSUE-88 rulesetPackaging |
CLOSED |
User interaction for ruleset confirmation when multiple APIs are used to provide functionality, usability etc |
2010-07-13 |
Privacy |
0 |
ISSUE-89 ruleSetsOverride |
CLOSED |
Clarify how rulesets interact with pre-existing relationships |
2010-07-13 |
Privacy |
0 |
ISSUE-90 webDevPrivacyBP |
CLOSED |
Create privacy best practices document for web site developer |
2010-07-13 |
Privacy |
0 |
ISSUE-91 apiProviderPrivacy |
CLOSED |
Be clear to distinguish site (service) privacy policy versus included location provider policy etc |
2010-07-14 |
Privacy |
0 |
ISSUE-92 getVsWatch |
CLOSED |
Sysinfo, permissions for get vs monitor; |
2010-07-14 |
System Information and Events API |
0 |
ISSUE-93 contactsWrite |
CLOSED |
Do we want to stage the release of contacts API between read and write access? |
2010-07-14 |
Contacts API |
0 |
ISSUE-94 powerboxPolicy |
CLOSED |
How do Powerbox and Policy interact and integrate |
2010-07-15 |
Policy Framework |
0 |
ISSUE-95 rulesetAndRegulation |
CLOSED |
Different regulatory environments and relationship to privacy and rulesets |
2010-07-16 |
Privacy |
0 |
ISSUE-96 monitoringStaticProperties |
CLOSED |
Some properties of sysinfo are static so monitor might not make sense |
2010-08-04 |
System Information and Events API |
0 |
ISSUE-97 writingIsHard |
CLOSED |
Write-access difficulties (in contacts and other APIs), see http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0112.html |
2010-08-04 |
APIs — General |
0 |
ISSUE-98 contactsDatamodel |
CLOSED |
On what data model should the contacts API be based? |
2010-08-25 |
Contacts API |
0 |
ISSUE-101 default-codec |
CLOSED |
Should we define a default audio (video?) codec for capture? if so, which? |
2010-09-01 |
Capture API |
0 |
ISSUE-102 eventsLoopSysinfo |
CLOSED |
Sysinfo asynchronous calls needs to be expressed in terms of events loop |
2010-09-15 |
System Information and Events API |
0 |
ISSUE-103 messagingContained |
CLOSED |
Does the messaging API fit outside of contained environments? |
2010-11-04 |
Messaging API |
0 |
ISSUE-104 trustedOrCurated |
CLOSED |
Find a better name for "trusted environments" |
2010-11-04 |
Policy Framework |
0 |
ISSUE-105 captureHint |
CLOSED |
Should the capture hint in HTML Media Capture be specified through a MIME parameter? |
2010-11-18 |
Capture API |
0 |
ISSUE-106 tzContacts |
CLOSED |
Does Contacts API having a timezone field make sense, should it be utfOffset or utcOffset and tz to better match vCard? |
2011-01-19 |
Contacts API |
0 |
ISSUE-107 messagingUris |
CLOSED |
How to better integrate URIs schemes in Messaging API |
2011-01-28 |
Messaging API |
0 |
ISSUE-108 |
CLOSED |
Should Contacts API have MUST instead of SHOULD for extended contact properties, is this a general issue for all specs? |
2011-02-09 |
|
0 |
ISSUE-109 |
CLOSED |
We need solid use cases for Feat Perms if it's going to fly |
2011-02-16 |
Device APIs Permissions |
0 |
ISSUE-110 contactEventLoop |
CLOSED |
Contacts API needs to integrate HTML Event Loop |
2011-03-16 |
Contacts API |
0 |
ISSUE-111 urlInContacts |
CLOSED |
Should (some of the) ContactField objects use URLs rather than free-form strings? |
2011-06-01 |
Contacts API |
0 |
ISSUE-112 batteryTimeRemaining |
CLOSED |
Do we need to give an estimated time remaining indication with battery events? |
2011-06-29 |
Battery Status API |
0 |
ISSUE-113 initialEventFiringBattery |
CLOSED |
AddEventListener in Battery Status has side effects |
2011-07-13 |
Battery Status API |
0 |
ISSUE-114 |
CLOSED |
Battery spec should note relative ordering of battery low versus battery critical in terms of criticality |
2011-07-19 |
Battery Status API |
0 |
ISSUE-115 |
CLOSED |
Do you get the batterylow event when you're charging and cross that boundary? |
2011-07-19 |
Battery Status API |
0 |
ISSUE-116 |
CLOSED |
HTML Media Capture doesn't make sense if accept=image and capture=microphone |
2011-07-20 |
HTML Media Capture |
0 |
ISSUE-117 |
CLOSED |
Should HTML Media Capture have options for front/user camera as in getUserMedia |
2011-07-20 |
HTML Media Capture |
0 |
ISSUE-118 |
CLOSED |
How would feature discovery work for REST APIs |
2011-07-21 |
APIs — General |
0 |
ISSUE-119 customErrorObjects |
CLOSED |
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 |
CLOSED |
How to handle exposing single vs multiple sensors of the same type |
2011-10-05 |
Sensor API |
0 |
ISSUE-121 sensorScope |
CLOSED |
Scope of sensor API and sensor discovery |
2011-10-14 |
Sensor API |
0 |
ISSUE-122 |
CLOSED |
Is low level data necessary for all sensor APIs, which ones have use cases and which not |
2011-11-03 |
|
0 |
ISSUE-123 |
CLOSED |
Low level discovery API security and privacy issues |
2011-11-04 |
|
0 |
ISSUE-124 |
CLOSED |
Concern on exposing raw sensor data |
2012-02-15 |
|
0 |
ISSUE-125 |
CLOSED |
Capabilities API compatibility with web privacy and security, assuming untrusted, fingerprinting risk |
2012-03-21 |
|
0 |
ISSUE-126 |
CLOSED |
Should DAP review and take advantage of SysApps security models |
2012-11-01 |
|
0 |
ISSUE-127 |
CLOSED |
Status section of Battery CR draft should include exit criteria and at-risk items |
2012-11-01 |
|
0 |
ISSUE-129 |
CLOSED |
Simplify Network Service Discovery API |
2013-07-09 |
Network Service Discovery |
0 |
ISSUE-130 |
CLOSED |
Enable variety of protocols (e.g. UPnP, Bonour) with protocol independent developer code |
2013-07-09 |
Network Service Discovery |
0 |
ISSUE-131 |
CLOSED |
Support UPnP device discovery by Device Type? |
2013-07-09 |
Network Service Discovery |
0 |
ISSUE-132 |
CLOSED |
Announce a webapp as a Network Services Discovery |
2013-07-09 |
Network Service Discovery |
0 |
ISSUE-133 |
CLOSED |
Fix UPnP events subscription and unsubscription |
2013-07-30 |
Network Service Discovery |
0 |
ISSUE-134 |
CLOSED |
Rename NetworkServices and NetworkService events |
2013-07-30 |
Network Service Discovery |
0 |
ISSUE-135 |
CLOSED |
Add security and privacy considerations section |
2013-08-09 |
Network Service Discovery |
0 |
ISSUE-136 |
CLOSED |
Issues related to garbage collection |
2013-08-09 |
Network Service Discovery |
0 |
ISSUE-137 |
CLOSED |
Issues related to garbage collection |
2013-08-09 |
Network Service Discovery |
0 |
ISSUE-138 |
CLOSED |
Issues related to garbage collection |
2013-08-09 |
Network Service Discovery |
0 |
ISSUE-139 |
CLOSED |
Add security and privacy considerations section |
2013-08-09 |
Network Service Discovery |
0 |
ISSUE-140 |
CLOSED |
Add security and privacy considerations section |
2013-08-09 |
Network Service Discovery |
0 |
ISSUE-141 |
CLOSED |
Allow for infinite values in DeviceLightEventInit dictionary |
2013-08-19 |
Ambient Light Events API |
0 |
ISSUE-142 |
CLOSED |
Allow for infinite values in DeviceProximityEventInit dictionary |
2013-08-19 |
Proximity API |
0 |
ISSUE-143 |
CLOSED |
should have a normative dependency on WebIDL, add reference |
2013-08-19 |
Ambient Light Events API |
0 |
ISSUE-144 |
CLOSED |
should have a normative dependency on WebIDL, add reference |
2013-08-19 |
Proximity API |
0 |
ISSUE-145 |
CLOSED |
initialize Default value for LightLevelState to empty string |
2013-08-19 |
Ambient Light Events API |
0 |
ISSUE-147 |
CLOSED |
Reference 'Requirements for Home Networking Scenarios' in Introduction |
2013-08-27 |
Network Service Discovery |
0 |
ISSUE-148 |
CLOSED |
NetworkService.name definition in 8.2.2.4 incoherent with definition in 7.1 (a human-readable title for the service) |
2013-09-04 |
Network Service Discovery |
0 |
ISSUE-149 |
CLOSED |
handling of long vibration list - truncate or no vibration at all |
2013-09-04 |
Vibration API |
0 |
ISSUE-150 |
CLOSED |
Should vibration be additive when multiple instances, e.g. iframes |
2013-09-04 |
Vibration API |
0 |
ISSUE-151 |
CLOSED |
USN should not be used as device identifier |
2013-09-06 |
Network Service Discovery |
0 |
ISSUE-153 |
CLOSED |
Would interface and event name change be possible and clearer |
2013-10-02 |
Proximity API |
0 |
ISSUE-154 |
CLOSED |
Security approach |
2013-10-02 |
Network Service Discovery |
0 |
ISSUE-157 |
CLOSED |
Style element appears in body before bibliography, should be in head (validation issue) |
2014-02-21 |
Network Service Discovery |
0 |
ISSUE-158 |
CLOSED |
Whatwg promises related links are broken and should be removed, new promises reference needed |
2014-02-21 |
Network Service Discovery |
0 |
ISSUE-159 |
CLOSED |
Diff link in WD broken, update in source |
2014-02-21 |
Network Service Discovery |
0 |
ISSUE-160 |
CLOSED |
Make query types specific to domain (e.g. discover printers rather than services in general) |
2014-05-15 |
Network Service Discovery |
0 |
ISSUE-161 |
CLOSED |
Enable progress discovery instead of returning fixed array of services |
2014-05-15 |
Network Service Discovery |
0 |
ISSUE-162 |
CLOSED |
Compatibility with existing libraries may not offer suitable control |
2014-05-15 |
Network Service Discovery |
0 |
ISSUE-163 |
CLOSED |
Should charging time be retained in battery api if inaccurate |
2014-06-26 |
|
0 |
ISSUE-164 |
CLOSED |
Correct default for charging time if unknown in battery |
2014-06-26 |
Battery Status API |
0 |
ISSUE-165 |
CLOSED |
Clarify language around multiple batteries |
2014-08-04 |
Battery Status API |
0 |
ISSUE-170 |
CLOSED |
light levels are not retrievable until a change causes the devicelight event to fire. |
2014-08-26 |
Generic Sensor API |
0 |
ISSUE-172 |
CLOSED |
Anssik update pr draft to change link from implementation report to https://w3c.github.io/test-results/battery-status/20160226.html |
2016-03-03 |
|
0 |
ISSUE-173 |
CLOSED |
Anssik to create pr publication draft, updating status section to note that there were no new issues since cr, that there were no features marked as at risk |
2016-03-03 |
|
0 |
ISSUE-174 |
CLOSED |
Anssik to put tentative date of 3 may 2016 in battery pr draft |
2016-03-03 |
|
0 |