jun: slide 4: xslt process for
converting data
... this is a complex activity, lots of different types of
files
... need to capture the details about what happened
... common thing they don't know where to put the details of
process
... slide 5- another typical practice of creating linked
data
... where to attach provenance information
... don't currently have guidance on where to attache
provenance information
... slide 6 - complex pipeline similar to a workflow
environemtn
... slide 7 - not straightforward to model all the provenance
in OPM
... slide 8 - need to track the provenance of non-digital
objects
... slide 8 - nice feature of OPM is that it represents not
only data but also the physical world
... slide 9: challenges of the data.gov.uk use case
... slide 10: summarize the gaps
... need a vocabulary, guidance, tool support, extensions
... slide 11 - opmv is simpler than opm
... slide 12 - design rational - straightforward
implementation, lightweight, reuse existing SW
technologies
... there are potential problems with named graphs... but
data.gov.uk uses Named Graphs a lot
... need to be aware of this when using opmv
... only core opm terms are definied in the core vocabulary,
opmv includes 4 extensions to opmv
... presenting examples of usage of opmv, from slide 15 to
18
... discuss the difference between dublic core provenance and
opmv provenance, for some things opmv is more verbose
... slide 17, describing the changes in an organization,
organization ontology uses opmv
... slide 19 - opmv is lightweight but has less semantics than
the opm owl serialization
... opmv is basically a vocabulary
... plans for opmv and decentralized development
... extremely important to have guidance on how to publish
provenance
... currently writing this guidnace
... data.gov.uk team like the vocabulary because it's easy to
understand
... data.gov.uk has not yet used provenance in production,
still need tooling support
... data.gov.uk - don't know where provenance info will be
used