-
Notifications
You must be signed in to change notification settings - Fork 3
/
crowd-voc.html
755 lines (620 loc) · 24.1 KB
/
crowd-voc.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
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<title>Crowdsourcing vocabulary</title>
<script
src='https://www.w3.org/Tools/respec/respec-w3c-common'
class='remove'></script>
<script class='remove'>
var respecConfig = {
specStatus: "unofficial",
editors: [{
name: "QROWD Project",
url: "www.qrowd-project.eu",
}
],
edDraftURI: "https://qrowd.github.io/crowd-voc/",
shortName: "crowd-voc"
};
</script>
<link type="text/css" rel="stylesheet" href="http://contsem.unizar.es/docs/styles/w3c-general.css"/>
<link type="text/css" rel="stylesheet" href="http://contsem.unizar.es/docs/styles/w3c-wd.css"/>
</head>
<body>
<section id='abstract'>
<p>
Crowd-Voc is a vocabulary for describing data that has been produced through crowdsourcing. Crowdsourcing is understood broadly, as any type of collective activity to solve a problem or achieve a goal. Data refers to the contributions of the crowd in their consolidated form, which are released in form of a 'dataset' which can be used in other contexts.
The first goal of the vocabulary is to allow crowdsourcing projects to describe what the data is about and how it came about to facilitate reuse and sharing across projects. The vocabulary should also help repeat and reproduce research that involves crowdsourcing by capturing the key design parameters of a crowdsourcing task and the way crowd answers have been validated, aggregated and otherwise processed before their release as a dataset. Finally, the vocabulary sets the ground for acknowledging contributions by the crowd, towards a fairer model for licensing crowdsourced data.
</p>
</section>
<section id='sotd'>
<p>
This is version 0.1
</p>
</section>
<section data-dfn-for="crowd-voc">
<h2>Introduction</h2>
<!-- <pre class="idl">
interface Foo {
attribute Bar bar;
void doTheFoo();
};
</pre>
<p>The <dfn>Foo</dfn> interface represents a Foo.</p>
<p>The <dfn>doTheFoo()</dfn> method does the foo.</p>
-->
<section>
<h2>Namespace declarations</h2>
<div id="ns" style="align:center;">
<table>
<caption> <a href="#ns"> Table 1</a>: Namespaces used in the document </caption>
<tbody>
<tr><td><b>crowd-voc</b></td><td><http://qrowd-project.eu/def/crowd-voc#></td></tr>
<tr><td><b>owl</b></td><td><http://www.w3.org/2002/07/owl#></td></tr>
<tr><td><b>rdfs</b></td><td><http://www.w3.org/2000/01/rdf-schema#></td></tr>
<tr><td><b>xsd</b></td><td><http://www.w3.org/2001/XMLSchema#></td></tr>
<tr><td><b>dcterms</b></td><td><http://purl.org/dc/terms/#></td></tr>
<tr><td><b>org</b></td><td><http://www.w3.org/ns/org#></td></tr>
<tr><td><b>s</b></td><td><http://schema.org/></td></tr>
<tr><td><b>skos</b></td><td><http://www.w3.org/2004/02/skos/core#></td></tr>
<tr><td><b>foaf</b></td><td><http://xmlns.com/foaf/0.1/></td></tr>
<tr><td><b>ex</b></td><td><http://example.com/></td></tr>
</tbody>
</table>
</div>
</section>
</section>
<section>
<h2>Overview</h2>
</section>
<p>
The core of the vocabulary is shown in the figure below. We reuse as much as possible existing vocabularies. The main entity is <b>Task</b>, a subclass of <b>prov:Activity</b> that describes the crowdsourcing task, ultimately generating a <b>dcat:Dataset</b>. An instance of <b>Task</b> is linked to a <b>Crowd</b>, which is a subclass of <b>prov:Agent</b>. Crowds consists of instances of <b>Crowdworker</b>, a type of <b>prov:Person</b>. A crowdworker may be part of many crowds, assembled to run different tasks. To establish the link between crowds and crowdworkers, we reuse the <b>Organization</b> ontology, making <b>Crowd</b> an instance of <b>org:Organization</b>, allowing the usage of the <b>org:hasMember</b> property. Crowdworkers are identified by ids, depending on the platform where the crowdsourcing task is being run. The aim is not to store personal data about contributors, which is not accessible when running a crowdsourcing task, but to be able to distinguish between multiple contributors - this is needed when validating and aggregating the data submitted by the crowd. The crowd of a task refers to the set of contributors to the task rather than all users registered on the crowdsourcing platform.
</p>
<p> A task is comprised by an <b>rdf:list</b> of <b>Questions</b> that models the order on which questions are asked to crowdworkers. Each question has a hasText property, and a <b>rdf:seeAlso</b> that links to a more complex representation of the question, if available.
</p>
<img src="./img/Example-Task-Questions.png" alt="contract classification" style="border:0px" height="500" width="900">
<div class="example">
<div class="example-title"><span>Example of Task</span></div>
<pre class="example highlight preprint">
ex:aTask
a prov:Activity;
a crowd-voc:Task;
dcterms:description "My crowdsourcing task";
prov:wasAssociatedWith ex:Crowd;
crowd-voc:hasQuestionList (ex:question1,ex:question2) .
ex:Crowd
a org:Organization;
org:hasMember ex:a_crowdworker
ex:a_crowdworker
a prov:Person;
ex:question1
a crowd-voc:Question;
crowd-voc:hasText "Identify cars in images".
ex:question2
a crowd-voc:Question;
crowd-voc:hasText "Now identify cars at traffic lights in images".
ex:aCrowd
a crowd-voc:Crowd;
a prov:Agent;
vocab-org:hasMember ex:Crowdworker.
ex:Crowdworker
a prov:Person.
ex:generatedDataset
a dcat:dataset;
dcterms:title "Dataset generated by the task";
prov:wasGeneratedBy ex:aTask .
</pre>
</div>
<p>
A task is a collection of different activities that ultimately results in a dataset. It can consist of subtasks of the same or different types. Our aim is to describe the design of the crowdsourcing effort, including standard classes of tasks, which are approached in a particular way in crowdsourcing (e.g., classification, sentiment analysis, transcription, review etc.) and activities the crowd was asked to carry out (e.g. answer questions, check a website, translate from one language to another etc.). The reader is provided with a broad overview of the workflow used, rather than a fully specified data or control flow, as in a workflow language.
Each task (and all its subtasks) is linked to an input dataset (e.g. a collection of images) and an output dataset, which the crowd has helped produce. The output dataset is a consolidated version of the answers provided by the crowd, including validation, aggregation etc. A task can contain several questions, which refer to the exact wording used to seek contributions (e.g. "Identify all people, places, and organisations in the following paragraph").
</p>
<p>
The below figure describes the subdivision of a task in subtasks, to model more complex situations on which different tasks (possibly with different crowds) are applied. The subtask list is modeled as a rdf:list of Tasks. Each subtask takes as input the dataset generated by the previous task.
</p>
<img src="./img/Example-SubTasks.png" alt="Task and subtask" style="border:0px" height="500" width="900">
<div class="example">
<div class="example-title"><span>Task division in subtasks </span></div>
<pre class="example highlight preprint">
ex:aTask
a prov:Activity;
dcterms:description "My crowdsourcing task";
prov:wasAssociatedWith ex:aCrowd;
prov:used ex:InputDataset;
prov:generated ex:OutputDataset;
crowd-voc:hasSubTasks (ex:question1,ex:question2) .
ex:subTask1
a crowd-voc:Task;
dcterms:description "Brexit tweets";
a crowd-voc:ClassificationTask .
crowd-voc:hasAggregation ex:s1_aggregation
crowd-voc:hasQCMechanism ex:s1_qc
crowd-voc:hasQuestion ex:s1_q1
ex:subTask2
a crowd-voc:Task;
dcterms:description "Sentiment analysis on tweets";
a crowd-voc:SentimentAnalysisTask .
crowd-voc:hasAggregation ex:s2_aggregation
crowd-voc:hasQCMechanism ex:s2_qc
crowd-voc:hasQuestion ex:s2_q1
ex:s1_aggregation
a crowd-voc:AggregationMethod
ex:s2_aggregation
a crowd-voc:AggregationMethod
ex:s1_qc
a crowd-voc:QCMechanism
ex:s2_qc
a crowd-voc:QCMechanism
ex:s1_q1
a crowd-voc:Question;
crowd_voc:question_text "Does the tweet mention Brexit?"
ex:s2_q1
a crowd-voc:Question;
crowd_voc:question_text "Is this a happy tweet?"
</pre>
</div>
</div>
<section>
<h2>Vocabulary description</h2>
<section>
<h2>Classes</h2>
<div class="classes">
<ul class="hlist">
<li> Task </li>
<li> ContentVerificationTask </li>
<li> ClassificationTask </li>
<li> MetadataFindingTask </li>
<li> MediaTranscriptionTask </li>
<li> RankingTask </li>
<li> ModerationTask </li>
<li> FeedbackTask </li>
<li> SentimentAnalysisTask </li>
<li> ContentCreationTask </li>
<li> Question </li>
<li> QCMechanism </li>
<li> AggregationMethod </li>
</ul>
</div>
<!-- Class description template
<div = id="ClassName" class="entity" >
<h3> Class Name </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> IRIClass </p>
<div class="comment">
<p>Class description.</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, hassubclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
-->
<div = id="ClassName" class="entity" >
<h3> Task </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A crowdsourcing task</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> ContentVerificationTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A task where the crowdworkers are asked to check predefined properties of an item by carrying out specific checks or consulting external sources</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
<div = id="ClassName" class="entity" >
<h3> ClassificationTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A generic classification task on text or other media</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, hassubclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> MetadataFindingTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A task of finding a set of predefined characteristics of an item, for instance the author or year of a book</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, hassubclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> MediaTranscriptionTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A generic task of transcription for different types of media</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> RankingTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A task ranking different items</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
<div = id="ClassName" class="entity" >
<h3> ModerationTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A task moderating content from other tasks</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> ContentCreationTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A task producing new content, for instance free labels or descriptions for items, shortened versions of text, media etc.</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> SentimentAnalysisTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A sentiment analysis task on text or other media</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> SubTask </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> TaskIRI </p>
<div class="comment">
<p>A SubTask that is part of CrowdSourcing Task, for example, an image labelling task might consists of one subTask about identifying a certain entity in the image, and another about cropping the image to center the</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, has subclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> Question </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> QuestionIRI </p>
<div class="comment">
<p>
A question that is shown to the Crowdworker
</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, hassubclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div = id="ClassName" class="entity" >
<h3> Quality control mechanism </h3>
<sup class="type-c" title="class">c</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#classes">Class ToC</a>
</span>
<p> <strong>IRI:</strong> QualityControlIRI </p>
<div class="comment">
<p>
Quality control mechanism applied to a task: verifiable/control question, pre-screening/test question, honeypot(sample-based filtering), agreement-based/consensus, none
</p>
<dl class="description">
<dt>characteristics (is disjoint, in range of, hassubclasses, etc)</dt>
<dd> <a href="href" title="title">class or property name</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
</div>
</section>
<section>
<h2>Properties</h2>
<div class="reused-properties">
<h3>Reused properties</h3>
<ul class="hlist">
<li> dcterms:hasPart </li>
<li> prov:used </li>
<li> prov:generated </li>
<li> prov:wasAssociatedWith </li>
<li> vocab-org:hasMember </li>
</ul>
<!--
Template for properties
<div class="entity" id="actualDuration">
<h3>Actual duration
<sup class="type-dp" title="data property">dp</sup>
<span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#dataproperties">Data Property ToC</a>
</span>
</h3>
<p>
<strong>IRI:</strong> http://contsem.unizar.es/def/sector-publico/pproc#actualDuration</p>
<div class="description">
<p>
<strong>has characteristics:</strong> functional</p>
<dl>
<dt>has super-properties</dt>
<dd>
<a href="#duration" title="http://contsem.unizar.es/def/sector-publico/pproc#duration">Duration</a>
<sup class="type-dp" title="data property">dp</sup>
</dd>
<dt>has domain</dt>
<dd>
<a href="#Contract" title="http://contsem.unizar.es/def/sector-publico/pproc#Contract">Public contract</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
-->
</div>
<div class="own-properties">
<h3>Own properties</h3>
<ul class="hlist">
<li> hasAggregationMethod </li>
<li> hasQCMechanism </li>
<li> hasQuestionList </li>
<li> hasSubTasks </li>
<li> hasIncentive </li>
<li> hasMotivation </li>
</ul>
<div class="entity" id="hasAggregationMethod">
<h3>hasAggregationMethod
<sup class="type-dp" title="data property">dp</sup>
<!-- <span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#dataproperties">Data Property ToC</a> -->
</span>
</h3>
<p>
<strong>IRI:</strong> </p>
<div class="description">
<p>
<strong>has characteristics:</strong> functional</p>
<dl>
<dt>has domain</dt>
<dd>
<a href="#Task" title="">Task</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
<dl>
<dt>has range</dt>
<dd>
<a href="#AggregationMethod" title="">AggregationMethod</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div class="entity" id="hasQCMechanism">
<h3>hasQCMechanism
<sup class="type-dp" title="data property">dp</sup>
<!-- <span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#dataproperties">Data Property ToC</a> -->
</span>
</h3>
<p>
<strong>IRI:</strong> </p>
<div class="description">
<p>
<strong>has characteristics:</strong> functional</p>
<dl>
<dt>has domain</dt>
<dd>
<a href="#Task" title="">Task</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
<dl>
<dt>has range</dt>
<dd>
<a href="#QCMechanism" title="">AggregationMethod</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
</div>
<div class="entity" id="hasQuestionList">
<h3>hasQuestion
<sup class="type-dp" title="data property">dp</sup>
<!-- <span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#dataproperties">Data Property ToC</a> -->
</span>
</h3>
<p>
A subTask has a question
<strong>IRI:</strong> </p>
<div class="description">
<p>
<strong>has characteristics:</strong> functional</p>
<dl>
<dt>has domain</dt>
<dd>
<a href="#Task" title="">Task</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
<dl>
<dt>has range</dt>
<dd>
<a href="#Question" title="">rdf:list of Question</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
</div>
<div class="entity" id="hasSubTasks">
<h3>hasSubTasks
<sup class="type-dp" title="data property">dp</sup>
<!-- <span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#dataproperties">Data Property ToC</a> -->
</span>
</h3>
<p>
List of subtasks of a task
<strong>IRI:</strong> </p>
<div class="description">
<p>
<strong>has characteristics:</strong> functional</p>
<dl>
<dt>has domain</dt>
<dd>
<a href="#Task" title="">Task</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
<dl>
<dt>has range</dt>
<dd>
<a href="#Task" title="">rdf:list of Task</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
</div>
<div class="entity" id="hasMotivation">
<h3>hasMotivation
<sup class="type-dp" title="data property">dp</sup>
<!-- <span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#dataproperties">Data Property ToC</a> -->
</span>
</h3>
<p>
Motivation of the task. Possible values are: monetary rewards, fun, personal achievement, social belonging, social status, altruism.
<strong>IRI:</strong> </p>
<div class="description">
<p>
<strong>has characteristics:</strong> functional</p>
<dl>
<dt>has domain</dt>
<dd>
<a href="#Task" title="">Task</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
<dl>
<dt>has range</dt>
<dd>
Literal
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
<div class="entity" id="hasWorkflow">
<h3>hasWorkflow
<sup class="type-dp" title="data property">dp</sup>
<!-- <span class="backlink"> back to <a href="#toc">ToC</a> or <a href="#dataproperties">Data Property ToC</a> -->
</span>
</h3>
<p>
Workflow of the task: Find-Fix-Verify, Iterative Improvement, Crowd-guided workflow, Threshold-based workflow, Sequential interdependent, Parallel
<strong>IRI:</strong> </p>
<div class="description">
<p>
<strong>has characteristics:</strong> functional</p>
<dl>
<dt>has domain</dt>
<dd>
<a href="#SubTask" title="">SubTask</a>
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
<dl>
<dt>has range</dt>
<dd>
Literal
<sup class="type-c" title="class">c</sup>
</dd>
</dl>
</div>
</div>
</div>
</section>
</section>
<section data-dfn-for="crowd-voc">
<h2>Acknowledgements</h2>
Crowd-Voc was set up by the QROWD project (http://qrowd-project.eu/), which received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 723088. We would also like to thank the participants of the project networking workshop help at HCOMP2018 in Zurich, Switzerland (https://hcompnetworking.wordpress.com/).
</section>
</body>
</html