Re: Meeting agenda for 22 July 2020

Hi everybody,
I’d like to give a quick overview as I read the whole Map Workshop abstract (https://www.w3.org/2020/maps/ <https://www.w3.org/2020/maps/>).
I see some nexus with my GeoAR work and the workshop. It’s important to state that they never talk about AR, and that they are interested in finding a way to standardise a native Map HTML element, and discuss about all topics related to that.

Anyway, I see some points of interesting related to my work:

https://www.w3.org/2020/maps/#topics <https://www.w3.org/2020/maps/#topics>

> other Web platform applications for map-viewer display and interaction patterns
> integrating geographic data and (hyper)text annotations or other semantic information about spatial things
>  communicating spatial information through non-visual technologies
> personalization of map viewer display and capabilities
> using spatial information to enhance accessibility in the physical environment

All this points can relate to the idea of providing an AR navigation in conjunction with a 2D Web Map. This can provide, for some users, a more accessible and alternative way to use geospatial map data.
Using ARIA attributes it’s technically possible to use speech synthesis to read navigation data (when set up) for both a 2D map but also for a GeoAR application. 
To sum up, I can give an overview of possibilities to provide this alternative way to use map data, that may be integrated with a 2D map. Users can decide to use 2D map view, AR view for navigation, or both, according to their needs. They should switch between the two seamlessly.

We can talk about this more in detail on the tomorrow meet, this is just an overview of major nexus topics I found.

Have a nice day,

Nicolò Carpignoli

Chialab Design Company
via Arrigo Lucchini 9
40134 Bologna, Italy
+39 0516154398 int. 507
www.chialab.it <https://www.chialab.it/>

> Il giorno 20 lug 2020, alle ore 16:09, White, Jason J <jjwhite@ets.org> ha scritto:
> 
> Meeting logistics:
> Wednesday 22 July 2020, 9:00am US eastern time (1300 UTC)
> Teleconference details: https://www.w3.org/2017/08/telecon-info_rqtf <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F08%2Ftelecon-info_rqtf&data=02%7C01%7Cjjwhite%40ets.org%7C96e1d912b97b43ebedfd08d8016f1173%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637260923837587515&sdata=mzjAkcI0zQvbTZS4PhnE%2FYeFZc%2FRqrEo%2BCQgnPqic18%3D&reserved=0>.
> This meeting continues the conversations and associated work undertaken last week. The agenda are as follows.
> Upcoming W3C workshops, including maps on the Web, and the Web and Machine Learning – discussion limited to 20 minutes:
> https://www.w3.org/2020/06/machine-learning-workshop/ <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2020%2F06%2Fmachine-learning-workshop%2F&data=02%7C01%7Cjjwhite%40ets.org%7Cf73444eacdf94f19f5c908d81a08d03f%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637287972452448236&sdata=6mI8kx1Bvg8HuYM4%2BLZKIkOR%2F1Wmj6BGvOHlBNr7oFE%3D&reserved=0>
> Real-Time Communication Accessibility User Requirements (RAUR), open issues, as identified below.
> Miscellaneous topics.
>  
> The RAUR issues identified by Josh are as follows.
>  
> Capture of on record/off record captions in RTC
> #102 opened on May 25 by RealJoshue108
> https://github.com/w3c/apa/issues/102 <https://github.com/w3c/apa/issues/102>
>  
> In a video conference session in which sign language interpretation is 
> provided, both the signer and the speaker should be visible
> #97 opened on Apr 8 by jasonjgw
> https://github.com/w3c/apa/issues/97 <https://github.com/w3c/apa/issues/97>
>  
> Audio and Video Quality RAUR
> #46 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/46 <https://github.com/w3c/apa/issues/46>
>  
> Clarification needed on Req 13a, 13b, 14a
> #45 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/45 <https://github.com/w3c/apa/issues/45>
>  
> Section 2.8: REQ 10a and 15a: Seem UI-related, and not WebRTC-related.
> #44 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/44 <https://github.com/w3c/apa/issues/44>
>  
> REQ 9a: Security Issues and Bias
> #43 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/43 <https://github.com/w3c/apa/issues/43>
>  
> Section 2.6: REQ 8a only refers to real-time text, but User Need 8 seems 
> to be calling for something more
> #42 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/42 <https://github.com/w3c/apa/issues/42>
>  
> REQ 2b: doesn’t make sense in view of the role of screen readers in 
> controlling the attached braille device.
> #41 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/41 <https://github.com/w3c/apa/issues/41>
>  
> Section 2.2: User need 2 – It isn’t clear what the need is here.
> #40 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/40 <https://github.com/w3c/apa/issues/40>
>  
> Section 2.1: Req 1a – consider dividing this into different cases and 
> elaborating each of them.
> #39 opened on Jan 29 by RealJoshue108
> https://github.com/w3c/apa/issues/39 <https://github.com/w3c/apa/issues/39>
>  
>  
> References:
> Directory of  Web of Things use cases:
> https://github.com/w3c/wot-usecases/tree/master/USE-CASES <https://github.com/w3c/wot-usecases/tree/master/USE-CASES>
> Smart Car Configuration Management
> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-2-1_smart-car-configuration-management.md <https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-2-1_smart-car-configuration-management.md>
> Interactive Public Spaces
> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-3-1_interactive-public-spaces.md <https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-3-1_interactive-public-spaces.md>
> Meeting Room Event Assistance
> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-3-2_meeting-room-event-assistance.md <https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-3-2_meeting-room-event-assistance.md>
> Health Notifiers
> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-4-1_health-notifiers.md <https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-4-1_health-notifiers.md>
> Multimodal Recognition Support
> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-5-1_multimodal-recognition-support.md <https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-5-1_multimodal-recognition-support.md>
> Enhancement of Synergistic Interactions
> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-5-2_enhancement-of-synergistic-interactions.md <https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-5-2_enhancement-of-synergistic-interactions.md>
> Note also the APA Working Group Call for Consensus at
> https://lists.w3.org/Archives/Public/public-apa-admin/2020Jun/0004.html <https://lists.w3.org/Archives/Public/public-apa-admin/2020Jun/0004.html>
> Minutes of the previous RQTF meeting are available at
> https://www.w3.org/2020/07/15-rqtf-minutes.html <https://www.w3.org/2020/07/15-rqtf-minutes.html>
>  
>  
>  
>  
> 
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
> 
> 
> Thank you for your compliance.
>