Comments (12)
For the sensor domain an use case may be sensor configurations, calibrations or error detection.
from rsp-ql.
@beortner If you could provide a concrete example, it would be really helpful.
from rsp-ql.
We can use the same simple example that we have already in the document.
like this:
:g1 :p _:t1.
:g1 {:axel :enter :RedRoom. :darko :enter :RedRoom }
:g2 :p _:t2.
:g2 {:axel :leave :BlueRoom. }
_:t2 time:after _:t1
:g3 :p _:t3.
:g3 {:tara :enter :RedRoom. :darko :leave :RedRoom }
_:t3 time:after _:t2
:g4 :p _:t4.
:g4 {:axel :enter :RedRoom. }
_:t4 time:after _:t3
Simple queries are like
- Which persons meet in red room?
I think using this example we could keep it simple and understandable.
One important point is that the RSP system should be able to reason over the blank node times.
@greenTara: Or do you want to have some real examples from event processing use cases?
from rsp-ql.
This example is good for the document, because it is similar to the other examples, so it is easy to see what the differences are. One point I think we should change (in all the examples) in order to make things clear - we should use a real timestamp predicate, not just :p .
For the use case wiki page https://www.w3.org/community/rsp/wiki/Use_cases, it would be best to describe more realistic examples.
from rsp-ql.
ok, time stamps like this
time:inXSDDateTime 2016-01-01T10:30:00-5:00 .
I will go over the use cases and try to find some good ones that can have such cases.
from rsp-ql.
We don't at present have a good timestamp predicate for this case:
- time:inXSDDateTime is not a timestamp predicate - the domain is time:Instant, not an RDF graph
- The predicate prov:generatedAtTime is not applicable to this case, because the range is xsd:dateTime, not time:TemporalEntity (or some other "entity" class).
I think we need to create new timestamp predicates, in some RSP namespace, specifically for this case. This is a long-standing issue #10 .
from rsp-ql.
Yes, I see the domain is not an RDF graph.
Do we have any proposals for the timestamp predicate?
from rsp-ql.
Here is a possibility: from https://www.w3.org/2005/Incubator/ssn/ssnx/ssn
http://purl.oclc.org/NET/ssnx/ssn#observationSamplingTime
It is a subproperty of http://www.loa-cnr.it/ontologies/DUL.owl#hsRegion, which doesn't appear to have any restriction of the domain, and the range is http://www.loa-cnr.it/ontologies/DUL.owl#Region, which has subclass http://www.loa-cnr.it/ontologies/DUL.owl#TimeInterval.
Although it doesn't appear in the formal ontology, the SSN specification indicates that the domain of ssn:observationSamplingTime is intended to be ssn:Observation, which is a subclass of DUL:Situation.
I don't know how much as stretch it would be to say that a graph name denotes a DUL:Situation. It is not that far off from the semantics motivation, which is "every graph defines its own context".
Note thate Dolce has its own predicate http://www.loa-cnr.it/ontologies/DUL.owl#isObservableAt, which has arbitrary domain and range of DUL#TimeInterval. We would have more freedom in using this compared to the more constrained ssn predicate.
from rsp-ql.
@kiat Regarding realistic use cases:
lat / long from movement paths of sensors are usually modelled as Linked list, .e.g
https://www.w3.org/community/rsp/wiki/Use_cases#Urban_Transport_Assistance
Sample Query:
- get areas with increased gps activity within a certain timespan ( 1 day / hour)
Furthermore I found another Use Case :
some states / events are also modelled as linked list, e.g.
https://www.w3.org/community/rsp/wiki/Use_cases#Monitoring_of_Multi-Cloud_Applications
from rsp-ql.
... because the range is xsd:dateTime, not time:TemporalEntity.
why is that a requirement for the "linked list" use cases?
from rsp-ql.
Regarding to temporal predicates for stream data, there is on-going work of Spatial on The Web working group(https://www.w3.org/2015/spatial/) that is discussing about OWL-Time and SSN(especially, temporal aspects of sensor observations), there a big list of relevant use cases at https://www.w3.org/2015/spatial/wiki/Working_Use_Cases, for example, I found this UC proposed by a fellow from Bosch quite interesting for temporal predicates, https://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Driving_to_work_in_the_snow_.28SSN.2C_Time.2C_Coverage.29
from rsp-ql.
@lisp - In principle, a predicate with range xsd:dateTime could be used for a linked list, with an IRI or blank node indicating the timestamp, but I think this would be confusing to readers, and it would limit the entailment regimes applicable to that stream, as the stream would be inconsistent in the OWL-DL entailment regime.[1]
The timestamp of a linked list does not have to be a time:TemporalEntity (I have edited the earlier comment). However time:TemporalEntity is the domain and range of time:after, which is used in the example for expressing the "links" of the linked list.
[1] While it is true that in the simple entailment regime, the value space of a datatype is a subclass of rdf:Resource, and so could be represented by an IRI or blank node, that is not permissible in OWL-DL.
from rsp-ql.
Related Issues (20)
- Should identifying an RDF Stream by an IRI be part of the abstract syntax? HOT 1
- RDF Stream Profile: Time Series HOT 23
- Discuss the practical uses of isomorphism
- Querying RDF graphs in windows HOT 5
- Revisit and Harmonize Examples HOT 1
- Functional Requirements HOT 10
- Reorganize material for correct sequential flow HOT 1
- Use "element" to refer to the time-stamped graphs in an RDF straem HOT 1
- Discuss streamed named graph
- Punctuation HOT 2
- Reference existing RSP QL
- Section 4.1: Input
- Windows in S2S operators HOT 2
- Structure of Section 4
- Example 30
- Conformance
- vocabularies and datatypes for time intervals
- Blank node as the name of a streamed graph HOT 4
- rename "timestamped graph" HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rsp-ql.