Automatically Adapting Source Code to Document Provenance

Simon Miles

doi:10.1007/978-3-642-17819-1_13

Automatically Adapting Source Code to Document Provenance

Simon Miles

Research output: Chapter in Book/Report/Conference proceeding › Conference paper

4 Citations (Scopus)

170 Downloads (Pure)

Abstract

Being able to ask questions about the provenance of sonic data requires documentation on each influence on that data's existence and content. Much software exists, and is being developed, for which there is no provenance-awareness, i.e. at best, the data it outputs can be connected to its inputs, but with no record of intermediate processing. Further, where sonic record of processing does exist, e.g. as logs, it is not in a form easily connected with that of other processes. We would like to enable compiled software to record useful documentation without requiring prior manual adaptation. In this paper, we present an approach to adapting source code from its original form without manual manipulation, to record information on data provenance during execution.

Original language	English
Title of host publication	Provenance and Annotation of Data and Processes
Subtitle of host publication	Third International Provenance and Annotation Workshop, IPAW 2010, Troy, NY, USA, June 15-16, 2010. Revised Selected Papers
Editors	Deborah L. McGuinness, James R. Michaelis, Luc Moreau
Place of Publication	Berlin
Publisher	Springer Berlin Heidelberg
Pages	102 - 110
Number of pages	9
ISBN (Electronic)	9783642178191
ISBN (Print)	9783642178184
DOIs	https://doi.org/10.1007/978-3-642-17819-1_13
Publication status	Published - 2010
Event	3rd International Provenance and Annotation Workshop - Troy, NY Duration: 15 Jun 2010 → 16 Jun 2010

Publication series

Name	Lecture Notes in Computer Science
Publisher	Springer Berlin Heidelberg
Volume	6378
ISSN (Print)	0302-9743
ISSN (Electronic)	1611-3349

Conference

Conference	3rd International Provenance and Annotation Workshop
City	Troy, NY
Period	15/06/2010 → 16/06/2010

Access to Document

10.1007/978-3-642-17819-1_13

Miles Automatically 2011Final published version, 252 KB

Cite this

Miles, S. (2010). Automatically Adapting Source Code to Document Provenance. In D. L. McGuinness, J. R. Michaelis, & L. Moreau (Eds.), Provenance and Annotation of Data and Processes: Third International Provenance and Annotation Workshop, IPAW 2010, Troy, NY, USA, June 15-16, 2010. Revised Selected Papers (pp. 102 - 110). (Lecture Notes in Computer Science; Vol. 6378). Springer Berlin Heidelberg. https://doi.org/10.1007/978-3-642-17819-1_13

Miles, Simon. / Automatically Adapting Source Code to Document Provenance. Provenance and Annotation of Data and Processes: Third International Provenance and Annotation Workshop, IPAW 2010, Troy, NY, USA, June 15-16, 2010. Revised Selected Papers. editor / Deborah L. McGuinness ; James R. Michaelis ; Luc Moreau. Berlin : Springer Berlin Heidelberg, 2010. pp. 102 - 110 (Lecture Notes in Computer Science).

@inbook{12226148779b46e0a55ab3a856526f0b,

title = "Automatically Adapting Source Code to Document Provenance",

abstract = "Being able to ask questions about the provenance of sonic data requires documentation on each influence on that data's existence and content. Much software exists, and is being developed, for which there is no provenance-awareness, i.e. at best, the data it outputs can be connected to its inputs, but with no record of intermediate processing. Further, where sonic record of processing does exist, e.g. as logs, it is not in a form easily connected with that of other processes. We would like to enable compiled software to record useful documentation without requiring prior manual adaptation. In this paper, we present an approach to adapting source code from its original form without manual manipulation, to record information on data provenance during execution.",

author = "Simon Miles",

year = "2010",

doi = "10.1007/978-3-642-17819-1_13",

language = "English",

isbn = "9783642178184",

series = "Lecture Notes in Computer Science",

publisher = "Springer Berlin Heidelberg",

pages = "102 -- 110",

editor = "McGuinness, {Deborah L. } and Michaelis, {James R. } and Moreau, {Luc }",

booktitle = "Provenance and Annotation of Data and Processes",

note = "3rd International Provenance and Annotation Workshop ; Conference date: 15-06-2010 Through 16-06-2010",

}

