Open ashepherd opened 5 years ago
Regarding # 4 I was really happy to see the community finally make some traction on this issue. For datasets which represent a range with the end time being 'present' or 'ongoing', we are using the start/..
notation which works quite nicely. Because this is a common scenario for operational datasets such as NASA, I think we should augment the Dataset.md documentation to accommodate that.
@lewismc, would you mind sending over one of your examples for open-ended time range and we can add it to the guidance docs? or i can make one up too!
This issue has been automatically marked as stale because it has not had recent activity.
https://webschemas.org/docs/releases.html#v3.5
Issue #1375: Renamed the various properties and labels from geospatiallyXyz to geoXyz for brevity, e.g. geoIntersects. See https://github.com/schemaorg/schemaorg/commit/000382ab9668d8896ef16fa12e28f60c2355bea4
ArchiveComponent for describing datasets in an archive or as a immutable package? Mentioned in Issue #1758
Issue #383: Added initial vocabulary towards improved support description of project-based funding, for example to use with Dataset citations. New types for Grant, MonetaryGrant, Project, FundingAgency, FundingScheme, and ResearchProject. Developed in collaboration with the Wikidata/Wikibase community.
Issue #1365: In temporalCoverage, added proposed ISO 8601 notation for open-ended date ranges, e.g. 1972-01/..