--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/mention/prov-links.html Mon Nov 26 12:21:06 2012 +0000
@@ -0,0 +1,1344 @@
+<!DOCTYPE html
+>
+
+<html><head>
+ <title>Linking Across Provenance Bundles</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+<script src="../model/prov-magic.js" class="remove"></script>
+
+<script src="../model/grammar/ll.js" class="remove"></script>
+<script src="../model/provbib.js" class="remove"></script>
+<script src="../model/glossary.js" class="remove"></script>
+
+<script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js" class="remove"></script>
+
+<style type="text/css">
+ .note { font-size:small; margin-left:50px }
+
+ .entity {
+ border: 1px solid navy;
+ margin:5px 0px 5px 0px;
+ padding: 5px;
+ }
+
+
+
+ .description {
+ border-top: 1px dashed gray;
+ border-bottom: 1px dashed gray;
+ background-color: rgb(242, 243, 244);
+ margin-top:5px;
+ padding-bottom:5px;
+ }
+
+ .description dl {
+ background-color: rgb(242, 243, 244);
+ }
+
+ .description ul {
+ padding-left: 12px;
+ margin-top: 0px;
+ }
+
+code {
+ color: black !important;
+}
+
+.diamond {
+ font-weight: normal;
+ font-style: normal;
+ font-size:100%;
+ font-family: sans-serif;
+}
+
+table.thinborder {
+ border-width: 1px;
+ border-spacing: 0px;
+ border-style: none;
+ border-color: gray;
+ border-collapse: collapse;
+}
+table.thinborder th {
+ border-width: 1px;
+ padding: 0px;
+ border-style: solid;
+ border-color: gray;
+ -moz-border-radius: ;
+}
+table.thinborder td {
+ border-width: 1px;
+ padding: 2px;
+ border-style: solid;
+ border-color: gray;
+ -moz-border-radius: ;
+}
+
+/* --- EDITORIAL NOTES --- */
+.pending {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #BFEFFF;
+}
+
+.pending::before {
+ content: "Pending Review";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+
+
+.resolved {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #9BCD9B;
+}
+
+.resolved::before {
+ content: "Resolved";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+.inference {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+
+.inference-example {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.syntax {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.syntax[id]::before {
+ content: "Syntax: " attr(id);
+ width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
+}
+
+
+.syntax::before {
+ content: "Syntax";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.unamedconstraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+
+.unamedconstraint::before {
+ content: "Constraint";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+
+.constraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+.constraint-example {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+
+.interpretation {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+.interpretation[id]::before {
+ content: "Interpretation: " attr(id);
+ width: 380px; /* How can we compute the length of "Interpretation: " attr(id) */
+}
+
+
+.interpretation::before {
+ content: "Interpretation";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.definition {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #777;
+ background: #fff;
+}
+
+.definition-example {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #777;
+ background: #fff;
+}
+
+.deprecatedconstraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+.deprecatedconstraint[id]::before {
+ content: "Deprecated: " attr(id);
+ width: 380px; /* How can we compute the length of "Deprecatedconstraint: " attr(id) */
+}
+
+
+.deprecatedconstraint::before {
+ content: "Deprecated";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.glossary-ref {
+ font-style: italic;
+}
+
+.dfn {
+ font-weight: bold;
+}
+
+
+.attribute {
+ font-style: italic;
+}
+
+
+.conditional {
+ color: blue;
+}
+
+.grammar {
+ margin-top: 1ex;
+ margin-bottom: 1ex;
+ padding-left: 1ex;
+ padding-right: 1ex;
+ padding-top: 1ex;
+ padding-bottom: 0.6ex;
+ border: 1px dashed #2f6fab;
+ font-size: 95%;
+}
+.nonterminal {
+ font-weight: bold;
+ font-family: sans-serif;
+ font-size: 95%;
+}
+
+.name {
+ font-family: monospace;
+}
+
+.math {
+ font-family: roman;
+ font-style:italic;
+}
+
+
+.xmpl {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.xmpl::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+.anexample {
+ margin-top: 1ex;
+ margin-bottom: 1ex;
+ padding-left: 1ex;
+ padding-right: 1ex;
+ padding-top: 1ex;
+ padding-bottom: 0.6ex;
+ border: 1px dashed #2f6fab;
+ background-color: #f9f9f9;
+}
+.anexample table {
+ background-color: #f9f9f9;
+}
+
+.conceptexample:before {
+ content: "Example:";
+ font-family: sans-serif;
+ font-size: 1.6ex;
+ font-weight: bold;
+}
+.conceptexample {
+ margin-top: 1ex;
+ margin-bottom: 1ex;
+ padding-left: 1ex;
+ padding-right: 1ex;
+ padding-top: 1ex;
+ padding-bottom: 0.6ex;
+ border: 1px dashed #2f6fab;
+ background-color: #f9f9f9;
+}
+
+.pnExpression {
+ font-weight: normal;
+ font-size:120%;
+ font-family: monospace;
+}
+
+
+div[class="grammar"] span[class="name"]:before {
+ content: "'";
+}
+
+div[class="grammar"] span[class="name"]:after {
+ content: "'";
+}
+
+
+div[class="grammar"] span[class="optional"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="optional"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")?";
+}
+
+
+div[class="grammar"] span[class="plus"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="plus"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")+";
+}
+
+
+div[class="grammar"] span[class="star"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="star"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")*";
+}
+
+div[class="grammar"] span[class="choice"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="choice"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")";
+}
+
+div[class="grammar"] span[class="group"]:before {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: "(";
+}
+
+div[class="grammar"] span[class="group"]:after {
+ font-weight: normal;
+ font-size:130%;
+ font-family: monospace;
+ content: ")";
+}
+
+table {
+ background-color: #f9f9f9;
+}
+
+.component1-color {
+ background-color: rgba(255,42,42,0.2);
+}
+
+.component2-color {
+ background-color: rgba(0,68,170,0.2);
+}
+
+.component3-color {
+ background-color: rgba(0,170,0,0.2);
+}
+.component4-color {
+ background-color: rgba(204,255,0,0.2);
+}
+
+.component5-color {
+ background-color: rgba(11,40,40,0.2);
+}
+
+.component6-color {
+ background-color: rgba(244,105,14,0.2);
+}
+
+.interpretation-forward::before {
+ content: "Interpretation: ";
+ font-weight: bold;
+}
+
+.structural-forward::before {
+ content: "Structural constraint: ";
+ font-weight: bold;
+}
+
+
+code {
+ color: black;
+}
+
+.ruleTitle {
+ font-family: sans-serif;
+ font-size: 1.6ex;
+ font-weight: bold;
+}
+
+
+
+
+.remark {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px dashed #000;
+ background: #F0F0F0;
+}
+
+.remark::before {
+ content: "Remark";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #000;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+table.thinborder {
+ border-width: 1px;
+ border-spacing: 0px;
+ border-style: none;
+ border-color: gray;
+ border-collapse: collapse;
+}
+table.thinborder th {
+ border-width: 1px;
+ padding: 0px;
+ border-style: solid;
+ border-color: gray;
+}
+table.thinborder td {
+ border-width: 1px;
+ padding: 2px;
+ border-style: solid;
+ border-color: gray;
+}
+
+
+</style>
+
+
+ <script type="text/javascript">
+/*
+ Written by Jonathan Snook, http://www.snook.ca/jonathan
+ Add-ons by Robert Nyman, http://www.robertnyman.com
+ Author says "The credit comment is all it takes, no license. Go crazy with it!"
+ From http://www.robertnyman.com/2005/11/07/the-ultimate-getelementsbyclassname/
+*/
+
+function getElementsByClassName(oElm, strTagName, oClassNames){
+ var arrElements = (! (! (strTagName == "*") || ! (oElm.all)))? oElm.all : oElm.getElementsByTagName(strTagName);
+ var arrReturnElements = new Array();
+ var arrRegExpClassNames = new Array();
+ if(typeof oClassNames == "object"){
+ for(var i=0; !(i>=oClassNames.length); i++){ /*>*/
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames[i].replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ }
+ else{
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames.replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ var oElement;
+ var bMatchesAll;
+ for(var j=0; !(j>=arrElements.length); j++){ /*>*/
+ oElement = arrElements[j];
+ bMatchesAll = true;
+ for(var k=0; !(k>=arrRegExpClassNames.length); k++){ /*>*/
+ if(!arrRegExpClassNames[k].test(oElement.className)){
+ bMatchesAll = false;
+ break;
+ }
+ }
+ if(bMatchesAll){
+ arrReturnElements.push(oElement);
+ }
+ }
+ return (arrReturnElements)
+}
+
+function set_display_by_class(el, cls, newValue) {
+ var e = getElementsByClassName(document, el, cls);
+ if (e != null) {
+ for (var i=0; !(i>=e.length); i++) {
+ e[i].style.display = newValue;
+ }
+ }
+}
+
+function set_display_by_id(id, newValue) {
+ var e = document.getElementById(id);
+ if (e != null) {
+ e.style.display = newValue;
+ }
+}
+</script>
+
+
+ <script type="text/javascript" class="remove">
+
+
+ $(document).ready(function(){
+ // if glossary is in a string:
+ $('#glossary_div').html(glossary_string)
+ $('#grammar_div').html(grammar_string);
+ updateGlossaryRefs();
+ updateFigCaptions();
+ updateCaptions();
+ updateGrammarRefs();
+ updateExamples();
+ updateExamplesRefs();
+
+ if (typeof String.prototype.startsWith != 'function') {
+ String.prototype.startsWith = function (str){
+ return this.indexOf(str) == 0;
+ };
+ }
+
+ });
+
+ </script>
+ <script class="remove">
+ function updateGrammarRefs() {
+ $('.grammar-ref').each(function(index) {
+ var ref=$(this).attr('data-ref');
+ console.log( "updating grammar for " + ref);
+// $('#'+ref).parents("tbody").clone().appendTo($(this));
+
+
+ // $(this).replaceWith(function() {return $('#'+ref).parents("tbody").clone()});
+
+ $(this).replaceWith($('#'+ref).parents("tbody").clone());
+
+ });
+ }
+ </script>
+ <script class="remove">
+ var addExtraReferences = function() {
+ for (var k in extraReferences)
+ berjon.biblio[k] = extraReferences[k];
+ };
+ var extraReferences = {
+ "CLOCK":
+ "Lamport, L. "+
+ "<a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\"><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>."+
+ "Communications of the ACM 21 (7): 558–565. 1978. "+
+ "URL: <a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> " +
+ "DOI: doi:10.1145/359545.359563.",
+ "CSP":
+ "Hoare, C. A. R. "+
+ "<a href=\"http://www.usingcsp.com/cspbook.pdf\"><cite>Communicating Sequential Processes</cite></a>."+
+ "Prentice-Hall. 1985"+
+ "URL: <a href=\"http://www.usingcsp.com/cspbook.pdf\">http://www.usingcsp.com/cspbook.pdf</a>",
+ "Logic":
+ "W. E. Johnson "+
+ "<a href=\"http://www.ditext.com/johnson/intro-3.html\"><cite>Logic: Part III</cite></a>."+
+ "1924. "+
+ "URL: <a href=\"http://www.ditext.com/johnson/intro-3.html\">http://www.ditext.com/johnson/intro-3.html</a>",
+ "PROV-SEM":
+ "James Cheney "+
+ "<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
+ "2011, Work in progress. "+
+ "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
+
+ "PROV-PRIMER":
+ "Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
+ "<a href=\"http://www.w3.org/TR/prov-primer/\"><cite>Prov Model Primer</cite></a>. "+
+ "2012, Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-primer/\">http://www.w3.org/TR/prov-primer/</a>",
+
+ "PROV-O":
+ "Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik "+
+ "<a href=\"http://www.w3.org/TR/prov-o/\"><cite>Provenance Formal Model</cite></a>. "+
+ "2012, Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>",
+
+
+ "PROV-CONSTRAINTS":
+ "James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
+ "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
+ "2012, Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
+
+ "PROV-N":
+ "Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes "+
+ "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N: The Provenance Notation</cite></a>. "+
+ "2012, Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
+
+ "PROV-AQ":
+ "Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
+ "<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
+ "2012, Working Draft. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
+
+ "UML":
+ "Object Management Group "+
+ "<a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\"><cite>Unified Modeling Language: Superstructure</cite></a>. "+
+ "version 2.0, 2005 "+
+ "URL: <a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\">http://www.omg.org/spec/UML/2.0/Superstructure/PDF/</a>",
+
+ "RDF-CONCEPTS11":
+ "Richard Cyganiak and David Wood (eds.) " +
+ "RDF 1.1 Concepts and Abstract Syntax "+
+ "<a href=\"http://www.w3.org/TR/rdf11-concepts/\"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. "+
+ "URL: <a href=\"http://www.w3.org/TR/rdf11-concepts/\">http://www.w3.org/TR/rdf11-concepts/</a>",
+
+ "Mappings":
+ "Satya Sahoo and Paul Groth and Olaf Hartig and Simon Miles and Sam Coppens and James Myers and Yolanda Gil and Luc Moreau and Jun Zhao and Michael Panzer and Daniel Garijo "+
+ "<a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\"><cite>Provenance Vocabulary Mappings</cite></a>. "+
+ "August 2010 "+
+ "URL: <a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>",
+
+
+
+ };
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "prov-links",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ //subtitle : "A single document for prov-mention related material",
+
+
+ // if you wish the publication date to be other than today, set this
+ //publishDate: "2012-07-24",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ //copyrightStart: "2011",
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ //previousPublishDate: "2012-07-24",
+ //previousMaturity: "ED",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/links/prov-links.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ lcEnd: "2012-09-18",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
+ company: "University of Southampton" },
+ { name: "Timothy Lebo", url: "http://tw.rpi.edu/instances/TimLebo",
+ company: "Rensselaer Polytechnic Institute" },
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ authors: [
+ ],
+
+ // name of the WG
+ wg: "Provenance Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/prov/",
+
+ // name (with the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "public-prov-comments",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46974/status",
+
+ // Add extraReferences to bibliography database
+ preProcess: [addExtraReferences, addProvReferences],
+
+ postProcess: [updateSectionRefs, updateDfn, updateFigures],
+ };
+ </script>
+ </head>
+ <body>
+
+ <section id="abstract">
+<p>
+Provenance is information about entities, activities, and people
+involved in producing a piece of data or thing, which can be used to
+form assessments about its quality, reliability or trustworthiness.
+Bundles, defined as sets of provenance descriptions, are a mechanism by
+which provenance of provenance can be expressed.</p>
+
+<p>
+In applications where provenance is created by multiple parties over time, it is useful for provenance descriptions created by one party to link to provenance descriptions created by another party. To address this issue, this document introduces a relation allowing an entity description to be linked to another entity description occurring in another bundle.
+</p>
+
+<p>The <a href="http://www.w3.org/TR/2012/WD-prov-overview-20121211/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
+
+ </section>
+
+<section id="sotd">
+<h4>PROV Family of Documents</h4>
+This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
+interchange of provenance information in heterogeneous environments such as the Web. These documents are:
+<ul>
+<li> <a href="http://www.w3.org/TR/2012/WD-prov-overview-20121211/">PROV-OVERVIEW</a> (To be published as Note), an overview of the PROV family of documents [[PROV-OVERVIEW]];</li>
+<li> <a href="http://www.w3.org/TR/2012/WD-prov-primer-20121211/">PROV-PRIMER</a> (To be published as Note), a primer for the PROV data model [[PROV-PRIMER]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/">PROV-O</a> (Candidate Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [[!PROV-O]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">PROV-DM</a> (Candidate Recommendation), the PROV data model for provenance [[!PROV-DM]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-n-20121211/">PROV-N</a> (Candidate Recommendation), a notation for provenance aimed at human consumption [[!PROV-N]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/">PROV-CONSTRAINTS</a> (Candidate Recommendation), a set of constraints applying to the PROV data model [[!PROV-CONSTRAINTS]];</li>
+<li> <a href="http://www.w3.org/TR/2012/WD-prov-aq-20120619/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [[PROV-AQ]]; </li>
+<li> <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/">PROV-XML</a> (To be published as Note), an XML schema for the PROV data model [[PROV-XML]];</li>
+<li> <a href="http://www.w3.org/TR/2012/WD-prov-link-20121211/">PROV-LINK</a> (To be published as Note), introduces a mechanism to link across bundles (this document).</li>
+
+</ul>
+<h4>How to read the PROV Family of Documentation</h4>
+<ul>
+<li>[[PROV-OVERVIEW]] overviews the PROV family of documents. </li>
+<li>The primer [[PROV-PRIMER]] is the entry point to PROV offering an introduction to the provenance model.</li>
+<li>The Linked Data and Semantic Web community should focus on [[!PROV-O]] defining PROV classes and properties specified in an OWL2 ontology. For further details, [[!PROV-DM]] and [[!PROV-CONSTRAINTS]] specify the constraints applicable to the data model, and its interpretation. </li>
+<li>The XML community should focus on [[PROV-XML]] defining an XML schema for PROV. Further details can also be found in [[!PROV-DM]] and [[!PROV-CONSTRAINTS]].</li>
+<li>Developers seeking to retrieve or publish provenance should focus on [[PROV-AQ]].</li>
+<li>Readers seeking to implement other PROV serializations
+should focus on [[!PROV-DM]] and [[!PROV-CONSTRAINTS]]. [[!PROV-O]], [[!PROV-N]], and [[PROV-XML]] offer examples of mapping to RDF, text, and XML, respectively.</li>
+</ul>
+</section>
+
+
+
+
+
+
+
+<section id="introduction">
+<h2>Introduction</h2>
+
+<p>
+<a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">Provenance</a>
+is a record that describes the people, institutions, entities, and
+activities involved in producing, influencing, or delivering a piece
+of data or a thing. The specifications [[!PROV-O]], [[!PROV-DM]],
+[[!PROV-N]], and [[PROV-XML]] have respectively defined the PROV
+ontology, the PROV conceptual model, the PROV notation, and the PROV
+XML schema, allowing provenance descriptions to be expressed,
+represented in various representations, and interchanged between systems across the Web.
+</p>
+
+<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it. To support this, provenance should be trusted, and therefore, provenance of provenance is itself a critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#concept-bundle">Bundle</a>: defined as a set of provenance descriptions, it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/#Bundle">Bundle</a> [[!PROV-O]] and <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/#term-Bundle">Bundle</a> [[PROV-XML]]). With bundles, blobs of provenance descriptions can be given names and can itself be regarded as entities, whose provenance can be described using PROV. </p>
+
+
+<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party creates some data and its provenance, whereas another party consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by another producer. For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em>, i.e. in its bundle, and <em>specialize it</em>, allowing the consumer to add their own view on this entity.</p>
+
+<p>This document introduces a new concept <a>Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. The document provides a conceptual definition <a>Mention</a>, but also the corresponding ontological, schema, and notational definitions, for the various representations of PROV. It also includes constraints that apply to this construct specifically. By defining <a>Mention</a> conceptually, and in the PROV representations will promote inter-operability.</p>
+
+<div class="note">The concept <a>Mention</a> is experimental, and for this reason was defined as part of the PROV recommendation-track documents. The Provenance Working Group is seeking feedback from the community on its usefulness in practical scenarios.
+</div>
+</section>
+
+<section id="mention-dm">
+<h2>Data Model Definition</h2>
+
+
+
+<p>An entity <span class="name">e1</span> may be mentioned in a bundle <span class="name">b</span>, which contains some
+ descriptions about this entity <span class="name">e1</span>: how <span class="name">e1</span> was generated and used, which activities <span class="name">e1</span> is involved with, the agents <span class="name">e1</span> is attributed to, etc. Other bundles may contain other descriptions about the same entity <span class="name">e1</span>.
+Some applications may want to interpret
+the latter descriptions of entity <span class="name">e1</span> with respect to the descriptions found in the bundle <span class="name">b</span> it occurs in. To this end, PROV allows a new entity <span class="name">e2</span> to be created, which is a specialization of the preceding entity <span class="name">e1</span>, and which presents an additional aspect: the bundle <span class="name">b</span> containing some descriptions of <span class="name">e1</span>. With this relation, applications that process <span class="name">e2</span>
+can know that the attributes of <span class="name">e2</span> may have been computed according to the descriptions of <span class="name">e1</span> in <span class="name">b</span>.</p>
+
+
+
+<p>
+ <a href="#figure-component5">Figure 1</a> depicts
+the relation MentionOf (<a>mention</a>).
+</p>
+
+
+<div style="text-align: center;">
+<figure style="max-width: 95%; ">
+<img src="figures/component5.png" alt="mention"/><br>
+<figcaption id="figure-component5">Mention UML Diagram</figcaption>
+</figure>
+</div>
+
+
+<p>Thus, the following notion is a relation between two entities with regard to a bundle.
+It is a special case of specialization.</p>
+
+
+<span class="glossary-ref" data-ref="glossary-mention"></span>
+
+
+
+<p>
+An entity is interpreted with respect to a bundle's description in a
+domain specific manner. The mention of this entity with respect to
+this bundle offers the opportunity to specialize it according to some
+domain-specific interpretation.
+</p>
+
+
+<p>A mention of an entity in a bundle results in a specialization of this entity with extra fixed aspects, including the bundle that it is described in.
+</p>
+
+
+
+
+<p><div class="attributes" id="attributes-mention">A <dfn title="mentionOf">mention</dfn> relation<span class="withPn">, written <span class="pnExpression">mentionOf(infra, supra, b)</span> in PROV-N,</span> has:
+<ul>
+<li><span class='attribute' id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
+of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
+<li><span class='attribute' id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being mentioned.</li>
+<li><span class='attribute' id="mention.bundle">bundle</span>: an identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
+</ul>
+</div>
+
+<p>A mention is not, as defined here, as an influence, and therefore does not have an id and attributes.</p>
+
+<table class="grammar">
+<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-mentionExpression" name="prod-mentionExpression"></a><span class="prodNo"></span> </td> <td><code class="production prod">mentionExpression</code></td> <td> ::= </td> <td><code class="content">"mentionOf" "(" <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-bIdentifier">bIdentifier</a></span> ")"</code></td> </tr> </tbody>
+<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-bIdentifier" name="prod-bIdentifier"></a> </td> <td><code class="production prod">bIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
+</table>
+</table>
+
+<p>The following table summarizes how each constituent of a PROV-DM Mention maps to a PROV-N syntax element.</p>
+<div style="text-align: left; ">
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<tr><td><b><a href="#dfn-mentionof">Mention</a></b></td><td><b>Non-Terminal</b></td></tr>
+<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
+
+
+<tr><td><a href="#mention.specificEntity"><span class='attribute' id="mention.specificEntity">specificEntity</span></a></td><td><code class="content"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+
+<tr><td><a href="#mention.generalEntity"><span class='attribute' id="mention.generalEntity">generalEntity</span></a></td><td><code class="content"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></code></td></tr>
+
+<tr><td><a href="#mention.bundle"><span class='attribute' id="mention.bundle">bundle</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-bIdentifier">bIdentifier</a></code></td></tr>
+
+</table>
+</div>
+
+
+
+<div class="anexample" id="anexample-mention-rating">
+<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
+<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
+
+<pre class="codeexample">
+bundle ex:run1
+ activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
+ wasAssociatedWith(ex:a1, ex:Bob, [prov:role="controller"])
+endBundle
+
+bundle ex:run2
+ activity(ex:a2, 2011-11-17T10:00:00, 2011-11-17T17:00:00) //duration: 7hours
+ wasAssociatedWith(ex:a2, ex:Bob, [prov:role="controller"])
+endBundle
+</pre>
+<p>The performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a mention of <span class="name">ex:Bob</span> as described in bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours.
+
+<pre class="codeexample">
+bundle tool:analysis01
+ agent(tool:Bob-2011-11-16, [perf:rating="good"])
+ mentionOf(tool:Bob-2011-11-16, ex:Bob, ex:run1)
+
+ agent(tool:Bob-2011-11-17, [perf:rating="bad"])
+ mentionOf(tool:Bob-2011-11-17, ex:Bob, ex:run2)
+endBundle
+</pre>
+</div>
+
+
+<div class="anexample" id="aexample-mention-viz">
+<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
+<pre class="codeexample">
+bundle obs:bundle1
+ entity(ex:report1, [ prov:type="report", ex:version=1 ])
+ wasGeneratedBy(ex:g1; ex:report1, -, 2012-05-24T10:00:01)
+ entity(ex:report2, [ prov:type="report", ex:version=2 ])
+ wasGeneratedBy(ex:g2; ex:report2, -, 2012-05-25T11:00:01)
+ wasDerivedFrom(ex:report2, ex:report1)
+endBundle
+entity(obs:bundle1, [ prov:type='prov:Bundle' ])
+wasAttributedTo(obs:bundle1, ex:observer01)
+</pre>
+Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool. It may useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered. The original bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+<pre class="codeexample">
+bundle tool:bundle2
+ entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
+ wasAttributedTo(tool:bundle2, viz:Visualizer)
+
+ entity(tool:report1, [ viz:color="orange" ])
+ mentionOf(tool:report1, ex:report1, obs:bundle1)
+
+ entity(tool:report2, [ viz:color="blue" ])
+ mentionOf(tool:report2, ex:report2, obs:bundle1)
+endBundle
+</pre>
+
+<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+
+<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
+</p>
+
+<p>The visualisation tool
+ created new identifiers <span class="name">tool:report1</span> and
+<span class="name">tool:report2</span>.
+They denote entities which are specializations of <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle1</span>, with visualization attribute for the color to be used when rendering these entities. </p>
+
+</div>
+
+
+
+</section>
+
+
+
+<section id="mention-ontology">
+ <h2>Ontological Definition of Mention</h2>
+
+<p>The ternary relation <a>mentionOf</a> is encoded as two properties:
+<a href="#mentionOf">prov:mentionOf</a> and
+<a href="#asInBundle">prov:asInBundle</a>, defined as follows.</p>
+
+<div class="entity" id="mentionOf">
+ <h3 id="property--prov-mentionof-op-----------------back-to-expanded-properties">
+ Property: <a href="#mentionOf"><span title="http://www.w3.org/ns/prov#mentionOf" class="dotted">prov:mentionOf</span></a> <sup title="object property" class="type-op">op</sup>
+
+ </h3>
+ <p><strong class="crossreference">IRI:</strong>http://www.w3.org/ns/prov#mentionOf</p>
+
+
+ <div class="description">
+ <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
+ </div>
+ <div class="comment "><p>prov:asInBundle is used to cite the Bundle in which the generalization was mentioned.</p>
+ </div>
+ <dl>
+
+ <dt>has super-properties</dt>
+ <dd>
+ <ul>
+ <li>
+ <a class="owlclass" href="#specializationOf" title="http://www.w3.org/ns/prov#specializationOf">prov:specializationOf</a> <sup title="object property" class="type-op">op</sup>
+ </li>
+ </ul>
+ </dd>
+
+ <dt>has domain</dt>
+ <dd>
+ <ul>
+ <li>
+ <a class="owlclass" href="#Entity" title="http://www.w3.org/ns/prov#Entity">prov:Entity</a>
+ </li>
+ </ul>
+ </dd>
+
+ <dt>has range</dt>
+ <dd>
+ <ul>
+ <li>
+ <a class="owlclass" href="#Entity" title="http://www.w3.org/ns/prov#Entity">prov:Entity</a>
+ </li>
+ </ul>
+ </dd>
+
+ <dt>PROV-DM term</dt>
+ <dd>
+ <a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/Overview.html#term-mention" title="prov-dm">mention</a> </dd>
+
+ </dl>
+ </div>
+ </div>
+
+
+<div class="entity" id="asInBundle">
+ <h3 id="property--prov-asinbundle-op-----------------back-to-expanded-properties">
+ Property: <a href="#asInBundle"><span title="http://www.w3.org/ns/prov#asInBundle" class="dotted">prov:asInBundle</span></a> <sup title="object property" class="type-op">op</sup>
+ </h3>
+ <p><strong class="crossreference">IRI:</strong>http://www.w3.org/ns/prov#asInBundle</p>
+
+
+ <div class="description">
+ <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
+ </div>
+ <dl>
+ <dt>has domain</dt>
+ <dd>
+ <ul>
+ <li>
+ <a class="owlclass" href="#Entity" title="http://www.w3.org/ns/prov#Entity">prov:Entity</a>
+ </li>
+ </ul>
+ </dd>
+
+ <dt>has range</dt>
+ <dd>
+ <ul>
+ <li>
+ <a class="owlclass" href="#Bundle" title="http://www.w3.org/ns/prov#Bundle">prov:Bundle</a>
+ </li>
+ </ul>
+ </dd>
+
+ <dt>PROV-DM term</dt>
+ <dd>
+ <a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/Overview.html#term-mention" title="prov-dm">mention</a> </dd>
+
+ </dl>
+ </div>
+ </div>
+
+ <div class="anexample" typeof="prov:Entity" about="#example-for-property-mentionOf">
+ <span resource="http://www.w3.org/ns/prov#mentionOf" rel="dcterms:subject"></span>
+
+<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example REF</span></a>, encoding in RDF the rating of Bob in the context of the second activity.</p>
+
+ <pre property="prov:value" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_mentionOf.ttl" rel="prov:wasQuotedFrom">@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix prov: <http://www.w3.org/ns/prov#> .
+@prefix tool: <http://example.com/tool/> .
+@prefix perf: <http://example.com/performance/> .
+@prefix : <http://example.com/> .
+
+:run2 {
+ :activity_2
+ a prov:Activity;
+ prov:startedAtTime "2011-11-17T10:00:00"^^xsd:dateTime;
+ prov:endedAtTime "2011-11-17T17:00:00"^^xsd:dateTime;
+ prov:wasAssociatedWith :bob;
+ .
+}
+
+tool:analysis_01 {
+ tool:bob-2011-11-17
+ a prov:Agent;
+ prov:mentionOf :bob;
+ prov:asInBundle :run2;
+ perf:rating perf:very-slow;
+ .
+}
+
+# This is inferred from prov:mentionOf
+tool:bob-2011-11-17 prov:specializationOf :bob .
+
+# This is inferred from prov:specializationOf
+tool:bob-2011-11-17 prov:alternateOf :bob .
+</pre>
+ </div>
+</section>
+
+
+<section id="mention-xml">
+ <h2>XML Schema for Mention</h2>
+
+
+
+<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Mention">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:EntityRef"/>
+ <xs:element name="generalEntity" type="prov:EntityRef"/>
+ <xs:element name="bundle" type="prov:EntityRef"/>
+ </xs:sequence>
+</xs:complexType>
+</pre>
+<p>Usage in XML:</p><pre class="schema-usage"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="mentionOf" type="prov:Mention"/>
+</pre>
+<div class="anexample">
+<pre><prov:document
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:perf="http://example.com/ns/perf#"
+ xmlns:tool="http://example.com/ns/tool#">
+
+ <prov:bundle prov:id="ex:run1">
+ <prov:activity prov:id="ex:a1">
+ <prov:startTime>2011-11-16T16:00:00</prov:startTime>
+ <prov:endTime>2011-11-16T17:00:00</prov:endTime>
+ </prov:activity>
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="ex:a1" />
+ <prov:agent prov:ref="ex:Bob" />
+ <prov:role xsi:type="xsd:QName">controller</prov:role>
+ </prov:wasAssociatedWith>
+ </prov:bundle>
+
+ <prov:bundle prov:id="ex:run2">
+ <prov:activity prov:id="ex:a2">
+ <prov:startTime>2011-11-17T10:00:00</prov:startTime>
+ <prov:endTime>2011-11-17T17:00:00</prov:endTime>
+ </prov:activity>
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="ex:a2" />
+ <prov:agent prov:ref="ex:Bob" />
+ <prov:role xsi:type="xsd:QName">controller</prov:role>
+ </prov:wasAssociatedWith>
+ </prov:bundle>
+
+ <prov:bundle prov:id="tool:analysis01">
+ <prov:agent prov:id="tool:Bob-2011-11-16">
+ <ex:perfrating>good</ex:perfrating>
+ </prov:agent>
+
+ <b><prov:mentionOf>
+ <prov:specificEntity prov:ref="tool:Bob-2011-11-16" />
+ <prov:generalEntity prov:ref="ex:Bob" />
+ <prov:bundle prov:ref="ex:run1" />
+ </prov:mentionOf></b>
+
+ <prov:agent prov:id="tool:Bob-2011-11-17">
+ <ex:perfrating>bad</ex:perfrating>
+ </prov:agent>
+
+ <b><prov:mentionOf>
+ <prov:specificEntity prov:ref="tool:Bob-2011-11-17" />
+ <prov:generalEntity prov:ref="ex:Bob" />
+ <prov:bundle prov:ref="ex:run2" />
+ </prov:mentionOf></b>
+ </prov:bundle>
+
+</prov:document></pre></div>
+</section>
+
+
+<div id="glossary_div" class="remove">
+<!-- glossary loaded from glossary.js will be hooked up here,
+ class remove, will remove this element from the final output.
+-->
+</div>
+<div id="grammar_div" class="remove">
+<!-- grammar loaded from glossary.js will be hooked up here,
+ class remove, will remove this element from the final output.
+-->
+</div>
+
+
+<section id="mention-constraints">
+ <h2>Constraints associated with Mention</h2>
+
+
+
+
+
+ <p id="mention-specialization-inference_text">If one entity is a mention of another in a bundle, then the former is also a specialization of the latter:</p>
+
+ <div class='inference' id="mention-specialization-inference">
+<p>
+<span class='conditional'>IF</span> <span class='name'>mentionOf(e2,e1,b)</span> <span class='conditional'>THEN</span> <span class='name'>specializationOf(e2,e1)</span>.</p>
+ </div>
+
+
+
+
+<div id='unique-mention_text'>
+<p>An entity can be the subject of at most one mention relation.</p>
+</div>
+
+
+<div class='constraint' id='unique-mention'>
+<p>
+<span class='conditional'>IF</span> <span class="name">mentionOf(e, e1, b1)</span> and <span class="name">mentionOf(e, e2, b2)</span>,
+<span class='conditional'>THEN</span> <span class="name">e1</span>=<span class="name">e2</span> and <span class="name">b1</span>=<span class="name">b2</span>.</p>
+</div>
+
+
+
+</section>
+
+
+
+<section class="appendix">
+ <h2>Acknowledgements</h2>
+ <p>
+
+This document has been produced by the PROV Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks to Ivan Herman and Sandro Hawke (W3C/MIT).
+ </p>
+
+<p>
+Members of the PROV Working Group at the time of publication of this document were:
+
+Ilkay Altintas (Invited expert),
+Reza B'Far (Oracle Corporation),
+Khalid Belhajjame (University of Manchester),
+James Cheney (University of Edinburgh, School of Informatics),
+Sam Coppens (IBBT),
+David Corsar (University of Aberdeen, Computing Science),
+Stephen Cresswell (The National Archives),
+Tom De Nies (IBBT),
+Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
+Simon Dobson (Invited expert),
+Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
+Kai Eckert (Invited expert),
+Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
+James Frew (Invited expert),
+Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
+Daniel Garijo (Universidad Politécnica de Madrid),
+Yolanda Gil (Invited expert),
+Ryan Golden (Oracle Corporation),
+Paul Groth (Vrije Universiteit),
+Olaf Hartig (Invited expert),
+David Hau (National Cancer Institute, NCI),
+Sandro Hawke (W3C/MIT),
+Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
+Ivan Herman, (W3C/ERCIM),
+Ralph Hodgson (TopQuadrant),
+Hook Hua (Invited expert),
+Trung Dong Huynh (University of Southampton),
+Graham Klyne (University of Oxford),
+Michael Lang (Revelytix, Inc.),
+Timothy Lebo (Rensselaer Polytechnic Institute),
+James McCusker (Rensselaer Polytechnic Institute),
+Deborah McGuinness (Rensselaer Polytechnic Institute),
+Simon Miles (Invited expert),
+Paolo Missier (School of Computing Science, Newcastle university),
+Luc Moreau (University of Southampton),
+James Myers (Rensselaer Polytechnic Institute),
+Vinh Nguyen (Wright State University),
+Edoardo Pignotti (University of Aberdeen, Computing Science),
+Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
+Carl Reed (Open Geospatial Consortium),
+Adam Retter (Invited Expert),
+Christine Runnegar (Invited expert),
+Satya Sahoo (Invited expert),
+David Schaengold (Revelytix, Inc.),
+Daniel Schutzer (FSTC, Financial Services Technology Consortium),
+Yogesh Simmhan (Invited expert),
+Stian Soiland-Reyes (University of Manchester),
+Eric Stephan (Pacific Northwest National Laboratory),
+Linda Stewart (The National Archives),
+Ed Summers (Library of Congress),
+Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
+Ted Thibodeau (OpenLink Software Inc.),
+Curt Tilmes (National Aeronautics and Space Administration),
+Craig Trim (IBM Corporation),
+Stephan Zednik (Rensselaer Polytechnic Institute),
+Jun Zhao (University of Oxford),
+Yuting Zhao (University of Aberdeen, Computing Science).
+</p>
+ </section>
+
+
+ </body>
+</html>
--- a/mention/prov-mention.html Mon Nov 26 12:11:39 2012 +0000
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,1344 +0,0 @@
-<!DOCTYPE html
->
-
-<html><head>
- <title>Linking Across Provenance Bundles</title>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-
-<script src="../model/prov-magic.js" class="remove"></script>
-
-<script src="../model/grammar/ll.js" class="remove"></script>
-<script src="../model/provbib.js" class="remove"></script>
-<script src="../model/glossary.js" class="remove"></script>
-
-<script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
-<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js" class="remove"></script>
-
-<style type="text/css">
- .note { font-size:small; margin-left:50px }
-
- .entity {
- border: 1px solid navy;
- margin:5px 0px 5px 0px;
- padding: 5px;
- }
-
-
-
- .description {
- border-top: 1px dashed gray;
- border-bottom: 1px dashed gray;
- background-color: rgb(242, 243, 244);
- margin-top:5px;
- padding-bottom:5px;
- }
-
- .description dl {
- background-color: rgb(242, 243, 244);
- }
-
- .description ul {
- padding-left: 12px;
- margin-top: 0px;
- }
-
-code {
- color: black !important;
-}
-
-.diamond {
- font-weight: normal;
- font-style: normal;
- font-size:100%;
- font-family: sans-serif;
-}
-
-table.thinborder {
- border-width: 1px;
- border-spacing: 0px;
- border-style: none;
- border-color: gray;
- border-collapse: collapse;
-}
-table.thinborder th {
- border-width: 1px;
- padding: 0px;
- border-style: solid;
- border-color: gray;
- -moz-border-radius: ;
-}
-table.thinborder td {
- border-width: 1px;
- padding: 2px;
- border-style: solid;
- border-color: gray;
- -moz-border-radius: ;
-}
-
-/* --- EDITORIAL NOTES --- */
-.pending {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #BFEFFF;
-}
-
-.pending::before {
- content: "Pending Review";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-
-
-.resolved {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #9BCD9B;
-}
-
-.resolved::before {
- content: "Resolved";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-.inference {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-
-.inference-example {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.syntax {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.syntax[id]::before {
- content: "Syntax: " attr(id);
- width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
-}
-
-
-.syntax::before {
- content: "Syntax";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-.unamedconstraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-
-.unamedconstraint::before {
- content: "Constraint";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-
-.constraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.constraint-example {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-
-.interpretation {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.interpretation[id]::before {
- content: "Interpretation: " attr(id);
- width: 380px; /* How can we compute the length of "Interpretation: " attr(id) */
-}
-
-
-.interpretation::before {
- content: "Interpretation";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-.definition {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #777;
- background: #fff;
-}
-
-.definition-example {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #777;
- background: #fff;
-}
-
-.deprecatedconstraint {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #00f;
- background: #fff;
-}
-
-.deprecatedconstraint[id]::before {
- content: "Deprecated: " attr(id);
- width: 380px; /* How can we compute the length of "Deprecatedconstraint: " attr(id) */
-}
-
-
-.deprecatedconstraint::before {
- content: "Deprecated";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #00f;
- background: #fff;
- padding: 3px 1em;
-}
-
-.glossary-ref {
- font-style: italic;
-}
-
-.dfn {
- font-weight: bold;
-}
-
-
-.attribute {
- font-style: italic;
-}
-
-
-.conditional {
- color: blue;
-}
-
-.grammar {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- font-size: 95%;
-}
-.nonterminal {
- font-weight: bold;
- font-family: sans-serif;
- font-size: 95%;
-}
-
-.name {
- font-family: monospace;
-}
-
-.math {
- font-family: roman;
- font-style:italic;
-}
-
-
-.xmpl {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #fff;
-}
-
-.xmpl::before {
- content: "Example";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-
-.anexample {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- background-color: #f9f9f9;
-}
-.anexample table {
- background-color: #f9f9f9;
-}
-
-.conceptexample:before {
- content: "Example:";
- font-family: sans-serif;
- font-size: 1.6ex;
- font-weight: bold;
-}
-.conceptexample {
- margin-top: 1ex;
- margin-bottom: 1ex;
- padding-left: 1ex;
- padding-right: 1ex;
- padding-top: 1ex;
- padding-bottom: 0.6ex;
- border: 1px dashed #2f6fab;
- background-color: #f9f9f9;
-}
-
-.pnExpression {
- font-weight: normal;
- font-size:120%;
- font-family: monospace;
-}
-
-
-div[class="grammar"] span[class="name"]:before {
- content: "'";
-}
-
-div[class="grammar"] span[class="name"]:after {
- content: "'";
-}
-
-
-div[class="grammar"] span[class="optional"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="optional"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")?";
-}
-
-
-div[class="grammar"] span[class="plus"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="plus"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")+";
-}
-
-
-div[class="grammar"] span[class="star"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="star"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")*";
-}
-
-div[class="grammar"] span[class="choice"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="choice"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")";
-}
-
-div[class="grammar"] span[class="group"]:before {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: "(";
-}
-
-div[class="grammar"] span[class="group"]:after {
- font-weight: normal;
- font-size:130%;
- font-family: monospace;
- content: ")";
-}
-
-table {
- background-color: #f9f9f9;
-}
-
-.component1-color {
- background-color: rgba(255,42,42,0.2);
-}
-
-.component2-color {
- background-color: rgba(0,68,170,0.2);
-}
-
-.component3-color {
- background-color: rgba(0,170,0,0.2);
-}
-.component4-color {
- background-color: rgba(204,255,0,0.2);
-}
-
-.component5-color {
- background-color: rgba(11,40,40,0.2);
-}
-
-.component6-color {
- background-color: rgba(244,105,14,0.2);
-}
-
-.interpretation-forward::before {
- content: "Interpretation: ";
- font-weight: bold;
-}
-
-.structural-forward::before {
- content: "Structural constraint: ";
- font-weight: bold;
-}
-
-
-code {
- color: black;
-}
-
-.ruleTitle {
- font-family: sans-serif;
- font-size: 1.6ex;
- font-weight: bold;
-}
-
-
-
-
-.remark {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px dashed #000;
- background: #F0F0F0;
-}
-
-.remark::before {
- content: "Remark";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #000;
- background: #fff;
- padding: 3px 1em;
-}
-
-table.thinborder {
- border-width: 1px;
- border-spacing: 0px;
- border-style: none;
- border-color: gray;
- border-collapse: collapse;
-}
-table.thinborder th {
- border-width: 1px;
- padding: 0px;
- border-style: solid;
- border-color: gray;
-}
-table.thinborder td {
- border-width: 1px;
- padding: 2px;
- border-style: solid;
- border-color: gray;
-}
-
-
-</style>
-
-
- <script type="text/javascript">
-/*
- Written by Jonathan Snook, http://www.snook.ca/jonathan
- Add-ons by Robert Nyman, http://www.robertnyman.com
- Author says "The credit comment is all it takes, no license. Go crazy with it!"
- From http://www.robertnyman.com/2005/11/07/the-ultimate-getelementsbyclassname/
-*/
-
-function getElementsByClassName(oElm, strTagName, oClassNames){
- var arrElements = (! (! (strTagName == "*") || ! (oElm.all)))? oElm.all : oElm.getElementsByTagName(strTagName);
- var arrReturnElements = new Array();
- var arrRegExpClassNames = new Array();
- if(typeof oClassNames == "object"){
- for(var i=0; !(i>=oClassNames.length); i++){ /*>*/
- arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames[i].replace(/\-/g, "\-") + "(\s|$)"));
- }
- }
- else{
- arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames.replace(/\-/g, "\-") + "(\s|$)"));
- }
- var oElement;
- var bMatchesAll;
- for(var j=0; !(j>=arrElements.length); j++){ /*>*/
- oElement = arrElements[j];
- bMatchesAll = true;
- for(var k=0; !(k>=arrRegExpClassNames.length); k++){ /*>*/
- if(!arrRegExpClassNames[k].test(oElement.className)){
- bMatchesAll = false;
- break;
- }
- }
- if(bMatchesAll){
- arrReturnElements.push(oElement);
- }
- }
- return (arrReturnElements)
-}
-
-function set_display_by_class(el, cls, newValue) {
- var e = getElementsByClassName(document, el, cls);
- if (e != null) {
- for (var i=0; !(i>=e.length); i++) {
- e[i].style.display = newValue;
- }
- }
-}
-
-function set_display_by_id(id, newValue) {
- var e = document.getElementById(id);
- if (e != null) {
- e.style.display = newValue;
- }
-}
-</script>
-
-
- <script type="text/javascript" class="remove">
-
-
- $(document).ready(function(){
- // if glossary is in a string:
- $('#glossary_div').html(glossary_string)
- $('#grammar_div').html(grammar_string);
- updateGlossaryRefs();
- updateFigCaptions();
- updateCaptions();
- updateGrammarRefs();
- updateExamples();
- updateExamplesRefs();
-
- if (typeof String.prototype.startsWith != 'function') {
- String.prototype.startsWith = function (str){
- return this.indexOf(str) == 0;
- };
- }
-
- });
-
- </script>
- <script class="remove">
- function updateGrammarRefs() {
- $('.grammar-ref').each(function(index) {
- var ref=$(this).attr('data-ref');
- console.log( "updating grammar for " + ref);
-// $('#'+ref).parents("tbody").clone().appendTo($(this));
-
-
- // $(this).replaceWith(function() {return $('#'+ref).parents("tbody").clone()});
-
- $(this).replaceWith($('#'+ref).parents("tbody").clone());
-
- });
- }
- </script>
- <script class="remove">
- var addExtraReferences = function() {
- for (var k in extraReferences)
- berjon.biblio[k] = extraReferences[k];
- };
- var extraReferences = {
- "CLOCK":
- "Lamport, L. "+
- "<a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\"><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>."+
- "Communications of the ACM 21 (7): 558–565. 1978. "+
- "URL: <a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> " +
- "DOI: doi:10.1145/359545.359563.",
- "CSP":
- "Hoare, C. A. R. "+
- "<a href=\"http://www.usingcsp.com/cspbook.pdf\"><cite>Communicating Sequential Processes</cite></a>."+
- "Prentice-Hall. 1985"+
- "URL: <a href=\"http://www.usingcsp.com/cspbook.pdf\">http://www.usingcsp.com/cspbook.pdf</a>",
- "Logic":
- "W. E. Johnson "+
- "<a href=\"http://www.ditext.com/johnson/intro-3.html\"><cite>Logic: Part III</cite></a>."+
- "1924. "+
- "URL: <a href=\"http://www.ditext.com/johnson/intro-3.html\">http://www.ditext.com/johnson/intro-3.html</a>",
- "PROV-SEM":
- "James Cheney "+
- "<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
- "2011, Work in progress. "+
- "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
-
- "PROV-PRIMER":
- "Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
- "<a href=\"http://www.w3.org/TR/prov-primer/\"><cite>Prov Model Primer</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-primer/\">http://www.w3.org/TR/prov-primer/</a>",
-
- "PROV-O":
- "Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik "+
- "<a href=\"http://www.w3.org/TR/prov-o/\"><cite>Provenance Formal Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>",
-
-
- "PROV-CONSTRAINTS":
- "James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
- "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
-
- "PROV-N":
- "Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes "+
- "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N: The Provenance Notation</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
-
- "PROV-AQ":
- "Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
- "<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
-
- "UML":
- "Object Management Group "+
- "<a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\"><cite>Unified Modeling Language: Superstructure</cite></a>. "+
- "version 2.0, 2005 "+
- "URL: <a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\">http://www.omg.org/spec/UML/2.0/Superstructure/PDF/</a>",
-
- "RDF-CONCEPTS11":
- "Richard Cyganiak and David Wood (eds.) " +
- "RDF 1.1 Concepts and Abstract Syntax "+
- "<a href=\"http://www.w3.org/TR/rdf11-concepts/\"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. "+
- "URL: <a href=\"http://www.w3.org/TR/rdf11-concepts/\">http://www.w3.org/TR/rdf11-concepts/</a>",
-
- "Mappings":
- "Satya Sahoo and Paul Groth and Olaf Hartig and Simon Miles and Sam Coppens and James Myers and Yolanda Gil and Luc Moreau and Jun Zhao and Michael Panzer and Daniel Garijo "+
- "<a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\"><cite>Provenance Vocabulary Mappings</cite></a>. "+
- "August 2010 "+
- "URL: <a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>",
-
-
-
- };
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "prov-links",
-
- // if your specification has a subtitle that goes below the main
- // formal title, define it here
- //subtitle : "A single document for prov-mention related material",
-
-
- // if you wish the publication date to be other than today, set this
- //publishDate: "2012-07-24",
-
- // if the specification's copyright date is a range of years, specify
- // the start date here:
- //copyrightStart: "2011",
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- //previousPublishDate: "2012-07-24",
- //previousMaturity: "ED",
-
- // if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/mention/prov-mention.html",
-
- // if this is a LCWD, uncomment and set the end of its review period
- lcEnd: "2012-09-18",
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
-
- // editors, add as many as you like
- // only "name" is required
- editors: [
- { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
- company: "University of Southampton" },
- { name: "Timothy Lebo", url: "http://tw.rpi.edu/instances/TimLebo",
- company: "Rensselaer Polytechnic Institute" },
- ],
-
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
-
- authors: [
- ],
-
- // name of the WG
- wg: "Provenance Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2011/prov/",
-
- // name (with the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-prov-comments",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46974/status",
-
- // Add extraReferences to bibliography database
- preProcess: [addExtraReferences, addProvReferences],
-
- postProcess: [updateSectionRefs, updateDfn, updateFigures],
- };
- </script>
- </head>
- <body>
-
- <section id="abstract">
-<p>
-Provenance is information about entities, activities, and people
-involved in producing a piece of data or thing, which can be used to
-form assessments about its quality, reliability or trustworthiness.
-Bundles, defined as sets of provenance descriptions, are a mechanism by
-which provenance of provenance can be expressed.</p>
-
-<p>
-In applications where provenance is created by multiple parties over time, it is useful for provenance descriptions created by one party to link to provenance descriptions created by another party. To address this issue, this document introduces a relation allowing an entity description to be linked to another entity description occurring in another bundle.
-</p>
-
-<p>The <a href="http://www.w3.org/TR/2012/WD-prov-overview-20121211/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
-
- </section>
-
-<section id="sotd">
-<h4>PROV Family of Documents</h4>
-This document is part of the PROV family of documents, a set of documents defining various aspects that are necessary to achieve the vision of inter-operable
-interchange of provenance information in heterogeneous environments such as the Web. These documents are:
-<ul>
-<li> <a href="http://www.w3.org/TR/2012/WD-prov-overview-20121211/">PROV-OVERVIEW</a> (To be published as Note), an overview of the PROV family of documents [[PROV-OVERVIEW]];</li>
-<li> <a href="http://www.w3.org/TR/2012/WD-prov-primer-20121211/">PROV-PRIMER</a> (To be published as Note), a primer for the PROV data model [[PROV-PRIMER]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/">PROV-O</a> (Candidate Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [[!PROV-O]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">PROV-DM</a> (Candidate Recommendation), the PROV data model for provenance [[!PROV-DM]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-n-20121211/">PROV-N</a> (Candidate Recommendation), a notation for provenance aimed at human consumption [[!PROV-N]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/">PROV-CONSTRAINTS</a> (Candidate Recommendation), a set of constraints applying to the PROV data model [[!PROV-CONSTRAINTS]];</li>
-<li> <a href="http://www.w3.org/TR/2012/WD-prov-aq-20120619/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [[PROV-AQ]]; </li>
-<li> <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/">PROV-XML</a> (To be published as Note), an XML schema for the PROV data model [[PROV-XML]];</li>
-<li> <a href="http://www.w3.org/TR/2012/WD-prov-link-20121211/">PROV-LINK</a> (To be published as Note), introduces a mechanism to link across bundles (this document).</li>
-
-</ul>
-<h4>How to read the PROV Family of Documentation</h4>
-<ul>
-<li>[[PROV-OVERVIEW]] overviews the PROV family of documents. </li>
-<li>The primer [[PROV-PRIMER]] is the entry point to PROV offering an introduction to the provenance model.</li>
-<li>The Linked Data and Semantic Web community should focus on [[!PROV-O]] defining PROV classes and properties specified in an OWL2 ontology. For further details, [[!PROV-DM]] and [[!PROV-CONSTRAINTS]] specify the constraints applicable to the data model, and its interpretation. </li>
-<li>The XML community should focus on [[PROV-XML]] defining an XML schema for PROV. Further details can also be found in [[!PROV-DM]] and [[!PROV-CONSTRAINTS]].</li>
-<li>Developers seeking to retrieve or publish provenance should focus on [[PROV-AQ]].</li>
-<li>Readers seeking to implement other PROV serializations
-should focus on [[!PROV-DM]] and [[!PROV-CONSTRAINTS]]. [[!PROV-O]], [[!PROV-N]], and [[PROV-XML]] offer examples of mapping to RDF, text, and XML, respectively.</li>
-</ul>
-</section>
-
-
-
-
-
-
-
-<section id="introduction">
-<h2>Introduction</h2>
-
-<p>
-<a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">Provenance</a>
-is a record that describes the people, institutions, entities, and
-activities involved in producing, influencing, or delivering a piece
-of data or a thing. The specifications [[!PROV-O]], [[!PROV-DM]],
-[[!PROV-N]], and [[PROV-XML]] have respectively defined the PROV
-ontology, the PROV conceptual model, the PROV notation, and the PROV
-XML schema, allowing provenance descriptions to be expressed,
-represented in various representations, and interchanged between systems across the Web.
-</p>
-
-<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it. To support this, provenance should be trusted, and therefore, provenance of provenance is itself a critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#concept-bundle">Bundle</a>: defined as a set of provenance descriptions, it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/#Bundle">Bundle</a> [[!PROV-O]] and <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/#term-Bundle">Bundle</a> [[PROV-XML]]). With bundles, blobs of provenance descriptions can be given names and can itself be regarded as entities, whose provenance can be described using PROV. </p>
-
-
-<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party creates some data and its provenance, whereas another party consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by another producer. For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em>, i.e. in its bundle, and <em>specialize it</em>, allowing the consumer to add their own view on this entity.</p>
-
-<p>This document introduces a new concept <a>Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. The document provides a conceptual definition <a>Mention</a>, but also the corresponding ontological, schema, and notational definitions, for the various representations of PROV. It also includes constraints that apply to this construct specifically. By defining <a>Mention</a> conceptually, and in the PROV representations will promote inter-operability.</p>
-
-<div class="note">The concept <a>Mention</a> is experimental, and for this reason was defined as part of the PROV recommendation-track documents. The Provenance Working Group is seeking feedback from the community on its usefulness in practical scenarios.
-</div>
-</section>
-
-<section id="mention-dm">
-<h2>Data Model Definition</h2>
-
-
-
-<p>An entity <span class="name">e1</span> may be mentioned in a bundle <span class="name">b</span>, which contains some
- descriptions about this entity <span class="name">e1</span>: how <span class="name">e1</span> was generated and used, which activities <span class="name">e1</span> is involved with, the agents <span class="name">e1</span> is attributed to, etc. Other bundles may contain other descriptions about the same entity <span class="name">e1</span>.
-Some applications may want to interpret
-the latter descriptions of entity <span class="name">e1</span> with respect to the descriptions found in the bundle <span class="name">b</span> it occurs in. To this end, PROV allows a new entity <span class="name">e2</span> to be created, which is a specialization of the preceding entity <span class="name">e1</span>, and which presents an additional aspect: the bundle <span class="name">b</span> containing some descriptions of <span class="name">e1</span>. With this relation, applications that process <span class="name">e2</span>
-can know that the attributes of <span class="name">e2</span> may have been computed according to the descriptions of <span class="name">e1</span> in <span class="name">b</span>.</p>
-
-
-
-<p>
- <a href="#figure-component5">Figure 1</a> depicts
-the relation MentionOf (<a>mention</a>).
-</p>
-
-
-<div style="text-align: center;">
-<figure style="max-width: 95%; ">
-<img src="figures/component5.png" alt="mention"/><br>
-<figcaption id="figure-component5">Mention UML Diagram</figcaption>
-</figure>
-</div>
-
-
-<p>Thus, the following notion is a relation between two entities with regard to a bundle.
-It is a special case of specialization.</p>
-
-
-<span class="glossary-ref" data-ref="glossary-mention"></span>
-
-
-
-<p>
-An entity is interpreted with respect to a bundle's description in a
-domain specific manner. The mention of this entity with respect to
-this bundle offers the opportunity to specialize it according to some
-domain-specific interpretation.
-</p>
-
-
-<p>A mention of an entity in a bundle results in a specialization of this entity with extra fixed aspects, including the bundle that it is described in.
-</p>
-
-
-
-
-<p><div class="attributes" id="attributes-mention">A <dfn title="mentionOf">mention</dfn> relation<span class="withPn">, written <span class="pnExpression">mentionOf(infra, supra, b)</span> in PROV-N,</span> has:
-<ul>
-<li><span class='attribute' id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
-of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
-<li><span class='attribute' id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being mentioned.</li>
-<li><span class='attribute' id="mention.bundle">bundle</span>: an identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
-</ul>
-</div>
-
-<p>A mention is not, as defined here, as an influence, and therefore does not have an id and attributes.</p>
-
-<table class="grammar">
-<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-mentionExpression" name="prod-mentionExpression"></a><span class="prodNo"></span> </td> <td><code class="production prod">mentionExpression</code></td> <td> ::= </td> <td><code class="content">"mentionOf" "(" <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-bIdentifier">bIdentifier</a></span> ")"</code></td> </tr> </tbody>
-<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-bIdentifier" name="prod-bIdentifier"></a> </td> <td><code class="production prod">bIdentifier</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-identifier">identifier</a></span></code></td> </tr> </tbody>
-</table>
-</table>
-
-<p>The following table summarizes how each constituent of a PROV-DM Mention maps to a PROV-N syntax element.</p>
-<div style="text-align: left; ">
-<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tr><td><b><a href="#dfn-mentionof">Mention</a></b></td><td><b>Non-Terminal</b></td></tr>
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-
-
-<tr><td><a href="#mention.specificEntity"><span class='attribute' id="mention.specificEntity">specificEntity</span></a></td><td><code class="content"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-
-<tr><td><a href="#mention.generalEntity"><span class='attribute' id="mention.generalEntity">generalEntity</span></a></td><td><code class="content"><a class="grammarRef" href="http://www.w3.org/TR/2012/CR-prov-n-20121211/#prod-eIdentifier">eIdentifier</a></code></td></tr>
-
-<tr><td><a href="#mention.bundle"><span class='attribute' id="mention.bundle">bundle</span></a></td><td><code class="content"><a class="grammarRef" href="#prod-bIdentifier">bIdentifier</a></code></td></tr>
-
-</table>
-</div>
-
-
-
-<div class="anexample" id="anexample-mention-rating">
-<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
-<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
-
-<pre class="codeexample">
-bundle ex:run1
- activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
- wasAssociatedWith(ex:a1, ex:Bob, [prov:role="controller"])
-endBundle
-
-bundle ex:run2
- activity(ex:a2, 2011-11-17T10:00:00, 2011-11-17T17:00:00) //duration: 7hours
- wasAssociatedWith(ex:a2, ex:Bob, [prov:role="controller"])
-endBundle
-</pre>
-<p>The performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a mention of <span class="name">ex:Bob</span> as described in bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours.
-
-<pre class="codeexample">
-bundle tool:analysis01
- agent(tool:Bob-2011-11-16, [perf:rating="good"])
- mentionOf(tool:Bob-2011-11-16, ex:Bob, ex:run1)
-
- agent(tool:Bob-2011-11-17, [perf:rating="bad"])
- mentionOf(tool:Bob-2011-11-17, ex:Bob, ex:run2)
-endBundle
-</pre>
-</div>
-
-
-<div class="anexample" id="aexample-mention-viz">
-<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
-<pre class="codeexample">
-bundle obs:bundle1
- entity(ex:report1, [ prov:type="report", ex:version=1 ])
- wasGeneratedBy(ex:g1; ex:report1, -, 2012-05-24T10:00:01)
- entity(ex:report2, [ prov:type="report", ex:version=2 ])
- wasGeneratedBy(ex:g2; ex:report2, -, 2012-05-25T11:00:01)
- wasDerivedFrom(ex:report2, ex:report1)
-endBundle
-entity(obs:bundle1, [ prov:type='prov:Bundle' ])
-wasAttributedTo(obs:bundle1, ex:observer01)
-</pre>
-Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool. It may useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered. The original bundle obviously cannot be changed. However, one can create a new bundle, as follows.
-<pre class="codeexample">
-bundle tool:bundle2
- entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
- wasAttributedTo(tool:bundle2, viz:Visualizer)
-
- entity(tool:report1, [ viz:color="orange" ])
- mentionOf(tool:report1, ex:report1, obs:bundle1)
-
- entity(tool:report2, [ viz:color="blue" ])
- mentionOf(tool:report2, ex:report2, obs:bundle1)
-endBundle
-</pre>
-
-<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
-
-<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
-</p>
-
-<p>The visualisation tool
- created new identifiers <span class="name">tool:report1</span> and
-<span class="name">tool:report2</span>.
-They denote entities which are specializations of <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle1</span>, with visualization attribute for the color to be used when rendering these entities. </p>
-
-</div>
-
-
-
-</section>
-
-
-
-<section id="mention-ontology">
- <h2>Ontological Definition of Mention</h2>
-
-<p>The ternary relation <a>mentionOf</a> is encoded as two properties:
-<a href="#mentionOf">prov:mentionOf</a> and
-<a href="#asInBundle">prov:asInBundle</a>, defined as follows.</p>
-
-<div class="entity" id="mentionOf">
- <h3 id="property--prov-mentionof-op-----------------back-to-expanded-properties">
- Property: <a href="#mentionOf"><span title="http://www.w3.org/ns/prov#mentionOf" class="dotted">prov:mentionOf</span></a> <sup title="object property" class="type-op">op</sup>
-
- </h3>
- <p><strong class="crossreference">IRI:</strong>http://www.w3.org/ns/prov#mentionOf</p>
-
-
- <div class="description">
- <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
- </div>
- <div class="comment "><p>prov:asInBundle is used to cite the Bundle in which the generalization was mentioned.</p>
- </div>
- <dl>
-
- <dt>has super-properties</dt>
- <dd>
- <ul>
- <li>
- <a class="owlclass" href="#specializationOf" title="http://www.w3.org/ns/prov#specializationOf">prov:specializationOf</a> <sup title="object property" class="type-op">op</sup>
- </li>
- </ul>
- </dd>
-
- <dt>has domain</dt>
- <dd>
- <ul>
- <li>
- <a class="owlclass" href="#Entity" title="http://www.w3.org/ns/prov#Entity">prov:Entity</a>
- </li>
- </ul>
- </dd>
-
- <dt>has range</dt>
- <dd>
- <ul>
- <li>
- <a class="owlclass" href="#Entity" title="http://www.w3.org/ns/prov#Entity">prov:Entity</a>
- </li>
- </ul>
- </dd>
-
- <dt>PROV-DM term</dt>
- <dd>
- <a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/Overview.html#term-mention" title="prov-dm">mention</a> </dd>
-
- </dl>
- </div>
- </div>
-
-
-<div class="entity" id="asInBundle">
- <h3 id="property--prov-asinbundle-op-----------------back-to-expanded-properties">
- Property: <a href="#asInBundle"><span title="http://www.w3.org/ns/prov#asInBundle" class="dotted">prov:asInBundle</span></a> <sup title="object property" class="type-op">op</sup>
- </h3>
- <p><strong class="crossreference">IRI:</strong>http://www.w3.org/ns/prov#asInBundle</p>
-
-
- <div class="description">
- <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
- </div>
- <dl>
- <dt>has domain</dt>
- <dd>
- <ul>
- <li>
- <a class="owlclass" href="#Entity" title="http://www.w3.org/ns/prov#Entity">prov:Entity</a>
- </li>
- </ul>
- </dd>
-
- <dt>has range</dt>
- <dd>
- <ul>
- <li>
- <a class="owlclass" href="#Bundle" title="http://www.w3.org/ns/prov#Bundle">prov:Bundle</a>
- </li>
- </ul>
- </dd>
-
- <dt>PROV-DM term</dt>
- <dd>
- <a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/Overview.html#term-mention" title="prov-dm">mention</a> </dd>
-
- </dl>
- </div>
- </div>
-
- <div class="anexample" typeof="prov:Entity" about="#example-for-property-mentionOf">
- <span resource="http://www.w3.org/ns/prov#mentionOf" rel="dcterms:subject"></span>
-
-<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example REF</span></a>, encoding in RDF the rating of Bob in the context of the second activity.</p>
-
- <pre property="prov:value" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_mentionOf.ttl" rel="prov:wasQuotedFrom">@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
-@prefix owl: <http://www.w3.org/2002/07/owl#> .
-@prefix prov: <http://www.w3.org/ns/prov#> .
-@prefix tool: <http://example.com/tool/> .
-@prefix perf: <http://example.com/performance/> .
-@prefix : <http://example.com/> .
-
-:run2 {
- :activity_2
- a prov:Activity;
- prov:startedAtTime "2011-11-17T10:00:00"^^xsd:dateTime;
- prov:endedAtTime "2011-11-17T17:00:00"^^xsd:dateTime;
- prov:wasAssociatedWith :bob;
- .
-}
-
-tool:analysis_01 {
- tool:bob-2011-11-17
- a prov:Agent;
- prov:mentionOf :bob;
- prov:asInBundle :run2;
- perf:rating perf:very-slow;
- .
-}
-
-# This is inferred from prov:mentionOf
-tool:bob-2011-11-17 prov:specializationOf :bob .
-
-# This is inferred from prov:specializationOf
-tool:bob-2011-11-17 prov:alternateOf :bob .
-</pre>
- </div>
-</section>
-
-
-<section id="mention-xml">
- <h2>XML Schema for Mention</h2>
-
-
-
-<p>Type definition in XML Schema:</p><pre class="schema-type"><xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Mention">
- <xs:sequence>
- <xs:element name="specificEntity" type="prov:EntityRef"/>
- <xs:element name="generalEntity" type="prov:EntityRef"/>
- <xs:element name="bundle" type="prov:EntityRef"/>
- </xs:sequence>
-</xs:complexType>
-</pre>
-<p>Usage in XML:</p><pre class="schema-usage"><xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="mentionOf" type="prov:Mention"/>
-</pre>
-<div class="anexample">
-<pre><prov:document
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:prov="http://www.w3.org/ns/prov#"
- xmlns:ex="http://example.com/ns/ex#"
- xmlns:perf="http://example.com/ns/perf#"
- xmlns:tool="http://example.com/ns/tool#">
-
- <prov:bundle prov:id="ex:run1">
- <prov:activity prov:id="ex:a1">
- <prov:startTime>2011-11-16T16:00:00</prov:startTime>
- <prov:endTime>2011-11-16T17:00:00</prov:endTime>
- </prov:activity>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="ex:a1" />
- <prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
- </prov:wasAssociatedWith>
- </prov:bundle>
-
- <prov:bundle prov:id="ex:run2">
- <prov:activity prov:id="ex:a2">
- <prov:startTime>2011-11-17T10:00:00</prov:startTime>
- <prov:endTime>2011-11-17T17:00:00</prov:endTime>
- </prov:activity>
-
- <prov:wasAssociatedWith>
- <prov:activity prov:ref="ex:a2" />
- <prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
- </prov:wasAssociatedWith>
- </prov:bundle>
-
- <prov:bundle prov:id="tool:analysis01">
- <prov:agent prov:id="tool:Bob-2011-11-16">
- <ex:perfrating>good</ex:perfrating>
- </prov:agent>
-
- <b><prov:mentionOf>
- <prov:specificEntity prov:ref="tool:Bob-2011-11-16" />
- <prov:generalEntity prov:ref="ex:Bob" />
- <prov:bundle prov:ref="ex:run1" />
- </prov:mentionOf></b>
-
- <prov:agent prov:id="tool:Bob-2011-11-17">
- <ex:perfrating>bad</ex:perfrating>
- </prov:agent>
-
- <b><prov:mentionOf>
- <prov:specificEntity prov:ref="tool:Bob-2011-11-17" />
- <prov:generalEntity prov:ref="ex:Bob" />
- <prov:bundle prov:ref="ex:run2" />
- </prov:mentionOf></b>
- </prov:bundle>
-
-</prov:document></pre></div>
-</section>
-
-
-<div id="glossary_div" class="remove">
-<!-- glossary loaded from glossary.js will be hooked up here,
- class remove, will remove this element from the final output.
--->
-</div>
-<div id="grammar_div" class="remove">
-<!-- grammar loaded from glossary.js will be hooked up here,
- class remove, will remove this element from the final output.
--->
-</div>
-
-
-<section id="mention-constraints">
- <h2>Constraints associated with Mention</h2>
-
-
-
-
-
- <p id="mention-specialization-inference_text">If one entity is a mention of another in a bundle, then the former is also a specialization of the latter:</p>
-
- <div class='inference' id="mention-specialization-inference">
-<p>
-<span class='conditional'>IF</span> <span class='name'>mentionOf(e2,e1,b)</span> <span class='conditional'>THEN</span> <span class='name'>specializationOf(e2,e1)</span>.</p>
- </div>
-
-
-
-
-<div id='unique-mention_text'>
-<p>An entity can be the subject of at most one mention relation.</p>
-</div>
-
-
-<div class='constraint' id='unique-mention'>
-<p>
-<span class='conditional'>IF</span> <span class="name">mentionOf(e, e1, b1)</span> and <span class="name">mentionOf(e, e2, b2)</span>,
-<span class='conditional'>THEN</span> <span class="name">e1</span>=<span class="name">e2</span> and <span class="name">b1</span>=<span class="name">b2</span>.</p>
-</div>
-
-
-
-</section>
-
-
-
-<section class="appendix">
- <h2>Acknowledgements</h2>
- <p>
-
-This document has been produced by the PROV Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks to Ivan Herman and Sandro Hawke (W3C/MIT).
- </p>
-
-<p>
-Members of the PROV Working Group at the time of publication of this document were:
-
-Ilkay Altintas (Invited expert),
-Reza B'Far (Oracle Corporation),
-Khalid Belhajjame (University of Manchester),
-James Cheney (University of Edinburgh, School of Informatics),
-Sam Coppens (IBBT),
-David Corsar (University of Aberdeen, Computing Science),
-Stephen Cresswell (The National Archives),
-Tom De Nies (IBBT),
-Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
-Simon Dobson (Invited expert),
-Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
-Kai Eckert (Invited expert),
-Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
-James Frew (Invited expert),
-Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
-Daniel Garijo (Universidad Politécnica de Madrid),
-Yolanda Gil (Invited expert),
-Ryan Golden (Oracle Corporation),
-Paul Groth (Vrije Universiteit),
-Olaf Hartig (Invited expert),
-David Hau (National Cancer Institute, NCI),
-Sandro Hawke (W3C/MIT),
-Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
-Ivan Herman, (W3C/ERCIM),
-Ralph Hodgson (TopQuadrant),
-Hook Hua (Invited expert),
-Trung Dong Huynh (University of Southampton),
-Graham Klyne (University of Oxford),
-Michael Lang (Revelytix, Inc.),
-Timothy Lebo (Rensselaer Polytechnic Institute),
-James McCusker (Rensselaer Polytechnic Institute),
-Deborah McGuinness (Rensselaer Polytechnic Institute),
-Simon Miles (Invited expert),
-Paolo Missier (School of Computing Science, Newcastle university),
-Luc Moreau (University of Southampton),
-James Myers (Rensselaer Polytechnic Institute),
-Vinh Nguyen (Wright State University),
-Edoardo Pignotti (University of Aberdeen, Computing Science),
-Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
-Carl Reed (Open Geospatial Consortium),
-Adam Retter (Invited Expert),
-Christine Runnegar (Invited expert),
-Satya Sahoo (Invited expert),
-David Schaengold (Revelytix, Inc.),
-Daniel Schutzer (FSTC, Financial Services Technology Consortium),
-Yogesh Simmhan (Invited expert),
-Stian Soiland-Reyes (University of Manchester),
-Eric Stephan (Pacific Northwest National Laboratory),
-Linda Stewart (The National Archives),
-Ed Summers (Library of Congress),
-Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
-Ted Thibodeau (OpenLink Software Inc.),
-Curt Tilmes (National Aeronautics and Space Administration),
-Craig Trim (IBM Corporation),
-Stephan Zednik (Rensselaer Polytechnic Institute),
-Jun Zhao (University of Oxford),
-Yuting Zhao (University of Aberdeen, Computing Science).
-</p>
- </section>
-
-
- </body>
-</html>