Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
UPM – Project Meeting Innsbruck - Feb/March 2011 WP1 – D1.1 - TOC Introduction (UPM) 2. Characterization Mechanisms for SingleModality Unknown or Changing Data Sources 3. Characterization Mechanisms for MultiModality Combinations of Unknown or Changing Data Sources 4. Conclusion (UPM) 1. 5/6/2017 Slide 2 of x WP1 – D1.1 – Single Modality 1. Characterization Mechanisms for SingleModality Unknown or Changing Data Sources ◦ 1.1 Sensor Data Streams: Semantic Model Generation (UPM + JSI + EPFL) ◦ Obtain domain ontologies based on metadata about sensors + numeric values obtained from them --- UPM Relate these sensor data sources with other external knowledge sources (e.g., from tags to Cyc/DBPedia) --JSI In all cases, overarching usage of SSN Ontology for sensor sources description (demonstrated with various platforms, like GSN, Pachube, ad-hoc deployments, etc.) --- JSI, EPFL, UPM 1.2 Text Streams: data analysis (JSI) e.g., Twitter 5/6/2017 Slide 3 of x WP1 – D1.1 – Multi Modality 2. Characterization Mechanisms for MultiModality Combinations of Unknown or Changing Data Sources ◦ 2.1 Near Real Time Mapping between Textual Sources and Social Networks (JSI) ◦ 2.2 Ontology-based Data Integration for MultiModality Data Sources (UPM) Integration of sensors with relational databases (e.g., current continuous temperature values with average (normal) values for a region) 5/6/2017 Slide 4 of x Background Previous work at UPM: ◦ Mapping data streams to ontologies ◦ Use ontological schemas to write queries over streaming data sources ◦ Rewriting SPARQL-Stream queries into declarative stream queries (e.g. SNEEql) ◦ Experience in Flood environmental sensor data. Calbimonte, J-P., Corcho O., Gray, A. Enabling Ontology-based Access to Streaming Data Sources. In ISWC 2010. 6 Slide 6 of x Ontology-based Data Access SPARQLStream algebra(S1 S2 Sm) Query translation q SNEEql Sensor Network (S1) Client SPARQLStream (Og) Stream-to-Ontology mappings [triples] Data translation Query Evaluator [tuples] Relational DB (S2) Stream Engine (S3) RDF Store (Sm) Ontology-based Streaming Data Access Service Slide 7 of x EPFL GSN Deployment for SwissEx Distributed environment: GSN Davos, GSN Zurich, etc. ◦ In each site, a number of sensors available ◦ Each one with different schema ◦ However overlapping concepts in the schemas, e.g. temperature ◦ Metadata stored in wiki Federated metadata management: ◦ Jeung H., Sarni, S., Paparrizos, I., Sathe, S., Aberer, K., Dawes, N., Papaioannus, T., Lehning, M.Effective Metadata Management in federated Sensor Networks. in SUTC, 2010 8 Slide 8 of x Initial look at GSN SwissEx data Mirror data available. Web service interface: planetdata.epfl.ch:22001/services/GSNWe bService?wsdl ◦ ListVirtualSensorNames wannengrat_gupf_unten wannengrat_unterhalb_felsen wan2 wan_sen7_2008 wan_sen4_2008 etc Each one has a schema (attributes and types, etc) 9 Slide 9 of x GSN getting data getMultiData ◦ Can request for a specific virtual sensor ◦ Can request data from ALL sensors ◦ Queries configured (can add new queries as well) Sample query: ◦ select pk, air_temperature, relative_humidity, incoming_shortwave_radiation, outgoing_shortwave_radiation, net_shortwave_radiation, wind_speed_50cm, wind_speed_100cm, wind_speed_200cm, wind_speed_max_50cm, wind_speed_max_100cm, wind_speed_max_200cm, wind_direction, precipitation, battery_voltage, timed from wannengrat_tib3 where timed > 1271638922851 and timed <= 1298473500346 and pk < 9223372036854775807 order by timed desc (size: 20 offset: 0) 10 Slide 10 of x GSN getting data The web service parameters allow basic query configuration: ◦ ◦ ◦ ◦ Include all/some fields (fieldNames) Add basic selection conditions Add aggregations Indicate lower/upper time (time-based selection) 11 Slide 11 of x Idea Add Ontology-based distributed query processing: ◦ ◦ ◦ ◦ provide me all temperature sensors that have shown higher than 30 degrees Use ontological schemas fro queries, internally map to the appropriate sensors Query rewritten and dispatched to the appropriate GSN instances Return query results URL query Metadata GSN Davos Wiki Distributed QP GSN Zurich GSN Chur Slide 13 of x WP1 – SSN Ontology Status : Stable ◦ http://www.w3.org/2005/Incubator/ssn/wiki/i mages/3/36/Ssn.xml Usage : 1. Data Discovery and Linking 2. Device Discovery and Selection 3. Provenance and Diagnosis 4. Device Operation Tasking and Programming ◦ http://www.w3.org/2005/Incubator/ssn/wiki/R eport_Motivating_Use_cases#Use_cases 5/6/2017 Slide 16 of x Ontologies overview Upper DOLCE UltraLite SSG4Env infrastructure SWEET SSN Schema Service External FOAF Ordnanc e Survey Flood domain Role Coastal Defences Addition al Regions Slide 17 of x 17 Ontologies Infrastucture ◦ Core sensor network ontology ◦ Service and schema ontologies Domain ◦ Flood use case ontology network Slide 18 of x 18 Legend Module Ontology module Class Class Individual Individual Subclass-of property Type property property Object or datatype property Equivalent to a restriction in an object property Subclass of a restriction in an object property Class = objectProperty only | some Class objectProperty only | some Class Slide 19 of x Overview of the SSN ontology modules System OperatingRestriction Deployment Process Device PlatformSite Data Skeleton MeasuringCapability ConstraintBlock Slide 20 of x Overview of the SSN ontologies deploymentProcesPart only Deployment System OperatingRestriction hasSubsystem only, some hasSurvivalRange only SurvivalRange DeploymentRelatedProcess hasDeployment only Deployment System hasOperatingRange only deployedSystem only deployedOnPlatform only Process Device inDeployment only Input PlatformSite Data hasInput only Device onPlatform only Platform OperatingRange Process Output attachedSystem only hasOutput only, some Skeleton isProducedBy some hasValue some Sensor implements some detects only observes only SensingDevice ObservationValue Sensing sensingMethodUsed only SensorOutput SensorInput isProxyFor only includesEvent some observationResult only Property isPropertyOf some observedProperty only hasProperty only, some observedBy only Observation featureOfInterest only MeasuringCapability FeatureOfInterest ConstraintBlock hasMeasurementCapability only MeasurementCapability forProperty only inCondition only inCondition only Condition Slide 21 of x Sensor and environmental properties Skeleton Property MeasuringCapability Communication hasMeasurementProperty only MeasurementCapability Accuracy DetectionLimit MeasurementProperty Resolution Drift Selectivity ResponseTime Frequency Sensitivity Precision Latency MeasurementRange OperatingRestriction EnergyRestriction hasOperatingProperty only OperatingProperty OperatingRange EnvironmentalOperatingProperty MaintenanceSchedule OperatingPowerRange hasSurvivalProperty only SurvivalRange SurvivalProperty EnvironmentalSurvivalProperty SystemLifetime BatteryLifetime Slide 22 of x Alignment to DOLCE UltraLite DOLCE UltraLite PhysicalObject InformationObject Event DesignedArtifact Process or Situation PlatformSite System Deployment Quality Region Process Process Platform System DeploymentRelated Process Object Method Event Device Deployment Device Skeleton Data Observation Sensor Sensing Property ObservationValue SensorOutput SensingDevice SensorInput FeatureOfInterest Slide 23 of x Ontologies Infrastucture ◦ Core sensor network ontology ◦ Service and schema ontologies Domain ◦ Flood use case ontology network Slide 24 of x 24 Service ontology XSD SWEET xsd:string xsd:anyURI hasSpatialExtent coversRegion hasStyleURL sw:Region hasTemporalExtent sw:Dataset hasEndpointReference sw:SpatialExtent hasDataset sw:TemporalExtent SSN Schema Metadata WebService hasSchema StatefulWebService includesProperty ssn:Property includesFeature ssn:FeatureOfInterest sm:Schema ISO 19119 hasInterface Interface containsOperation Operation hasParameter Parameter hasServiceType ServiceType OGCS.T. SSG4EnvS.T. DataAccessInterface GeoJSONS.T. XMLS.T. … RSSXMLS.T. Slide 25 of x 25 Schema Metadata ontology hasPrimaryKey Extent SSN PrimaryKey ssn:Property hasExtent Relation Schema DatabaseSchema Stream hasTimestampAttribute DataStreamSchema hasAttribute or equivalentToProperty Attribute hasSQLType SQLType TimestampAttribute Slide 26 of x 26 Ontologies Infrastucture ◦ Core sensor network ontology ◦ Service and schema ontologies Domain ◦ Flood use case ontology network Slide 27 of x 27 Coastal Defences ontology SSN ssn:hasProperty locatedInRegion ssn:Property ssn:FeatureOfInterest SWEET sw:Region OS Asset … os:TopographicObject hasOceanRegionProperty AssetProperty … OceanRegionProperty TideHeight OceanRegion WaveHeight Slide 28 of x 28 Features and properties • • • • Physical atmosphere Air temperature Wind speed Wind direction Visibility • • • • • • • • Asset Height Condition Class Width Inspection date Maintainer Location Mastermap Id • Flood plain Water depth • Flood zone Flood zone type • Flood defence policy Strategic defence option • • Ocean region Wave height Tide height • • • • • • • • Vessel Location Name Bearing Type Size Callsign Speed ETA • • • • Road problem Location Road identifier Description Event time Slide 29 of x 29 Additional Regions ontology Coastal Defence Partnership • Coastal Defence Partnership (Modelled area) • Solent • Solent (Modelled area) sw:Region • South East England • South East England (BRANCH) gz:NamedPlace • South East England (CCO) • Southern Coastal England (CCO) • Solent (AIS live) • South East England (Highways Agency) • South West England (Highways Agency) • Slide 30 of x 30 Role ontology SWEET sw:Region operatesWithin appliesTo hasRegionOfResponsibility Duty hasSubOrganization isAssignedTo defines FOAF foaf:Organization hasResponsibility Responsibility foaf:member foaf:Person isFulfilledBy hasPosition occupies Position SSN hasRelatedProperty assumesRole Role undertakesTask ssn:Property ssn:hasProperty Task hasRelatedFeature ssn:FeatureOfInterest Slide 31 of x 31 WP2 – Contribution Plan Tools for transforming geography objects (GML, Oracle Spatial, etc) to RDF ◦ http://mccarthy.dia.fi.upm.es/geometry2rdf/ ◦ Geometry2rdf presentation for more detail 5/6/2017 Slide 34 of x WP4 – PlanetData Vocabulary Document uploaded on wiki WP4 page (Jan 2011) ◦ Feedback and comments? Analysis of existing vocabularies General Purpose Vocabularies Dataset Purpose Vocabularies Stream Purpose Vocabularies ◦ Identify prominent features of analyzed vocabularies ◦ DC ◦ Dcat ◦ Void ◦ Pachube Information Model ◦ Sstream ◦ SSN 5/6/2017 Slide 35 of x WP4 – PlanetData Vocabulary Some Examples - SStream Pollution sensor measuring CO2 emission ◦ Continuous ◦ Valid for 1 hour :COSensor1 a ss:Sensor. :COSensor1Stream a ss:ContinuosStream; ss:expires P1H; contains :COSensor1StreamContent. 5/6/2017 Slide 36 of x WP4 – PlanetData Vocabulary Some Examples - Pachube Not clearly defined Environment properties ◦ Based on its API ◦ Static vs dynamic ◦ Outdoor vs indoor ◦ Live vs frozen : MadridStreet1 a pachube:Environment; pachube:location_lat 40.26; pachube:location_long 3.42; pachube:environment_disposition "Static"; pachube:environment_exposure "Outdoor"; pachube:environment_domain "Physical"; pachube:feed_status "Live"; pachube:hasDatastream :COSensor1. :COSensor1 a pachube:DataStream. 5/6/2017 Slide 37 of x WP4 – PlanetData Vocabulary Some Examples – Sstream+Pachube Sensor on Fred ◦ ◦ ◦ ◦ Heart rate Private data Restriction to hospital Every 5 minutes :Fred a foaf:Person; ss:sensor :HeartSensor. :HeartSensor a ss:Sensor; ss:attachedTo :Fred. dc:description "Heart rate sensor". dc:publisher _:bnode1. _:bnode1 a ss:PeriodicStream; ss:publishedBy :HeartSensor. ss:dataType xs:decimal. ss:contains _:bnode2. dc:accrualPeriodicity _:bnode3. _:bnode2 a ss:StreamContent; rdfs:about <http://fredHospital.org/fred/heartRate.trdf>; pachube:ip_restriction :HOSPITAL_IP. _:bnode3 a ss:Frequency;} ss:duration P0Y0M0DT0H5M. 5/6/2017 Slide 38 of x WP4 – PlanetData vocabulary Some Proposals Dynamic dataset properties Subjective/Objective properties Location properties beyond standard geographic features Access Control ◦ Expiration properties ◦ Continuous/periodic ◦ Feed status (live/frozen) ◦ dcat:dataQuality ◦ ssn:precision ◦ mobile or static location ◦ indoor or outdoor ◦ ◦ ◦ ◦ ◦ Public sensors: pollution sensors Private sensors: heart-rate sensors Allowed/blocked sources Access duration Frequency limit 5/6/2017 Slide 39 of x WP4 – Relevant Data sets Channel Coastal Observatory ◦ Pending final confirmation that it can be used AEMET (Agencia Española de Meteorología) ◦ Currently working on its transformation. Demonstrator soon InfoTerre : In/Out? PSA : In/Out? Sensorbase : In/Out 5/6/2017 Slide 40 of x WP6 - curriculum Motivation Streaming data models Semantic streaming data Query processing ◦ Comparison with Relational DB storage ◦ ◦ ◦ ◦ Unbounded streams Tuples, Windows Timestamps K-constraints Query Languages ◦ Relational operatorsWindow operators, temporal operators ◦ Aggregators ◦ Joins 5/6/2017 ◦ RDF Stream data models ◦ SPARQL extensions for RDF Streams ◦ Reasoning with Streams ◦ Complex event processing ◦ Linked Streaming Data ◦ Continuous queries ◦ Window evaluation ◦ Aggregates evaluation, approximative queries ◦ Static optimization ◦ Query optimization, statistics ◦ Load shedding ◦ Sampling Slide 41 of x