Miles, S 2010, Automatically Adapting Source Code to Document Provenance. in DL McGuinness, JR Michaelis & L Moreau (eds), Provenance and Annotation of Data and Processes: Third International Provenance and Annotation Workshop, IPAW 2010, Troy, NY, USA, June 15-16, 2010. Revised Selected Papers. Lecture Notes in Computer Science, vol. 6378, Springer Berlin Heidelberg, Berlin, pp. 102 - 110, 3rd International Provenance and Annotation Workshop, Troy, NY, 15/06/2010. https://doi.org/10.1007/978-3-642-17819-1_13

Automatically Adapting Source Code to Document Provenance. / Miles, Simon.
Provenance and Annotation of Data and Processes: Third International Provenance and Annotation Workshop, IPAW 2010, Troy, NY, USA, June 15-16, 2010. Revised Selected Papers. ed. / Deborah L. McGuinness; James R. Michaelis; Luc Moreau. Berlin: Springer Berlin Heidelberg, 2010. p. 102 - 110 (Lecture Notes in Computer Science; Vol. 6378).

Research output: Chapter in Book/Report/Conference proceeding › Conference paper

TY - CHAP

T1 - Automatically Adapting Source Code to Document Provenance

AU - Miles, Simon

PY - 2010

Y1 - 2010

N2 - Being able to ask questions about the provenance of sonic data requires documentation on each influence on that data's existence and content. Much software exists, and is being developed, for which there is no provenance-awareness, i.e. at best, the data it outputs can be connected to its inputs, but with no record of intermediate processing. Further, where sonic record of processing does exist, e.g. as logs, it is not in a form easily connected with that of other processes. We would like to enable compiled software to record useful documentation without requiring prior manual adaptation. In this paper, we present an approach to adapting source code from its original form without manual manipulation, to record information on data provenance during execution.

AB - Being able to ask questions about the provenance of sonic data requires documentation on each influence on that data's existence and content. Much software exists, and is being developed, for which there is no provenance-awareness, i.e. at best, the data it outputs can be connected to its inputs, but with no record of intermediate processing. Further, where sonic record of processing does exist, e.g. as logs, it is not in a form easily connected with that of other processes. We would like to enable compiled software to record useful documentation without requiring prior manual adaptation. In this paper, we present an approach to adapting source code from its original form without manual manipulation, to record information on data provenance during execution.

UR - http://www.scopus.com/inward/record.url?scp=78651085687&partnerID=8YFLogxK

U2 - 10.1007/978-3-642-17819-1_13

DO - 10.1007/978-3-642-17819-1_13

M3 - Conference paper

SN - 9783642178184

T3 - Lecture Notes in Computer Science

SP - 102

EP - 110

BT - Provenance and Annotation of Data and Processes

A2 - McGuinness, Deborah L.

A2 - Michaelis, James R.

A2 - Moreau, Luc

PB - Springer Berlin Heidelberg

CY - Berlin

T2 - 3rd International Provenance and Annotation Workshop

Y2 - 15 June 2010 through 16 June 2010

ER -

Miles S. Automatically Adapting Source Code to Document Provenance. In McGuinness DL, Michaelis JR, Moreau L, editors, Provenance and Annotation of Data and Processes: Third International Provenance and Annotation Workshop, IPAW 2010, Troy, NY, USA, June 15-16, 2010. Revised Selected Papers. Berlin: Springer Berlin Heidelberg. 2010. p. 102 - 110. (Lecture Notes in Computer Science). doi: 10.1007/978-3-642-17819-1_13

Automatically Adapting Source Code to Document Provenance

Abstract

Publication series

Conference

Access to Document

Other files and links

Fingerprint

Cite this