Strawperson model for Place

hybox / models

Data Modeling repository for HyBox (ontologies, vocabularies, best practices, requirements, etc)

Apache License 2.0

5 stars 3 forks source link

Strawperson model for Place #26

Closed azaroth42 closed 7 years ago

azaroth42 commented 8 years ago

Most useful subset of geonames? Pull in @mejackreed.

mejackreed commented 8 years ago

Let me know what you mean and happy to contribute.

no-reply commented 8 years ago

DPLA MAPv4 uses edm:Place, assuming a base compatibility with geonames:Feature (this makes it a subclass of schema:Place). This compatibility is improved in Geonames Ontology 3.1, which removes cardinality constraints from gn:Feature.

It may be worth looking at the status of ongoing work of the W3C Spatial Data on the Web WG.

A few questions:

Do we have use cases for cartographic points, bounding boxes, polygons, multi-polygons, and/or all of the above?
Do we have use cases for geographic/administrative feature hierarchies?

no-reply commented 8 years ago

Feature hierarchies are welcome in the same way as broader/narrower concepts.

azaroth42 commented 8 years ago

What relationships are there from resources to Places? dcterms:spatial (which seems like it could just be subject, no?) schema:birthPlace / deathPlace ... we should have some sort of place of creation (bf:originPlace ?). There isn't an event model, which would be the obvious place for it.

anarchivist commented 7 years ago

We should add dcterms:spatial for the sake of alignment with DPLA MAPv4.

Closing, because documentation exists.