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
    … are there other stakeholders that you can identify that should be looped into this conversation?
    … do people agree standardizing maps for the web is worthwhile? I know some disagree
    Fred Esch
    @fredesch
    standardization is good
    Bryan Haberberger
    @thehabes
    Absolutely. There are many stakeholders in cultural heritage and digital humanities. We are a group that represents that stakeholder, and can be found at https://iiif.io/community/
    And specifically https://iiif.io/community/groups/maps/
    tguild
    @tguild
    … what are the next steps? try to form a new Working Group at W3C? perhaps a joint group with OGC or go back to the Community Group...
    Bryan Haberberger
    @thehabes
    Next steps : Integrate as implementers, do some small P.O.C's within the group if possible, and connect with feedback.
    tguild
    @tguild
    … I got making maps a first class citizen on web backward, first we need to get stakeholders, especially those wishing to fund this involved
    Nicolas
    @NicolasRafaelPalomino
    Worthy goal? maps is the future for sure.
    Peter Rushforth
    @prushforth
    I forgot to mention internationalization
    tguild
    @tguild
    Doug: summary not as neccessary given people can watch the videos at their leisure
    … focusing on take aways, future directions better for next stage
    Amelia: we should strive to have a report with conclusions within a month
    … whether it is just a summary or makes recommendations on how to advance
    Peter: text rendering built into browsers should not have to be duplicated or repeated but can be leveraged
    … I agree we should wholeheartedly embrace all the effort that went into browser rendering
    Bryan: we work with museums, librariers etc and I look forward to bringing this to my group and willing to work on proofs of concepts and bring back feedback
    … 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
    tguild
    @tguild
    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