This site has been permanently archived. This is a static copy provided by the University of Southampton.
@TECHREPORT{processDocDM, author = {Steve Munroe and Paul Groth and Sheng Jiang and Simon Miles and Victor Tan and Luc Moreau}, title = {{Data model for Process Documentation}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13047/", dissemination = "public", abstract = {This document describes the data model for \emph{process documentation}; information describing process. It starts by describing the logical organisation of process documentation, before drilling down into the models of the different forms of process documentation. It then describes how individual pieces of process documentation and data items can be identified. Finally, a model of context is provided.} } @TECHREPORT{ScalabilityDM, author = {Steve Munroe and Victor Tan and Paul Groth and Sheng Jiang and Simon Miles and Luc Moreau}, title = {{A WS-Addressing Profile for Distributed Process Documentation}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13057/", dissemination = "public", abstract = {Process documentation can often be distributed across different provenance stores. To enable the discovery of related process documentation, a mechanism is required to link disparate but related process documentation to enable the effective collection of such documentation in order to answer provenance queries. This document represents a WS-addressing profile on distributed process documentation that provides mechanisms to solve this problem.} } @TECHREPORT{StndGloss06, author = {Victor Tan and Paul Groth and Sheng Jiang and Simon Miles and Steve Munroe and Luc Moreau}, title = {{WS Provenance Glossary}}, institution = {Electronics and Computer Science, University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13048/", dissemination = "public", abstract = {This glossary defines a set of terms used in the draft Provenance standard specification documents (\cite{processDocDM}, \cite{docstyleDM}, \cite{ScalabilityDM}, \cite{SecurityDM}, \cite{RecordingDM}, \cite{QueryingDM}, \cite{XPathProvenanceQuery}) for the process documentation data model. The terms described here are intended to be implementation and technology independent, with the intent that they can be analyzed and applied to as many contexts as possible.} } @TECHREPORT{docstyleDM, author = {Victor Tan and Steve Munroe and Paul Groth and Sheng Jiang and Simon Miles and Luc Moreau}, title = {{Basic Transformation Profile for Documentation Style}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13049/", dissemination = "public", abstract = {The data model for process documentation \cite{processDocDM} provides descriptions of different ways in which processes may be documented. The primary method involves recording messages exchanged between interacting services, as well as the state of those services at the time of message exchange. These messages and states may have their contents transformed when recorded due to application dependent security and scalability requirements. The documentation style describes the types of transformations that can be performed. An actor that processes the recorded documentation must understand the transformations performed on it in order to interpret or utilise it appropriately. This document is a profile of several basic documentation style transformations that are likely to be useful in application domains that use process documentation. It is not intended to be exhaustive; other profiles may be provided of alternative documentation style transformations which may be generic or more specific in nature.} } @TECHREPORT{provenanceQuery, author = {Simon Miles and Luc Moreau and Paul Groth and Victor Tan and Steve Munroe and Sheng Jiang}, title = {{Provenance Query Protocol}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13050/", dissemination = "public", abstract = {A related document \cite{processDocDM} defines schemas to be used for documentation about the execution of a process, \emph{process documentation}. It also defines the provenance of a data item as the process that led to that item. A \emph{provenance query} is a query for the provenance of a data item and the results of such a query is documentation of the process that led to the item. In this document, we specify a protocol by which a querying actor and provenance store can communicate in performing a provenance query. This primarily takes the form of an abstract WSDL interface defining messages to be accepted and produced by a provenance store.} } @TECHREPORT{XPathProvenanceQuery, author = {Simon Miles and Luc Moreau and Paul Groth and Victor Tan and Steve Munroe and Sheng Jiang}, title = {{XPath Profile for the Provenance Query Protocol}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13051/", dissemination = "public", abstract = {The provenance query protocol \cite{provenanceQuery} has been defined, and includes the request for, algorithm to execute and result from a provenance query, as executed by a provenance query engine. Many parts of the request document are unspecified, being dependent on the provenance query engine implementation. This document defines an XPath-based profile by which provenance queries can be fully specified against process documentation that is in, or can be mapped to, XML format. } } @TECHREPORT{QueryingDM, author = {Simon Miles and Steve Munroe and Paul Groth and Sheng Jiang and Victor Tan and John Ibbotson and Luc Moreau}, title = {{Process Documentation Query Protocol}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13052/", dissemination = "public", abstract = {A related document \cite{processDocDM} defines schemas to be used for documentation about the execution of a process, \emph{process documentation}, and introduce a \emph{provenance store}, a type of Web Service with the capability for storing and giving access to process documentation. In particular, process documentation has a defined schema, the \emph{p-structure}, which clients of a provenance store can navigate in queries to extract particular pieces of process documentation. In this document, we specify a protocol by which a querying actor and provenance store can communicate in performing a process documentation query. This primarily takes the form of an abstract WSDL interface defining messages to be accepted and produced by a provenance store.} } @TECHREPORT{RecordingDM, author = {Paul Groth and Victor Tan and Steve Munroe and Sheng Jiang and Simon Miles and Luc Moreau}, title = {{Process Documentation Recording Protocol}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13053/", dissemination = "public", abstract = {Related documents \cite{processDocDM,StandardsVision} define schemas to be used for documentation about the execution of a process, \emph{process documentation}, and introduce a \emph{provenance store}, a type of Web Service with the capability for storing and giving access to process documentation. In particular, process documentation has a defined schema, the \emph{p-structure}, which clients use when creating process documentation to be recorded. In this document, we specify an interface, the P-assertion Recording Protocol (PReP) \cite{Groth2004a}, by which a recording actor can communicate with a provenance store in order to record process documentation. This primarily takes the form of an abstract WSDL interface defining messages to be accepted and produced by a provenance store.} } @TECHREPORT{SecurityDM, author = {Victor Tan and Steve Munroe and Paul Groth and Sheng Jiang and Simon Miles and Luc Moreau}, title = {{A Profile for Non-Repudiable Process Documentation}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13054/", dissemination = "public", abstract = { The data model for process documentation \cite{processDocDM} describes p-assertions as individual units for documenting process. These p-assertions can be cryptographically signed by asserting actors in order to establish accountability for their creation. This document extends on the data model for the basic p-assertions (relationship, actor-state and interaction) to include support for signatures.} } @TECHREPORT{StandardsVision, author = {Steve Munroe and Victor Tan and Paul Groth and Sheng Jiang and Simon Miles and Luc Moreau}, title = {{The Provenance Standardisation Vision}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13139/", dissemination = "public", abstract = {This document provides an overview of a model of provenance along with a description of a family of detailed specification documents that support the model. Important aspects of the model are specified within these documents in a detailed and clear manner that provides an unambiguous reference for developers. } } @TECHREPORT{SOAPBinding, author = {Steve Munroe and Victor Tan and Paul Groth and Sheng Jiang and Simon Miles and Luc Moreau}, title = {{A SOAP Binding For Process Documentation}}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13056/", dissemination = "public", abstract = {This document describes a SOAP binding for the process documentation p-header. It presents a specification of the p-header and can be considered an extension of the process documentation data model presented in \cite{processDocDM}.} } @TechReport{Munroe:WP03Method, author = {Steve Munroe and Simon Miles and Victor Tan and Paul Groth and Sheng Jiang and Luc Moreau and and John Ibbotson and Javier V\'{a}zquez-Salceda}, title = {Pr{IM}e: A Methodology for Developing Provenance-Aware Applications}, institution = {University of Southampton}, year = {2006}, url="http://eprints.ecs.soton.ac.uk/13046/", dissemination = "public", OPTkey = {}, OPTtype = {}, OPTnumber = {}, OPTaddress = {}, OPTmonth = {}, OPTnote = {}, OPTannote = {}, abstract="PrIMe is a methodology for adapting applications to make them provenance-aware, that is to enable them to document their execution in order to answer provenance questions. A provenance-aware application can satisfy provenance use cases, where a use case is a description of a scenario in which a user interacts with a system by performing particular functions on that system, and a provenance use case requires documentation of past processes in order to achieve the functions. In this report the PrIMe is described. In order to illustrate the steps necessary to make an application provenance aware, an Organ Transplant Management example application is used." }