-
-
Save cspanring/825314 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| category : "", // Required Single category from (http://opencivicdata.com/#categories-wg) | |
| properties : {} // Required Common bin for domain specific properties from from (http://opencivicdata.com/#properties-wg) | |
| meta : { // Optional: Simple Dublin Core Metadata Element Set | |
| title : "", | |
| creator : "", | |
| subject : "", | |
| description : "", | |
| publisher : "", | |
| contributor : "", | |
| date : "", | |
| type : "", | |
| format : "", | |
| identifier : "", | |
| source : "", | |
| language : "", | |
| relation : "", | |
| coverage : "", | |
| rights : "" | |
| } | |
| geometry : {} // Optional Geojson location feature (http://geojson.org/geojson-spec.html) | |
| } |
a time range is data, dublincore is for metadata
data should belong in properties, metadata should belong in meta
ok, I'm clearly too GIS biased... http://www.fgdc.gov/metadata/csdgm-new/09.html
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The beauty of the dublin core is that it's a widely accepted simple metadata spec. I think in terms of interoperability it's good to build on top of it. It can be extended and tailored to your application, e.g. just add time-range to the list if that suits your data (the meta properties are the 15 simple elements). I also think optional is important, it shouldn't stop anybody from sharing data.