provtools.github.io/index.xml at master · ProvTools/provtools.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ProvTools</title>
    <link>http://provtools.org/</link>
    <description>Recent content on ProvTools</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>

	<atom:link href="http://provtools.org/index.xml" rel="self" type="application/rss+xml" />


    <item>
      <title>CPL</title>
      <link>http://provtools.org/stores/cpl/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/stores/cpl/</guid>
      <description></description>
    </item>

    <item>
      <title>Provenance</title>
      <link>http://provtools.org/faq/provenance/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/faq/provenance/</guid>
      <description>What is provenance? Provenance is information about the processes that used and produced data.
Why use it? Knowing the relationships among computational processes and data allows us to conduct formal analyses about entire computer pipelines without having to re-run it. In other words, although having code and input data permits reproduction, there&amp;rsquo;s is no way of positively knowing what the software will do without running.
More info on provenance provenance@harvard</description>
    </item>

    <item>
      <title>Rclean</title>
      <link>http://provtools.org/analyzes/rclean/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/analyzes/rclean/</guid>
      <description></description>
    </item>

    <item>
      <title>provR</title>
      <link>http://provtools.org/captures/provr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/captures/provr/</guid>
      <description></description>
    </item>

    <item>
      <title>CamFlow</title>
      <link>http://provtools.org/captures/camflow/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/captures/camflow/</guid>
      <description></description>
    </item>

    <item>
      <title>cplR</title>
      <link>http://provtools.org/stores/cplr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/stores/cplr/</guid>
      <description></description>
    </item>

    <item>
      <title>encapsulator</title>
      <link>http://provtools.org/analyzes/encapsulator/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/analyzes/encapsulator/</guid>
      <description></description>
    </item>

    <item>
      <title>provDown</title>
      <link>http://provtools.org/analyzes/provdown/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/analyzes/provdown/</guid>
      <description></description>
    </item>

    <item>
      <title>provViz</title>
      <link>http://provtools.org/analyzes/provviz/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>http://provtools.org/analyzes/provviz/</guid>
      <description></description>
    </item>

  </channel>
</rss>