See also: IRC log
<jasonjgw> Authentication questions: https://lists.w3.org/Archives/Public/public-rqtf/2017Aug/0004.html
<scribe> scribe: janina
[discussion of consensus in W3C process]
jgw: Do we have qurom for a decision?
js: No
sh: Didn't we decide liast time?
js: Amost
<jasonjgw> https://lists.w3.org/Archives/Public/public-rqtf/2017Aug/0004.html
js: OK with David's and Judy's comments. Will post revised draft
jgw: Will cfc, just for the record
jgw: Thanks to SH for litt review
sh: Not as much depth as would
have liked
... Useful consideration about pwds need to use their assistive
tools even in VR
jgw: Do we build this into the VR apps? Or some kind of AT support?
<jasonjgw> Janina notes that assistive technologies designed for VR environments don't appear to be available; standards-based VR would allow such specialist components/technologies to be plugged into these environments.
<jasonjgw> Janina: having the level of the ground in a VR enviornment adjusted might be useful.
<jasonjgw> Janina: there's also the option of creating VR-based training environments to educate people who will be working with others who have disabilities.
<jasonjgw> Janina notes that these technologies should be broadly available - not restricted to clinical or other specialized settings.
<jasonjgw> Janina: example - simulator of the experience of a eprson with low vision.
js: Look at lighthouse.org for low vision
sh: Lots of scoping, but little
prototyping/implementation
... Four key areas:
... 1. Underpinnings -- APIs and how to interface any required
AT, vs what to build in
... 2. Provision of specific new AT -- virtual white cane
... Also adjusting heights vis a vis wheel chair
... 3. Simulation support
js: Virtual crutches
sh: Before you're handed the real ones to use for a few months
jgw: Coga people can find VR as useful as the real thing
sh: Not much to report --
research continues a few more weeks
... Will go beyond end of month a bit, but likely not past
September
<jasonjgw> Janina notes the involvement of some internet service providers in aggregating Internet of Things-related data from devices on the user's premises.
<jasonjgw> Janina: examples - sampling and tracking of air temperature, traffic tracking sensors, monitoring water usage, etc.
<jasonjgw> Janina notes a well developed low-level protocol used in Europe.
<jasonjgw> Janina: interoperability resides at the wireless data communications protocol level.
<jasonjgw> The long life required of some of the batteries imposes power constraints that demand the use of specialized protocols.
<jasonjgw> Janina: it appears there are too many competing protocols, and this needs to be addressed before interoperability moves forward - insufficiently many devices with common protocols.
<jasonjgw> Actual deployment will take time due to the interoperability issues.
<jasonjgw> Janina offers to provide references to the competing low-level protocols.
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: janina, scott_h WARNING: Replacing previous Present list. (Old list: (no, one), janina, scott_h) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ janina, scott_h Present: janina scott_h WARNING: Fewer than 3 people found for Present list! Found Scribe: janina Inferring ScribeNick: janina WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 23 Aug 2017 Guessing minutes URL: http://www.w3.org/2017/08/23-rqtf-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]