-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
415 lines (306 loc) · 23.4 KB
/
index.html
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
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
---
title: Research Intent Ontology
description: A vocabulary for open research on the Web.
kind: specification
---
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Research Intent Ontology</title>
<script src="respec-w3c-extensions.js" class="remove"></script>
<script src="/js/jsonld.js" class="remove"></script>
<script src="relode.js" class="remove"></script>
<!-- Grab W3C's respec; fall back to local if offline -->
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" async class="remove"></script>
<script>window.respecVersion || document.write('<script src="/js/respec-w3c-common.js" async class="remove"><\/script>')</script>
<script class="remove">
var respecConfig = {
specStatus: "unofficial",
shortName: "research-intent-ontology",
subtitle: "A vocabulary for open research on the Web",
copyrightStart: "2014",
edDraftURI: "<%= path_to(@item, absolute: true) %>",
editors: [
{ name: "Chris Chapman", /*url: "http://cman.ch",*/ w3cid: "61593", company: "Pentandra", companyURL: "https://pentandra.com/" },
],
otherLinks: [{
key: "Version history",
data: [{
value: "Commit history",
href: "https://github.com/pentandra/specifications/commits/master/research-intent-ontology"
}]
}],
alternateFormats: [
{ uri: "rio.ttl", label: "Turtle" },
{ uri: "rio.jsonld", label: "JSON-LD" },
{ uri: "rio.rdf", label: "RDF/XML" },
{ uri: "rio.html", label: "HTML5/RDFa" },
],
localBiblio: localBibliography,
doRDFa: false // Let's do our own for now...
};
</script>
<style type="text/css">
.section { margin-top: 1em; margin-bottom: 1em; }
.resource { border: 1px solid navy; margin: 5px 0; padding: 5px; }
.relationships { border-top: 1px dashed gray; border-bottom: 1px dashed gray; background-color: rgb(242, 243, 244); margin-top: 5px; padding-bottom: 5px; }
.invisible { display: none; }
dl.inline dt, dl.inline dd { display: inline-block; }
dl.inline dd { margin-left: 0.6em; }
dl.inline dt { clear: both; }
table.data-table { font-size: 0.9em; text-align: left; border-style: none; border-collapse: collapse; }
table.data-table th { background-color: #e8e8e8; font-weight: normal; }
table.data-table th:hover { background-color: #f0f0f0; }
table.data-table th, table.data-table td { border: 1px solid #aaa; padding: 0.3em; }
table.data-table th.extended { min-width: 24em; }
.nanotabs ul { padding: 0; margin-top: 0.5em; font-size: 0.8em; }
.nanotabs li { display: inline-block; list-style: none; }
.nanotabs a[href] { display: block; padding: 0.4em 0.8em; border-radius: 2em; background: #fcfaee; color: #b9ab2d; text-decoration: none; }
.nanotabs a[href]:hover { background: #fffce5; color: #550; }
.nanotabs a[href].selected { background: #fff; }
.syntaxmenu { border: 1px dotted black; padding: 0.5em; }
.syntaxmenu.nanotabs ul { font-size: inherit; }
.syntaxmenu.nanotabs a[href] { background: #e0cb52; color: #fff; }
.syntaxmenu.nanotabs a[href]:hover { background: #e0cb52; color: #fff; }
.syntaxmenu.nanotabs a[href].selected { background: #c83500; }
</style>
</head>
<body typeof="schema:TechArticle fabio:SpecificationDocument" prefix="rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# rdfs: http://www.w3.org/2000/01/rdf-schema# owl: http://www.w3.org/2002/07/owl# xsd: http://www.w3.org/2001/XMLSchema# rdfa: http://www.w3.org/ns/rdfa# vs: http://www.w3.org/2003/06/sw-vocab-status/ns# foaf: http://xmlns.com/foaf/0.1/ dc: http://purl.org/dc/terms/ voaf: http://purl.org/vocommons/voaf# prov: http://www.w3.org/ns/prov# schema: http://schema.org/ deo: http://purl.org/spar/deo/ doco: http://purl.org/spar/doco/ fabio: http://purl.org/spar/fabio# rio: https://w3id.org/rio#">
<section id="abstract" resource="#abstract" property="dc:hasPart" typeof="doco:Abstract">
<div property="schema:description">
<div about="[rio:]" property="rdfs:comment">
<p>The Research Intent Ontology is a lightweight, flow-centric framework for open research for the <a href="https://en.wikipedia.org/wiki/Open_Web_Platform">Open Web Platform</a>. The Research Intent Ontology partition research into manageable units, called <dfn>research cases</dfn>, that make explicit the chain of questions that goes through the researcher's mind as research progresses.</p>
<p>Research cases are intended to be powerful enough to describe the most complex and intricate of research problems, and simple enough to be useful for informal research that could be thought of more as proactive learning. Research cases make knowledge creation explicit and allow research and knowledge to be built upon and shared openly and in context across platforms and research disciplines.</p>
</div>
</div>
</section>
<section id="sotd">
<p class="disclaimer">This draft is very much a work in progress. Please don't critique too harshly while we're working on it. Instead, please join in the effort to improve it!</p>
<p>To participate in the development of this specification, please visit <a href="https://researchcases.org">https://researchcases.org</a> and join the mailing list.</p>
</section>
<section id="introduction" resource="#introduction" property="dc:hasPart" typeof="deo:Introduction">
<h2>Introduction</h2>
<p>One of the most common things we do on the Web is to go to our favorite search engine and look something up. Then we click through the results hoping to find what we are looking for. Yet the queries we so generously feed to the search engines do not become part of the Web. They get sent to the search engine service, and they don't come back. This is probably fine when searching for a specific resource on the Web and we can't remember the <a href="https://en.wikipedia.org/wiki/Uniform_Resource_Locator"><abbr title="Uniform Resource Locator">URL</abbr></a> [[rfc1738]], or trying to learn more about a specific concept that is considered public knowledge, for example, in a Wikipedia article, but it doesn't work as well for things that are on the fringe of our collective knowledge spaces—or beyond. We need some way to keep track of where we are in our search for knowledge. Sometimes we don't remember after a half-an-hour of researching has passed by, what it was exactly that we were looking for in the first place. <em>The journey of the researcher matters, and needs to be part of the Web.</em></p>
<p>The end goal of research is to create some new bit of knowledge. This knowledge may be an earth-shattering idea that revolutionizes how we, collectively, think of the world around us (such as the general theory of relativity), or it may be already known to others, and only new to the particular researcher that just discovered it for himself or herself. Research is, at its essence, structured learning and often involves asking a series of ever more refined questions as the research progresses. This series of questions frames the research context and delineates the learning trajectory of the researcher, and is of great value for others that are trying to understand or reconstruct the research later on. Theoretically, every piece of knowledge could trace its roots back to some bit of research that discovered it. Research cases organize and preserve this process. They broaden the scope of what has traditionally been thought of as <i>research</i>, modeling it holistically as the process the researcher goes through from an initial research question all the way to the resultant answer. Anyone can then step backwards and forwards <em>through time</em>, as it were, to see how that bit of knowledge came about.</p>
<p>Most knowledge found on the Web today is taken at face value. The social reputation built up by a knowledge provider is the only thing that influences trust. For a news provider this might be adequate, yet for other things it would be helpful, or even necessary, to see how that knowledge was created before placing trust in it. Research cases open up this process, making provenance of <i>knowledge creation</i> more discernible and transparent, allowing each of us to make more informed and accurate trust judgments.</p>
<section>
<h2>Conformance</h2>
<p>The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [[!rfc2119]].</p>
</section>
<section>
<h2>Syntaxes</h2>
<p>The examples below can be represented by any of <a href="http://www.w3.org/TR/rdf11-primer/#section-graph-syntax">the available syntaxes for RDF</a> [[rdf11-primer]], and we provide Turtle [[turtle]], <abbr title="JavaScript Object Notation for Linked Data">JSON-LD</abbr> [[json-ld]], RDF/XML [[rdf-syntax-grammar-20040210]], and <abbr title="HyperText Markup Language">HTML</abbr>/<abbr title="Resource Description Language in Attributes">RDFa</abbr> [[html-rdfa]] representations of the RDF model. You can control which syntaxes are shown throughout the document by using the buttons below.</p>
<div class="syntaxmenu nanotabs">
<p>The buttons below can be used to select between the available syntaxes.</p>
<ul>
<li><a href="#ttl">Turtle Syntax</a></li>
<li><a href="#jsonld">JSON-LD Syntax</a></li>
<li><a href="#rdfxml">RDF/XML Syntax</a></li>
<li><a href="#rdfa">HTML/RDFa Syntax</a></li>
</ul>
</div>
</section>
</section>
<section class="informative">
<h2>Research Intent Ontology Overview</h2>
<p>The Research Intent Ontology can be used across a wide variety of tools to organize the process of learning and the creation of knowledge. Much like a <a href="https://en.wikipedia.org/wiki/Version_control"><abbr title="Version Control System">VCS</abbr></a> provides a scaffolding of provenance, attribution, and context around the incremental development process of a software codebase, research cases provide a similar scaffolding around the process of knowledge creation. This specification builds upon the efforts of the <a href="http://www.w3.org/TR/prov-overview/">PROV</a> [[prov-overview]] and <a href="http://www.w3.org/annotation/">Web Annotation</a> [[!annotation-model]] communities.</p>
<section>
<h2>At a Glance</h2>
</section>
<section>
<h2>Design Goals and Rationale</h2>
<p>Research cases satisfies the following design goals:</p>
<dl>
<dt>Incremental</dt>
<dd>There is an overwhelming deluge of data, information, and knowledge on the Web. Research cases should provide a scaffolding for this knowledge, so researchers can focus and build on top of this knowledge in a sustainable, incremental way.</dd>
<dt>Pragmatic & lightweight</dt>
<dd>We're aiming for a good balance between simple and comprehensive. We need to be able to preserve the most important elements of the research process without getting bogged down in pointless formalities. Research cases should be as easy as possible for users and developers to understand and implement, and provide an obvious return on investment.</dd>
<dt>Domain agnostic</dt>
<dd>Should work for any domain of knowledge. If domain-specific extensions to the <a href="#cross-reference">core vocabulary</a> are needed, they should be minimal. Research cases enable interoperability across domains of knowledge, working alongside domain-specific vocabularies which describe the objects of the study.</dd>
<dt>Client focused</dt>
<dd>Machines can take the time to connect things that we humans just don't have time for or desire to do on our own. Research cases should make researchers’ lives easier and more productive at the same time, by connecting research to related research and researchers to researchers that are working in similar areas.</dd>
<dt>Researcher centric</dt>
<dd>Research cases are about the researcher’s personal journey through the discovery process. This journey is unique to each researcher, since each one of us has a unique <a href="https://en.wikipedia.org/wiki/World_view">world view</a>. Research cases allow researchers of any skill level pursue what they think needs to be pursued next using the knowledge that they have at the time. If you already know something, you don't need to research it. Looking at it a different way, there is more than one road that can lead to a given answer. <q cite="https://en.wiktionary.org/wiki/all_roads_lead_to_Rome">[Many] roads lead to Rome.</q></dd>
<dt>Open & transparent</dt>
<dd>Enable the learning process—the journey of discovery—to be preserved and shared in context, in an open and transparent way. Everything should be publishable: the good, the bad, and, yes, even the ugly.</dd>
</dl>
</section>
<section>
<h2>The Basic Framework</h2>
<section class="informative">
<h2>Question</h2>
<p>There SHOULD only be one question per research case.</p>
<aside title="Who was Leonardo da Vinci?" class="example">
<div class="ttl">
<pre class="highlight" title="Who was Leonardo da Vinci? (Turtle syntax)">
<http://example.org/question1> a rio:Question ;
rio:text "Who was Leonardo da Vinci?"@en .
</pre>
</div>
<div class="jsonld">
<pre class="highlight" title="Who was Leonardo da Vinci? (JSON-LD syntax)">
{
"@context": "https://pentandra.com/solutions/research-intent-ontology/examples/context.json",
"@id": "http://example.org/question1",
"@type": "Question",
"text": {
"en": "Who was Leonardo da Vinci?"
}
}
</pre>
</div>
<div class="rdfxml">
<pre class="highlight" title="Who was Leonardo da Vinci? (RDF/XML syntax)">
<Question rdf:about="http://example.org/question1">
<text xml:lang="en">Who was Leonardo da Vinci?</text>
</Question>
</pre>
</div>
<div class="rdfa">
<pre class="highlight" title="Who was Leonardo da Vinci? (RDFa syntax)">
<p resource="#question1" typeof="rio:Question">Who was Leonardo da Vinci?</p> .
</pre>
</div>
</aside>
</section>
<section class="informative">
<h2>Research Case</h2>
<p>A research case is an intention to find an answer to a question, and embodies one and only one intention. This focus on one discrete intention at a time is a unique characteristic of research cases.</p>
</section>
<section class="informative">
<h2>Research Context</h2>
<p>The research context keeps track of where the researcher is in the research process. It’s intention is to model real-world research processes, which may be composed of one person researching alone, or of several people working together as is commonplace in research or open-source software development collaborations.</p>
<aside title="A Research Context" class="example">
<div class="ttl">
<pre class="highlight" title="A Research Context (Turtle)">
<http://example.org/project1> a rio:ResearchContext .
</pre>
</div>
<div class="jsonld">
<pre class="highlight" title="A Research Context (JSON-LD)">
{
"@context": "https://pentandra.com/solutions/research-intent-ontology/examples/context.json",
"@id": "http://example.org/project1",
"@type": "ResearchContext"
}
</pre>
</div>
<div class="rdfxml">
<pre class="highlight" title="A Research Context (RDF/XML)">
<Question rdf:about="http://example.org/question1">
<text xml:lang="en">Who was Leonardo da Vinci?</text>
</Question>
</pre>
</div>
<div class="rdfa">
<pre class="highlight" title="A Research Context (HTML/RDFa)">
<h1 resource="#project1" typeof="rio:ResearchContext">Research Project: <span property="dc:title">Leonardo da Vinci</span></h1> .
</pre>
</div>
</aside>
</section>
</section>
</section>
<section id="cross-reference" property="foaf:primaryTopic" resource="[rio:]" typeof="owl:Ontology voaf:Vocabulary">
<h2>Vocabulary Cross-Reference</h2>
</section>
<section class="appendix">
<h2>Namespace Prefixes</h2>
The following namespace prefixes are used throughout this specification:
<table class="section data-table">
<thead>
<tr><th>Prefix</th><th class="extended">Namespace IRI</th><th>Definition</th></tr>
</thead>
<tbody>
<tr>
<td><code>rdf</code></td>
<td><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></td>
<td>The <abbr title="Resource Description Framework">RDF</abbr> namespace [[!rdf-concepts]]</td>
</tr>
<tr>
<td><code>xsd</code></td>
<td><code>http://www.w3.org/2000/10/XMLSchema#</code></td>
<td>The <abbr title="eXtensible Markup Language">XML</abbr> Schema Namespace [[!xmlschema11-2]]</td>
</tr>
<tr>
<td><code>owl</code></td>
<td><code>http://www.w3.org/2002/07/owl#</code></td>
<td>The <abbr title="Web Ontology Language">OWL</abbr> namespace [[!owl2-overview]]</td>
</tr>
<tr>
<td><code>prov</code></td>
<td><code>http://www.w3.org/ns/prov#</code></td>
<td>The <abbr title="W3C Provenance">PROV</abbr> namespace [[!prov-o]]</td>
</tr>
<tr>
<td><code>oa</code></td>
<td><code>http://www.w3.org/ns/oa#</code></td>
<td>The <abbr title="Open Annotation Data Model">OA</abbr> namespace [[!annotation-model]]</td>
</tr>
<tr>
<td><code>rio</code></td>
<td><code>https://w3id.org/rio#</code></td>
<td>The Research Intent Ontology namespace (this specification)</td>
</tr>
<tr>
<td>(others)</td>
<td>(various)</td>
<td>All other namespace prefixes are used in examples only. In particular, <abbr title="Internationalized Resource Identifier">IRI</abbr>s starting with <code>http://example.com</code> represent some application-dependent IRI [[!rfc3987]].</td>
</tr>
</tbody>
</table>
</section>
<section class="appendix informative">
<h2>Extended Examples</h2>
<section>
<h2>Leonardo da Vinci Full Example</h2>
<aside title="Who was Leonardo da Vinci? (full example)" class="example">
<div class="ttl">
<pre class="highlight" title="Who was Leonardo da Vinci? (full example in Turtle)" data-include="examples/leonardo-oa.ttl" data-include-format="text"></pre>
</div>
<div class="jsonld">
<pre class="highlight" title="Who was Leonardo da Vinci? (full example in JSON-LD)" data-include="examples/leonardo-oa.jsonld" data-include-format="text"></pre>
</div>
<div class="rdfxml">
<pre class="highlight" title="Who was Leonardo da Vinci? (full example in RDF/XML)" data-include="examples/leonardo-oa.rdf" data-include-format="text"></pre>
</div>
<div class="rdfa">
<pre class="highlight" title="Who was Leonardo da Vinci? (full example in HTML5/RDFa)" data-include="examples/leonardo-rdfa/index.html" data-include-format="text"></pre>
</div>
</aside>
</section>
<section>
<h2>Steps to the Future: Researching the Backcountry Birth of George F. Ring</h2>
<p>From a <em>real</em> research project by Dr. John Phillip Colletta, published as <cite>Building Context around Biographical Facts: A Process Illustrated by the Backcountry Birth of George F. Ring</cite> in the National Genealogical Society Quarterly.</p>
</section>
</section>
<section class="appendix">
<h2>Alignment with Similar Ideas and Vocabularies</h2>
<section>
<h2>IBIS</h2>
<p><abbr title="Issue-Based Information System">IBIS</abbr> is a system and grammar initially designed to support coordination and planning of political decision processes. It is based on three simple elements: Question, Idea, and Argument. Usually IBIS is represented on a graphical issue map. Research cases are distributed in nature, while IBIS was introduced as a centralized model. Multiple datasets of research cases could be combined, however, into a single graph and displayed graphically. Another distinction is that research cases are focused on factual questions only, while IBIS is more abstract.</p>
</section>
<section>
<h2>Micropublications</h2>
<p><a about="[rio:]" property="voaf:similar" href="http://purl.org/mp/">Micropublications</a> [[mp]] is a model and ontology developed by Tim Clark, Paolo Ciccarese, and Carole Goble for claims, evidence, arguments and annotations in biomedical communications.</p>
</section>
</section>
<section class="appendix informative">
<h2>Acknowledgments</h2>
<p>And, of course, thanks to Robin Berjon for making our lives so much easier with <a property="prov:wasGeneratedBy" href="http://www.w3.org/respec/">ReSpec</a>.</p>
</section>
<section id="tof"></section>
<script class="remove">
window.addEventListener('DOMContentLoaded', function() {
relode.init('rio.jsonld', 'cross-reference');
});
</script>
<script>
/* nanotabs ~ Sean Catchpole - Version 0.9 - MIT/GPL */
(function(){var q=function(a){return document.getElementsByClassName(a)};if(!document.getElementsByClassName)var f=document.getElementsByTagName("*"),q=function(a){var b=[];a=" "+a+" ";for(var c=0;c<f.length;c++)0<=(" "+f[c].className+" ").indexOf(a)&&b.push(f[c]);return b};var n=function(a){var b;return(b=document.getElementById(a))&&[b]||q(a)},t=function(a){var b=this;return function(){return a.apply(b,arguments)}},h=function(a,b,c){for(var e=0;e<b.length;e++)a.apply(b[e],c||[])},u=function(a){this.className=
this.className.replace(new RegExp("(^|\\s)"+a+"(\\s|$)","g"),"")},v=function(){this.style.display="none"},w=function(){this.style.display="block"},r=function(a,b,c,e){h(u,b,[e.s]);this.className+=e.s;h(v,c);h(w,n(a))};nanotabs=function(a){var b;a=a||{};var c=["c","e","s","d","f"];for(b in c)a[c[b]]=a[c[b]]||nanotabs.settings[c[b]];var c=n(a.c),e=function(){var b=this[0],c=[this[1],this[2],this[3],this[4]];a.f&&!1===a.f.apply(b,c)||r.apply(b,c);return!1};for(b=0;b<c.length;b++){for(var l=0,f=[],g=
[],k=[],m=c[b].getElementsByTagName("a"),d=0;d<m.length;d++)if(m[d].href.match(/#/)){k.push(m[d].href.split("#")[1]);"string"==typeof a.d&&k[l]==a.d&&(a.d=l);g.push(m[d]);for(var h=n(k[l]),p=0;p<h.length;p++)f.push(h[p]);l++}for(d=0;d<g.length;d++)g[d]["on"+a.e]=t.call([g[d],k[d],g,f,a],e);"number"==typeof a.d&&0<=a.d&&r.call(g[a.d],k[a.d],g,f,a)}};nanotabs.settings={c:"nanotabs",e:"click",s:"selected",d:0,f:!1};nanotabs()})();
</script>
</body>
</html>