Human-Aware Sensor Networks Ontology (HASNet-O):
PROV-O/OBOE/VSTO Alignments
Paulo Pinheiro
Lake George, NY
Establish a strategic partnership that becomes the global model for sustained ecosystem understanding and protection
3
The Jefferson Project at Lake George: Science to Inform Solutions
Mod
els Experim
ents
Observations
Smart Lake:Integrative Approach to
Understanding Lake Stressors and Predicting Future Outcomes
Science-based Solutions:Leveraging deep
understanding for solutions with staying power for a healthy
Lake George for future generations
informs
Cyberinfrastructure/Data Platform/Viz Lab
Semantic DataModel
4
We Have Completed Initial Sensor Deployment Locations and Phasing
5
Sensor Deployment Phasing
NB: associated deployment and maintenance resources are are not captured in this table.
6
Software Architecture
RPI management of production quality assets, consuming Deep Thunderdata as a service
Sensor Network Knowledge
• Sensor data provide a mean for humans to understand characteristics of physical entities
• Most knowledge about sensor networks cannot be inferred from sensor data themselves. Moreover, the lack of contextual knowledge about sensor data can render them useless. For example, one can only understand sensor data if one minimally knows the following:– what are the physical entity characteristics being
measured– how these characteristics relate to data values and
measurement units
Selected Ontologies
• Provenance Knowledge– When a sensor network changes, how those changes occur?
How machines can be aware of changes when changes are occurring on themselves?
• Sensor Infrastructure Knowledge– How can machines learn about the infrastructure of a sensor
network, and the impact of the infrastructure on measurements?
• Measurements Knowledge– How can machines learn about the meaning of measurements
in terms of physical entities, their characteristics, and the units used to quantify these measurements?
PROV-O Concepts
OBOE Concepts
VSTO ConceptsPlatform
Deployment
Instrument
Detector
Parameter
Dataset
hasDeployment
hasInstrument
hasDetector
hasMeasuredParameter
hasContainedParameter
isFromInstrument
Alignments – VSTO and OBOEvsto:Platform
vsto:Deployment
vsto:Instrument
vsto:Detector
vsto:Parameter
vsto:Dataset
hasDeployment
hasInstrument
hasDetector
hasMeasuredCharacteristic
hasContainedParameter
isFromInstrument
oboe:Characteristic
Oboe:Observation
hasContainedObservation
Alignments – PROV-O and OBOE
provo:Activity
oboe:Observation
isA
Alignments – VSTO and PROV-O
provo:Entity provo:Agent
vsto:Dataset vsto:Instrument(or InstrumentOperatingMode)
isA
isA
isFromInstrument(or isFromInstrumentOperatingMode)
WasAttributedTo
provo:SoftwareAgent provo:Person
isA isA
vsto:Deployment
Provo:Activity
isA
WasGeneratedBy
Used
HIO Additions
provo:Entity provo:Agent
ConfigurationFile Configurator
isA
isA
Provo:Person
isA
WasAttributedTo
Provo:Software Agent
isA
isA
SensorConfiguration
Skill
Alignments & Additions Summary
provo:Entity provo:Agent
vsto:Dataset vsto:Instrument
isA isA
wasAttributeToprovo:Activity
oboe:Observation
isA
oboe:Characteristicoboe:Measurement
hasMeasurement
wasGeneratedBy
wasAssociatedWith
used
ConfigurationFile
isA
vsto:Deployment
isA
provo:Person
isA
ConfiguratorhasInstrument
isAofCharacteristic
containsObservation
Deployment(the state of being deployed)
Key Sensor Lifecycle(State Diagram)
Not Deployed
Obsertavion(the state of observing)
IdleRedeployment
Deployment: activity moving a sensor from ‘not deployed’ to ‘deployed’ or from ‘deployed’ to ‘deployed’ (redeployment).Observation: activity of being in the ‘Observing’ state
Deployment’s startedAtTime
Deployment’s endedAtTime
