The YAOM data model follows the basics of the OSM data model: geometries are represented as nodes, ways and relations; and attributes as tags (key=value).
The YAOM data model follows the basics of the OSM data model: geometries are represented as nodes, ways and relations; and attributes as tags (key=value).
While it has important flaws, it has the backing of valuable open-source software projects that can work with OSM data for variety of purposes. If and when the [OSM data model evolves](https://media.jochentopf.com/media/2022-08-15-study-evolution-of-the-osm-data-model.pdf), YAOM shall adapt to the changes to continue benefiting from the ecosystem of compatible software.
While it has important flaws, it has the backing of valuable open-source software projects that can work with OSM data for a variety of purposes. If and when the [OSM data model evolves](https://media.jochentopf.com/media/2022-08-15-study-evolution-of-the-osm-data-model.pdf), YAOM shall adapt to the changes to continue benefiting from the ecosystem of compatible software.
The tagging tries to be compatible with the "de facto" tags and values used in OSM, to benefit the most from current and future compatible software. But instead of an "open tagging" approach, all tags are unambiguously defined in the documentation after being discussed and agreed by the community.
The tagging tries to be compatible with the "de facto" tags and values used in OSM, to benefit the most from current and future compatible software. But instead of an "open tagging" approach, all tags are unambiguously defined in the documentation after being discussed and agreed by the community.
@ -87,7 +87,7 @@ The individual datasets and the planet file are distributed as **PBF** files.
### Numbering
### Numbering
In order to merge all the datasets into one coherent database, unique IDs are required. The merge script takes care of it before merging all datasets.
In order to merge all the datasets into one coherent database, unique IDs are required. The merge script takes care of it before merging all datasets.
All ID's on YAOM can change. Future versions of this specification could make mandatory for features to have a permanent and unique ID that could be linked to.
All ID's on YAOM can change. Future versions of this specification could make it mandatory for features to have a permanent and unique ID that could be linked to.
### Tagging
### Tagging
When choosing a name for a tag, the tag names already in use in OSM for that type of object or attribute shall be always considered first.
When choosing a name for a tag, the tag names already in use in OSM for that type of object or attribute shall be always considered first.
