-
Notifications
You must be signed in to change notification settings - Fork 3
Adding new Dataset SubClasses #9
Description
Hi @jbedia,
For the current use of the ontologies in the BSC and SUNSET, I've been thinking that it would be useful to add more specific entities to describe the types of datasets or data subsets our program works with. Specifically, I’m considering adding subclasses of Dataset, such as DecadalHindcast, SubseasonalHindcast, DecadalForecast, and SubseasonalForecast, to provide more specificity regarding the time range the datasets cover. This would also require to modify the definition of other classes. Before adding a definition and submitting a PR, I wanted to consult with you and get your thoughts on this.
Currently, I’ve noticed that the class SeasonalHindcast doesn't clearly specify the time extent it refers to, which should be seasonal. It is mentioned, but I believe it's not entirely clear. The current definition is: "A seasonal hindcast (a.k.a. 'reforecast') is a forecast made for a period in the past using only information available before the beginning of the forecast. The hindcast can be used for verification purposes, helping to build trust (or not) in the forecasting system. Hindcasts typically encompass a relatively long period (i.e. 30 years or more) in order to provide more robust skill assessments." Here, we could specify the approximate time horizon considered to be seasonal, and then add other entities for different time horizons, such as DecadalHindcast or SubseasonalHindcast.
Another option to address this issue could be to leave SeasonalHindcast as simply Hindcast (and the same for the other classes) and include a class like Horizon in the ontology, with an object property such as hasTimeHorizon to specify the horizon extent.
Let me know your thoughts on this matter.
Thanks,
Albert