You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please have a look at the attached spreadsheet, including comments. I have tried to give a sense of "what MapML aims to achieve / how is this different from where we are now", which were questions asked of me during our face to face meeting and re-iterated at the last monthly meeting.
In particular, it was mentioned that:
our concern is to understand how MapML is better than what we have today, so that we may sell it
so I have tried to enumerate how MapML, and of course Maps for HTML seeks to change the status quo, in some cases by highlighting how the objectives embody (some of) the best practices published by the Spatial Data on the Web working group, and the related Data on the Web working group, and other relevant documents.
Hopefully this and the above mentioned use cased / requirements document will give rise to some fruitful discussion, here or on the Maps for HTML repos.
The text was updated successfully, but these errors were encountered:
For those who are interested, although the document is a bit old now, I set out some use cases and requirements for declarative maps on the Web when I first started working on this, they may still be relevant however and they might answer some questions that I noticed from our face to face meeting that may still be outstanding.
prushforth
changed the title
How does MapML advance the state of Web mapping
How does MapML relate to the Spatial Data on the Web Best Practices
Jun 6, 2018
Please have a look at the attached spreadsheet, including comments. I have tried to give a sense of "what MapML aims to achieve / how is this different from where we are now", which were questions asked of me during our face to face meeting and re-iterated at the last monthly meeting.
In particular, it was mentioned that:
so I have tried to enumerate how MapML, and of course Maps for HTML seeks to change the status quo, in some cases by highlighting how the objectives embody (some of) the best practices published by the Spatial Data on the Web working group, and the related Data on the Web working group, and other relevant documents.
Hopefully this and the above mentioned use cased / requirements document will give rise to some fruitful discussion, here or on the Maps for HTML repos.
The text was updated successfully, but these errors were encountered: