transform our data modeling process from OpenStreetMap to Linked Data.

Tags: #<Tag:0x00007fd5d8b158b8> #<Tag:0x00007fd5d8b157f0>

@almereyda

do you mean by that,
from here: http://wiki.openstreetmap.org/wiki/Nominatim
to here: https://schema.org/PostalAddress / https://schema.org/Place

I did a little research on so to speak standards (in my non technical language).

At the Transition Network Conference, I also had a really interesting conversation with Ade Stuart from the Transition Network IT-Team. He is fascinated by the idea, that TransforMap generates a standard, that then can be applied by a broad variety of communities.
He would go for something in relation to JSON LD and Schema.org

See also https://github.com/openvocab

I think @almereyda is aware of this project. We think there is a lot of overlap between the goals and content of the openvocab project and TransforMap projects.

I think we should stick to schema.org wherever possible or practical.


But OSM does currently not, because:
a) schema.org is often impractical, and to loosely specified.
b) noone really has done a comparision and synchronisation of the different “tagging schemes” if OSM and schema.org yet - which is a pity (and worth a research topic!)!

Two examples, where the current OSM spec is more practical than schema.org:

Addresses:

http://wiki.openstreetmap.org/wiki/Key:addr (this is the better link @josef should refer to)
schema.org does not consider the different methods addresses are used in different parts of the world.

  • e.g. the addr:state is mandatory in the US, but not in most European countries.
  • it is a wrong assumption, that addr:street is used globally. E.g. in some Asian countries, buildings are referred to the block and not to a street. Also in Austria, on very small villages where no street names exist yet, the address Hinterlobming 32 refers to the village name (addr:hamlet) and not to the street.
  • also there are e.g. addr:district, addr:suburb, addr:quarter which are used locally missing in schema.org

Opening Hours:

Another example where I would use the OSM schema over schema.org. There are also graphical editors, see this thread.

@species I think schema.org makes a lot of sense. FYI, not sure if mentioned before but I really like the approach the Popolo Project took with pragmatic reuse of multiple existing standards. See http://www.popoloproject.com/specs/#standard-reuse and http://www.popoloproject.com/specs/organization.html as example model.