- From: Adam Shepherd via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Jul 2019 23:56:53 +0000
- To: public-sdwig@w3.org
Hey folks, there's a group of data repositories interested in publishing a temporal extent that expresses a seasonal coverage across multiple years. Rather, they want to express that data was collected in an aggregate of multiple intervals.
The use case for an extension to OWL-Time for this case is driven by search precision and recall. For example if the data were collected in June, July and August across the years 2012 to 2015, a temporal interval extending from 2012 to 2015 would hit as a match for a search looking for data between January 2013 and May 2013 which would be wrong in this case.
In discussions with @dr-shorthair , he recommended a small extension of one class and one property:
```
time:TemporalAggregate rdf:subClassOf time:TemporalEntity .
time:hasMember a owl:ObjectProperty;
rdfs:domain time:TemporalAggregate ;
rdfs:range time:TemporalEntity .
```
With this aggregate class, we can express a collection of Temporal entities that explicitly describes the collection activity.
Thoughts?
--
GitHub Notification of comment by ashepherd
Please view or discuss this issue at https://github.com/w3c/sdw/issues/1139#issuecomment-513414629 using your GitHub account
Received on Friday, 19 July 2019 23:56:55 UTC