Ongoing chat among participants of the Joint W3C-OGC Workshop on Maps for the Web https://www.w3.org/2020/maps/supporting-material
(insert "map reduce" joke here)
Iván Sánchez Ortega
Answering @tomkralidis , I see a dystopian future where only three web mapping platforms work well natively in three web browsers.
Being fully on the developer side, I hate that I had to learn about different coordinate reference systems and why my coordinates don't work the same everywhere. This makes Features way more abstract than they should be. Even when lat/lon order doesn't matter, like [12,12]. That should always put me in Africa.
From Jonathan Moules: What Daniel's talking about is a flavour of the Jevons Paradox - https://en.wikipedia.org/wiki/Jevons_paradox - "When technological progress or government policy increases the efficiency with which a resource is used the rate of consumption of that resource rises due to increasing demand"
I don't hear anyone talking about how you relay the semantics of a map to a screen reader. I did miss the first hour on Wednesday...
If you get a native element. you must also define the semantics of the element and the accessibly APIs
Making controls a commonly available API helps everyone, especially accessibility; you can make them flexible through the API
@fredesch I think the <feature> element would be where I would say to start?
Are maps considered for "offline" functionality, like how it can be with downloaded local Google Map data
Was just going to say that.
Already covered by existing standards.
From Chris Little on Zoom: Question: does the panel think that maps will only take off when AR does?
Maps are already big!
Iván Sánchez Ortega
Offline/cached stuff is a political/economical problem, not a technical one. As I said yesterday, preventing users from caching means more billable HTTP requests, which means more cash.
Yeah like service workers I suppose. I guess since <map> would be HTML that ties right in. +1
I feel like there are two very different aspects to the a11y questions... part of that is about interaction/interactive elements.. The answer to that is it should use the existing platform or fill in what is missing. If it is about making the rendering accessible, are the existing forms not all there too?
There's a 50MB limit on iOS, by the way. >Service wirker cache