Proposed SysInfo updates and notes for actions/issues

Trying to get caught up on the open actions for SysInfo, here are some
proposed updates and  comments on other actions/issues. I sent the updated
editor's draft to the chairs for upload since I don't yet have CVS access
working.

For http://www.w3.org/2009/dap/track/issues/92 (Sysinfo, permissions for get
vs monitor)
[new text is in brackets]

       For the monitor method, distinct permission to monitor properties
       MUST be granted, and a maximum monitor period MUST be applied by the
user
       agent. [When requesting the user's express permission for use of the
       monitor method, the user agent MUST clearly indicate that this
provides
       ongoing access to the monitored property, as compared to a one-shot
       access.]

For http://www.w3.org/2009/dap/track/issues/102: (Sysinfo asynchronous calls
needs to be expressed in terms of events loop)
Not sure what to do here. The referenced email (
http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0031.html)
says "we should define callback operations in terms of event loops, tasks,
and task queues". But is there an example already of this for DAP APIs that
I can use as template for the changes?

For http://www.w3.org/2009/dap/track/actions/323 (Update sysinfo related to
power discussion)
Not sure what to do here. The discussion on the email list did not seem to
result in a specific set of proposed text changes.

For http://www.w3.org/2009/dap/track/issues/64 ("Generic" sensors may permit
discovering sensitive information)
I don't think any further changes are needed at this time. Since this issue
was created, we have enhanced the spec with explicit privacy considerations
and user expressed permission for the different groups or properties
according to their perceived sensitivity. If the user is well-informed and
consents to this information being accessed, I don't see larger issues with
providing the ability to access it.

For Claes's comments in
http://lists.w3.org/Archives/Public/public-device-apis/2010Nov/0028.html
function wifiMonitorCB(connection) {
  document.getElementById(indicator, "Wireless signal at
"+(connection.signalStrength*100)+"%");
}
was replaced by:
function wifiMonitorCB(connection) {
  document.getElementById(indicator).innerHTML = "Wireless signal at " +
connection.currentSignalStrength*100 + "%";
}

A start on Robin's comments (
http://lists.w3.org/Archives/Public/public-device-apis/2010Oct/0056.html):
- "to avoid side-channel attacks"...
[Bryan: enhanced as suggested]
- "webIDL" -> WebIDL (multiple times).
[Bryan: corrected as suggested]
- Properties are given two equivalent identifiers...
[Bryan: I will work on the suggestions]
- "through calls to the get or monitor() functions"...
[Bryan: corrected as suggested]
- This is confusing: we have a section called "The SystemInfo interface"...
[Bryan: I will work on the suggestions]

(to be continued)

Bryan Sullivan | AT&T