Language-integrated provenance in Links

James Cheney; Stefan Fehrenbach

Language-integrated provenance in Links

James Cheney, Stefan Fehrenbach

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

Abstract / Description of output

Today’s programming languages provide no support for data provenance. In a world that increasingly relies on data, we need provenance to judge the reliability of data and therefore should aim for making it easily accessible to programmers. We report our work in progress on an extension to the Links programming language that builds on its support for language-integrated query to support where-provenance queries through query rewriting and a type system extension that distinguishes provenance metadata from other data. Our approach aims to work solely within the language implementation and thus require no changes to the database system. The type system together with automatic propagation of provenance metadata will prevent programmers from accidentally changing provenance, losing it, or misattributing it to other data.

Original language	English
Title of host publication	Workshop on Theory and Practice of Provenance (TaPP 2015)
Publisher	USENIX Association
Number of pages	6
Publication status	Published - 10 Jul 2015
Event	Workshop on Theory and Practice of Provenance (TaPP 2015) - Edinburgh , United Kingdom Duration: 8 Jul 2015 → 9 Jul 2015

Workshop

Workshop	Workshop on Theory and Practice of Provenance (TaPP 2015)
Country/Territory	United Kingdom
City	Edinburgh
Period	8/07/15 → 9/07/15

Access to Document

documentAccepted author manuscript, 239 KB

https://www.usenix.org/system/files/tapp15-fehrenbach.pdf

DIACHRON - Managing the Evolution and Preservation of the Data Webb (RTD)
Viglas, S., Buneman, P. & Cheney, J.
EU government bodies
1/04/13 → 31/03/16
Project: Research

Cite this

@inproceedings{7b7b4da928804e9893dcba839010191d,

title = "Language-integrated provenance in Links",

abstract = "Today{\textquoteright}s programming languages provide no support for data provenance. In a world that increasingly relies on data, we need provenance to judge the reliability of data and therefore should aim for making it easily accessible to programmers. We report our work in progress on an extension to the Links programming language that builds on its support for language-integrated query to support where-provenance queries through query rewriting and a type system extension that distinguishes provenance metadata from other data. Our approach aims to work solely within the language implementation and thus require no changes to the database system. The type system together with automatic propagation of provenance metadata will prevent programmers from accidentally changing provenance, losing it, or misattributing it to other data.",

author = "James Cheney and Stefan Fehrenbach",

year = "2015",

month = jul,

day = "10",

language = "English",

booktitle = "Workshop on Theory and Practice of Provenance (TaPP 2015)",

publisher = "USENIX Association",

note = "Workshop on Theory and Practice of Provenance (TaPP 2015) ; Conference date: 08-07-2015 Through 09-07-2015",

}

TY - GEN

T1 - Language-integrated provenance in Links

AU - Cheney, James

AU - Fehrenbach, Stefan

PY - 2015/7/10

Y1 - 2015/7/10

N2 - Today’s programming languages provide no support for data provenance. In a world that increasingly relies on data, we need provenance to judge the reliability of data and therefore should aim for making it easily accessible to programmers. We report our work in progress on an extension to the Links programming language that builds on its support for language-integrated query to support where-provenance queries through query rewriting and a type system extension that distinguishes provenance metadata from other data. Our approach aims to work solely within the language implementation and thus require no changes to the database system. The type system together with automatic propagation of provenance metadata will prevent programmers from accidentally changing provenance, losing it, or misattributing it to other data.

AB - Today’s programming languages provide no support for data provenance. In a world that increasingly relies on data, we need provenance to judge the reliability of data and therefore should aim for making it easily accessible to programmers. We report our work in progress on an extension to the Links programming language that builds on its support for language-integrated query to support where-provenance queries through query rewriting and a type system extension that distinguishes provenance metadata from other data. Our approach aims to work solely within the language implementation and thus require no changes to the database system. The type system together with automatic propagation of provenance metadata will prevent programmers from accidentally changing provenance, losing it, or misattributing it to other data.

M3 - Conference contribution

BT - Workshop on Theory and Practice of Provenance (TaPP 2015)

PB - USENIX Association

T2 - Workshop on Theory and Practice of Provenance (TaPP 2015)

Y2 - 8 July 2015 through 9 July 2015

ER -

Language-integrated provenance in Links

Abstract / Description of output

Workshop

Access to Document

Fingerprint

Projects

DIACHRON - Managing the Evolution and Preservation of the Data Webb (RTD)

Cite this