-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathparticipating.html
More file actions
175 lines (135 loc) · 7.67 KB
/
participating.html
File metadata and controls
175 lines (135 loc) · 7.67 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
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
<!DOCTYPE html>
<html lang="en">
<head>
<title>Structured Commons :: Participating</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><a href="http://www.structured-commons.org/org.html">Organization</a></li>
<li class="active"><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>Participating</h1>
<p>How <em>you</em> can participate:</p>
<dl class="docutils">
<dt><strong>As an author</strong>, <em>any</em> of the following helps:</dt>
<dd><ul class="first last simple">
<li><strong>display fingerprints</strong> and Structured Commons access links for
your content on your personal web page, blog or social network.</li>
<li><strong>announce</strong> your work, even "non-public" objects, by registering
<strong>certificates of existence</strong> and publishing your <strong>object
metadata</strong> in part or in full in the Structured Commons network.</li>
<li><strong>request custom licensing</strong> agreements when publishing your work
with "traditional" journals or conferences, so you keep the
right to distribute your own copies independently from your
publisher. (Suprisingly, most publishers are willing to cooperate!)</li>
<li><strong>release your work on public data stores</strong> to seed the Structured
Commons network, when you own licensing rights or have the right
to redistribute.</li>
</ul>
</dd>
<dt><strong>As a scholar</strong> who reads, cites or reviews scientific work, <em>any</em> of the following helps:</dt>
<dd><ul class="first last simple">
<li><strong>use fingerprints</strong> in citations when your new works refer to
objects that already exist in the Structured Commons network.</li>
<li><strong>publish your reviews</strong> in the Structured Commons network while
you participate in conference program committees or journal
editorial boards.</li>
<li><strong>publish post-hoc citations</strong> when you discover a link between
otherwise unconnected scientific works.</li>
<li><strong>use Structured Commons query engines</strong> to discover and rank
the "top" publications in your field, based on object metadata, published
reviews and post-hoc citations.</li>
<li><strong>run a personal data store</strong> to share non-public documents and digital objects
with specific colleagues, friends, reviewers and selected peers.</li>
</ul>
</dd>
<dt><strong>As a journal editor or conference organizer</strong>, <em>any</em> of the following helps:</dt>
<dd><ul class="first last simple">
<li><strong>advocate</strong> Structured Commons best practices to authors
and reviewers, especially pre-submission content registration
and fingerprint-based citations.</li>
<li><strong>register review objects</strong> in the Structued Commons network
using certificates of existence during the review process.</li>
<li><strong>offer to publish reviews</strong> to authors, after review processes are completed.</li>
</ul>
</dd>
<dt><strong>As a publisher</strong>, <em>any</em> of the following helps:</dt>
<dd><ul class="first last simple">
<li><strong>Display fingerprints</strong> next to Structured Commons content on your
publication media.</li>
<li>Provide <strong>access links</strong> to one or more download methods
in the Structured Commons network for both the <strong>source</strong> objects
and the <strong>representations</strong> of the content you publish.</li>
</ul>
</dd>
<dt><strong>As a supporting organization</strong>, <em>any</em> of the following helps:</dt>
<dd><ul class="first last simple">
<li><strong>provide services to authors</strong> to support document creation,
editing, packaging, fingerprinting and uploading to the Structured
Commons network.</li>
<li><strong>run public data stores</strong> to support object long-term storage,
dissemination, access and metadata indexing.</li>
<li><strong>run query engines</strong> and web portals for them to enable users
search, filter and order object listings based on metadata.</li>
<li><strong>reward academic staff</strong> who participate in the Structured Commons network
by publishing new works or reviews.</li>
</ul>
</dd>
<dt><strong>As a technology developer</strong>, <em>any</em> of the following helps:</dt>
<dd><ul class="first last simple">
<li><strong>Extend your databases</strong> to include Structured Commons fingerprints
and access links for online content.</li>
<li><strong>Define and publish fingerprinting methods</strong> for new document formats with
a separation between "source" and "published" forms.</li>
<li><strong>Design and implement metadata extraction algorithms</strong> for Structured Commons digital objects
without author-supplied metadata.</li>
<li><strong>Participate</strong> in the Structured Commons technology steering committee by contributing
protocol specifications, guidelines, reference implementations or advocacy materials.</li>
</ul>
</dd>
</dl>
</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>