Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define MapML element Categories? #206

Open
Malvoz opened this issue Aug 13, 2021 · 0 comments · May be fixed by #230
Open

Define MapML element Categories? #206

Malvoz opened this issue Aug 13, 2021 · 0 comments · May be fixed by #230
Labels

Comments

@Malvoz
Copy link
Member

Malvoz commented Aug 13, 2021

The body element's Content model includes Features, and many elements' Categories include Feature data, these are not defined but I assume they mean the same thing.

From the elements' Categories, these seem to be considered Feature content:

  • feature
  • featurecaption
  • properties
  • geometry
  • Geometries (point, linestring, etc.)
  • a
  • coordinates
  • image

Should we define Feature content?


The following elements' Categories are set to "N/A", except for the extent element which is set to "Metadata content":

  • extent
  • input
  • datalist
  • label
  • select
  • option

Should these elements be considered a separate element category? e.g. Extent content?


Another issue is how we categorize the following elements as (HTML) Metadata content:

because the HTML definition of Metadata content includes elements we don't want to support (script, template, nocript) so perhaps we should define Metadata content ourselves? (related issue: #84)


And then there's tile as well, allowed child of body (in mapml documents) / layer (in html documents).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant