A Semantic Web Approach for the Third Provenance Challenge Tetherless World Rensselaer Polytechnic Institute James Michaelis, Li Ding, Rui Huang, Zhenning Shangguan, Deborah L. McGuinness 11/3/2016

Introduction Our approach the Third Provenance Challenge (called TetherlessPC3) is designed to leverage Semantic Web technologies Support for two things useful for answering the provided queries: Declarative inference – SPARQL + OWL Syntax Augmenting provenance data derived from the workflow execution with supplementary information – SPARQL 21/3/2016

TetherlessPC3 Approach 1/3/20163 Provenance Generator Query Front-End Import/Export Component 12 3

Provenance Generator Query Front-End Import/Export Component TetherlessPC3 Approach Trace (OPM) Run TW’s Workflow code Run other team’s Workflow code Trace (OPM’) Trace (OWL) PC3OPM (OWL) Trace (PML) Run Query (Pellet/Jena) Query (SPARQL) Results (Text) Normalization (OPM’-OPM) Query (English) 12 3 Translation (OPM-PC3OPM) Translation (PC3OPM-PML) Translation (English-Sparql)

Provenance Generator Query Front-End Import/Export Component TetherlessPC3 Approach Trace (OPM) Run TW’s Workflow code Run other team’s Workflow code Trace (OPM’) Trace (OWL) PC3OPM (OWL) Trace (PML) Run Query (Pellet/Jena) Query (SPARQL) Results (Text) Normalization (OPM’-OPM) Query (English) 12 3 Translation (OPM-PC3OPM) Translation (PC3OPM-PML) Translation (English-Sparql) Produces provenance traces in Web Ontology Language (OWL) format, using Jena – a Java-based Semantic Web framework These are structured based on the PC3OPM Ontology at PC3OPM is designed to be compatible with the OPM Specification v1.01

Provenance Generator Query Front-End Import/Export Component TetherlessPC3 Approach Trace (OPM) Run TW’s Workflow code Run other team’s Workflow code Trace (OPM’) Trace (OWL) PC3OPM (OWL) Trace (PML) Run Query (Pellet/Jena) Query (SPARQL) Results (Text) Normalization (OPM’-OPM) Query (English) 12 3 Translation (OPM-PC3OPM) Translation (PC3OPM-PML) Translation (English-Sparql) To get the provenance workflow execution service used This is designed to run a modified version of the workflow emulation code provided by Yogesh Simmhan (Microsoft Research) This modified version contains injected code (in section for executing high level workflow) to recording provenance information based on PC3OPM

Three properties of PC3OPM Provide direct mappings to OPM concepts Example: PC3OPM:Artifact to the OPM concept “Artifact” Reification of OPM relations Example: For the relationship (Process1, WasTriggeredBy, Process2) Declare an instance of the class PC3OPM:WasTriggeredBy. Extend the definitions in OPM through new concepts Domain dependent: some terminology specific to Third Provenance Challenge workflow Example: CSVFileEntry (subclass of OPM Artifact) Domain independent: Terminology from the Proof Markup Language (PML) We added a new concept “Function” based on (pmlp:inferenceRule), where an OPM process is an execution of a “Function” 1/3/20167

WHAT IS IT? A Provenance interlingua designed for representing and sharing explanations generated by various intelligent systems. Originally designed to explain activity of theorem proof generators Part of the Inference Web framework (which includes tools for browsing, validating PML) THREE PARTS Justification: Provides structure for describing how a conclusion was derived Provenance: Metadata on information referenced in Justification Trust: Metadata on trust for information referenced in Justification 1/3/20168 Proof Markup Language (PML)

Provenance Generator Query Front-End Import/Export Component TetherlessPC3 Approach Trace (OPM) Run TW’s Workflow code Run other team’s Workflow code Trace (OPM’) Trace (OWL) PC3OPM (OWL) Trace (PML) Run Query (Pellet/Jena) Query (SPARQL) Results (Text) Normalization (OPM’-OPM) Query (English) 12 3 Translation (OPM-PC3OPM) Translation (PC3OPM-PML) Translation (English-Sparql) What we have done 1.Review given English-based queries and form corresponding SPARQL Queries 2.Update PC3OPM ontology to assist with (1) and re-generate the Provenance trace 3.Run queries, and get back results

