<Judy> scribe: Judy
[jb: notes meeting starting late due to logistics]
janina: Update to my role in w3c. In this group I will continue as a W3C Invited Expert. Separately I will be a consultant to Amazon, and will be communicating from a different email addess in that work, in Accessibility Guidelines Working Group.
scott: Congratulations
judy: Thanks for update. Can confirm that W3C has had people representing different roles in different groups.
<janina> scribe: janina
jgw: XR engages multiple specifications. We need to develop a list of which
<Judy> https://immersive-web.github.io/webxr/
<Judy> https://www.khronos.org/webgl/
jgw: notes XR Device API, which
in turn rests on existing WebGL
... Future versions could other rendering specs
... Gamepad API for input is included
... New grx specs for a WebGPU under development in a community
group
<Judy> https://www.imore.com/putting-web-graphics-pedal-metal
jgw: May be more ...
<Judy> https://www.khronos.org/gltf/
jb: Excellent review
... The canvas dependency raises a11y concerns
<Judy> https://www.w3.org/community/gpu/
sh: Can you explain a bit more about what WebGPU is?
jb: I'm not the best explainer
for that
... Notes this GL transmission protocol is already a Rev 2
spec
... May be helpful to a11y
... GLTF CG has explainers
... The GPU spec is expected to go to a W3C WG
<jasonjgw> Janina: asks with whom we could have a conversation to gain a good overview of the documents, in addition to reviewing them.
jgw: Agrees to read ahead, then a conversation
sh: Agree we need th insights
<jasonjgw> Janina notes these are foundational technologies that will appear in a range of applications over time - not just those traditionally associated with XR (e.g., publishing, real-time communication).
<jasonjgw> Janina agrees with Judy that APA needs to be familiarized with these specifications; RQTF culd be a useful vehicle for doing so.
jgw: Let's give ourselves some
time to read using the links above.
... We can then work toward a meeting with an expert
guest
... One we might announce more broadly
jgw: These are the various draft
documents in preparation mainly from Josh
... We should identify any issues so far
... We want to get these docs sufficiently drafted to ask for
wider comment and response
... Notes many are listed in today's agenda email
... Judy added a few more
<scribe> ACTION: jasonjgw to create an RQTF wiki of Use Cases Documents in Preparation
<trackbot> Error finding 'jasonjgw'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.
<scribe> ACTION: jasonjgw to create an RQTF wiki of Use Cases Documents in Preparation
<trackbot> Error finding 'jasonjgw'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.
jgw: Any comments yet from anyone?
<Judy> https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Main_Page
<Judy> [jb: I had to go through 5 layers of pages to get to RQTF current work... let's please not add another]
<Judy> [jb: better if we can surface the lower-down content in the level above]
<Judy> [jw: yes, can do that, pull it up one layer]
<jasonjgw> Janina notes that the comment period closes Friday.
<jasonjgw> Substantive issues raised in comments (even if slightly after the close of the comment period) will be addressed.
<jasonjgw> Janina plans to clarify that we aren't providing a catalogue of all CAPTCHA-related products and technologies, and that we are choosing what we cite selectively.
<jasonjgw> If there are no more comments, a Call for Consensus to advance to Note status will be circulated to APA.
<jasonjgw> Janina notes a single paragraph of difference between the current editor's draft and the wide review draft - resulting from changes suggested by internationalization review.
jgw: Just a general request for info on people's availability for the next month or so
<jasonjgw> Janina: available through August, up close to TPAC. We probably won't meet the week after TPAC.
janina: Will be here up to TPAC
Steve: Will be here
sh: wishes it were summer, but will be here
jb: Will be unavailable week of
Aug 7 which is Geek Week at W3C, well, but given RQTF works on
emerging technologies, I may indeed be here
... 21 & 28 will be gone
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/by/from/ Succeeded: s/welel, may be here/well, but given RQTF works on emerging technologies, I may indeed be here/ Default Present: jasonjgw, janina, Joshue, Matthew_Atkinson, MichaelC, SteveNoble, scott-H, Judy, scott_h Present: jasonjgw janina Joshue Matthew_Atkinson MichaelC SteveNoble scott-H Judy scott_h Found Scribe: Judy Inferring ScribeNick: Judy Found Scribe: janina Inferring ScribeNick: janina Scribes: Judy, janina ScribeNicks: Judy, janina Found Date: 24 Jul 2019 People with action items: jasonjgw WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]