IW Meeting 2012-06-28

From Inference Web

Jump to: navigation, search


Meeting Information



  • Tim (regrets)

Meeting Preparation

Around the room

* Add a section for yourself 2 hours before meeting.
* Mark any discussion point that you would like to raise during meeting (with DURING MEETING). 
* Otherwise, assume that others will read the rest before meeting. 
* Also, please be considerate and read others' discussion points before the meeting starts.


  • Per the F2F, PML 3.0 can be a Member Submission
  • from deborah - this would be a good idea. what about the prov <-> pml mapping?
  • PROV-DM is finalizing this week. PROV-O OWL to sync with it Friday.
  • Graham is pouncing on contextualization/bundlization/asInBundle, stays At Risk in LC.
  • Stephan is leading the Call for Implementations. Will collect and report on apps/apis/vocabs that make and consume PROV.


  • Reviewing FUSE indicator data from BAE
  • Developing first draft design/implementation for indicator summarization module.
  • soon to be focusing on the storyboard


  • Extensions to PML/IW for FUSE domain specific classes.
  • Auto-generated FUSE explanation demo.


  • Slides for IPAW talk, done
  • Made progress on provenance ^ datacube lit review, Call for References
  • no progress on PML3 mapping
  • mostly working on datacube stuff. Provenance is going to be an integral dimension (specOf, time, location).





  • meetings at IPAW
  • meetings at Web Science
  • usgs and sem escience
  • Fuse
  • currently writing for escience with ping, linyun, evan
  • anyone writing in the next week or two?

Outstanding Items

  • TODO: Tim to Patrice: water quality portal data. conversion - where does it happen?
    • Go into more detail with Tim
    • come up to speed on converter
    • everything that Tim did on the project.
    • what datasets should Patrice look at first?
    • Doing S2S on water quality data.
  • http://inference-web.org/wiki/Mapping_PROV_to_PML_2.0 TODO: everyone please review above link

Today's discussions

  • Report out from IPAW:
    • Good question on both Tim's and Jim's paper. How do we get some of these annotations?
    • Went well in general
    • Stephan's poster on SPCDIS went well.
    • DataOne consequences (positive)
  • Looks like we will get a USGS collaborative agreement. Looking to do a eScience class project with it.
  • PROV->PML mapping
    • Discussion about the analysis of heavily used PML constructors.
    • Jim brought up that tim was lacking PML instance data
  • Brainstorming future prov / explanation environment focus areas and needs
    • New areas for PML 3:
      • data provenance
      • provenance of data and entities, provenance of information artifacts (data) using FRIR
    • James has been doing work on user profile-based presentation.
    • possibly UI-based provenance
  • Types of provenance by use: (how does this map to who, what, when, where, why)
    • Ownership Provenance, or o-provenance, is the provenance of who owns the data in question, who should get credit for the use of the data, and what licenses the data is available under. somewhat PML-P
    • Data Provenance, or d-provenance, is the provenance of data transformations and preparation. Extraction, Transformation, and Loading processes primarily produce d-provenance, as does normalization and correction processes. PML-P and PML-J
    • Analytical Provenance, or a-provenance, is the provenance of data analysis and computational workflows. This describes the work that is done to produce scientific results and conclusions from the data under study. Statistical and machine learning algorithms, as well as search and visualization tools, produce analytical provenance.


    • Methodological Provenance, or m-provenance, is the provenance of the methods used to produce the data. This relates to instruments, instrument configuration, and how the instruments were used to produce the information. In biomedical research, this is often referred to as an assay or experimental protocol. rules probably within PML-J
    • Entity Provenance, or e-provenance, is the provenance of the entities under study. The timing of the observations, the history of the entity under study (especially important for biomedical research), and the context in which the entity is being observed are all parts of e-provenance. - somewhat PML-P
    • Quality Provenance, or q-provenance, is the provenance needed to ensure data quality. Issues like missing values, adherence to protocol, and measurement bais are addressed through q-provenance. absent in pml except a little
    • consider temporal
    • consider geospatial provenance - are likely two different categories
    • consider trust provenance - potentially separate from quality but related. this would be PML-T



Outstanding Items


  • Patrice to talk to Tim more about everything. -

todo - patrice in particular the conversion and enhancements. patrice will email tim to set it up.

  • Jim to email Tim about PML 3 as member submission (what is the time frame exactly?)
  • James to inform Tim on SPCDIS PML instance data availability and precise pointers
  • question - is there PNNL PML data that can be used
  • question - did tim get the TPTP instance data link from cynthia? cynthia says yes.
  • Cynthia to send Tim link to TPTP PML data. todo


  • Jim to continue PML to PROV mapping (no, really)
  • deborah should ask stephan to give a presentation on the Observations and Measurements work

Next Week's Agenda

  • Jim M. to present data cube work (10 minutes) (what it's doing,
  • James M. to present FUSE special purpose presentations to be included in the storyboard
Facts about IW Meeting 2012-06-28RDF feed
Date28 June 2012  +
Personal tools