--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/overview/prov-overview.html Tue Dec 04 12:13:01 2012 +0100
@@ -0,0 +1,552 @@
+<!DOCTYPE html
+>
+
+<html><head>
+ <title>PROV-Overview</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <!--
+ === NOTA BENE ===
+ For the three scripts below, if your spec resides on dev.w3 you can check them
+ out in the same tree and use relative links so that they'll work offline,
+ -->
+<link href="datatable.css" rel="stylesheet" type="text/css" />
+
+
+ <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>
+
+ <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 src="../model/glossary.js" class="remove"></script>
+ <script src="../model/provbib.js" class="remove"></script>
+
+
+ <script class="remove">
+function insertProductionDefinition(doc, content, name) {
+
+ var xml=$.parseXML(content);
+
+ var segment = $(xml).find('a[name~="' + name + '"]').parents("tbody")[0];
+
+// return doc._esc((new XMLSerializer()).serializeToString(segment));
+ return (new XMLSerializer()).serializeToString(segment);
+}
+
+function insertProductionGeneration(doc, content) { return insertProductionDefinition(doc,content,'prod-prov_n_LL-generationExpression'); }
+
+ </script>
+ <script class="remove">
+ function updateGlossaryRefs() {
+ $('.glossary-ref').each(function(index) {
+ var ref=$(this).attr('data-ref');
+ var span=$(this).attr('data-withspan')
+ $(this).removeAttr('data-withspan');
+ $(this).removeAttr('data-ref');
+
+ $('#'+ref+'.glossary').contents().clone().appendTo($(this));
+// $(this).attr("prov:hadOriginalSource",glossary_hg);
+ if (span) {
+ $(this).children('dfn').replaceWith(function(){return $('<span>').addClass('dfn').append($(this).contents())});
+ }
+ });
+ }
+
+ // function to replace figcaption since not allowed by prov rules, and not transformed by respec.js
+ function updateFigCaptions() {
+ var figureCount=1;
+
+ $('figcaption').each(function(index) {
+
+ var myid=$(this).attr('id');
+ var mycount=figureCount++;
+
+ $(this).replaceWith(function(){return $('<span>').addClass('figcaption').attr('data-count', mycount).attr('id',myid).append("Figure " + mycount)
+.append($('<sup>').append($('<a>').addClass('internalDFN').attr('href','#'+myid).append($('<span>').addClass('diamond').append(" ◊:")))).append(" ")
+.append($(this).contents())});
+ });
+ }
+
+ // function to update caption with linkable diamond
+ function updateCaptions() {
+ var tableCount=1;
+
+ $('caption').each(function(index) {
+
+ var myid=$(this).attr('id');
+ var mycount=tableCount++;
+
+ $(this).attr('data-count', mycount)
+.prepend($('<span>').append("Table " + mycount)
+ .append($('<sup>').append($('<a>').addClass('internalDFN').attr('href','#'+myid).append($('<span>').addClass('diamond').append(" ◊:")))).append(" "))
+ });
+ }
+
+ // function to replace figure since not allowed by prov rules, and not transformed by respec.js
+ function updateFigures() {
+ $('figure').each(function(index) {
+
+ var myid=$(this).attr('id');
+ var mystyle=$(this).attr('style');
+
+ console.log( "figure " + myid + " " + $(this).contents());
+
+ $(this).replaceWith(function(){
+ var aNewElement=$('<span>').addClass('figure').append($(this).contents());
+ if (myid) {
+ aNewElement.attr('id',myid)
+ }
+ if (mystyle) {
+ aNewElement.attr('style',mystyle)
+ }
+ return aNewElement });
+
+
+
+ // $(this).replaceWith(function(){return $('<span>').addClass('figure').attr('id',myid).attr('style',mystyle).append($(this).contents())});
+ console.log( "figure " + myid);
+ });
+ }
+
+ function updateExamples() {
+ var count=1;
+ $('.anexample').each(function(index) {
+
+ var myid=$(this).attr('id');
+ var mycount=count++;
+
+ if (myid==undefined) {
+ myid='example_' + mycount;
+ $(this).attr('id',myid);
+ }
+
+
+ $(this).attr('data-count', mycount).prepend($('<div>').addClass('anexampleTitle')
+ //.append($('<a>').addClass('internalDFN').attr('href','#'+myid).append("Example " + mycount))
+ .append("Example " + mycount)
+ .append($('<sup>').append($('<a>').addClass('internalDFN').attr('href','#'+myid).append($('<span>').addClass('diamond').append(" ◊"))))
+ );
+
+
+ //console.log( "example for " + myid + " " + mycount);
+
+ });
+ }
+
+
+
+ function updateDfn() {
+ var count=1;
+ $('dfn').each(function(index) {
+
+ var myid=$(this).addClass('internalDFN').attr('id');
+
+ $(this).after($('<sup>').append($('<a>').addClass('internalDFN').attr('href','#'+myid).append($('<span>').addClass('diamond').append(" ◊")))); //◊//♦
+
+// console.log( "dfn for " + myid + " ");
+
+ });
+ }
+
+
+ function updateExamplesRefs() {
+ $('.anexample-ref').each(function(index) {
+
+ myhref=$(this).attr('href');
+
+ //console.log( "example ref for " + myhref);
+
+ mycount=$(myhref).attr('data-count');
+
+ //console.log( "example ref for " + myhref + " " + mycount);
+
+ $(this).children('span').replaceWith(function(){return $('<span>').append("Example " + mycount)});
+
+ });
+
+ $('.anexample').each(function(index) {
+ $(this).removeAttr('data-count');
+ });
+
+ $('caption').each(function(index) {
+ $(this).removeAttr('data-count');
+ });
+
+ $('.figcaption').each(function(index) {
+ $(this).removeAttr('data-count');
+ });
+
+ }
+
+
+ function updateSectionRefs() {
+
+ $('.section-ref').each(function(index) {
+
+ myhref=$(this).attr('href');
+
+ console.log( "section ref for " + myhref);
+
+ if (myhref.startsWith("#")) {
+
+
+ //Problem, this returns all span.secno elements, and concatenates their text
+ // I shoul just get the first one
+ mysectionNumber=$(myhref).find('span.secno').first().text().trim();
+
+
+
+
+ console.log( "section ref for " + myhref + " " + mysectionNumber);
+
+ $(this).children('span').replaceWith(function(){return $('<span>').append("Section " + mysectionNumber)});
+
+ }
+
+ });
+ }
+
+
+
+ $(document).ready(function(){
+ // if glossary is in a string:
+ $('#glossary_div').html(glossary_string)
+ updateGlossaryRefs();
+ updateFigCaptions();
+ updateCaptions();
+ 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 = {
+
+ };
+
+ 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-overview",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ subtitle : "An Overview of the PROV Family of Documents",
+
+
+ // 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: "2012",
+
+ // 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/overview/prov-overview.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", "../model/extra-dm.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
+ company: "VU University Amsterdam" },
+ { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
+ company: "University of Southampton" },
+
+ ],
+
+ // 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. The PROV Family of Documents defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web. This document provides an overview this family of documents.
+
+ </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> PROV-OVERVIEW (To be published as Note), an overview of the PROV family of documents (this document); </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-dc-20121211/">PROV-DC</a> (To be published as Note), describes a mapping between Dublin Core and PROV [[PROV-DC]].</li>
+<li> <a href="http://www.w3.org/TR/2012/WD-prov-links-20121211/">PROV-LINKS</a> (To be published as Note), introduces a mechanism to link across bundles [[PROV-LINKS]].</li>
+</ul>
+
+</section>
+
+<section id="introduction">
+ <h2>Introduction</h2>
+This document provides a non-normative overview of the PROV Family of Documents and provides a roadmap to using these these documents.
+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. The goal of PROV is to enable the wide publication and interchange of provenance on the Web and other information systems. PROV enables one to represent and interchange provenance information using widely available formats such as RDF and XML. In addition, it provides definitions for accessing provenance information, validating it, and mapping to Dublin Core.
+
+<p>
+Below is the organization of PROV. At its core is a conceptual data model, which defines a common vocabulary used to describe provenance. This is instantiated by various serializations. These serializations are what are used by implementations to interchange provenance. To help developers and users create valid provenance, a set of constraints are defined, which can be used to create provenance validators. Finally, to further support the interchange of provenance, additional definitions are provided for protocols to locate and access provenance, connect sets of provenance descriptions and define how to interoperate with the widely used Dublin Core vocabulary.
+</p>
+
+<div>
+<img alt="Organization of PROV" src="./prov-family.png">
+</div>
+
+</section>
+
+<section id="roadmap">
+<h2>Document Roadmap</h2>
+PROV consists of 10 documents (including this one). In order to use PROV, one need not be familiar with all of these documents. Indeed, PROV was specifically designed so that users and developers may get started quickly with basic usage and then incrementally progress to more advanced usage scenarios To help navigate PROV, each document is broadly classified as being intended for a specific audience.
+
+<ol>
+<li> Users - this audience wants to understand PROV and use applications that support PROV.
+<li> Developers - this audience wants to develop or build applications that create and consume provenance using PROV.
+<li> Advanced - this audience aims to create validators, new PROV serializations, or other advanced provenance systems.
+</ol>
+
+In the table below, we also denote the track that each document on whether it is intended to be a W3C Recommendation or a Working Group Note.
+
+<table class="open-data-table">
+<tr><th>Part</th><th>Audience</th><th>Type</th><th>Document</th></tr>
+<tr><td style="text-align: center;">1</td><td style="background: #DFF">Users</td><td>Note</td><td><a href="http://www.w3.org/TR/2012/WD-prov-primer-20121211/">PROV-PRIMER</a> is the entry point to PROV offering an introduction to the provenance model. This is where you should start and for many may be the only document needed.</td></tr>
+<tr><td style="text-align: center;">2</td><td style="background: #CDD">Developers</td><td>Rec</td><td><a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/">PROV-O</a> defines a light-weight OWL2 ontology for the provenance model. This is intended for the Linked Data and Semantic Web community. </td></tr>
+<tr><td style="text-align: center;">3</td><td style="background: #CDD">Developers</td><td>Note</td><td><a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211">PROV-XML</a> defines an XML schema for the provenance model. This is intended for developers who need a native XML serialization of PROV</td></tr>
+<tr><td style = "text-align: center;">4</td><td style="background: #FDD">Advanced</td><td>Rec</td><td><a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">PROV-DM</a> defines a conceptual data model for provenance including UML diagrams. PROV-O and PROV-XML are serializations of this conceptual model.</td></tr>
+<tr><td style = "text-align: center;">5</td><td style="background: #FDD">Advanced</td><td>Rec</td><td><a href="http://www.w3.org/TR/2012/CR-prov-n-20121211/">PROV-N</a> defines a human-readable notation for provenance. This is used to define the conceptual model as well as PROV-CONSTRAINTS. </td></tr>
+<tr><td style = "text-align: center;">6</td> <td style="background: #FDD">Advanced</td><td>Rec</td><td> <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/">PROV-CONSTRAINTS</a> defines a set constraints that define a notion of valid provenance. It is specifically aimed at the implementors of validators. </td></tr>
+<tr><td style="text-align: center;">7</td><td style="background: #CDD">Developers</td><td>Note</td><td><a href="http://www.w3.org/TR/2012/WD-prov-aq-20120619/">PROV-AQ</a> defines how to use Web-based mechanisms to locate and retrieve provenance information. </td></tr>
+<tr><td style="text-align: center;">8</td><td style="background: #CDD">Developers</td><td>Note</td><td><a href="https://dvcs.w3.org/hg/prov/raw-file/default/dc-note/Overview.html">PROV-DC</a> defines a mapping between Dublin Core and PROV. </td></tr>
+<tr><td style = "text-align: center;">9</td><td style="background: #FDD">Advanced</td><td>Note</td><td><a href="http://dvcs.w3.org/hg/prov/raw-file/default/links/prov-links.html">PROV-LINKS</a> Defines extensions to PROV to enable linking provenance information across containers for provenance</td></tr>
+
+</table>
+
+</section>
+
+<section>
+<h2>Additional Information</h2>
+In addition, to these specifications, the <a href="http://www.w3.org/2001/sw/wiki/PROV-FAQ">PROV FAQ</a> page addresses common questions as well as sets PROV in a broader context. This page is continually updated. Working group members have also given several <a href="http://www.w3.org/2011/prov/wiki/OutreachInformation">tutorials</a> about PROV including hands-on exercises, these may be a useful place to start. In addition, one can find a variety of blog posts and web pages on PROV - a short list can be found <a href="http://www.w3.org/2011/prov/wiki/OutreachInformation">here</a>.
+
+For a broader review of provenance that led to the creation of PROV, there are several reports produced by the <a href="http://www.w3.org/2005/Incubator/prov/wiki/W3C_Provenance_Incubator_Group_Wiki">W3C Provenance Incubator group</a> including:
+
+<ol>
+<li> <a href="http://www.w3.org/2005/Incubator/prov/wiki/images/0/02/Provenance-XG-Overview.pdf"> An Overview of Provenance on the Web (slideshow - pdf)</a></li>
+<li> <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/#Requirements_for_provenance">Requirements for Provenance on the Web</a></li>
+<li> <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/#State_of_the_art_and_technology_gaps">State of the Art Report</a></li>
+</ol>
+
+Finally, the simplest way to use PROV is through one of the many <a href="http://www.w3.org/2011/prov/wiki/ProvImplementations">applications</a> that support it.
+
+
+</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>
+
+
+
+<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.
+ </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>