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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add <featurecaption> element child of <feature> (#163)
* Get rid of references to MicroXML, update Abstract
* Add link to UCR
* Add text-valued <title> element child of <feature> per Maps4HTML/MapML.js#316.
Change mapml vocabulary to the xhtml namespace.
Fix error in URL introduced in previous commit.
* Rename <feature><title> to <feature><featurecaption>
* Add spec description of <featurecaption>. Remove obsolete sch file.
* Revise feature, featurecaption, properties specifications, links.
* Delete redundant paragraph. Fix incorrect link reference. Remove redundant
text description.
Copy file name to clipboardExpand all lines: schema/README.md
+7-10Lines changed: 7 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,22 @@
1
1
# MapML
2
2
3
-
[Map Markup Language](http://maps4html.github.io/MapML/spec/) is 'MicroXML' vocabulary for maps.
3
+
[Map Markup Language](https://maps4html.org/MapML/spec/) is a proposed HTML vocabulary for maps.
4
4
Although document validity is not a concept that can be strictly enforced on the internet,
5
5
the documents in this directory are an attempt to provide guidance to map authors on what
6
6
constitutes markup that is understood as being within scope of the MapML specification.
7
7
8
-
In principle, a MapML document should be parseable with an HTML-like parser, because
9
-
many of the elements are copied from the HTML vocabulary and are intended to have
10
-
identical processing semantics to their counterpart in HTML.
8
+
In principle, a MapML document should be parseable the HTML parser, because
9
+
many of the elements are extended from the HTML namespace and are intended to have
10
+
identical processing semantics to their counterpart in HTML apart from extensions specified in MapML.
11
11
12
-
In practice, no such MapML parser exists at the time of writing, and it should be good enough to encode
13
-
a MapML document in [MicroXML](https://dvcs.w3.org/hg/microxml/raw-file/tip/spec/microxml.html)syntax so that an XML parser can be used. When such a parser is used,
12
+
In practice, no such MapML/HTML parser exists at the time of writing, and it should be good enough to encode
13
+
a MapML document in HTML5 XML syntax so that Web browsers' XML parsers can be used. When such a parser is used,
14
14
it should be possible to use the schema / schematron documents in this directory to validate certain
15
15
rules of MapML documents. The schemas / schematron files in this directory are intended to
16
-
evolve as the concept of MapML evolves, and perhaps at some point when enough people
17
-
get involved we will be able to 'fork' the nu validator / parser for HTML to provide a similarly
18
-
robust parsing and validation service online.
16
+
evolve as the concept of MapML evolves.
19
17
20
18
## Instructions
21
19
22
-
The files microxml.sch (a single [schematron](http://schematron.com/) validation rule for MicroXML syntax),
23
20
mapml.rnc (a [RelaxNG](http://www.relaxng.org/compact-tutorial-20030326.html) compact syntax schema) and mapml.sch (post-schema validation MapML
24
21
schematron rules) are intended to be applied in that order.
<dd>An optional <ahref="#the-geometry-element"><code>geometry</code></a> element and an optional <ahref="#the-properties-element"><code>properties</code></a> element.</dd>
<dd><code>zoom</code> — the 'native' zoom level of the feature geometry.</dd>
@@ -2157,8 +2159,36 @@ <h5>The <code><<dfn id="the-feature-element">feature</dfn>></code> element
2157
2159
</dl>
2158
2160
2159
2161
<p>
2160
-
A <ahref="#the-feature-element"><code>feature</code></a> element represents a geographic feature. A <ahref="#the-feature-element"><code>feature</code></a> element has an optional <ahref="#the-properties-element"><code>properties</code></a> child element, and a required child
<dt><ahref="https://html.spec.whatwg.org/multipage/dom.html#concept-element-contexts">Contexts in which this element can be used</a>:</dt>
2170
-
<dd>A child of the <ahref="#the-feature-element"><code>feature</code></a> element, containing elements representing the properties of the feature.</dd>
2200
+
<dd>A child of the <ahref="#the-feature-element"><code>feature</code></a> element.</dd>
@@ -2183,9 +2213,6 @@ <h5>The <code><<dfn id="the-properties-element">properties</dfn>></code> e
2183
2213
</dd>
2184
2214
</dl>
2185
2215
2186
-
<p>
2187
-
A <ahref="#the-feature-element"><code>feature</code></a> element can have zero or one <ahref="#the-properties-element"><code>properties</code></a> element, which contains zero or more unknown elements, whose content is text.
<p>A <ahref="#the-geometry-element"><code>geometry</code></a> element has one child element, which can be a <ahref="#the-point-element"><code>point</code></a>,
2215
-
<ahref="#the-linestring-element"><code>linestring</code></a>, <ahref="#the-polygon-element"><code>polygon</code></a>, <ahref="#the-multipoint-element"><code>multipoint</code></a>, <ahref="#the-multilinestring-element"><code>multilinestring</code></a>, <ahref="#the-multipolygon-element"><code>multipolygon</code></a>, or <ahref="#the-geometrycollection-element"><code>geometrycollection</code></a>.</p>
2241
+
<p>A <ahref="#the-geometry-element"><code>geometry</code></a> element has one child element,
2242
+
which can be a <ahref="#the-point-element"><code>point</code></a>,
0 commit comments