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. However, it is assumed that the average target audience will not read standards (or, if they do, not need more than superficial knowledge), but are still interested in a simpler approach to make tooling interoperable.
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. (More about OSMF Trademark Policy)
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.
At this moment, this section is mostly a list to make respecs show references at the bottom of the page. Some may be removed, and others added.
For more information about this section, see RDF Vocabularies and Namespace IRIs in [[[rdf11-concepts]]].
While this section already uses RFC2119 keywords, the actual suggestions are an early draft and open to testing and discussion.
Is RECOMMENDED to use the following conventions for namespace IRIs.
The examples in this document may omit the prefixes. The list below provides their equivalence.
Please see examples above where XML encoding has <tag k="" v="" /> and RDF/Turtle uses
osmt: prefix.
This section contains examples able to make changes on data or explain past changes from [[[#data-primitives]]].
See https://wiki.openstreetmap.org/wiki/Preset.
name-suggestion-index also releases their data as Presets? Humm. See https://github.com/osmlab/name-suggestion-index/tree/main/dist/presets.
The idea of Quality Assurance is for files not already covered by more specific topics, but still dedicated to checking for potential errors.
See [[[shacl]]].
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.
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).
The inference may be moved out of this document.
This is required for specifications that contain normative material.