-
Notifications
You must be signed in to change notification settings - Fork 7
/
cwrc-preamble-template-EN.html
453 lines (393 loc) · 61.8 KB
/
cwrc-preamble-template-EN.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
<!DOCTYPE html>
<html lang="en">
<head>
<title>CWRC Ontology Preamble - ONTOLOGY_VERSION</title>
<meta charset="utf-8"/>
<!-- Bootstrap core CSS -->
<link href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm" crossorigin="anonymous"/>
<link href="css/cwrc.css" rel="stylesheet" type="text/css" />
<link rel="shortcut icon" href="css/favicon.ico" type="image/x-icon"/>
<link rel="icon" href="css/favicon.ico" type="image/x-icon"/>
</head>
<body>
<nav class="navbar navbar-expand-lg navbar-dark fixed-top bg-dark">
<a class="navbar-brand" href="/">
<img src="http://sparql.cwrc.ca/images/cwrclogo-vert-white.png" height="30" class="align-top" alt="CWRC Logo" /> CWRC Linked Data</a>
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarCollapse" aria-controls="navbarCollapse" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarCollapse">
<ul class="navbar-nav mr-auto">
<li class="nav-item"><a class="nav-link" href="/">Home</a></li>
<li class="nav-item"><a class="nav-link" href="https://yasgui.lincsproject.ca/">SPARQL Queries</a></li>
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
Preambles
</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdown">
<a class="dropdown-item" href="cwrc-preamble-EN.html">CWRC Ontology</a>
<a class="dropdown-item" href="genre-preamble-EN.html">Genre Ontology</a>
<a class="dropdown-item" href="ii-preamble-EN.html">II Ontology</a>
</div>
</li>
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
Specifications
</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdown">
<a class="dropdown-item" href="cwrc.html">CWRC Ontology</a>
<a class="dropdown-item" href="genre.html">Genre Ontology</a>
<a class="dropdown-item" href="ii.html">II Ontology</a>
</div>
</li>
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
Documentation
</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdown">
<a class="dropdown-item" href="documentation/our-dataset.html">Our Dataset</a>
<div class="dropdown-divider"></div>
<a class="dropdown-item" href="documentation/sparql-query-guide.html">SPARQL Query Guide</a>
<a class="dropdown-item" href="documentation/intro-to-sparql.html">Intro to SPARQL</a>
<a class="dropdown-item" href="documentation/query-modifiers.html">Query Modifiers</a>
<a class="dropdown-item" href="documentation/sample-queries.html">Sample Queries</a>
<a class="dropdown-item" href="documentation/load-into-huviz.html">Load into HuViz</a>
</div>
</li>
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="NavbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
About
</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdown">
<a class="dropdown-item" href="documentation/cwrc.html">CWRC</a>
<a class="dropdown-item" href="documentation/linked-data.html">Linked Data</a>
<a class="dropdown-item" href="our-team-EN.html">Our Team</a>
<a class="dropdown-item" href="https://github.com/cwrc/ontology">Github</a>
</div>
</li>
</ul>
<span class="navbar-text">The Ontology of the Canadian Writing Research Collaboratory</span>
</div>
</nav>
<div class="container-fluid">
<div class="row">
<nav class="col-xl-2 col-lg-3 col-md-12 d-none d-lg-block bg-light sidebar">
<div class="sidebar-sticky">
<div class="sidebar-heading justify-content-between align-items-center px-3 mt-4 mb-1 text-muted">
<span>Table of Contents</span>
<a class="d-flex align-items-center text-muted" href="#"></a>
<div id="toc">
<!-- Table of Contents -->
</div>
</div>
</div>
</nav>
<main role="main" class="col-xl-10 col-lg-9 col-md-12 ml-sm-auto pt-3 px-4" data-spy="scroll" data-target="#toc">
<h1>CWRC Ontology Preamble</h1>
<hr/>
<h2 id="abstract">Abstract</h2>
<p>The Ontology of the Canadian Writing Research Collaboratory (<a href="http://www.cwrc.ca">cwrc.ca</a>) brings together various linked data materials produced within the Collaboratory related to the writers, writing, and culture.</p>
<h2 id="introduction">1. Introduction</h2>
<p>Although it contains quite general components for activities such as annotation and citation, the focus of the CWRC ontology is on describing and relating aspects of literary studies and literary history, with a strong emphasis on gender and intersectional analysis indebted to its roots in <a href="http://www.artsrn.ualberta.ca/orlando/">The Orlando Project, a history of women’s writing in the British Isles</a>. It links to a number of standards while attempting to indicate the complexity of the relationship between representation and provenance in the production of linked data, and to convey the situatedness (<a href="#cwrc:f62e94d6-bd04-494c-9282-53af0a3f3376">Haraway, 1988</a>) of the knowledge that it represents. </p>
<p>Some of the materials associated with this ontology are produced by activities conducted within the Collaboratory. Others are produced through a process of translation from embedded XML markup. In other words, some are the product of human creation or curation, and others are machine-generated. </p>
<h2 id="status">2. About this Document</h2>
<p>This document is a human-readable version of the ontology that cannot document all of its data structures. The ontology itself should be the primary source for understanding how the ontology works. </p>
<p>The intended audience of this document is the scholar that wishes to understand how the ontology tackles concrete data recording problems and the linked open data practitioner that intends to make use of this ontology. </p>
<h2 id="status_ontology">3. Status of this dynamic ontology</h2>
<p>This document and the associated ontology will grow iteratively with modifications made over time as data is progressively translated and further ontological concerns are identified. Continuity is ensured using the OWL ontology annotations for ontological compatibility and for deprecated classes and properties. Deprecated ontology terms remain present but are marked as such. </p><p>The ontology is understood to be a living document that makes no claims to completeness. Instances have been derived from particular datasets and will be expanded progressively over time. </p><p>We welcome suggestions for new classes, properties, and predicates from those wishing to use the ontology for their own datasets, as well as suggestions related to the complexity of vocabularies associated with existing terms. Please submit suggestions via an issue or a pull request to the <a href="https://github.com/cwrc/ontology">CWRC Ontology code repository</a>.</p>
<h2 id="background">4. Background on the Orlando source data</h2>
<p>In 1995, the Orlando Project embarked on a history of women’s writing in the British Isles from the beginnings to the present (<a href="#cwrc:775357d1-e547-4674-9467-50b0308354ca">Brown, Clements and Grundy, 2007a</a>;<a href="#cwrc:772b1b45-8046-46b0-a746-bbdc8849a6c8">Brown, Clements and Grundy, 2007b</a>).</p>
<p>This born-digital collaboration devised a knowledge representation (<a href="#cwrc:d95dce89-623d-4226-afd5-c602db0b6c7f">Brown, Clements et al., 2006</a>) in the form of a bespoke SGML tagset to encode the project’s intellectual priorities and concepts in the text as it was being written. This tagset structures the biocritical, chronological, and bibliographical content of the resulting history of more than 8 million words and 2 million tags. The schema provides the basis of that of the Canadian Writing Research Collaboratory for similar content, and provides the foundation of this ontology. Some of the source data is produced via extraction from XML tags embedded in Orlando Project materials and the similarly structured content within the Collaboratory (<a href="#cwrc:aaa909f5-ffb5-4995-8245-b169d3c64746">Simpson and Brown, 2013</a>). </p>
<p><i>Orlando: Women’s Writing in the British Isles from the Beginnings to the Present</i> (<a href="#cwrc:d95dce89-623d-4226-afd5-c602db0b6c7f">Brown and Clements and et al., 2006</a>) is published by <a href="http://orlando.cambridge.org">Cambridge University Press</a>.</p>
<p>The scholarly introduction and introduction to the Orlando tagset are available here: <a href="http://orlando.cambridge.org/public/svDocumentation?&d_id=ABOUTTHEPROJECT">Introduction to Orlando Tagset</a>.</p>
<p>Contributors to Orlando are listed here: <a href="http://orlando.cambridge.org/public/svDocumentation?formname=t&d_id=CREDITSANDACKNOWLEDGEMENTS">Orlando Project Contributors</a>.</p>
<p>The Orlando Project’s XML schemas and the CWRC Project’s XML schema are available on <a href="https://github.com/cwrc/CWRC-Schema/tree/master/schemas">Github</a>. </p>
<h2 id="goals">5. Basic ontological goals</h2>
<h3 id="principals">a. Principles</h3>
<p>The schema covers entities, classes, and relationships associated with the domains of literature and literary and cultural history as understood from an intersectional feminist perspective. The ontology design responds to the challenges of shifting from semi-structured to structured data (<a href="#cwrc:26ad3610-a0bb-4e62-8fbc-d6be9ccbbdf6">Smith, 2013</a>). Although linked data triples stand on their own formally, many are derived from discursive prose and are best read in an environment that links back to their original context. The CWRC ontology design avoids representing RDF extractions from Orlando data as positivist assertions, and yet produces machine-readable OWL/RDF-compliant graph structures. It allows references to, without endorsing, external ontological vocabularies that are nevertheless part of documenting cultural processes and identities.</p>
<h3 id="competency">b. Competency Questions</h3>
<p>Competency questions are meant to provide a sense of scope to an ontology. These can serve a number of purposes including giving users a sense of what kind of information they might find in datasets that employ the ontology, and giving the ontology developers criteria against which to measure the success of the ontology. The CWRC ontology represents a wide range of information about writers’ lives, literary careers, and literary works. Moreover, as with other humanities data, this information may be put to a wide range of uses, many of which will not be foreseeable. For instance, the nineteenth-century novels of Susanna Moodie have been searched for evidence of specific weather events by researchers into climate change. This list will therefore not be exhaustive, but it should give some sense of the range of questions we would expect the ontology to be able to address. The fact that the datasets represented by this ontology cannot be comprehensive also needs to be stressed: the unevenness of the archival and published record, in addition to the necessarily selective and variously prioritized ways in which the information has been collected and recorded, mean that any sense of statistical significance or representativeness related to the kind of data for which this ontology is designed must be highly qualified and contextualized.</p>
<h4>Biography-based questions</h4>
<ol>
<li>What people are known to have attended school in a certain city over a particular period of time?</li>
<li>What British authors attended the same schools as each other?</li>
<li>What writers were taught by or schooled alongside another woman writer?</li>
<li>Who is recorded to have died from a particular cause of death in a particular time period?</li>
<li>What family members is a particular person recorded to have had, and how were they related? </li>
<li>Which queer/lesbian identified authors are recorded as having attended single-sex institutions?</li>
</ol>
<h4>Cultural Formation</h4>
<ol start="7">
<li>What people were identified with a particular race, colour, or nationality?</li>
<li>What women during the Victorian period were associated with multiple nationalities?</li>
<li>What writers had some form of Jewishness in common?</li>
<li>What British writers were associated with both Protestantism and Catholicism in the nineteenth century?</li>
<li>What literary texts engage with a particular religion or denomination?</li>
<li>What is the breakdown by the different genders represented in this dataset of novels published during a particular period?</li>
<li>Which writers are associated with a particular political affiliation?</li>
<li>Are writers more likely to be associated with gender-related causes at particular points in history?</li>
</ol>
<h4>Human Relationships</h4>
<ol start="15">
<li>Does a connection exist between two particular people?</li>
<li>How close is the connection? Is it asserted frequently in the data, as opposed to occurring only once or twice?</li>
<li>What types of connections to other people does a particular person have?</li>
<li>What family ties does this person have?</li>
<li>If two people are not connected, what is the shortest path between them via relationships with other people, or with other entities such as organizations or texts?</li>
<li>What connections exist between a set of people during a specified period in time?</li>
<li>How many people cite a particular author as influential in their own work?</li>
<li>How many writers are related to a particular organization? More specifically, which feminist organizations were supported by two or more generations of writers from a single family?</li>
<li>Who are all the people noted here with whom this author collaborated professionally (editor to writer relationships; author to author; editor to editor, etc.)?</li>
<li>Who had a relative involved in professional publishing spheres?</li>
</ol>
<h4>Clustering/Networking People</h4>
<ol start="25">
<li>What authors are most interconnected with other authors in terms of their influence?</li>
<li>Can we identify clusters of writers who seem to be operating as a community in terms of having a tight network of friendships, literary relationships, use of the same publishers, reviewing each other’s works, etc.?</li>
<li>Can we identify individuals who were key connections between different groups?</li>
<li>Whose work was influenced by British and/or international writers of colour?</li>
<li>Who was involved in both feminist groups and animal welfare activism? </li>
<li>Who was in touch with non-literary artistic groups?</li>
</ol>
<h4>Texts/Works based questions</h4>
<ol start="31">
<li>What books were important to this author’s education? </li>
<li>What reviews exist for a particular book?</li>
<li>In what languages has a particular work been published?</li>
<li>Is there any acknowledged intertextual relation between X and Y? </li>
<li>In which journals does a particular author’s work appear?</li>
<li>How many intertextual relationships does an author have to female-authored literary works?</li>
<li>Find all the responses to this book that are deemed to be gendered. </li>
<li>Which works are represented as the most translated?</li>
<li>Find particular themes and topics in texts, such as which works of the imagination contain depictions of women’s colleges? Which depict political organizations?</li>
<li>Which authors wrote for the same journal and in the same time period?</li>
<li>Which fictional works allude to a particular type of activism? </li>
<li>Are there references to fictional works in this author’s non-fictional work? </li>
<li>Which European fictional texts are set outside of Europe? </li>
<li>Who destroyed her own works? Whose works were destroyed by others?</li>
<li>Which works seem to have been influenced by certain theorists or philosophers? </li>
</ol>
<h4>Geography based questions</h4>
<ol start="46">
<li>Which texts were or were not published in a particular country?</li>
<li>Which texts were or were not reviewed in a particular country?</li>
<li>In which cities or nations did a particular author reside?</li>
<li>Which cities or nations are depicted or discussed in an author’s work?</li>
<li>In what locations has a particular play been performed over time?</li>
<li>Which works were written during travels? </li>
<li>Which texts were published or otherwise shared in countries outside of Europe? Which texts were reviewed in countries outside of Europe? </li>
</ol>
<h4>Time- (and Event-) Related Questions</h4>
<ol start="53">
<li>What are the most discussed texts of a particular temporal period within this dataset?</li>
<li>Trace the impact of a particular text through time and space.</li>
<li>What is the relative rise or fall of a writer’s reputation over time, in relation to other writers in the period?</li>
<li>What events in this person’s life were related to aspects of social identity such as religion, social class, or political affiliation?</li>
<li>What changes over time are recorded in the frequency of the kinds of relationships that the data describes, across numerous writers? E.g. Does this dataset record greater degrees of intertextuality with male writers or female writers, relatively speaking, at different points in time? </li>
<li>What major social or historical events and developments are reflected in the literary record?</li>
<li>Can we target exploration of the data at particular temporal periods, such as the Victorian period?</li>
<li>Which authors are likely to have known each other, due to overlapping chronologies, locations, and other connections in common?</li>
</ol>
<h4>Complex questions</h4>
<p>In many cases the ontology will play a part in investigating a more complex question or as a component of a larger hermeneutical process. For instance:</p>
<ol>
<li>Let me compare the publication patterns of writers, distinguishing by gender and by the number of children that they had. Looking at it over time, does their rate of literary productivity increase or decrease in relation to the number of children they have?</li>
<li>Show all the elements of both self-taught and formal education (books, subjects, instructors) that are also alluded to in a writer’s works.</li>
<li>Trace the impact of developments in writing, such as the emergence of a particular theme or formal feature, to a larger social development.</li>
<li>Test claims about the rise of genres or literary movements and see how they look when inflected by a dataset focused on women’s writing.</li>
</ol>
<h3 id="tools">c. Anticipated tools and functionalities</h3>
<p>Also relevant to the structure of the ontology are the kinds of tools and functionalities that it aims to support. These are:</p>
<ol>
<li>Searches through SPARQL queries;</li>
<li>Browsing, including faceting according to various criteria based on the ontology, including temporal periods, geographical locations, or the properties of writers;</li>
<li>Linking to our instance data by way of their URIs;</li>
<li>Discovery of significant information about instances through dereferenceable web pages;</li>
<li>Discovery of materials across the web that reference instances or other components of the ontology;</li>
<li>Graph Visualization of the structure of the ontology, including the properties and relationships it contains;</li>
<li>Network Visualization of the relationships between people and other people, and influence and relationship graphs showing connections between people and other entities such as books, indicating the directionality of relationships where appropriate.</li>
<li>Mapping of components of the data associated with geospatial information;</li>
<li>Timelines of components of the data associated with temporal information;</li>
<li>Use of SHACL rules and other logical inferencing tools to check for data errors, omissions, and consistencies;</li>
<li>Use of SHACL rules and other inferencing tools to derive new information from the combination of existing data and the ontologies;</li>
<li>Expose the unevenness of datasets by enabling the tracking of sources, provenance, and degrees of certainty in order to provide insight into gaps in the knowledge base;</li>
<li>Expose conflicts, contradictions, and outliers within datasets as a basis for inquiry.</li>
</ol>
<h3 id="linkages">d. Linkages to external ontologies</h3>
<p>We employ a number of strategies for linking to other ontologies. Our architecture does not typically import other ontologies wholesale, but relates to large vocabularies in defined ways. We try not to abuse sameAs predicates (<a href="#cwrc:a5686049-f450-415c-9ca6-deee26e30899">Halpin, Hayes et al., 2010</a>).</p>
<p> We adopt external namespaces and associated classes and terms wherever possible when they are in widespread use and their vocabularies are broadly compatible with ours, as in the case of the <a href="http://xmlns.com/foaf/spec/">FOAF</a> and <a href="http://bibliontology.com/">BIBO</a> vocabularies. For some terms, such as those for religious denominations or genres, we are happy to draw on other vocabularies’ terms and definitions in part or in whole, as in the case of terms from the <a href="#cwrc:db2f8571-a773-4068-a35f-34262950bb8f">Getty Art and Architecture Thesaurus</a> (<a href="http://www.getty.edu/research/index.html">Getty Research Institute</a>). Other terms are referenced, but usually at a distance rather than through wholesale import. This is particularly common in relation to <a href="cwrc.html#CulturalForm">cultural forms</a>, which, as explained more fully below, are understood primarily as representational and linked, where multiple related terms exist within the ontology, to terms typed as <a href="cwrc.html#TextLabels">textual labels</a>. By means of this structure, our vocabulary positions all terms associated with processes of Cultural Form as discursive labels, retaining the ambiguity of terms implicated in the complex social construction of identities within a narrative. Cultural forms may in turn be related to external ontologies in a number of ways. If an external ontology term aligns semantically with ours, then we use OWL- or SKOS-based relationships such as <code><owl:equivalentClass></code>, <code><skos:narrower></code> or <code><skos:broader></code>. If an external term's definition or use is not commensurate with a term in the CWRC ontology but its application in external datasets is such that it will be useful nevertheless to link those terms to ours (for instance for broadening searches using the problematic ISO5218 <a href="https://www.iso.org/standard/36266.html">Codes for the representation of human sexes</a>), then the <a href="cwrc.html#hasFunctionalRelation">has functional relation</a> predicate is employed to indicate that the relationship is specified semantically but may be leveraged for processing.</p>
<p>At the top level, the CWRC ontology makes use of the following well known ontologies:
<ol>
<li>The <a href="http://xmlns.com/foaf/spec/">FOAF</a> ontology for the representation of people and organizations.</li>
<li>The <a href="http://bibliontology.com/">BIBO</a> ontology for the representation of bibliographic data.</li>
<li>The <a href="https://www.w3.org/TR/owl-time/">TIME</a> ontology for the representation of events and points in time where <a href="https://www.w3.org/XML/Schema">ISO8601/XML Schema times</a> are not appropriate.</li>
<li>The <a href="https://www.w3.org/TR/annotation-model/">Web Open Annotation</a> data model is used to link the original Orlando text to specific <a href="cwrc.html#Context">Contexts</a>.</li>
<li>The <a href="https://www.w3.org/TR/skos-reference/">SKOS</a> vocabulary is used to represent taxonomical relationships within certain <a href="cwrc.html#CulturalForm">Cultural Form</a>s and to fully document ontology terms.</li>
<li>Some <a href="http://dublincore.org/documents/dcmi-terms/">Dublin Core</a> vocabulary terms are used for well known documentation tags such as <code><dcterms:title></code>.</li>
<li>The <a href="https://www.w3.org/TR/prov-overview/">W3C Provenance ontology</a> is used to indicate indebtedness, derivation or provenance of term descriptions as well as Cultural Context source annotations. </li>
<li>Linkages are made to the <a href="http://www.cidoc-crm.org/">CIDOC-CRM</a> ontology to cultural instances that are in common with CWRC.</li>
</ol>
</p>
<p>Established ontologies and vocabularies are used in the definition of numerous classes and instances. For instance, the religious terms of the <a href="http://www.getty.edu/research/tools/vocabularies/aat/">Getty Art and Architecture Thesaurus</a> provide suitable definitions for many religions, as does <a href="http://dbpedia.org/">DBPedia</a> for many terms throughout the ontology. Sometimes definitions draw on scholarly print and online sources. Quotation marks around the text of the description indicate wholesale adoption of the source definition. Where the description is not surrounded by quotation marks, the term has been defined by the CWRC team, but links may be provided to external resources such as a scholarly article or closely related DBpedia entry.</p>
<p>In other cases, terms from external ontologies are adopted in CWRC datasets without having been imported into our ontology. What follows is a non-exhaustive list of such vocabularies and the classes for which they are most frequently used:</p>
<ol>
<li><a href="http://geonames.org/">Geonames</a> terms are often used for locations and for many instances of <i><a href="cwrc.html#GeographicHeritage">geographic heritage</a></i>.</li>
<li><a href="http://id.loc.gov/vocabulary/languages.html">Library of Congress Languages</a> codes are typically used for instances of <i><a href="cwrc.html#Language">language</a></i>.</li>
</ol>
<h3 id="provenance">e. Provenance and contexts</h3>
<p>As noted above, some data associated with this ontology has been generated from XML structures (<a href="#cwrc:aaa909f5-ffb5-4995-8245-b169d3c64746">Simpson and Brown, 2013</a>). Provenance is thus particularly important, given that such data was not originally produced in RDF but rather in the form of tags embedded in a discursive context. In such cases, the relevant portions of the text are provided in the form of snippets, which within the dataset become instances of contextual notes or human-readable annotations to which the dataset nodes are directly tied. </p>
<p>The wholesale import of entire vocabularies within the CWRC ontology was likely to cause logical and ontological problems. To this end, we opted not to use the <code><owl:import></code> construct and instead either to link to vocabularies externally or to clone specific sets of terms from selected vocabularies. Similarly, not all vocabularies are well-defined from an ontological standpoint, but drawing from their narrative or some of their properties proved useful. To this end, we avoided the use of <code><owl:sameAs></code> so as not to bring unintended properties or ontological structures into the CWRC ontology. In other cases, the Provenance ontology property <code><prov:wasDerivedFrom></code> is used to indicate that the term was constructed using information from other terms without necessarily being equivalent. Direct linkages to other ontologies are usually made through the use of subClasses or <code><owl:equivalentClass></code>.</p>
<h3 id="labels">f. Labels</h3>
<p>For labelling, CWRC utilizes two means of promoting searchability. <code>rdfs:label</code> represents the human-readable nomenclature for a concept, instance, or predicate. This is the terminology used when representing components of the ontology in documentation and diagrams, except where a URI is provided.</p><p>As noted above in relation to <a href="cwrc.html#CulturalForm">cultural form</a>, however, when <a href="cwrc.html#TextLabels">textual label</a> is used to type a class, this is an indication of the representationality or discursivity of that class. <code>cwrc:TextLabels</code> are frequently used for ambivalent, overlapping, and culturally contested terms.</p>
<p>In addition, to support those with knowledge of prior datasets whose strings or terms have been linked for extraction purposes to CWRC terms, the ontology provides additional linguistic context for CWRC ontology terms. Alternative labels, signified by <code>skos:altLabel</code>, indicate terms from source datasets that have been employed to create relationships to this concept. Alt labels typically cannot serve as replacements for rdfs:label. Within the ontology, such alternative labels primarily exist for search and retrieval by allowing ontology terms to be located under a larger number of labels. Although some reflect the idiosyncrasies of the source data, they may be useful for broadening searches.</p>
<figure>
<img src="figures/TextLabelandAltLabel.png" style="display: block; margin: auto;width: 100%;"/>
<!-- <figcaption>Figure 3 - Change Set Example using both external descriptions and internal descriptions</figcaption> -->
</figure>
<h3 id="culturalformationsgeneric">g. Cultural diversity</h3>
<p>Cultural diversity has been an increasing source of debate beyond and within the digital humanities community. The concentration within the <i>Debates in Digital Humanities</i> series (<a href="#cwrc:f77171be-f937-4067-8dbe-fd9982822a96">Gold, 2012</a>; <a href="cwrc.html#matthew_k._gold_debates_2016">Gold and Klein, 2016</a>) of pieces reflecting the increasing prominence of matters related to race, gender, cultural diversity, and difference is but one marker of the extent to which diversity matters. This ontology seeks to convey an intersectional understanding of identity categories, as instantiated in The Orlando Project’s XML Biography schema.</p>
<p>The Cultural Form portion of the ontology recognizes categorization as endemic to social experience, while incorporating variation in terminology and the contextualization of identity categories. It understands social classification as culturally produced, intersecting, and discursively embedded. We invoke categories as the grounds for cultural investigation rather than fixed classifications, since such categories have never been stable or mutually exclusive (<a href="#cwrc:c3a52178-f054-494c-9afd-7421ddcb384a">Algee-Hewitt, Porter, and Walser, 2016</a>). For a more detailed explication of cultural formation, see <a href="#cwrc:7d891586-52df-49f4-9cef-77e26f1a0ed6">Brown et al 2017</a>.</p>
<h2 id="structures">6. CWRC ontological structures</h2>
<p>Source data from CWRC spans multiple types of data, including granular material such as bibliographic metadata and discursive, interpretive, or analytical content. The CWRC linked open dataset represents such information as a series of assertions, frequently associated with particular contexts.</p>
<p>While full, integrated traceability has always been a core need of repeatable experiments, this comes at a complexity cost within a linked open dataset in that the queries required to retrieve basic information become unwieldy. To this end, the CWRC ontology records information through a design that supports the tracking of provenance, certainty, and other complex components of the data, but is easily queried to produce simple triples. This design relies heavily upon and extends the <a href="https://www.w3.org/TR/annotation-model/">Web Annotation Data model</a>. Web Annotation supports quite standard forms of annotation, such as identifying entities named in a text or providing a keyword or correction, connecting the entities to the associated source in a way that supports provenance.</p>
<p>CWRC also builds on the Web Annotation structure to carry properties associated with those entities through a series of <a href="cwrc.html#Context">Contexts</a>, typed according to a number of high-level classes such as <a href="cwrc.html#EducationContext">EducationContext</a>, <a href="cwrc.html#CulturalFormContext">CulturalFormContext</a>, and <a href="cwrc.html#OccupationContext">OccupationContext</a>.The properties associated with entities for each Context have parallel subject-centric versions, that support the use of SPARQL Construct commands to derive entity-centric triples that simply link individuals to their personal attributes. In this way, deep provenance tracking is enabled while the production of granular subject-predicate-objects views of the data is supported by the ontology structure. Contexts thus link a fragment of source text to the individuals or entities whom it references, the properties or assertions situated within that context, and the class of experience or activity to which it belongs.</p>
<h3 id="identifying">a. Identifying Annotations</h3>
<p>Much CWRC linked data will involve the identification of named entities within CWRC documents, which is a straight-forward use-case for Web Annotation. Here below is a diagram of a Web Annotation identifying the person entity L.E.L. (Letitia Elizabeth Landon) within an excerpt or snippet from the Orlando Project’s published textbase.</p>
<!--Insert first L.E.L. image here -->
<figure>
<img src="figures/Schema-based-contexts-LEL_causeOfDeath_identifying.png" alt="Identifying context of L.E.L's Death" style="display: block; margin: auto;width:100%;"/>
<figcaption>Web Annotation identifying L.E.L. in a portion of the Orlando Project</figcaption>
</figure>
<h3 id="contextontology">b. Contexts (Describing Annotations)</h3>
<!--Insert summary here of how contexts are related to both properties and snippets through OA. -->
<p>The Context class uses Web Annotations to provide the discursive context for interpretive assertions in the ontology. Where the assertions have been generated from a web-accessible source text, a Context provides the text, or the relevant snippet of a longer text, from which they have been extracted. Contexts help to ground the data in its source materials, which can provide users with a sense of the nuance and complexity of assertions related to human subjects and cultural phenomena.</p>
<p>Contexts are typed by major semantic categories including, for biographical material, Cultural Forms, Birth, Death, Education, Occupation, and Politics, and, for literary content, Production, Reception, and Textual Features.</p>
<p>The major context classes are as follows:</p>
<p><a href="cwrc.html#BiographyContext">BiographyContext</a>, <a href="cwrc.html#BirthContext"> BirthContext</a>, <a href="cwrc.html#CulturalFormContext"> CulturalFormContext</a>, <a href="cwrc.html#DeathContext"> DeathContext</a>, <a href="cwrc.html#EconomicContext"> EconomicContext</a>, <a href="cwrc.html#EducationContext"> EducationContext</a>, <a href="cwrc.html#FamilyContext"> FamilyContext</a>, <a href="cwrc.html#FriendsAndAssociatesContext"> FriendsAndAssociatesContext</a>, <a href="cwrc.html#HealthContext"> HealthContext</a>, <a href="cwrc.html#IntimateRelationshipContext"> IntimateRelationshipContext</a>, <a href="cwrc.html#LeisureContext"> LeisureContext</a>, <a href="cwrc.html#NameContext"> NameContext</a>, <a href="cwrc.html#OccupationContext"> OccupationContext</a>, <a href="cwrc.html#SpatialContext"> SpatialContext</a>, and<a href="cwrc.html#ViolenceContext"> ViolenceContext</a>.</p>
<p>CWRC Contexts build on the Web Annotation structure, classing Annotations by Context. While identifying annotations are used to indicate the presence of particular entities, we shift the motivation of the annotation to describing when it comes to properties such as cause of death, since these annotations are describing what Orlando is saying, as well as engaging in description themselves.</p>
<!--Insert second L.E.L. image here -->
<figure>
<img src="figures/Schema-based-contexts-LEL_causeOfDeath-full-white.png" alt="Full Schema based Context" style="display: block; margin: auto;width:100%;"/>
<figcaption>Web Annotation incorporating L.E.L. cause of text through Web Annotation Context-centric triples</figcaption>
</figure>
<p>The relationship between L.E.L. and her cause of death is present here, but in a “Context-centric” rather than a subject-centric way. What we think of intuitively as the “Subject” of the cause of death triple, that is L.E.L., is present but is structurally an object: L.E.L, however, has a special, CWRC-defined relationship to the Annotation as the “contextFocus”, which is to say the subject of this particular Context. The “contextFocus” property, like other CWRC-defined properties linked to the annotations, becomes a subproperty of the standard oa:hasBody property. Links to source documents from which the RDF was extracted are there, as is certainty, citation links (not shown here), and potentially other information about this complex assertion. This graph is not as intuitively human-readable, but allows us to retain key contextualizing information that we consider key to creating robust humanities LODsets.</p>
<p>The Context-centric model allows for subject-centric triples, but these would need to be generated from the source data through SPARQL Construct queries. The CWRC Ontology provides both context-centric and subject-centric versions of predicates (for instance, causeOfDeath and hasCauseOfDeath, respectively), so that this can be done as a batch script to create a derivative dataset for those who want to see more direct relationships, or through the SPARQL Construct commands when running queries.</p>
<p>Moreover, the relationship between two different contextualized assertions provides a means of dealing with contradictory data through an OR relation that allows both Contexts to exist even though two assertions associated with them cannot logically both be true – as is the case with L.E.L. whose cause of death is asserted to be both murder or suicide in the source document. In such a case, a low certainty value could be generated based on this contradiction in the data. This model thus provides support for reasoning that will help to identify inaccuracies in the data. It will also help to highlight areas of controversy, edge cases, differences across datasets, and cases of negation or contradiction, not as noise or dirt to be weeded out of the data, but rather as things that humanities scholars frequently want to zero in on and examine more closely.</p>
<h3 id="persona">c. Persons, Personas and Roles</h3>
<p>The distinction between persons, personas, and roles is an important component of the complexity of human experiences and relationships.</p>
<p>This ontology adopts the broad FOAF definition of a <a href="http://xmlns.com/foaf/spec/#term_Person"><code>foaf:person</code></a>, which can be applied to any entity considered to be a person, including non-humans. We define two subclasses of Person: a <a href="cwrc.html#NaturalPerson">NaturalPerson</a> or human being, and a <a href="cwrc.html#FictionalPerson">FictionalPerson</a>, since fictional characters are important to literary studies. If a historical person who is a NaturalPerson is fictionalized as a <code>Character</code> [not yet created] in a text, they also become a FictionalPerson. If a text simply alludes or refers to a NaturalPerson, however, they are not also a FictionalPerson.</p>
<p>In some cases, a Person will be associated with a Persona. A person can occupy a <code>Role</code> [not yet created] in relation to a specific event or situation.</p>
<p>The author Michael Field offers an example of the extent to which "personhood is both a complex and a crucial characteristic that ontologies must be designed to capture appropriately" <a href="https://cwrc.ca/islandora/object/cwrc%3Aaaa909f5-ffb5-4995-8245-b169d3c64746">(Brown and Simpson 2013)</a>. The persona of Michael Field was produced by the artistic and lived collaboration between Katherine Harris Bradley and Edith Emma Cooper at the turn of the twentieth century. Even though he was not a biological person, Michael Field had an important role in the two women’s careers, their social lives, and their personal relationship. "Michael Field" can neither be assigned to one of the authors over the other, nor can it be considered only a shared pseudonym. Michael Field is associated with two natural persons at the same time. We seek in the CWRC ontology to capture such manifestations of the originality and the plurality of personhood. The ontology thus includes the "persona" class of person to describe entities such as Michael Field.</p>
<p>It might be argued that such personae are simply pen-names or stage names, such as "Currer Bell" for Charlotte Brontë. However, personae are more than alternative signatures. Personae inflect the ways in which artists socially, symbolically, intimately or artistically embody authorship. While a pen-name can be described as a publication strategy related to a specific context, a persona has its own performed personality that goes beyond a signature. A contemporary example is the <a href="https://en.wikipedia.org/wiki/FASTW%C3%9CRMS">FASTWÜRMS art collective</a>. The collective operates as more than a creative identity, to the point of holding a single academic position at the University of Guelph.</p>
<p>A particular persona is an original creation, often bearing meaning related to the biographical, historical and sociological context of its creator. A persona in this sense is also not generally associated with mental illness or multiple personality disorders that result from distorted or uncontrolled perceptions of reality. At the heart of a persona is an identity with which others interact and that can be confused with a Natural Person. It is incarnated and developed by a natural person, may have specific properties such as gender or sexuality that differ from those of the natural person with whom it is associated, and may engage in social, literary, artistic or political activities. Although Personae are FOAF Persons, they are distinct from the CWRC Natural Persons who embody them and from Fictional Persons, unless they become fictionalized by themselves or others.</p>
<p>As documented for the recent Persona tag incorporated in the Text Encoding Initiative Guidelines, personae are not <a href="cwrc.html#Role"><code>Role</code></a>s either: "A role may be assumed by different people on different occasions, whereas a persona is unique to a particular person, even though it may resemble others. Similarly, when an actor takes on or enacts the role of a historical person, they do not thereby acquire a new persona." (<a href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSE">http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSE</a>).</p>
<p>A Role can be adopted by either personae or natural persons, but a persona cannot be adopted by people generally: it is specific to one natural person, or more rarely several natural persons (as in the case of the collaborative Field and the artistic collective <a href="https://en.wikipedia.org/wiki/FASTW%C3%9CRMS">FASTWÜRMS art collective</a>).</p>
<p>Roles are characters or functions performed in specific occasions and situations, which is to say events. Dramatic roles, that is to say <code>#Character</code> in a creative work, are adopted by actors for particular performances. By analogy, social roles are adopted by particular individuals in relation to particular events or occurrences, which may be of brief or long duration. Key roles in relation to events are those of agents, spectators, and commentators. Occupations, jobs, or significant activities are not the same as roles, although they may be related to them, as may familial or social relationships. Roles will be further fleshed out in relation to the event component of the ontology, which is currently under development.</p>
<h3 id="culturalformationsontology">d. Cultural Form</h3>
<p>The <a href="cwrc.html#CulturalForm">CulturalForm</a> classes recognize categorization as endemic to social experience, while incorporating variation in terminology and contextualization of identity categories by employing instances at different discursive levels. A cultural form represents an aspect of lived social subjectivities and/or classification of a person through categories such as race or colour, ethnicity, gender, language, sexuality, politics, or religion. Most of the properties associated with specific Cultural Forms may also have the additional modifiers of reported and self-reported, allowing for the qualification of individual statements.</p>
<p>Cultural Form sub-classes and instances describe the subject positions of individuals through <a href="cwrc.html#Context">Context</a>s. Contexts are linked to granular Cultural Form properties that are in turn associated with the person who is the <a href="cwrc.html#contextFocus">contextFocus</a> of the annotation. This has its roots in the Orlando arrangement of Cultural Form encodings that points users towards a framework for raising and debating complex matters for cultural investigation rather than invoking reified categories.</p>
<p>The shift from embedded semantic markup to a linked open data approach presented the challenge of making this approach compatible with linkages to other ontologies and datasets outside of the Orlando frame of reference. The move from "strings to links" or "strings to things" was in some sense at odds with the former embrace of the ambiguity of strings such as white, black, English, etc.: white and black can represent race or ethnicity, while English can also be invoked as an ethnicity, nationality, or a national heritage. Orlando marks these strings using its Cultural Forms tagset as specific to, for example, the context of race or ethnicity, mandating a similar association, within the linked data representation, with a specific instance of Cultural Form. Thus, there exist Cultural Form instances that point to the discursive construction of <a href="cwrc.html#whiteRace">white</a> as a race and <a href="cwrc.html#whiteEthnicity">white</a> as an ethnicity. Lastly, there also exists a <a href="cwrc.html#whiteLabel">white</a> label that can be instantiated as either race or ethnicity, but not both within the same assertion (although multiple assertions are possible).</p>
<p>This is a departure from previous (non-linked open data) controlled vocabularies, in that the appearance of the term or label (in this case "white") does not indicate the specific cultural formation being invoked, the specific instance does. This also means that linkages to other datasets or vocabularies can be made appropriately, since multiple representations of the same label are present within the CWRC ontology. As a last resort, or for data mining purposes, the term is also available as a concept whose actual Cultural Form is undecided amongst the CWRC-defined options. This allows for linkages to an external ontology, such as can be required by text mining, without endorsing the corresponding definition or interpretation of the term. Finally, <a href="https://www.w3.org/2012/09/odrl/semantic/draft/doco/skos_altLabel.html">skos:altLabel</a> properties provide variant terms that indicate the unstructured vocabulary terms or strings that have been translated to these vocabulary instances.</p>
<h4 id="granularproperties">i. Granular Properties</h4>
<p> Granular properties provide a simple means of indicating cultural categories as as presumed, perceived, or otherwise assigned to a person according to cultural conventions, or as self-reported by the person themselves. Some of the properties are associations inherited from forebears.</p><p>Most properties take noun forms in keeping with conventions for ontologies, but in some cases idiom makes adjectival forms preferable, even though these terms function as nouns, as in the case of the sexual identity <code>celibate</code>.</p>
<h3 id="taxonomiesontology">e. Built-in Taxonomies</h3>
<h4 id="religion_taxonomy">i. Religion</h4>
<p>The original Orlando data makes religious reporting a challenge in that the original contexts had no differentiation between religious belief, membership in a religious organization, and absence of any religious belief combined with adherence to values or practices.</p>
<p>We use a taxonomy for enumerating the categories associated with this spectrum. The taxonomy in itself is SKOS-based and represents a loose mixture of the shared beliefs and historical offshoots.</p>
<p>The taxonomy attempts to trace in a subjective way the theological and/or historical lineage of the belief system. Like applying the labels to an individual, this is an interpretive process.</p>
<p><a href="figures/religionTaxonomy-ONTOLOGY_DATE-EN.svg">The specific taxonomy is:</a></p>
<object type="image/svg+xml" id="religion-tax" data="figures/religionTaxonomy-ONTOLOGY_DATE-EN.svg"></object>
<h4 id="politicalAffliation_taxonomy">ii. Political Affiliation</h4>
<p>Political affiliation categories cover a broad range of political parties, more and less organized movements, and various causes. The instances here involve a strong emphasis on British political matters historically of interest to women and a recognition that movements such as feminism are contested and change with time and location. Some affiliations are linked via SKOS relations, but there are other cross-currents among different groups that cannot be captured here as well as in the contextualized data itself. As for the other components of this ontology, this vocabulary makes no claims to comprehensiveness, having been derived from the Orlando dataset, and is open to expansion as needed.</p>
<p><a href="figures/politicalAffiliationTaxonomy-ONTOLOGY_DATE-EN.svg">The specific taxonomy is:</a></p>
<object type="image/svg+xml" id="pa-tax" data="figures/politicalAffiliationTaxonomy-ONTOLOGY_DATE-EN.svg"></object>
<h4 id="genre_taxonomy">iii. Genre </h4>
<p>The separate <a href="genre.html">CWRC Genre ontology</a> contains a taxonomy of cultural media, forms, and genres, with a strong emphasis on literary genres, based on a combined <a href="https://www.w3.org/OWL/">OWL</a> and <a href="https://www.w3.org/2004/02/skos/">SKOS</a> approach. In order to facilitate the ability both to apply terms to particular cultural productions and enable them to be discussed as concepts, genres are instances within the CWRC Genre ontology, and are related to particular cultural works through the hasgenre property.</p><p>Because it is useful for a number of purposes to be able to move between broader genres and more specific ones, the ontology organizes its terms through a combination of <a href="https://www.w3.org/OWL/">OWL</a> classes that provide broad groupings and
<a href="https://www.w3.org/2004/02/skos/">SKOS</a> taxonomical relations amongst instances. The OWL classes provide the ability to reason from narrower to broader terms, while the SKOS properties
provide more limited transitive narrower/broader relationships.</p>
<!-- Reintroduce this once the visualization is available again. <p><a href="figures/genreTaxonomy-ONTOLOGY_DATE-EN.svg">The structure is:</a></p>
<object type="image/svg+xml" id="genre-tax" data="figures/genreTaxonomy-ONTOLOGY_DATE-EN.svg"></object>-->
<h3 id="changeSets">f. Notes on ChangeSets</h3>
<p>Change Sets exist to track changes to instances, terms, and classes within the ontology, they are therefore used by both the authors of the ontology as well as users who are making additions or modifications. Change sets are instances that are linked either to or from a structure in the ontology. This is done through the object properties <i>affected entity</i> or through the <code>skos:changeNote</code>. A single change set may apply to several entities therefore the <a href="cwrc.html#affectedEntity">cwrc:affectedEntity</a> relation may be applied 0 or more times. Change sets also track the user through the <a href="cwrc.html#alteredBy">cwrc:alteredBy</a> relation and may link to any <a href="cwrc.html#NaturalPerson">cwrc:NaturalPerson</a>. In addition dates and times are kept track of through <code>time:inXSDDateTimeStamp</code> using xsd:dateStamps to track the instant the change was applied to the ontology. This will allow change sets to be used as release by selecting them between a particular date to show major changes. Through provenance Change Sets may link to external resources allowing extended discussion to be kept out of the ontology. Shorter descriptions are included through the <code>skos:changeNote</code> relation as well as a title using a standard <code>rdfs:label</code>. Change Sets are to be used anytime an issue is completed by ontology developers or an instance is changed by a user. Automated mechanisms will be used to offset some of the work required.</p>
<figure>
<img src="figures/ChangeSets.png" style="display: block; margin: auto;width:100%;"/>
<figcaption>Figure 3 - Change Set Example using both external descriptions and internal descriptions</figcaption>
</figure>
<h3 id="functionallyRelates">g. Has Functional Relation</h3>
<p>The Functional Relation predicate indicates that the two terms may be treated as related for functions such as querying and retrieval, but it also denies a semantic relationship between the two terms. This predicate is designed to bring together incommensurate terms for processing purposes but also to exclude them from semantic operations. This differentiates from, for instance, the <code>skos:semanticRelation</code> property and the <code>skos:closeMatch</code> predicate which serves a similar purpose but asserts a semantic proximity.</p>
<p>One of the purposes for this relation is to facilitate comparisons and relationships to other ontologies and vocabularies with which users are more familiar. Use of this relationship does not assert that the two terms are not related semantically, but rather that the current semantic relationships available within OWL, SKOS, and other ontologies used by this ontology are not sufficiently nuanced to allow for a semantic relationship to be specified in a way that can be processed appropriately by other tools (such as inference engines).</p>
<h2 id="notesSKOS">7. CWRC Ontology Design Rules</h2>
<p>Beyond the formalism of <a href="https://www.w3.org/TR/owl-primer/">The OWL 2 Web Ontology Language</a>, the CWRC ontology follows the following design rules and styles:</p>
<ul>
<li>The contents of rdfs:labels tags are always in lowercase, with the
following exceptions:</li>
<ul>
<li>Labels for religions, political affiliations and groups of people derived from a proper name will begin with an uppercase letter.</li>
</ul>
<li>Whenever possible, the original Orlando XML tag equivalent is contained within the rdf:value tag of any term within the ontology.</li>
<li>Whenever referencing a geographical location, use the most precise item within the database.</li>
<li>Definitions in French, English (and other serendipitously available languages) are never word-for-word translations, and are definitions in their own right.</li>
</ul>
<h2 id="notesSKOSOWL">8. Notes on SKOS and OWL</h2>
<p>SKOS (Simple Knowledge Organization System) enjoys widespread popularity in the semantic web community as it provides simple terms for taxonomies without requiring reasoner support. Whenever appropriate, SKOS terms are inserted within this ontology to link terms to each other. However, since these terms are not ontologically powered, their scalability is limited since each additional layer of terms within a taxonomy requires another database query.</p>
<p>Some of the constructs within the CWRC ontology are deep and require reasoning support. OWL is the preferred means of using this ontology, though the usage of the terms, SKOS-style, is possible.
</p>
<h2 id="conclusion">9. Conclusion and Future Work</h2>
<p>This is a draft ontology that is very much in progress. It will continue to be developed, expanded, and revised, and potentially broken up into modules, as we discover the implications of how we have structured the ontology through using it to extract and explore our data, and as fresh data and use cases necessitate expansion or refinement, and as new needs, understandings, and debates arise.</p>
<h2 id="version_history">10. Version History</h2>
<ul>
<li><p>0.99 - Initial public release.</p></li>
<li><p>0.99.2 - Periodic release with updated logos, genres, documentation, and proper masthead data.</p></li>
<li><p>0.99.6 - Periodic release with updated styling, competency questions and documentation regarding events and changesets</p></li>
<li><p>0.99.75 - Periodic release </p></li>
<li><p>0.99.80 - Periodic release with addition of occupations, educational award types, education credentials</p></li>
</ul>
<h2 id="bibliography">11. Bibliography</h2>
m4_include(cwrc-citations.html)
</main>
</div>
</div>
<!-- Bootstrap core JavaScript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<script src="https://code.jquery.com/jquery-3.2.1.slim.min.js" integrity="sha384-KJ3o2DKtIkvYIK3UENzmM7KCkRr/rE9/Qpg6aAZGJwFDMVNA/GpGFF93hXpG5KkN" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.11.0/umd/popper.min.js" integrity="sha384-b/U6ypiBEHpOf/4+1nzFpr53nxSS+GLCkfwBdFNTxtclqqenISfwAzpKaMNFNmj4" crossorigin="anonymous"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js" integrity="sha384-JZR6Spejh3U02d8jOt6vLEHfe/JQGiRRSQQxSfFWpi1MquVdAyjUar5+76PVCmYl" crossorigin="anonymous"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.bundle.min.js" integrity="sha384-feJI7QwhOS+hwpX2zkaeJQjeiwlhOP+SdQDqhgvvo1DsjtiSQByFdThsxO669S2D" crossorigin="anonymous"></script>
<script src="js/toc.js"></script>
<script src="js/svg-pan-zoom.min.js"></script>
<script>
window.onload = function() {
var options = {
selector: 'h2, h3, h4, h5',
scope: 'main'
};
var container = document.querySelector('#toc');
var toc = initTOC(options);
container.appendChild(toc);
// Expose variable for testing purposes
window.panZoomPA = svgPanZoom('#pa-tax', {
zoomEnabled: true,
minZoom: 1,
controlIconsEnabled: true,
fit: true,
center: true
});
window.panZoomR = svgPanZoom('#religion-tax', {
zoomEnabled: true,
minZoom: 1,
controlIconsEnabled: true,
fit: true,
center: true
});
window.panZoomG = svgPanZoom('#genre-tax', {
zoomEnabled: true,
minZoom: 1,
controlIconsEnabled: true,
fit: true,
center: true
});
};
</script>
</body>
</html>