Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strawperson model for Place #26

Closed
azaroth42 opened this issue Mar 18, 2016 · 5 comments
Closed

Strawperson model for Place #26

azaroth42 opened this issue Mar 18, 2016 · 5 comments

Comments

@azaroth42
Copy link
Contributor

Most useful subset of geonames? Pull in @mejackreed.

@mejackreed
Copy link

Let me know what you mean and happy to contribute.

@no-reply
Copy link

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
Copy link

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

@azaroth42
Copy link
Contributor Author

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
Copy link
Member

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

Closing, because documentation exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants