Skip to content

Define MapML element Categories? #206

Open
@Malvoz

Description

@Malvoz

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions