NickFitz opened this issue
Jun 14, 2019
· 2 comments
Labels
discussion: capabilitya specific capability or feature: should it be included? what details? should it be a requirement?section: client-side APICapabilities & use cases for client-side APIsstatus: placeholderthere's a matching section heading / some text in the report, but it's far from complete
In the document, it says "Based on the limited data, we are undecided about whether this should be a requirement." which is hard to understand. Even image maps need data sources, and geospatial maps are not different. Just because the big mapping providers don't support mixing data sources doesn't mean it's not a requirement for the Web. By analogy, just imagine if you could only use YouTube for videos in Chrome, etc.
@prushforth "Undecided" is the default conclusion from the template (found towards the end of index.html with id "capability-template"). I'm currently working on fleshing out the use cases, required capabilities, and examples for the Client APIs section, and will be updating the conclusions accordingly. And as you say, this one in particular will be a necessity :-)
discussion: capabilitya specific capability or feature: should it be included? what details? should it be a requirement?section: client-side APICapabilities & use cases for client-side APIsstatus: placeholderthere's a matching section heading / some text in the report, but it's far from complete
2 participants
You can’t perform that action at this time.
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.
This issue is for discussion of the required API capability "Define a data source for a tile layer".
The text was updated successfully, but these errors were encountered: