-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
690 lines (626 loc) · 24.1 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
<!--
This is a draft. Examples to format this document
- See https://github.com/w3c/respec
- https://respec.org/docs/
- https://github.com/w3c/respec/wiki/ReSpec-Editor's-Guide
- https://github.com/w3c?q=rdf
- https://w3c.github.io/rdf-star/cg-spec/2021-07-01.html
- https://github.com/w3c/rdf-star/blob/main/cg-spec/2021-07-01-src.html
- https://w3c.github.io/json-ld-syntax/
-->
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<!-- <title>Replace me with a real title</title> -->
<title>Semantic Conventions for OpenStreetMap™ 2023</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove" defer></script>
<script class="remove">
// All config options at https://respec.org/docs/
var respecConfig = {
latestVersion: "https://eticaai.github.io/openstreetmap-semantic-conventions-2023/",
specStatus: 'unofficial',
// noRecTrack: true,
authors: [
{
name: "OpenStreetMap contributors",
company: "OpenStreetMap",
companyURL: "https://www.openstreetmap.org/copyright",
},
],
editors: [
{
name: "Emerson Rocha",
company: "EticaAI",
url: "https://orcid.org/0000-0002-9022-8054"
},
{
name: "(Open to new editors!)",
url: "https://github.com/EticaAI/openstreetmap-semantic-conventions-2023#become-an-editor"
}
],
// github: "some-org/mySpec",
github: "eticaai/openstreetmap-semantic-conventions-2023",
shortName: "osm-sc-23",
// xref: "web-platform",
// group: "my-working-group",
// We're not really from W3C, but using this for now
// group: "geosemweb", // Not really,
// group: "geosemweb-external", // Not really,
license: 'cc0',
// additionalCopyrightHolders: "Copyright%20©Internet Engineering Task Force",
doJsonLd: true,
localBiblio: {
OSMSchemav06: {
title: "OpenStreetMap v0.6 XML Schema",
href: "https://wiki.openstreetmap.org/wiki/OSM_XML",
// status: "RSCND",
publisher: "OSM",
},
OSMLevel0: {
title: "Level0 Schema",
href: "https://wiki.openstreetmap.org/wiki/Level0",
// status: "RSCND",
publisher: "OSM",
},
OSMLevel0: {
title: "OsmChange",
href: "https://wiki.openstreetmap.org/wiki/OsmChange",
// status: "RSCND",
publisher: "Unknow",
},
OSMDataModel2022Topf: {
title: "Evolution of the OSM Data Model (2022)",
date: "2022",
href: "https://media.jochentopf.com/media/2022-08-15-study-evolution-of-the-osm-data-model.pdf",
// status: "RSCND",
authors: [
"Jochen Topf"
],
//publisher: "Jochen Topf",
},
WikiAsBase: {
title: "Data extraction from MediaWiki markup",
href: "https://github.com/fititnt/wiki_as_base-py",
authors: [
"Emerson Rocha"
],
},
},
lint: {
"check-punctuation": true,
"local-refs-exist": true,
"no-headingless-sections": true,
"no-http-props": true,
},
};
</script>
<script>
function escapeExample(utils, content, url) {
return content.replace(/</g, "<").replace(/>/g, ">");
}
function removeExamplePREFIX(utils, content, url) {
return content.replace(/PREFIX (.*)/g, "");
}
function escapeExampleCommentsLineStart(utils, content, url) {
return content.replace(/^# (.*)/g, "");
}
</script>
<style>
.todo-issue {
border-color: #e05252;
background: #fbe9e9;
color: black;
overflow: auto;
}
</style>
</head>
<body>
<h1 id="title">Semantic Conventions for OpenStreetMap™ 2023</h1>
<h2 id="subtitle">Mappings from common file formats to RDF, and other considerations</h2>
<section id="abstract">
<h2>Abstract</h2>
<p>
This document contains reference examples of types files with their schemas known to be used for exchanging data with developers of tools around the ecosystem of OpenStreetMap with potential conventions to their counterpart with one or more encodings of Semantic Web standards.
<strong>However, it is assumed that the average target audience will not read standards</strong> (or, if they do, not need more than superficial knowledge), <strong>but are still interested in a simpler approach to make tooling interoperable.</strong>
</p>
<!--
<p>
Instead of explaining each kind of format, the intent here is to be a very superficial, example-oriented, quick
reference between each format. Readers are recommended to look for the [[[#references]]].
</p>
-->
<!-- <p>This is required.</p> -->
<!-- <p class="ednote" title="Document is an early draft">
Use <a href="https://respec.org/docs/">https://respec.org/docs/</a> as reference for markup.
</p> -->
</section>
</section>
<section id="sotd">
<p>
OpenStreetMap™ is a trademark of the OpenStreetMap Foundation,
and is used with their permission.
This project is not endorsed by or affiliated with the OpenStreetMap Foundation.
<em>(More about <a href="https://wiki.osmfoundation.org/wiki/Trademark_Policy">OSMF Trademark Policy</a>)</em>
</p>
</section>
<section class="informative">
<h2>Introduction</h2>
<!--
<p class="ednote" title="Missing introduction">
Is necessary to add introduction which already is not a copy from the abstract.
</p>
-->
<p>
The OpenStreetMap ecosystem has several ways to exchange data,
including machine-readable documentation and validation.
Instead of explaining each kind of format, the intent here is to be a very superficial, example-oriented, quick reference between each format.
Readers interested in more details are recommended to look for the [[[#references]]].
However, the idea here is to be a quick start for developers who just want to get things working,
while also having a general overview good enough to consistently encode so many file formats that without such superficiality,
never would be possible.
</p>
</section>
<section class="informative">
<h2>Terminology</h2>
<!--
<dfn data-abbr="PoS">point of sale</dfn>
<dl data-sort>
<dt>Bananas</dt>
<dd>Are the best!</dd>
<dt>Zebra</dt>
<dd>Are quite stripy.</dd>
<dt>Apples</dt>
<dd>🍎s are delicious.</dd>
<dd>🍏s are great in a pie!.</dd>
</dl>
-->
<section class="conformance">
<h3>Related specifications</h3>
<p class="ednote" title="drafted initial list">
At this moment, this section is mostly a list to make <a href="https://respec.org/docs/">respecs</a> show
references at the bottom of the page.
Some may be removed, and others added.
</p>
<ul>
<li>[[[OSMSchemav06]]]</li>
<li>[[[OSMLevel0]]]</li>
<li>[[[OSMDataModel2022Topf]]]</li>
<li>[[[WikiAsBase]]]</li>
<li>[[[rdf11-concepts]]]</li>
<li>[[[Turtle]]]</li>
<li>[[[sparql11-query]]]</li>
<li>[[[owl-time]]]</li>
<li>[[[json-ld11]]]</li>
<li>[[[owl2-syntax]]]</li>
<li>[[[shacl]]]</li>
</ul>
<!--
See also https://www.w3.org/TR/?tag=data
-->
</section>
</section>
<section class="conformance">
<h2>Namespaces</h2>
<!--
<p>
(TODO link to <a href="https://www.w3.org/TR/rdf-syntax-grammar/#section-Namespace">https://www.w3.org/TR/rdf-syntax-grammar/#section-Namespace</a>)
</p>
-->
<p>
For more information about this section, see <em>RDF Vocabularies and Namespace IRIs</em> in [[[rdf11-concepts]]].
</p>
<p class="ednote" title="The namespaces for OpenStreetMap are a draft">
While this section already uses RFC2119 keywords, the actual suggestions are an early draft and open to testing
and discussion.
</p>
<section class="conformance">
<h3>Namespaces dedicated to OpenStreetMap use</h3>
<p>
Is RECOMMENDED to use the following conventions for namespace IRIs.
</p>
<pre class="example" data-content-type="text/turtle" data-oninclude="escapeExample"
data-include="prefixes-min.ttl">
</pre>
</section>
<section class="informative">
<h3>Common namespaces</h3>
<p>The examples in this document may omit the prefixes. The list below provides their equivalence.</p>
<pre class="example" data-content-type="text/turtle" data-oninclude="escapeExample" data-include="prefixes.ttl">
</pre>
</section>
</section>
<section>
<h2>Data Primitives</h2>
<ul>
<li>See <a
href="https://wiki.openstreetmap.org/wiki/Talk:Elements">https://wiki.openstreetmap.org/wiki/Talk:Elements</a>
</li>
</ul>
<section>
<h3>Node</h3>
<pre class="example" title="A Node in OpenStreetMap v0.6 XML (canonical) reference" data-content-type="xml"
data-oninclude="escapeExample" data-include="reference/node-1.xml">
</pre>
<pre class="example" title="The reference Node in Level0" data-content-type="txt" data-oninclude=""
data-include="reference/node-1.level0.txt">
</pre>
<pre class="example" title="The reference Node in RDF/Turtle" data-content-type="text/turtle"
data-oninclude="escapeExample removeExamplePREFIX" data-include="proposal/node-1.ttl">
</pre>
</section>
<section>
<h3>Way</h3>
<pre class="example" title="A Way in OpenStreetMap v0.6 XML (canonical) reference" data-content-type="xml"
data-oninclude="escapeExample" data-include="reference/way-100.xml">
</pre>
<pre class="example" title="The reference Way in Level0" data-content-type="txt" data-oninclude=""
data-include="reference/way-100.level0.txt">
</pre>
<pre class="example" title="The reference Way in RDF/Turtle" data-content-type="text/turtle"
data-oninclude="escapeExample removeExamplePREFIX" data-include="proposal/way-100.ttl">
</pre>
</section>
<section>
<h3>Relation</h3>
<pre class="example" title="A Relation in OpenStreetMap v0.6 XML (canonical) reference" data-content-type="xml"
data-oninclude="escapeExample" data-include="reference/relation-10000.xml">
</pre>
<pre class="example" title="The reference Relation in Level0" data-content-type="txt" data-oninclude=""
data-include="reference/relation-10000.level0.txt">
</pre>
<pre class="example" title="The reference Relation in RDF/Turtle" data-content-type="text/turtle"
data-oninclude="escapeExample removeExamplePREFIX" data-include="proposal/relation-10000.ttl"></pre>
</section>
<section>
<h3>Tag</h3>
<p>
Please see examples above where XML encoding has <code><tag k="" v="" /></code> and RDF/Turtle uses
<code>osmt:</code> prefix.
</p>
</section>
</section>
<section>
<h2>Data change</h2>
<p>
This section contains examples able to make changes on data or explain past changes from [[[#data-primitives]]].
</p>
<section>
<h3>Changeset</h3>
<ul>
<li>See <a
href="https://wiki.openstreetmap.org/wiki/Changeset">https://wiki.openstreetmap.org/wiki/Changeset</a>
</li>
</ul>
<pre class="example" title="A Changeset in OpenStreetMap v0.6 XML (canonical) reference" data-content-type="xml"
data-oninclude="escapeExample" data-include="reference/changeset-1.xml">
</pre>
<div class="issue" data-number="2">
How to represent changesets in RDF/Turtle?
<ul>
<li><a href="https://www.w3.org/TR/sparql11-update/">https://www.w3.org/TR/sparql11-update/</a></li>
<li><a href="https://www.w3.org/2009/12/rdf-ws/papers/ws07">https://www.w3.org/2009/12/rdf-ws/papers/ws07</a>
</li>
<li><a href="https://www.w3.org/DesignIssues/Diff.html">https://www.w3.org/DesignIssues/Diff.html</a></li>
</ul>
</div>
</section>
<section>
<h3>History</h3>
</section>
</section>
<section>
<h2>Tag metadata</h2>
<section>
<h3>Wiki Infobox Tag</h3>
<div class="issue" data-number="1">
How to encode Wiki infoboxes for tags in RDF/Turtle?
</div>
<pre class="example" title="Tag:highway=track (reference)" data-content-type="txt" data-oninclude="escapeExample"
data-include="reference/highway=track.wiki.txt"></pre>
<!-- <pre class="example" title="Tag:highway=track in RDF/Turtle" data-content-type="text/turtle"
data-oninclude="escapeExample removeExamplePREFIX" data-include="proposal/highway=track.wiki.ttl"></pre> -->
<pre class="example" title="Tag:highway=track in RDF/Turtle" data-content-type="text/turtle"
data-oninclude="escapeExample" data-include="proposal/highway=track.wiki.ttl"></pre>
<pre class="example" title="Tag:highway=track in JSON-LD/Wiki-as-base" data-content-type="text/turtle"
data-oninclude="escapeExample" data-include="proposal/wiki-as-base/highway=track.wiki.jsonld"></pre>
</section>
</section>
<section>
<h2>Presets</h2>
<p>See <a href="https://wiki.openstreetmap.org/wiki/Preset">https://wiki.openstreetmap.org/wiki/Preset</a>.</p>
<p class="ednote" title="name-suggestion-index presets">
name-suggestion-index also releases their data as Presets? Humm. See
<a
href="https://github.com/osmlab/name-suggestion-index/tree/main/dist/presets">https://github.com/osmlab/name-suggestion-index/tree/main/dist/presets</a>.
</p>
<!--
- About unifying presets
- https://github.com/osmlab/editor-presets/issues/1
- https://github.com/osmlab/osm-planning/issues/27#issuecomment-1018930029
- https://github.com/openstreetmap/id-tagging-schema/issues/646
-->
<section>
<h3>iD style presets</h3>
<ul>
<li>
<a href="https://wiki.openstreetmap.org/wiki/Preset#iD">
https://wiki.openstreetmap.org/wiki/Preset#iD
</a>
</li>
<li>
<a href="https://github.com/openstreetmap/id-tagging-schema/">
https://github.com/openstreetmap/id-tagging-schema/
</a>
</li>
<li>
<a
href="https://raw.githubusercontent.com/osmlab/name-suggestion-index/main/dist/presets/nsi-id-presets.json">
https://raw.githubusercontent.com/osmlab/name-suggestion-index/main/dist/presets/nsi-id-presets.json
</a>
</li>
</ul>
</section>
<section>
<h3>JOSM style presets</h3>
<div class="issue" data-number="3">
Opinions are welcome.<br>
What about https://wiki.openstreetmap.org/wiki/Name_Suggestion_Index ?
</div>
<ul>
<li>
<a href="https://josm.openstreetmap.de/wiki/TaggingPresets">
https://josm.openstreetmap.de/wiki/TaggingPresets
</a>
</li>
<li>
<a href="https://wiki.openstreetmap.org/wiki/Customising_JOSM_Presets">
https://wiki.openstreetmap.org/wiki/Customising_JOSM_Presets
</a>
</li>
<li>
<a href="http://josm.openstreetmap.de/tagging-preset-1.0">
http://josm.openstreetmap.de/tagging-preset-1.0
</a>
</li>
</ul>
<pre class="example" title="A JSOM Preset (canonical) reference, preset-josm-hello" data-content-type="xml"
data-oninclude="escapeExample" data-include="reference/preset/preset-josm-hello.xml">
</pre>
<pre class="example" title="A JSOM Preset (canonical) reference, preset-josm-gas" data-content-type="xml"
data-oninclude="escapeExample" data-include="reference/preset/preset-josm-gas.xml">
</pre>
<pre class="example" title="A NSI+JSOM Preset (canonical) reference, preset-nsi-josm" data-content-type="xml"
data-oninclude="escapeExample" data-include="reference/preset/preset-nsi-josm.xml">
</pre>
<pre class="example" title="A NSI+ID Preset (canonical) reference, preset-nsi-id" data-content-type="json"
data-oninclude="escapeExample" data-include="reference/preset/preset-nsi-id.json">
</pre>
</section>
<section>
<h3>OsmAnd style presets</h3>
<ul>
<li>
<a href="https://wiki.openstreetmap.org/wiki/Preset#OsmAnd">
https://wiki.openstreetmap.org/wiki/Preset#OsmAnd
</a>
</li>
<li>
<a href="https://github.com/osmandapp/OsmAnd-resources/blob/master/poi/poi_types.xml">
https://github.com/osmandapp/OsmAnd-resources/blob/master/poi/poi_types.xml
</a>
</li>
</ul>
</section>
<!--
Trivia: Merkaartor have XSD https://github.com/openstreetmap/merkaartor/tree/master/Templates/
-->
</section>
<section>
<h2>name-suggestion-index</h2>
<!--
<div class="issue" data-number="1">
How to encode Wiki infoboxes for tags in RDF/Turtle?
</div>
-->
<div class="issue" data-number="4">
Opinions are welcome.
</div>
<ul>
<li>
<a href="https://nsi.guide/">
https://nsi.guide/
</a>
</li>
<li>
<a href="https://github.com/osmlab/name-suggestion-index">
https://github.com/osmlab/name-suggestion-index
</a>
</li>
<li>
<a href="https://github.com/osmlab/name-suggestion-index/tree/main/schema">
https://github.com/osmlab/name-suggestion-index/tree/main/schema
</a>
</li>
<li>
<a href="https://github.com/osmlab/name-suggestion-index/tree/main/dist">
https://github.com/osmlab/name-suggestion-index/tree/main/dist
</a>
</li>
</ul>
<section>
<h3>nsi.json</h3>
<pre class="example" title="nsi.json (reference)" data-content-type="json" data-oninclude=""
data-include="reference/name-suggestion-index/nsi.json">
</pre>
</section>
<section>
<h3>replacements.json</h3>
<pre class="example" title="replacements.json (reference)" data-content-type="json" data-oninclude=""
data-include="reference/name-suggestion-index/replacements.json">
</pre>
<pre class="example" title="replacements.rq SPARQL" data-content-type="application/sparql-query" data-oninclude=""
data-include="proposal/name-suggestion-index/replacements.rq">
</pre>
</section>
<section>
<h3>warnings.json</h3>
<pre class="example" title="warnings.json (reference)" data-content-type="json" data-oninclude=""
data-include="reference/name-suggestion-index/warnings.json">
</pre>
<!--
Here good candidate for SHACL
-->
</section>
</section>
<!--
<section>
<h2>@TODO better group here</h2>
<section>
<h3>Preset</h3>
<p>See <a href="https://wiki.openstreetmap.org/wiki/Preset">https://wiki.openstreetmap.org/wiki/Preset</a>.</p>
<p>See <a
href="https://wiki.openstreetmap.org/wiki/Customising_JOSM_Presets">https://wiki.openstreetmap.org/wiki/Customising_JOSM_Presets</a>.
</p>
</section>
<section>
<h3>Role</h3>
<p>See <a
href="https://wiki.openstreetmap.org/wiki/Relation#Roles">https://wiki.openstreetmap.org/wiki/Relation#Roles</a>.
</p>
</section>
<section>
<h3>History</h3>
</section>
</section>
-->
<section>
<h2>Semantic elements</h2>
<ul>
<li>See <a
href="https://wiki.openstreetmap.org/wiki/Semantic_elements">https://wiki.openstreetmap.org/wiki/Semantic_elements</a>
</li>
</ul>
<section>
<h3>Point</h3>
</section>
<section>
<h3>Linear features</h3>
</section>
<section>
<h3>Areas</h3>
</section>
<section>
<h3>Relational</h3>
</section>
<section>
<h2>Wiki-as-base</h2>
<ul>
<li>See <a
href="https://wiki.openstreetmap.org/wiki/Semantic_elements">https://wiki.openstreetmap.org/wiki/Semantic_elements</a>
</li>
</ul>
<section>
<h3>Point</h3>
</section>
<section>
<h3>Linear features</h3>
</section>
<section>
<h3>Areas</h3>
</section>
<section>
<h3>Relational</h3>
</section>
</section>
<section>
<h2>Quality Assurance</h2>
<p class="ednote" title="Quality Assurance is a draft">
The idea of Quality Assurance is for files not already covered by more specific topics, but still dedicated to
checking for potential errors.
</p>
<!--
https://josm.openstreetmap.de/browser/josm/trunk/src/org/openstreetmap/josm/data/validation/tests
https://josm.openstreetmap.de/browser/josm/trunk/resources/data/validator
https://wiki.openstreetmap.org/wiki/JOSM/Validator
https://github.com/tyrasd/overpass-turbo/tree/master/js/jsmapcss
https://wiki.openstreetmap.org/wiki/Cascadenik
https://wiki.openstreetmap.org/wiki/CartoCSS
https://github.com/OSMBrasil/validador-josm/blob/master/Rules_Brazilian-Specific.validator.mapcss
SHACL
- https://shacl.org/playground/
- https://shacl-playground.zazuko.com/
-->
<section>
<h3>JSOM data validator (mapcss)</h3>
<pre class="example" title="highway.mapcss (reference)" data-content-type="css" data-oninclude=""
data-include="reference/qa/highway.mapcss"></pre>
<pre class="example" title="proposal/qa/highway.shacl.ttl (SHACL)" data-content-type="text/turtle" data-oninclude="escapeExample removeExamplePREFIX"
data-include="proposal/shacl/highway.shacl.ttl"></pre>
</section>
</section>
<section>
<h2>SHACL</h2>
<p>
See [[[shacl]]].
</p>
<section>
<h3>Data Primitives SHACL</h3>
<p class="ednote" title="About use of SHACL to validate malformed data">
This section documents how to use SHACL to validate [[[#data-primitives]]] if encoded like the [[[#data-primitives-ontology]]].
It's simple, allows readers to have an overview on how to use SHACL to check for errors with rules most people would already agree with.
<br>
But this use might be not necessary if the input data is known to be working (e.g. either database or validations of file formats would detect syntax errors).
</p>
<pre class="example" title="poc/osm-wiki-onto2023.shacl.ttl" data-content-type="text/turtle"
data-oninclude="escapeExample removeExamplePREFIX" data-include="poc/osm-wiki-onto2023.shacl.ttl"></pre>
</section>
</section>
<section>
<h2>Inference</h2>
<p class="ednote" title="">
The inference may be moved out of this document.
</p>
<section>
<h3>Wiki explanation about maxspeed</h3>
<pre class="example" title="proposal/text/maxspeed-simple.md (reference)" data-content-type="text" data-oninclude=""
data-include="proposal/text/maxspeed-simple.md"></pre>
<!-- <pre class="example" title="Tag:highway=track in RDF/Turtle" data-content-type="text/turtle"
data-oninclude="escapeExample" data-include="proposal/highway=track.wiki.ttl"></pre> -->
</section>
</section>
<section class="appendix informative">
<h2>Data Primitives Ontology</h2>
<pre class="example" title="poc/osm-wiki-onto2023.owl.ttl" data-content-type="text/turtle"
data-oninclude="escapeExample removeExamplePREFIX" data-include="poc/osm-wiki-onto2023.owl.ttl"></pre>
</section>
<!--
<section data-dfn-for="Foo">
<h2>Start your spec!</h2>
<pre class="idl">
[Exposed=Window]
interface Foo {
attribute DOMString bar;
undefined doTheFoo();
};
</pre>
<p>The <dfn>Foo</dfn> interface represents a {{Foo}}.</p>
<p>
The <dfn>doTheFoo()</dfn> method does the foo. Call it by running
{{Foo/doTheFoo()}}.
</p>
<ol class="algorithm">
<li>A |variable:DOMString| can be declared like this.</li>
</ol>
</section>
-->
<section id="conformance">
<p>
This is required for specifications that contain normative material.
</p>
</section>
<section id="index" class="appendix">
<!-- All the terms will magically appear here -->
</section>
</body>
</html>