TWC-SWQP: A Semantically-Enabled Provenance-Aware Water Quality Portal Ping Wang, Jin Guang Zheng, Linyun Fu, Evan W. Patton, Timothy Lebo, Li Ding, Joanne S. Luciano, Deborah L. McGuinness Tetherless World Constellation RPI

Outline Introduction Data Sources Semantic Web Approach Future Work

Outline Introduction Data Sources Semantic Web Approach Future Work

SWQP Overview

Apply CA Regulation

Retrieval by Characteristic

Detailed polluting facility

Provenance of water data

Provenance of regulations

Measurement Visualization

Outline Introduction Data Sources Semantic Web Approach Future Work

Data Sources Data TypeData Source Water Quality DataEPA Enforcement & Compliance History Online (ECHO) Database USGS National Water Information System (NWIS) Water-Quality Web Services Water Quality Regulation EPA (National Water Regulation) California Code of Regulations Massachusetts Department of Environmental Protection New York Department of Health State of Rhode Island Department of Environmental Management

Outline Introduction Data Sources Semantic Web Approach Future Work

Domain Knowledge Modeling Core ontology design 1 1

Domain Knowledge Modeling Regulation ontology design 2 2 e.g., and others are listed at

Reasoning Domain Data with Regulations Combining the water measurement data, the core and regulation ontologies, a reasoner can decide if a water body is polluted using OWL2 classification. Benefits The core ontology is small: 18 classes, 4 object properties, and 10 data properties. The ontology component can be easily extended to incorporate more regulations Flexible querying and reasoning: the user can select the regulation to apply

Data Integration We used the open source tool csv2rdf4lod 3,4. –Linking ontological terms –Aligning instance references –Converting complex objects C1_VALUEC1_UNITC2_VALUEC2_UNIT 34.07MPN/100ML53.83MPN/100ML 3 Lebo, T., Williams, G.T., Converting governmental datasets into linked data. Proceedings of the 6th International Conference on Semantic Systems, I-SEMANTICS ’10, pp. 38:1–38:3. 4

Provenance Support Provenance Capture Provenance Usage –Data Source Widget –Data Trace Visualization

Water Data Provenance Capture Integration StateProvenanceScript Retrievalsource URL, modification time, inference engine, inference rule, involved actor purl.sh Adjustantecedent data, modification time inference engine, inference rule, involved actor punzip.sh justify.sh Convertantecedent data, invocation time, inference engine, interpretation rule convert*.sh (conversion trigger) PublishURL of published dump file, publish time, involved actor publish.sh

Water Regulation Provenance Capture See complete table at SWQP/compare_five_regulation

Water Regulation Provenance Capture See complete table at SWQP/compare_five_regulation

Data Source Widget InputURL of SPARQL endpoint and (optional) list of its named graphs, and name of the SimpleNamedGraphSourceGraph instance OutputSimpleNamedGraphSourceGraph instance filled with simple descriptions of the source organizations responsible for the data ProcessWalk a big provenance graph for each named graph and abstracts it into one triple: dct:source

Data Source Widget Usage Presentation of the data sources on the interface Source based data retrieval

Provenance Visualization

Future Work Convert data and encode the regulations for the remaining states Linking to Health Domain Utilize data from other sources, e.g. weather and flood forecasts Apply this architecture to other applications, e.g. the Clean Air Status and Trends demo 5 5

Thank you!