-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathorg.html
More file actions
157 lines (117 loc) · 7.13 KB
/
org.html
File metadata and controls
157 lines (117 loc) · 7.13 KB
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
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
<!DOCTYPE html>
<html lang="en">
<head>
<title>Structured Commons :: Organization</title>
<meta charset="utf-8" />
<link href="http://www.structured-commons.org/feeds/all.atom.xml" type="application/atom+xml" rel="alternate" title="Structured Commons Full Atom Feed" />
<!-- Mobile viewport optimized: j.mp/bplateviewport -->
<meta name="viewport" content="width=device-width,initial-scale=1, maximum-scale=1">
<link rel="stylesheet" type="text/css" href="http://www.structured-commons.org/theme/gumby.css" />
<link rel="stylesheet" type="text/css" href="http://www.structured-commons.org/theme/style.css" />
<link rel="stylesheet" type="text/css" href="http://www.structured-commons.org/theme/pygment.css" />
<script src="http://www.structured-commons.org/theme/js/libs/modernizr-2.6.2.min.js"></script>
</head>
<body id="index" class="home">
<div class="container">
<div class="row">
<header id="banner" class="body">
<h1><a href="http://www.structured-commons.org">Structured Commons <strong></strong></a></h1>
</header><!-- /#banner -->
<div id="navigation" class="navbar row">
<a href="#" gumby-trigger="#navigation > ul" class="toggle"><i class="icon-menu"></i></a>
<ul class="columns">
<li><a href="http://www.structured-commons.org/online-forum.html">Forum</a></li>
<li><a href="http://www.structured-commons.org/index.html">About</a></li>
<li><a href="http://www.structured-commons.org/mission.html">Mission statement</a></li>
<li class="active"><a href="http://www.structured-commons.org/org.html">Organization</a></li>
<li><a href="http://www.structured-commons.org/participating.html">Participating</a></li>
<li><a href="http://www.structured-commons.org/scep0000.html">SCEPs</a></li>
</ul>
</div>
<h1>Organization</h1>
<p>The Structured Commons <strong>project</strong> is to <strong>develop</strong> and <strong>promote</strong>
the Structured Commons model and network, as a new way for scholars to
"do" academic publishing. See the <a class="reference external" href="mission.html">Mission Statement</a> for an overview of the goals.</p>
<p>The <strong>strategy</strong> to achieve this is illustrated by the following figure:</p>
<img alt="Diagram of the Structured Commons dual approach." class="align-center" src="sc-focus.png" style="width: 80%;" />
<p>In short, the initiative is <em>dual-headed</em>:</p>
<ul class="simple">
<li>a <strong>model-centered approach</strong> based on <strong>advocacy</strong>, tailored to
audiences sensitive to innovation in science
evaluation (how to best perform peer review), innovation in
long-term archival and persistence of the citation network,
competition with the legacy publishing industry, and progressive
evolution of the sociological aspects around science (eg. alternate
performance metrics).</li>
<li>a <strong>technology-centered approach</strong> based on <strong>gradual adoption</strong>
via "grassroots" tooling initiatives, tailored to audiences
sensitive to the practical organization of conferences, workshops
and new-generation journals (eg. how to implement open peer review),
peer-to-peer legal distribution of academic works, structured
re-indexing of legacy document repositories, review-based search <span class="amp">&</span>
filtering, and the cryptographic web-of-trust.</li>
</ul>
<p>The initial drive to achieve this initiative will be provided by the
Structured Commons <strong>Technical Steering Committee</strong> (<span class="caps">SCTSC</span>). This
self-appointed, non-profit group of technology-minded scholars will
push the <span class="caps">SC</span> agenda and temporarily hold the responsibility for
coordinating the definition of the <span class="caps">SC</span> model and network protocols.</p>
<div class="section" id="structured-commons-technical-steering-committee">
<h2>Structured Commons Technical Steering Committee</h2>
<p><strong>Mission:</strong></p>
<ul class="simple">
<li>to advocate the Structured Commons vision and discuss its development;</li>
<li>to maintain a set of "core" specification documents and
reference/example tool implementations;</li>
<li>to publish said documentation and code in the public domain.</li>
</ul>
<p><strong>Current members:</strong></p>
<ul class="simple">
<li>Sebastian Altmeyer, University of Amsterdam, <span class="caps">NL</span></li>
<li>Roy Bakker, University of Amsterdam, <span class="caps">NL</span></li>
<li>Roeland Douma, University of Amsterdam, <span class="caps">NL</span></li>
<li>Raphael Poss, University of Amsterdam, <span class="caps">NL</span></li>
<li>Mark Thompson, <span class="caps">LUMC</span>, <span class="caps">NL</span></li>
</ul>
<p><strong>Duration:</strong> eventually, this steering committee is intended to be
superseded by a network of organizations that follow the Structured
Commons model and support the Structured Commons network.</p>
<p><strong>Membership:</strong> membership to the <span class="caps">SCTSC</span> is free but candidate members should be
affiliated with a recognized academic institution, provide evidence of
basic expertise with the dynamics of academic publishing (including,
but not limited to, an established publication record), and "opted in"
by existing members.</p>
</div>
<div class="section" id="works-maintained-by-the-sctsc">
<h2>Works maintained by the <span class="caps">SCTSC</span></h2>
<ul class="simple">
<li><a class="reference external" href="http://www.structured-commons.org/scep0000.html">Structured Commons Enhancement Proposals</a>, as set of
documents that describe and specify the Structured Commons model and network.</li>
<li><a class="reference external" href="http://github.com/structured-commons/tools">Example tools, libraries and utilities</a> for authors and users of Structured Commons objects and documents.</li>
</ul>
</div>
</div><!-- /.row -->
</div><!-- /.container -->
<div class="container.nopad bg">
<footer id="credits" class="row">
<div class="seven columns left-center">
<address id="about" class="vcard body">
Proudly powered by <a href="http://getpelican.com/">Pelican</a>,
which takes great advantage of <a href="http://python.org">Python</a>.
<br />
Based on the <a target="_blank" href="http://gumbyframework.com">Gumby Framework</a>
</address>
</div>
<div class="seven columns">
<div class="row">
<ul class="socbtns">
</ul>
</div>
</div>
</footer>
</div>
<script src="http://www.structured-commons.org/theme/js/libs/jquery-1.9.1.min.js"></script>
<script src="http://www.structured-commons.org/theme/js/libs/gumby.min.js"></script>
<script src="http://www.structured-commons.org/theme/js/plugins.js"></script>
</body>
</html>