Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    tguild
    @tguild
    … I will be more helpful and informed instead of have intrepidations
    Peter: this proposal needs champions
    Bryan: we took on following GeoJSON and this workshop enforced it is being widely embraced
    Peter: before we can describe this as a polyfill it needs to be tested
    Amelia: there are two sides to this story, we had a good discussion on low level issues such as rendering
    … there is the other end where content creators who want an easy API for expressing their content on a map
    … I suspect these things would need to move forward in parallel
    … there are already leaf widgets. Peter's map element polyfill is currently done as a wrap around leaflet but there are other ways it could be done
    Bryan Haberberger
    @thehabes
    All these institutions tend to have people that can dabble in HTML, but scripting is a major gap to cross.
    tguild
    @tguild
    … just playing around what the markup could look like while leveraging existing map engines worthwhile
    Bryan Haberberger
    @thehabes
    Those people would definitely be less intimidated by a <map> element
    tguild
    @tguild
    … Bryan's clients don't care about the implementation details but how it works and to describe their content
    Bryan Haberberger
    @thehabes
    @tguild Which is why "including" the user the whole time in development doesn't always work in the devs favor
    Fred Esch
    @fredesch
    Having done charting engines, my concern is semantics, interactivity and accessibility
    Bryan Haberberger
    @thehabes
    @prushforth and that's how most people treat them. I want a map CMS that works like Omeka.
    tguild
    @tguild
    Peter: I don't think anything is changed on the server side, this is just a more natural format with less friction
    Bryan Haberberger
    @thehabes
    And I say that is not a real thing
    And then we pick a stack
    tguild
    @tguild
    … this is why the ESRI and MapBoxes don't see mapML as a threay
    s/threay/threat/
    Doug Schepers
    @shepazu
    All these worlds are yours, @tguild, except Europa… attempt no landing there.
    tguild
    @tguild
    Fred: semantics, accessibility all needed for html co-element
    … I think widgets are fine. having been in ARIA and other working group, trying to change elements a humungous task better to work on widgets
    … we need better interactive ability, line of site, pan, zoom and understand spatial relationships
    … it is possible and more so than just with mouse over
    … there are big gaps being missed
    Satoru Takagi
    @satakagi

    I think you have GeoJSON if only to represent the data.

    For elements to represent geographic information other than mapml's map,layer elements.

    tguild
    @tguild
    Amelia: good points Fred
    Doug Schepers
    @shepazu
    I think that there were lots of explorations of accessibility throughout the workshop
    Nicolas
    @NicolasRafaelPalomino
    I wonder why's maps and widgets are not yet being utilized and actively being developed in applications
    tguild
    @tguild
    … how can we describe geographic content and interaction patterns in a standard way
    Iván Sánchez Ortega
    @IvanSanchez_gitlab
    @fredesch You missed my thing with the joysticks?
    Chris Hodgson
    @cmhodgson
    I think that semantics, interactivity and accessibility are the motivations for the <feature> element - we need something in the DOM to attach that too
    1 reply
    tguild
    @tguild
    … maps on the web are not addressing these needs
    … we need to make map widgets more accessible to more people
    1 reply
    Simon: we covered accessibility extensively earlier in these preceedings, what accessible maps can be like with eg touch and vibration for maps
    … we should include this in the design by default
    Fred: most maps fail all WCAG2 guidelines
    … if you have a map element you should permit people to migrate around the map as easily with a keyboard as with a mouse, it is just essential
    Simon: one of the requirements should be maps need to be accessible
    … we need to have extensive discussions with the accessiblity community in order to make this successful
    Gobe: we have done a good job at discussing needs. for future events we should try to engage the hardware manufacturers, not just mouse manufacturers but all forms of interaction with applications
    Doug Schepers
    @shepazu
    FWIW, gaming has really improved their accessibility in both hardware and software in recent years
    tguild
    @tguild
    … there is considerable research on machine interfaces
    Fred Esch
    @fredesch
    @IvanSanchez_gitlab I saw your joystick that was very insightful
    1 reply
    tguild
    @tguild
    Peter: I will post a link to Discourse chat so people can contribute their ideas on next steps and conclusions
    1 reply
    Iván Sánchez Ortega
    @IvanSanchez_gitlab
    I'm starting to really wonder if the joystick/gamepad behaviour from 2D maps in videogames (snapping to POIs, etc) could be ported over
    1 reply
    tguild
    @tguild
    Wendy: as Strategy Lead at W3C, happy to hear the discussion here and learn of new work you would like to see started at W3C
    Simon Pieters
    @zcorpan
    From the zoom chat:
    Accessibility links:
    https://accessiblemaps.de/?page_id=121&lang=en
    http://docs.opengeospatial.org/per/19-032.html
    http://docs.opengeospatial.org/is/14-005r5/14-005r5.html
    https://www.w3.org/community/lda/
    
https://wheelmap.org/search
    Bocoup review: https://bit.ly/bocoup-testbed16
    tguild
    @tguild
    [adjourned]