1. Enriching trajectory and trajectory pattern semantics with background knowledge Chiara Renso, Roberto Trasarti KDDLab, ISTI, CNR, Italy Stefano Spaccapietra, Christine Parent, Jose Macedo , Zhixian Yan EPFL, Lausanne, Switzerland Miriam Baglioni Pisa University, Italy Monica Wachowicz Technical University of Madrid, Spain
2. Athena: Trajectories and city places Athena the greek goddess of wisdom Hotel University Monuments Show kinds of points of interest and landmarks
3. And more … select kinds of trajectories according to the application domain TouristTrajectory ≡ Trajectory ⊓ ∃hasStop.∃isLocatedIn.TouristPlace ⊓∃hasStop.∃isLocatedIn.AccomodationPlace SELECT trajectory FROM ‘?trajectory rdf:type :TouristTrajectory’; Tourist Trajectories
15. Semantic Trajectory HasTrajectory hasComponents BEStop 0:N list 1:1 2:N list 1:1 IsIn 0:1 0:N Move ƒ(T) To 0:1 1:1 1:1 0:1 Its personalization --> IsIn 0:1 0:N The hooks TravelingOT Trajectory SpatialOT1 Bird name birth year location Does Migration year North/South StopsIn Country 0:N list 1:1 2:N list 0:N From SpatialOT2
Advantages: Oracle is the DMBS chosen in Geopkdd for storing sptaio-temporal data. It also has been chosen for data warehouse. We aim at experimenting the reasoning capabilities. Disadvantages: The tools is not very friendly to use, the OWL reasoning engine is available from version 11g, just distributed on the market. The OWL fragment is a subset of OWL DL called OWLPRIME. Limited expressive power
Advantages: this is the simplest case, exploiting of the ontology reasoning capabilities. The user query the ontology directly. Disadv: size of the ontology may grow, the query are possible only on the ontology: no possibility to query ontology joint with relational data Other scenarios are possible
Advantages: this is the simplest case, exploiting of the ontology reasoning capabilities. The user query the ontology directly. Disadv: size of the ontology may grow, the query are possible only on the ontology: no possibility to query ontology joint with relational data Other scenarios are possible
This step allow to link the ontology concepts with the data in the database. All the data become triples and populate the ontology.
Advantages: this is the simplest case, exploiting of the ontology reasoning capabilities. The user query the ontology directly. Disadv: size of the ontology may grow, the query are possible only on the ontology: no possibility to query ontology joint with relational data Other scenarios are possible
This step allow to link the ontology concepts with the data in the database. All the data become triples and populate the ontology.
This step allow to link the ontology concepts with the data in the database. All the data become triples and populate the ontology.
Advantages: this is the simplest case, exploiting of the ontology reasoning capabilities. The user query the ontology directly. Disadv: size of the ontology may grow, the query are possible only on the ontology: no possibility to query ontology joint with relational data Other scenarios are possible
This step allow to link the ontology concepts with the data in the database. All the data become triples and populate the ontology.
This step allow to link the ontology concepts with the data in the database. All the data become triples and populate the ontology.