search

Maps4HTML / MapML-Specification

Map Markup Language is hypertext for Web maps, like HTML is hypertext for Web pages https://maps4html.org/MapML-Specification/spec/
Other
55 stars 12 forks source link

Merge in the <map> element proposal #78

Closed Malvoz closed 4 years ago

Malvoz commented 4 years ago

The way I've approached this, to merge in the <map> (and CO) element proposal, isn't very sophisticated, in a nutshell I have copied the contents (and some CSS) from the map element proposal into the corresponding section in the MapML specification (and changed link references accordingly).

I understand if you had different plans, or if you don't agree with the new document structure, or think that some sections have to be rewritten, taking into consideration the addition of the map element proposal's content. I'd take no offense if you wish to disregard this PR.

With that said I think this works and (for the most part) makes sense.

Malvoz commented 4 years ago

Additionally, I changed almost all references to W3C HTML5 to their counterparts in the WHATWG Living Standard.

Notably I changed all instances of: "Content model: Empty" to "Content model: Nothing", however I'm not 100% sure if they mean the same thing, I couldn't find the W3C HTML definition of "Empty".

prushforth commented 4 years ago

Robert, thank you for doing this work, it is very much appreciated. I think, as you say, it mostly works, textually speaking.

Notably I changed all instances of: "Content model: Empty" to "Content model: Nothing", however I'm not 100% sure if they mean the same thing, I couldn't find the W3C HTML definition of "Empty".

It must be obsolete, and "Nothing" looks about right to me anyway.