Identify a time vocabulary

[AlasdairGray]

To support the data model where a graph can be annotated with different types of timestamp, we need to agree on a vocabulary of standard predicates for representing these time relationships.
Alejandro has mentioned that there is work taking place in the W3C Spatial Data on the Web Working Group

[allaves]

Yes, as you can see at the link pointing to the group's charter, section 3, the idea is to standardize the Time Ontology in OWL (http://www.w3.org/TR/owl-time/).

[AlasdairGray]

That ontology does not seem to have the types of property that we are looking for, e.g. time that a sensor made a reading or time that the data arrived at the processing engine.

[beta2k]

what if we create our own micro-vocab for that? as it seems to me we won't
really need many different terms, right?

On Thu, Jun 11, 2015 at 2:06 PM, Alasdair Gray notifications@github.com
wrote:

That ontology does not seem to have the types of property that we are
looking for, e.g. time that a sensor made a reading or time that the data
arrived at the processing engine.

—
Reply to this email directly or view it on GitHub
#10 (comment)
.

[AlasdairGray]

I think we will have to. Hence this issue to keep track of needing to do that.

[amileo]

As far as I remember, some time ago we tried to use the Prov Ontology to represent sources and time of generation and consumption of streaming events by activities (things like generatedAtTime). Wonder whether some concepts could be used from there, along with a subset of concepts from the TIME ontology in OWL, instead of creating our own (even if small) vocabulary…

[beta2k]

ok, yes. why not! i'd agree. I just wasn't aware of the fact that we could
use a combination of ProvO and the TIME Ontology and that this might allow
us to model everything we need. I think we should put this on the Agenda of
our next call.

On Thu, Jun 11, 2015 at 2:30 PM, Alessandra Mileo notifications@github.com
wrote:

As far as I remember, some time ago we tried to use the Prov Ontology to
represent sources and time of generation and consumption of streaming
events by activities (things like generatedAtTime). Wonder whether some
concepts could be used from there, along with a subset of concepts from the
TIME ontology in OWL, instead of creating our own (even if small)
vocabulary…

—
Reply to this email directly or view it on GitHub
#10 (comment)
.

[greenTara]

It is clearly a good idea to avoid having different terms for the same thing, but it would also be nice to allow other predicates if a relationship is desired that is not one of the standard terms.

[agiurca]

Dear all,
Sorry to enter a bit late into the discussion. Following the documents and emails I've seen that a timestamped graph is defined as a triple (g,p,t) where t is a time instant. The set of time instants is assumed (total) ordered and countable (isomorphic with N). As such I wonder which kind of predicates p are useful. I see "before" (g is available before time t), "after" (g is available after time t) and "at" (g is available at time t). Would be possible to have more like this?

[nimonika]

I would be wary of creating a new vocabulary for temporal properties (time points) unless there is a really strong use case which goes beyond, "before", "after", "at" and "until". I see these relationships appearing every now and again, especially in upper level ontologies and those that cover the events domain.

[AlasdairGray]

The vocabulary in question here is not for time points or relationships between time points. It is for relationships between when a graph of triples was created/processed/received and the point in time that event occurred. For example
:g_1, prov:wasGeneratedAt, "2015-06-16T14:27:59+01:00"^^xsd:dateTime.

[agiurca]

prov:wasGeneratedAt looks to be quite similar with ex:at...A set of examples would be useful.similar question by https://github.com/keski at #11 He uses "observed at". But it looks that all "prov:generatedAt", ex:at and "observedAt" are quite similar.

[nimonika]

Ah yes indeed! I misinterpreted it. I remember I was looking for something similar when I wanted to associate my supply chain event graph with a timestamp. What is the interpretation of these operations? If the creating/processing/receiving of a graph is considered an event, one could use the upper level http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasEventDate property or at least specialise from it.