-
Notifications
You must be signed in to change notification settings - Fork 0
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
Should spatialCoverageDescription be required? #18
Comments
We used this to describe spatial coverage that couldn't be immediately translated into a URI for a modern administrative division. If the source explicitly said "Israel" or "France" or "Sicily" or anything else resolvable against a modern gazetteer, we put that information here (like "Mesopotamia" or "Northern Etruria") to indicate that we had to do some parsing to get our spatial coverage. If it's more consistent to have this for all entries, all the blanks should just repeat the spatial coverage value. |
Isn't it possible that the source says nothing explicit about spatial coverage but that it can be inferred (e.g. given the topic/focus of the source)? In which case it's possible that there is no |
Yes -- for instance, a book on "Iron Age France" or "the Bronze Age Aegean". This is how we did it in the spreadsheet. So I guess that undermines my statement that you can copy spatialCoverage to spatialCoverageDescription, because the author may never have explicitly said "and I'm talking about France". |
Here's my proposed answer to my provocatively-posed question, combining both of your comments
(2) applies even when (1) can be mapped to a modern administrative division. So, if the source says a time period covers "Spain", the spatial coverage will still have an entry for "Spain" in geonames (or dbpedia, or whatever). This is similar to our approach with start/stop dates: a textual label directly from the source, and derived structured data that estimates the natural language for use in a computer interface. |
Yes, I think this is more or less what we've already been doing, but On Thu, Mar 12, 2015 at 1:00 PM, Patrick Golden notifications@github.com
|
Some entries in the dataset do not currently have a value for
spatialCoverageDescription
, which (if I understand correctly) is the spatial coverage explicitly defined within the source (ie not added by the curator)The text was updated successfully, but these errors were encountered: