Separate the Use Cases and Requirements into a separate document from the MapML spec

[prushforth]

No description provided.

[Malvoz]

Now that we have https://github.com/Maps4HTML/HTML-Map-Element-UseCases-Requirements is this just a matter of removing (or hiding) section 3.1 and 3.2 while perhaps linking to the repo from section 3?

Edit: The UCR report does not cover use cases and requirements that are specific to MapML, so I guess removing those sections entirely is not desirable.

Edit 2: The Use Cases and Requirements text to be moved to a separate document is now hidden can be found here.

[prushforth]

I hope the Web standards community will see enough in MapML that it can become, if not a standard as such, at least the kernel of a place to start discussing and iterating on a solution to the currently evolving Use Cases and Requirements. I would say it represents the best efforts of the geospatial Web community to bind our standards to Web standards / architecture.