-
Notifications
You must be signed in to change notification settings - Fork 0
/
military-template-EN.html
325 lines (264 loc) · 16.9 KB
/
military-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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en"
>
<head>
<title>Military Ontology Specification - ONTOLOGY_VERSION</title>
<meta http-equiv="content-type" content="text/xhtml+xml; charset=utf-8" />
<!-- With Apologies to Dan Brickley and Libby Miller -->
<link href="xmlns-style.css" rel="stylesheet" type="text/css" />
<link href="style.css" rel="stylesheet" type="text/css" />
<link rel="mvcb:generatorAgent" type="application/rdf+xml" title="DOAP" href="http://rdfohloh.wikier.org/project/specgen" />
</head>
<body>
<h1 id="title">Military Ontology Specification - ONTOLOGY_VERSION</h1>
<h2 id="subtitle">The Muninn Military Ontology marks up information
about military people, organizations and events.
</h2><img src="Army-officer-icon.png" alt="A
people icon representing a soldier, by Rion" align="right">
<!-- http://commons.wikimedia.org/wiki/File:Army-officer-icon.png -->
<h3 id="mymw-doctype">Working Draft — ONTOLOGY_LONGDATE</h3>
<dl>
<dt>Previous version:</dt>
<dd><a
href="http://rdf.muninn-project.org/ontologies/military-PREVIOUS_ONTOLOGY.html">http://rdf.muninn-project.org/ontologies/military-PREVIOUS_ONTOLOGY.html</a>
(<a
href="http://rdf.muninn-project.org/ontologies/military-PREVIOUS_ONTOLOGY.owl">owl</a>)
</dd>
<dt>This version:</dt>
<dd><a
href="http://rdf.muninn-project.org/ontologies/military-ONTOLOGY_DATE.html">http://rdf.muninn-project.org/ontologies/military-ONTOLOGY_DATE.html</a>
(<a
href="http://rdf.muninn-project.org/ontologies/military-ONTOLOGY_DATE.owl">owl</a>)
</dd>
<dt>Latest version:</dt>
<dd><a
href="http://rdf.muninn-project.org/ontologies/military.html">http://rdf.muninn-project.org/ontologies/military.html</a>
(<a
href="http://rdf.muninn-project.org/ontologies/military.owl">owl</a>)
</dd>
<dt>Last Update: ONTOLOGY_VERSION</dt>
<dd>Date: ONTOLOGY_LONGDATE</dd>
<dt>Authors:</dt>
<dd>Robert Warren, The Muninn Project</dd>
<dt>Translations:</dt>
<dd>Cathrin Weiss</dd>
<dt>Contributors:</dt>
<dd>Margaret Warren, State Library of Queensland, Australia</dd>
<dd>Daniel Wilksch, Public Record Office Victoria, Australia</dd>
</dl>
<p class="copyright"><a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">
<img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/88x31.png" />
</a><br/>This work is licensed under a
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons / Attribution-ShareAlike 3.0 Unported License</a>.</p>
<!-- ===================================================================== -->
<hr />
<h2 id="abstract">Abstract</h2>
<p>
This specification defines a set of classes and properties that
structure information about military history.
</p>
<h3 id="status">Status of this Document</h3>
<p>
This document grows iteratively over time, with modification made over
time. Continuity is ensured using the <a
href="http://www.w3.org/TR/owl-ref/#Annotations">OWL ontology
annotations</a> for ontological compatibility and for deprecated classes and properties.
Ontology terms remain present whether deprecated or not.
</p>
<p><i>This ontology is going through large documentation changes. Terms should be considered to be stable.</i></p>.
<h2 id="contents">Table of Contents</h2>
<ol id="toc">
m4_include(military-toc.html)
</ol>
<hr />
<h3 id="organi">Military Trades, Appointments and Ranks</h3>
<p>The human resources of military organizations are complex, redundant and sometimes follow traditions that are long running.
To this end the ontology makes use of three different classes:
<a href="http://rdf.muninn-project.org/ontologies/military#MilitaryRank">Military Rank</a>,
<a href="http://rdf.muninn-project.org/ontologies/military#MilitaryAppointment">Military Appointments</a> and
<a href="http://rdf.muninn-project.org/ontologies/military#MilitaryTrade">Military Trades</a>. All ontology terms regarding
personnel posts are instances of these three classes. This complexity is necessary to deal with the entailment of a person being in a single post within a military organization
where the relationship between a person's title, tasks performed, authority and rate of pay are more than merely complex.</p>
<p>The terms were created from extracts of military databases, Wikipedia and book extracts. Whenever possible, a term has a
generic instances that is sub-classed for specific military contexts.</p>
<h3 id="armedServices">Armed Services</h3>
<p>The following services have concepts within the ontology:
<a href="http://rdf.muninn-project.org/ontologies/military#NavyServiceBranch">Navy</a>,
<a href="http://rdf.muninn-project.org/ontologies/military#ArmyServiceBranch">Army</a> and
<a href="http://rdf.muninn-project.org/ontologies/military#AirForceServiceBranch">Air Force</a>. A
<a href="http://rdf.muninn-project.org/ontologies/military#ProtoAirForce">special term</a> exists for
air force units that are attached to Navy or Army units.
</p>
<h3 id="arms">Arms</h3>
<p>The following arms have concepts within the ontology:
<a href="http://rdf.muninn-project.org/ontologies/military#Armor">Armor</a>,
<a href="http://rdf.muninn-project.org/ontologies/military#Artillery">Artillery</a>,
<a href="http://rdf.muninn-project.org/ontologies/military#Cavalry">Cavalry</a> and
<a href="http://rdf.muninn-project.org/ontologies/military#Infantry">Infantry</a>. The
<a href="http://rdf.muninn-project.org/ontologies/military#NavyServiceBranch">Navy Service Branch</a> and
<a href="http://rdf.muninn-project.org/ontologies/military#ProtoAirForce">ProtoAirForce</a>/<a href="http://rdf.muninn-project.org/ontologies/military#AirForceServiceBranch">Air Force Service Branch</a> are also
instances of arms.
</p>
<h3 id="arms">Notes on naming, labelling in multicultural environments</h3>
<p>One of the issues in semantic web databases is that <i>difference between the thing and the name of thing</i>, which
throws off most beginners first using the semantic web.In most cases, a modern label exists in most languages that can be
used to identify the thing for human consumption. In other cases, the label
itself entails more information that can be can be conveyed through a simple
property such as rdfs:label or muninn:acronym. In these situations, the
terms is typed as an skos-xl label instance that labels both the underlying
instance of the thing and links to the contextual use of that label, such as
slang, historical period.</p>
<h3 id="">Countries / Organizations</h3>
<p>The cross reference of ranks, appointments and trades by country.</p>
<div style="padding: 1em; border: dotted; background-color: #ddd;">
m4_include(rank_TOC.html)
</div>
<h3 id="armedServices">Examples</h3>
<h4 id="example_NamedRegiment">A named regiment: The Blue Puttees</h2>
<p>The <a
href="http://rdf.muninn-project.org/ww1/2011/11/11/Regiment/newfoundland">Newfoundland Regiment</a> was initially raised after the onset
of the British declaration of war on Germany as the Dominion of
Newfoundland's contribution to the war effort. After the battle of the
Ypres, the <a href="http://rdf.muninn-project.org/ww1/2011/11/11/Regiment/rnewfoundland">Royal Newfoundland
Regiment<a/> was recognized for its achievements by <a href="http://dbpedia.org/resource/George_V">King George V</a> with the Royal prefix to its name.</p>
<p>Founded in 1914, the Battalion-Sized regiment numbered 500 initially
and was nicknamed the 'Blue Puttees' for the color of their <a
href="http://en.wikipedia.org/wiki/Puttee">Puttee</a>
that were dark blue instead of khaki. By the end of the Great War, over 2,200 Newfoundlanders served in the Regiment. The <a href="http://rdf.muninn-project.org/ww1/2011/11/11/Regiment/rnewfoundland">Royal Newfoundland
Regiment<a/> is commemorated by both a residential street "Blue Puttee Drive"
in St. John's, Newfoundland (2005) and one of the ferry that links
Newfoundland to the mainland, the MV Blue Puttes.</p>
<div class="example" style="white-space: pre-wrap;" id="basic">
<pre>
<mil:Regiment rdf:about="<a href="http://rdf.muninn-project.org/ww1/2011/11/11/Regiment/rnewfoundland">Royal Newfoundland Regiment</a>">
<foaf:name xml:lang="en">Royal Newfoundland Regiment<foaf:name>
<foaf:nickname>The Blue Puttees</foaf:nickname>
<graves:hasCommemoration>
<naval:Ship rdf:about="MvBluePuttess">
<foaf:name xml:lang="en">Blue Puttees<foaf:name>
<naval:Ship>
</graves:hasCommemoration>
<graves:hasCommemoration rdf:resource="<a href="http://linkedgeodata.org/triplify/way77366106">Blue Puttee Drive on OSM</a>"/>
</mil:Regiment>
</pre>
</div>
<p>A void description of all Royal Newfoundland Regiment soldiers can be found <a
href="http://rdf.muninn-project.org/ww1/SoldiersNewfoundland">here</a> and an example query of all Royal Newfoundland
Regiment personnel is <a
href="http://rdf.muninn-project.org/sparql?query=SELECT+*+WHERE+{+?s+?p+<http://rdf.muninn-project.org/ww1/SoldiersNewfoundland>+}&output=htmltab&jsonp=&key=&show_inline=1">here</a>.</p>
<h4 id="example_RegimentalRoll">Recording regimental rolls</h2>
<p>A Regimental Roll, a document recording the soldiers part of a Regiment at a point in time is a commonly seen historical
document. However, they are problematic in that they represent the roster of the Regiment at a single point in time whereas
soldiers are continually joining and leaving the unit over time. This is also true of some biographical information that
will be listed in some commemoration plaques that list a rank along with the person's details.
</p>
<div class="example" style="white-space: pre-wrap;" id="basic">
<pre>
<mil:Soldier rdf:about="<a href="http://rdf.muninn-project.org/bna/2011/11/11/Soldier/7b9c018d7774454517039fb700d1d145"> Pvt. Joseph Preston </a>">
<rdfs:label xml:lang="en">Joseph Preston (Soldier, British Army)</rdfs:label>
<-- Not sure when this happened, but Joseph was still a private when he died. -->
<mil:heldRank rdf:resource="<a href="http://rdf.muninn-project.org/ontologies/military#Rank_Private_England">Rank of Private, British Army </a>"/>
<mil:isPrincipalOf rdf:resource="<a href="http://rdf.muninn-project.org/bna/2011/11/11/PostToUnit/7b9c018d7774454517039fb700d1d145"> Pvt. Preston joins the Regt. </a>"/>
<mil:deathday rdf:resource="<a href="http://rdf.muninn-project.org/bna/2011/11/11/Death/7b9c018d7774454517039fb700d1d145"> Joseph's Death</a>"/>
<-- These properties are inherited from the foaf ontologies -->
<mil:name>Joseph Preston</mil:name>
<mil:firstName>Joseph</mil:firstName>
<mil:lastName>Preston</mil:lastName>
<mil:birthday rdf:resource="<a href="http://rdf.muninn-project.org/bna/2011/11/11/Birth/7b9c018d7774454517039fb700d1d145"> Joseph's Birth</a>"/>
</mil:Soldier>
</pre>
</div>
<p>One could generate an empty event that would account for Private Preston's enlistment and promotion to Private, however in
some cases the complexity in descriptive RDF is not warranted or wanted. The heldRank property is for these occasions and
special case should be made to ensure that the data has provenance information so that a gross temporal period can be
assigned to the event.</p>
<h3 id="definition_list">Global cross reference</h3>
<!-- The list of classes and properties goes here -->
%s
<!-- End of the terms list -->
<h3>Rank instances cross referenced by country.</h3>
<!-- ranks are xref here -->
m4_include(military-ranks.links)
<h2 id="reference">Detailed references for all terms, classes and
properties.</h2>
<p></p>
<!-- The following is the script-generated list of classes and properties -->
%s
<!-- End of the terms list -->
<h3 id="linkages">Linkages to other ontologies and vocabularies.</h3>
<div style="padding: 1em; border: dotted; background-color: #66FFFF;margin-left: auto; margin-right: auto;">
<p>
m4_include(military-links.html)
</p>
</div>
<h2 id="notesEvent">Notes on Military Events</h2>
<p>There are over a half-dozen vocabularies that deal with events, each with different semantics. At present none are
dominant or able to deal in a structured way with all of the facets of recording a real world event. To record events, the
military ontology provides a term MilitaryEvent that is really an empty class that is ontologically linked to every known
class resembling an event. While not intended as a long term solution, it provides SKOS/OWL translation to as many
alternate vocabularies and ontologies without claiming to be a superior solution. Temporal anchoring is provided by Time
OWL, participants are recorded by being linked to the event through a Role with the notable exception of the hasPrincipal
properties that links the principal actors to their event.</p>
<h2 id="notesSKOS">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 the military 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 military ontology are deep and require reasoning support.
OWL is the preferred means of using this ontology, through the usage of the terms, SKOS-style,
is possible. </p>
</p>
<h2 id="conclusion">Conclusion and Future Work</h2>
<p>Modelling military organizations is a complex endeavour that is made all that more so because of historical changes made to
them over time. This ontology is a first step in standardizing references to military units, ranks and events.</p>
<h2 id="version_history">Version History</h2>
<ul>
<li><p>0.1 - Initial unstable release.</p></li>
<li>0.2</li>
<ul><li> - Add Canadian Expeditionary Force references. </li>
<li> - Fixes to Unicode URLs.</li>
</ul>
<li>0.3</li>
<ul>
<li> Fix improper shorthand references in resource URLs. Thank you to Bernard Vatant
and Pierre-Yves Vandenbussche of the <a href="http://lov.okfn.org">LOV</a> project for spotting
this.</li>
<li> - Added <a href="http://vocab.org/vann/">vann:preferredNamespacePrefix</a> to mil.</li>
<li> - Fix ontology headers and declare previous ontologies incompatible because of improper
shorthand. This will <it>not</it> affect term instances which remain the
same.</li>
<li> - Standardized a number of ranks from the CEF.</li>
<li> - Add data-set description. </li>
<li>- Dropped references to Muninn Organization ontology and moved to W3 Organization Ontology.</li>
<li>- Added references to Roman era troops. Thank you to Scott Vanderbilt.</li>.
<li>- Forced split between Service and Country.</li>
</ul>
<li>0.5</li>
<ul>
<li> - Added missing void:inDataset and rdfs:isDefinedBy statements.</li>
<li> - Added CEF ranks. </li>
<li> - deprecated toUnit in favour of W3 Org term <a href="http://www.w3.org/ns/org#unitOf">unitOf</a>.</li>
<li> - Fixes to MilitaryEvent.</li>
<li> - deprecated Official Timocracy of Sapinetia as a fake country in Wikipedia / DBPedia. See
<a href="http://en.wikipedia.org/wiki/Official_Timocracy_of_Sapinetia">Deletion Log</a>.</li>
</ul>
<li>0.7</li>
<ul>
<li>Fixed minor issues with missing objects.
</ul>
<li>0.9</li>
<ul>
<li>Added more terms related to <a href="#AncientRome">Ancient Rome</a>.
<li>Fixes on internal structure.
</ul>
</ul>
<h2>Bibliography</h2>
m4_include(military-citations.html)
<!-- =====================================================================
===================================================================== -->
</body>
</html>