Provenance Generator Query Front-End Import/Export Component TetherlessPC3 Approach Trace (OPM) Run TW’s Workflow code Run other team’s Workflow code Trace (OPM’) Trace (OWL) PC3OPM (OWL) Trace (PML) Run Query (Pellet/Jena) Query (SPARQL) Results (Text) Normalization (OPM’-OPM) Query (English) 12 3 Translation (OPM-PC3OPM) Translation (PC3OPM-PML) Translation (English-Sparql) Technologies used SPARQL - RDF Query Language Pellet – an Open Source OWL Reasoner

Query Answering Example Provenance Challenge core question 3: “Which operation executions were strictly necessary for the Image table to contain a particular (non-computed) value?” Our interpretation: Find the Process X which generated the Image table Look for the processes X T (directly or indirectly) triggered X Return X and as X T as query results Handling this query: Rather than write a recursive program, we use OWL-based transitive properties in the answer 111/3/2016

Enhancing Provenance Trace To keep our provenance trace simple and concise, we don’t put in transitive properties – since most of the queries don’t need them To insert them when necessary, we create additional RDF data through a SPARQL CONSTRUCT query 1/3/201612

SPARQL SELECT Query PREFIX rdf: PREFIX PC3: PREFIX PC3OPM: SELECT ?fxn1 ?fxn2 FROM FROM FROM WHERE { ?wgb PC3OPM:wgbSource PC3:provVarDbEntryP2ImageMeta_0. ?wgb PC3OPM:wgbTarget ?fxn1. OPTIONAL { ?fxn1 PC3OPM:opWasTriggeredBy ?fxn2. } } 131/3/2016

SPARQL CONSTRUCT Query PREFIX rdf: PREFIX PC3: PREFIX PC3OPM: CONSTRUCT { ?FXN PC3OPM:opWasTriggeredBy ?FXN2 } FROM WHERE { ?USD PC3OPM:usdSource ?FXN. ?USD PC3OPM:usdTarget ?VAR. ?WGB PC3OPM:wgbSource ?VAR. ?WGB PC3OPM:wgbTarget ?FXN2 } 141/3/2016

Provenance Generator Query Front-End Import/Export Component TetherlessPC3 Approach Trace (OPM) Run TW’s Workflow code Run other team’s Workflow code Trace (OPM’) Trace (OWL) PC3OPM (OWL) Trace (PML) Run Query (Pellet/Jena) Query (SPARQL) Results (Text) Normalization (OPM’-OPM) Query (English) 12 3 Translation (OPM-PC3OPM) Translation (PC3OPM-PML) Translation (English-Sparql) Can Import: OPM Graphs Can Export: OPM Graphs PML Proofs The Import/Export protocols for OPM are handled through the OPM API Likewise, the import/export Protocols for PML are handled Through a PML API developed by our lab.

Discussion: Importing From Other Teams Some OPM graphs generated by other teams were not parsable by OPM API, so normalization was needed Our SPAQRL queries (used on our provenance trace) only needed slight modification to handle imported provenance (change URIs of artifacts) Some information loss was observed with many teams dumping provenance traces to OPM Control flow traces were not captured by some teams 1/3/201616

Comparing with other Teams: Answering Core Query 3 Blue Team Our TeamGreen Team

Conclusions Semantic Web technologies useful for handling provenance data Provenance generation – RDF/OWL helps clarify the domain specific concepts/entities in provenance metadata Provenance Query – supported by SPARQL + OWL inference We can capture control flow and data flow Using transitive inference rules, we don’t need to write a program to implement a recursive query Provenance integration – RDF/OWL syntax of OPM (with references to domain terminology) will help avoid information loss issues when exporting OPM data 1/3/201618

References OWL SPARQL Pellet Jena PML API OPM API 1/3/201619

BACK 1/3/201620

PC3 OPM Ontology 1/3/201621