-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
759 lines (700 loc) · 24.5 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
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
756
757
758
759
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8"/>
<title>On Compositionality of ISO 25964 Hierarchical Relations (BTG, BTP, BTI)</title>
<link rel="stylesheet" href="../../reveal.js/css/reveal.min.css"/>
<link rel="stylesheet" href="../../reveal.js/css/theme/default.css" id="theme"/>
<!-- If the query includes 'print-pdf', include the PDF print sheet -->
<script>
if( window.location.search.match( /print-pdf/gi ) ) {
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = '../../reveal.js/css/print/pdf.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
}
</script>
<style type="text/css">
h1,h2,h3,h4,h5,h6,h7 {font-family: Arial}
// don't want empty lines in auto-postamble
.author, .date, .creator {-webkit-margin-before: 0em; -webkit-margin-after: 0em}
// style for #+begin_abstract
.abstract {margin: 1em; padding: 1em; border: 1px solid black}
.abstract:before {content: "Abstract: "; font-weight: bold}
// center the preamble (author name) and make it bigger
#preamble p { font-size: 110%; margin-left: auto; margin-right: auto; text-align: center; }
// table headers aligned same as table data
th.left {text-align:left}
th.right {text-align:right}
// table horizontal&vertical borders. First value is top&bottom, second is left&right. http://www.w3schools.com/css/css_border.asp
th, td {border-width: 1px; border-style: solid solid; border-spacing: 2px 2px; padding:4px 2px}
// colored TODO keywords
.CANCELED {color: blue}
.MAYBE {color: blue}
.POSTPONED {color: blue}
.INPROGRESS {color: orange}
.NEXT {color: orange}
.IER {color: orange}
</style>
<style>
.reveal .slides {text-align:left}
h1,h2,h3,h4,h5,h6,.center {text-align:center}
img,table {display: block; margin-left:auto!important; margin-right:auto!important}
td>img {width:250px; display:block; margin-left:auto!important; margin-right:auto!important; margin-top:0px!important; margin-bottom:0px!important}
.reveal th, .reveal td {font-size:80%; border: 1px; border-style: solid solid; border-spacing:0; padding:0px 2px}
span.clouditem {padding-left: 0.15em; padding-right: 0.15em; line-height: 90%}
#table-of-contents {font-size:70%}
</style>
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<h3>On Compositionality of ISO 25964 Hierarchical Relations (BTG, BTP, BTI)</h2> <p class='center'>Vladimir Alexiev, Ontotext Corp<br/> Jutta Lindenthal, Consultant to digiCULT-Verbund eG<br/> Antoine Isaac, Europeana and VU Amsterdam</p><br/> <p class='center'><a href="https://at-web1.comp.glam.ac.uk/pages/research/hypermedia/nkos/nkos2014/programme.html">Networked Knowledge Organization Systems (NKOS 2014) Workshop</a></p> <p class='center'>DL2014 Conference, London, 12 Sep 2014</p><br/> <p class='center'> <a href='http://VladimirAlexiev.github.io/pres/20140912-NKOS-compositionality/index.html' target='_blank'>2D interactive version</a>, <a href='http://VladimirAlexiev.github.io/pres/20140912-NKOS-compositionality/BTG-BTP-BTI-compositionality.pdf'>pdf</a>, <a href='http://www.slideshare.net/valexiev1/btgbtpbti-compositionality' target='_blank'>slideshare</a>.</p> <p class='center'>Press <a href='javascript:Reveal.toggleOverview()'>O for overview</a>, <a href='../../reveal.js/reveal-help.html' target='_blank'>H for help</a>.</p> <p class='center'>Proudly made in plain text with <a href='https://github.com/hakimel/reveal.js/'>reveal.js</a>, <a href='https://github.com/yjwen/org-reveal'>org-reveal</a>, <a href='http://orgmode.org'>org-mode</a> and <a href='http://www.gnu.org/s/emacs/'>emacs</a>.</p></section>
<section id="table-of-contents">
<h2>Table of Contents</h2><ul>
<li>
<a href="#/sec-1">BTG, BTP, BTI</a>
</li>
<li>
<a href="#/sec-2">Problem Statement</a>
</li>
<li>
<a href="#/sec-3">BTG, BTP, BTI Compositionality</a>
</li>
<li>
<a href="#/sec-4">Usage: Inferring ISO relations</a>
</li>
<li>
<a href="#/sec-5">BTP Imprecisions</a>
</li>
<li>
<a href="#/sec-6">BTI Elaborations</a>
</li>
<li>
<a href="#/sec-7">Thanks for your time!</a>
</li>
</ul>
</section>
<section>
<section id="sec-1" >
<h2>BTG, BTP, BTI</h2>
<p>
KOS have used different kinds of hierarchical relations for a long time:
</p>
<table border="1" cellspacing="0" cellpadding="0" rules="all" frame="box">
<colgroup>
<col class="left" />
<col class="left" />
<col class="left" />
<col class="left" />
</colgroup>
<tbody>
<tr>
<td class="left"><b>Relation</b></td>
<td class="left"><b>Abbr</b></td>
<td class="left"><b>Name</b></td>
<td class="left"><b>Example</b></td>
</tr>
<tr>
<td class="left">broaderGeneric</td>
<td class="left">BTG</td>
<td class="left">Genus/Species Relation</td>
<td class="left">mineral BTG inorganic material (AAT)</td>
</tr>
<tr>
<td class="left"> </td>
<td class="left"> </td>
<td class="left"> </td>
<td class="left">Iceland spar BTG calcite (AAT)</td>
</tr>
<tr>
<td class="left">broaderPartitive</td>
<td class="left">BTP</td>
<td class="left">Part/Whole Relation</td>
<td class="left">Tuscany BTP Italy (TGN)</td>
</tr>
<tr>
<td class="left">broaderInstantial</td>
<td class="left">BTI</td>
<td class="left">Kind/Instance Relation</td>
<td class="left">Rembrandt van Rijn BTI person (ULAN)</td>
</tr>
<tr>
<td class="left"> </td>
<td class="left"> </td>
<td class="left"> </td>
<td class="left"><a href="http://d-nb.info/gnd/5055902-3">SG Dynamo Dresden</a> BTI <a href="http://d-nb.info/gnd/4155742-6">football clubs</a> (GND)</td>
</tr>
</tbody>
</table>
</section>
<section id="sec-1-1" >
<h3>Use of BTG, BTP, BTI in Thesauri</h3>
<p>
Examples:
</p>
<ul class="org-ul">
<li>Deutsche Nationalbibliothek: <a href="http://d-nb.info/standards/elementset/gnd">Gemeinsame Normdatei Ontology</a>
<ul class="org-ul">
<li>gndo:broaderTermInstantial (see <a href="http://d-nb.info/050559028/about/rdf">Dynamo Dresden</a> in <a href="http://www.dnb.de/EN/lds">Linked Data Service</a>)
</li>
</ul>
</li>
<li>Some vocabs in xTree (vocnet.org) by digiCULT-Verbund eG
</li>
<li><a href="http://www.ldf.fi/schema/skosext/">FinnONTO SKOS Extensions</a> (Aalto University)
</li>
<li><a href="https://wordnet.princeton.edu/wordnet/man/wn.1WN.html">WordNet</a>, with BTP distinctions: member vs part vs substance meronym/holonym
</li>
<li><a href="http://purl.org/iso25964/skos-thes">ISO 25964 Ontology</a>: officially formalized (as "step" properties)
</li>
<li>Most recently, <a href="http://vocab.getty.edu">Getty Vocabulary Program (GVP) LOD</a>
<ul class="org-ul">
<li>First industrial application of ISO 25964
</li>
<li>Many examples in this presentation are from GVP
</li>
</ul>
</li>
</ul>
</section>
<section id="sec-1-2" >
<h3>Definitions in ISO 25964</h3>
<ul class="org-ul">
<li>BTG: amenable to logical all-and-some test
<ul class="org-ul">
<li>Children should all be a type, or kind of the parent
</li>
<li>From the parent's point of view, it encompasses only some of any given child
</li>
<li>Can be concluded it's comparable to rdfs:subClassOf (isA): transitive
</li>
</ul>
</li>
<li>BTP: part of entity/system belongs uniquely to particular possessing whole in any context
<ul class="org-ul">
<li>The part may not belong to more than one whole, and BTP has to be universally valid
</li>
<li><a href="http://www.getty.edu/research/tools/vocabularies/guidelines/aat_3_1_hierarchical_rels.html">AAT Guidelines</a>: "Each child should be part of the parent and all ancestors above it" (transitive)
</li>
</ul>
</li>
<li>BTI: individual instance to general class
<ul class="org-ul">
<li>Instances often represented by proper name (also called "classes of one")
</li>
<li>Instances may not have further BTI nor BTG
</li>
<li>But may be further subdivided: use custom relationship (BTX), eg BTS (subdivision)
</li>
</ul>
</li>
</ul>
</section>
<section id="sec-1-3" >
<h3>GVP Hierarchical Relation Counts</h3>
<img src="./img/hier-rel-per-type.png" alt="hier-rel-per-type.png" style="width:600px" />
</section>
<section id="sec-1-4" >
<h3>GVP Hierarchical Relations</h3>
<ul class="org-ul">
<li>AAT: most are BTG, but there is a variety of BTP:
<ul class="org-ul">
<li>(C) BTP (C): calendars of relics BTP cabinets of relics
</li>
<li>(C) BTP (G): anvil components BTP <anvils and anvil accessories>
</li>
<li>(G) BTP (C): <jewelry and accessory components> BTP jewelry
</li>
<li>(G) BTP (G): <grinding and milling equipment components> BTP <grinding and milling equipment>
</li>
<li>(C) BTP (H): building divisions BTP Single Built Works
</li>
</ul>
</li>
<li>TGN: all are BTP
<ul class="org-ul">
<li>placeType: in the current TGN LOD (2.0) has no relation to BTI
</li>
<li>May reconsider and make it subprop of BTI, see <a href="http://lists.w3.org/Archives/Public/public-esw-thes/2014Mar/att-0001/TGN-place-type.docx">TGN Place Type Relation</a> discussion paper
</li>
</ul>
</li>
<li>ULAN: most are BTI, e.g. Rembrandt (ULAN) Persons facet (ULAN)
<ul class="org-ul">
<li>May consider more specific, eg Rembrandt (ULAN) BTI Painters (AAT)
</li>
<li>Some BTP, e.g. corporate body BTP another corporate body
</li>
</ul>
</li>
</ul>
</section>
<section id="sec-1-5" >
<h3>GVP Hierarchy Structure</h3>
<ul class="org-ul">
<li>Subjects include (C)oncepts; but also: (F)acets, (H)ierarchies, (G)uide Terms
<ul class="org-ul">
<li>Not for indexing, only to structure. Implemented as iso:ThesaurusArray
</li>
<li>G and C can be intermixed: F>H>(G|C)
</li>
</ul>
</li>
</ul>
<img src="./img/007-subject-hierarchy.png" alt="007-subject-hierarchy.png" style="width:1100px" />
</section>
<section id="sec-1-6" >
<h3>SKOS/ISO vs GVP Impedance Mismatch</h3>
<ul class="org-ul">
<li>SKOS and ISO define <a href="http://vocab.getty.edu/doc/#Standard_Hierarchical_Relations">Standard Hierarchical Relations</a>
<ul class="org-ul">
<li>Only between Concepts
</li>
<li>skos:broader, iso:broaderGeneric, etc
</li>
</ul>
</li>
<li>We define custom <a href="http://vocab.getty.edu/doc/#GVP_Hierarchical_Relations">GVP Hierarchical Relations</a>
<ul class="org-ul">
<li>Connect the hierarchy uniformly
</li>
<li>gvp:broader, gvp:broaderGeneric, etc
</li>
</ul>
</li>
<li>We infer appropriate standard relations when they connect concepts directly
<ul class="org-ul">
<li>Notice the "thread-through" skos:narrower in the prev diagram
</li>
</ul>
</li>
</ul>
</section>
</section>
<section>
<section id="sec-2" >
<h2>Problem Statement</h2>
<p>
What are the appropriate combinations (compositions) of BTG, BTP, BTI?
</p>
<ul class="org-ul">
<li>Matters with respect to appropriate closure for information retrieval
</li>
<li>It's a prerequisite for sensible search expansion
</li>
<li>Has not been systematically analyzed to date
</li>
</ul>
</section>
<section id="sec-2-1" >
<h3>The problem with broaderTransitive</h3>
<p>
ISO 25964 formalized BTG, BTP, BTI as sub-properties of skos:broader
</p>
<ul class="org-ul">
<li>skos:broader contributes unconditionally to skos:broaderTransitive<br />
(broaderGeneric|broaderPartitive|broaderInstantial) => broader => broaderTransitive
</li>
<li><a href="https://at-web1.comp.glam.ac.uk/pages/research/hypermedia/nkos/nkos2012/presentations/TPDL2012_NKOS_Ambiguities.pptx">Ambiguities in representing thesauri using extended SKOS - examples from real life</a> (NKOS 2012):<br />
broaderTransitive should be established only for BTG and BTP, but not for BTI, nor mixed paths BTG+BTP
</li>
<li>skos:broaderTransitive may include semantically inappropriate statements
<ul class="org-ul">
<li>a place inherits all place types of its parents
</li>
<li>eg: Sofia BTP Bulgaria BTI country => Sofia BTI country
</li>
</ul>
</li>
<li>Lively discussion at SKOS mailing list <a href="http://lists.w3.org/Archives/Public/public-esw-thes/2013Nov/%20">from Nov 2013</a> to April 2014
</li>
</ul>
</section>
<section id="sec-2-2" >
<h3>The Time Has Come!</h3>
<p>
We <b>have</b> to resolve this issue for GVP LOD representation:
</p>
<ul class="org-ul">
<li>To infer appropriate thread-through standard relations
</li>
<li>Makes sense to represent TGN place types and ULAN actor roles as BTI
<ul class="org-ul">
<li>But skos:broaderTransitive causes confusion and bloat (100M=>400M statements)
</li>
</ul>
</li>
<li>So we want to infer only appropriate compositions (see <a href="http://vocab.getty.edu/doc/#BTG_BTP_BTI_Inference">BTG, BTP, BTI Inference</a>)
<ul class="org-ul">
<li>BTGE, BTPE, BTIE (gvp:broaderGenericExtended, gvp:broaderPartitiveExtended, gvp:broaderInstantialExtended)
</li>
<li>Their disjunction gvp:broaderExtended
</li>
<li>(Also gvp:broaderPreferred and gvp:broaderPreferredExtended)
</li>
</ul>
</li>
</ul>
</section>
</section>
<section>
<section id="sec-3" >
<h2>BTG, BTP, BTI Compositionality</h2>
<ul class="org-ul">
<li>Basic decision table. BT*x means BT*|BT*E
</li>
</ul>
<table border="1" cellspacing="0" cellpadding="0" rules="all" frame="box">
<colgroup>
<col class="left" />
<col class="left" />
<col class="left" />
<col class="left" />
</colgroup>
<tbody>
<tr>
<td class="left"> </td>
<td class="left"><b>BTGx</b></td>
<td class="left"><b>BTPx</b></td>
<td class="left"><b>BTIx</b></td>
</tr>
<tr>
<td class="left"><b>BTGx</b></td>
<td class="left">BTGE</td>
<td class="left">BTPE</td>
<td class="left">no</td>
</tr>
<tr>
<td class="left"><b>BTPx</b></td>
<td class="left">BTPE</td>
<td class="left">BTPE</td>
<td class="left">no</td>
</tr>
<tr>
<td class="left"><b>BTIx</b></td>
<td class="left">BTIE</td>
<td class="left">no</td>
<td class="left">no</td>
</tr>
</tbody>
</table>
<ul class="org-ul">
<li>BTG=>BTGE, BTP=>BTPE, BTI=>BTIE: basic inferences
</li>
</ul>
</section>
<section id="sec-3-1" >
<h3>BTG, BTP, BTI Compositionality (2)</h3>
<ul class="org-ul">
<li>BTGx/BTGx=>BTGE
<ul class="org-ul">
<li>If X is kind of Y and Y is kind of Z then X is kind of Z
</li>
<li>Eg: racehorses BTG <horses by use or role> BTG Equus caballus => racehorses BTGE Equus caballus
</li>
</ul>
</li>
<li>BTGx/BTPx=>BTPE
<ul class="org-ul">
<li>If X is kind of Y and Y is part of Z then X is part of Z (X can play the role of Y)
</li>
<li>Eg: beak irons BTG anvil components BTP <anvils and anvil accessories => beak irons BTPE <anvils and anvil accessories>
</li>
</ul>
</li>
<li>BTGx/BTIx=>n/a
<ul class="org-ul">
<li>A generic concept may not be hierarchically subordinate to an instance.
</li>
<li>The understanding of instance, as described in ISO, excludes this composition
</li>
</ul>
</li>
</ul>
</section>
<section id="sec-3-2" >
<h3>BTG, BTP, BTI Compositionality (3)</h3>
<ul class="org-ul">
<li>BTPx/BTGx=>BTPE.
<ul class="org-ul">
<li>If X is part of Y and Y is kind of Z then X is part of Z (Z can play the role of Y)
</li>
<li>Eg: anvil components BTP <anvils and anvil accessories> BTG <forging and metal-shaping tools> => anvil components BTPE <forging and metal-shaping tools>
</li>
</ul>
</li>
<li>BTPx/BTPx=>BTPE
<ul class="org-ul">
<li>If X is part of Y and Y is part of Z then X is part of Z
</li>
<li>Eg: Sofia BTP Bulgaria, Bulgaria BTP Europe, so Sofia BTP Europe
</li>
<li>But see mereological exceptions/imprecisions below!
</li>
</ul>
</li>
<li>BTPx/BTIx=>no
<ul class="org-ul">
<li>Counter-example: Sofia BTP Bulgaria BTI country. But Sofia is no country
</li>
</ul>
</li>
</ul>
</section>
<section id="sec-3-3" >
<h3>BTG, BTP, BTI Compositionality (4)</h3>
<ul class="org-ul">
<li>BTIx/BTGx=>BTIE
<ul class="org-ul">
<li>If X is instance of Y and Y is kind of Z, then X is instance of Z (Z can play the role of Y)
</li>
<li>Eg: Mt Athos BTI orthodox religious center BTG Christian religious center => Mt Athos BTIE Christian religious center
</li>
</ul>
</li>
<li>BTIx/BTPx=>no
<ul class="org-ul">
<li>Counter-example: Statue of Liberty pedestal BTI pedestals BTP statues. That particular pedestal is neither BTI nor BTP statues in general
</li>
<li>But see "beyond paths" below
</li>
</ul>
</li>
<li>BTIx/BTIx=>n/a
<ul class="org-ul">
<li>An instance as a class of one cannot have instances
</li>
<li>But see BTI Elaborations below
</li>
</ul>
</li>
</ul>
</section>
</section>
<section>
<section id="sec-4" >
<h2>Usage: Inferring ISO relations</h2>
<img src="./img/anvils-components.png" alt="anvils-components.png" style="width:800px" />
</section>
<section id="sec-4-1" >
<h3>Inferring ISO relations</h3>
<img src="./img/Secretariat-inference.png" alt="Secretariat-inference.png" />
</section>
<section id="sec-4-2" >
<h3>Inference Dependencies</h3>
<p>
<img src="./img/hierarchicalRelations-simplified.png" alt="hierarchicalRelations-simplified.png" />
(A bit simplified, see <a href="http://vocab.getty.edu/doc/#Hierarchical_Relations_Inference">GVP Hierarchical Relations Inference</a>)
</p>
</section>
<section id="sec-4-3" >
<h3>Usage 2: Query Expansion in Information Retrieval</h3>
<p>
The main purpose of a proper broader relation is to enable query expansion in information retrieval, eg:
</p>
<ul class="org-ul">
<li>Sofia BTP Bulgaria BTP Europe => Sofia BTPE Europe
<ul class="org-ul">
<li>Enables a search for places in Europe to also find Sofia
</li>
</ul>
</li>
<li>Mt Athos BTI orthodox religious centers BTG Christian religious centers BTG religious centers => Mt Athos BTIE religious centers
<ul class="org-ul">
<li>Enables a search for religious centers to also find Mt Athos
</li>
</ul>
</li>
</ul>
</section>
<section id="sec-4-4" >
<h3>Usage 3: Beyond Chain Inferences</h3>
<p>
If X <b>necessary</b> BTP Y and Z BTI X and T BTI Y then Z BTP T
</p>
<img src="./img/statue-pedestal.png" alt="statue-pedestal.png" />
<img src="./img/statue-pedestal.png" alt="statue-pedestal.png" style="width:600px" />
</section>
<section id="sec-4-5" >
<h3>Usage 3: Beyond Chain Inferences</h3>
<p>
If X <b>necessary</b> BTP Y and Z BTG Y then X BTP Z
</p>
<img src="./img/keyboard-instrument.png" alt="keyboard-instrument.png" style="width:600px" />
</section>
<section id="sec-4-6" >
<h3>Usage 4: Quality Checking</h3>
<img src="./img/swell-boxes.png" alt="swell-boxes.png" style="width:1000px" />
<ul class="org-ul">
<li>"swell boxes" BTG "organ components" BTP "organs (aerophones)" => BTPE
</li>
<li>"swell boxes" BTG "organs (aerophones)" is asserted in error
</li>
<li>Can catch it if we declare BTGE & BTPE as owl:disjointProperty
</li>
<li>But is this true in all cases?
</li>
</ul>
</section>
</section>
<section>
<section id="sec-5" >
<h2>BTP Imprecisions</h2>
<ul class="org-ul">
<li>Mixing partial vs full inclusion; and physical vs administrative:<br />
Netherlands Antilles BTP Netherlands BTP Europe ??
</li>
</ul>
<img src="./img/NetherlandsAntilles.png" alt="NetherlandsAntilles.png" style="width:900px" />
<ul class="org-ul">
<li>was until 1954: is in TGN with historic date qualification
</li>
<li>sample query: <a href="http://vocab.getty.edu/doc/#Places_Outside_Bounding_Box_Overseas_Possessions">Places Outside Bounding Box (Overseas Possessions)</a>
</li>
</ul>
</section>
<section id="sec-5-1" >
<h3>BTP Imprecisions (2)</h3>
<ul class="org-ul">
<li>Mixing Partial vs full inclusion:<br />
Istanbul BTP Turkey BTP Asia
</li>
</ul>
<p>
<img src="./img/Turkey.png" alt="Turkey.png" style="width:500px" />
How about Istanbul BTP Europe? It does straddle the Bosphorus strait:
</p>
<img src="./img/Istanbul_and_Bosporus.jpg" alt="Istanbul_and_Bosporus.jpg" style="width:200px" />
</section>
<section id="sec-5-2" >
<h3>BTP Imprecisions (3)</h3>
<ul class="org-ul">
<li>Mixing member vs substance meronym:<br />
chicken feet BTP chicken BTP chicken soup ??
</li>
<li>Mixing intrinsic vs extrinsic BTP; and categories (person vs group):<br />
Mick Jagger's BTP Mick Jagger BTP The Rolling Stones ??
</li>
</ul>
<p>
Mereology is a complex topic spanning: philosophy, mathematical logic, theoretical computer science, physics, Sheaf, Topos, or Category Theory, object-oriented programming.
</p>
<ul class="org-ul">
<li><a href="http://en.wikipedia.org/wiki/Mereology">Wikipedia article</a>
</li>
<li><a href="http://www.inf.unibz.it/krdb/pub/TR/KRDB06-3.pdf">Introduction to part-whole relations: mereology, conceptual modelling and mathematical aspects</a> (Maria Keet, 2006)
</li>
</ul>
</section>
</section>
<section>
<section id="sec-6" >
<h2>BTI Elaborations</h2>
<ul class="org-ul">
<li><a href="http://en.wikipedia.org/wiki/Metaclass">Metaclasses</a> in OOP and <a href="http://www.w3.org/2007/OWL/wiki/Punning">Punning</a> in OWL allow classes of classes, and use them profitably
</li>
<li>ISO: instance may have parts/subdivisions, recommends custom relation BTX (eg BTS=subdivsion)).<br />
Eg "BMW E87" BTS "BMW 1 Series" BTI "Automobiles"
</li>
<li>Biological classification: concepts belong to different levels (taxonomic ranks).<br />
Eg Secretariat (ULAN <named animal>) BTI racehorses BTG Equus caballus BTI species
</li>
</ul>
</section>
<section id="sec-6-1" >
<h3>BTI in Taxonomic Relations</h3>
<img src="./img/Secretariat.png" alt="Secretariat.png" />
</section>
<section id="sec-6-2" >
<h3>Do Individuals Belong in a Thesaurus?</h3>
<ul class="org-ul">
<li>TGN gave up placeType<BTI for now, because of non-sensical broaderTransitive
</li>
<li>If you exclude BTI then broaderExtended coincides with broaderTransitive: <code>BTG* | (BTG|BTP)* = (BTG|BTP)*</code>
</li>
<li>Some CRM SIG members: "Individuals don't belong to a thesaurus. Mixing individuals and generics is logically inconsistent"
</li>
<li>Eg in Getty LOD: <a href="http://vocab.getty.edu/tgn/7011781">tgn:7009977</a> London is gvp:adminplaceconcept, gvp:subject, skos:concept
<ul class="org-ul">
<li>Separate node <a href="http://vocab.getty.edu/tgn/7011781-place">tgn:7009977-place</a> is schema:Place, wgs:SpatialThing
</li>
<li>Such <a href="http://vocab.getty.edu/doc/#Concept_vs_Place_Duality">Concept vs Place Duality</a> is respected by VIAF, UK BL, FR BnF, SE KB; but not US LoC, DE DNB
</li>
</ul>
</li>
</ul>
</section>
<section id="sec-6-3" >
<h3>Do Individuals Belong in a Thesaurus? (2)</h3>
<p>
We think yes: main role of a thesaurus is a list of fixed values (concepts, people, etc)
</p>
<ul class="org-ul">
<li>Eg GND mixes 10M things: materials, subjects, football clubs, deities, ghosts
</li>
<li>Eg British Museum LOD: <a href="http://collection.britishmuseum.org/id/place/x17731">London England</a> is ecrm:E53_Place, skos:Concept (but latter may be removed)
</li>
<li>Eg LoC MARC Relators: <a href="http://id.loc.gov/vocabulary/relators/aut.html">Author</a> is skos:Concept, rdf:Property, owl:ObjectProperty !
</li>
</ul>
</section>
</section>
<section>
<section id="sec-7" >
<h2>Thanks for your time!</h2>
<ul class="org-ul">
<li><a href="https://drive.google.com/file/d/0B7BFygWDV2_PNkQycHl0bWNLak0">Draft paper</a> (some months old, these ideas are still evolving)
</li>
<li>Research conducted as part of GVP LOD publication: <a href="http://vocab.getty.edu">http://vocab.getty.edu</a>
<ul class="org-ul">
<li>See <a href="http://VladimirAlexiev.github.io/pres/20140905-CIDOC-GVP/index.html">CIDOC 2014 presentation</a>
</li>
<li>See doc (100 pages!): <a href="http://vocab.getty.edu/doc">http://vocab.getty.edu/doc</a>
</li>
</ul>
</li>
<li>The financial support of the J. Paul Getty Trust is gratefully acknowledged
</li>
</ul>
<img src="./img/QuestionMark.jpg" alt="QuestionMark.jpg" style="width:400px" />
</section>
</section>
</div>
</div>
<script src="../../reveal.js/lib/js/head.min.js"></script>
<script src="../../reveal.js/js/reveal.min.js"></script>
<script>
// Full list of configuration options available here:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: false,
center: true,
slideNumber: true,
rollingLinks: false,
keyboard: true,
overview: true,
width: 1200,
height: 925,
theme: Reveal.getQueryHash().theme, // available themes are in /css/theme
transition: Reveal.getQueryHash().transition || 'default', // default/cube/page/concave/zoom/linear/fade/none
transitionSpeed: 'default',
// Optional libraries used to extend on reveal.js
dependencies: [
{src: '../../reveal.js/js/reveal-help.js', async: true, condition: function() {return !!document.body.classList}}, {src: '../../reveal.js/js/reveal-tagcloud.js', async: true, condition: function() {return !!document.body.classList}},
{ src: '../../reveal.js/lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: '../../reveal.js/plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: '../../reveal.js/plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: '../../reveal.js/plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: '../../reveal.js/plugin/zoom-js/zoom.js', async: true, condition: function() { return !!document.body.classList; } },
{ src: '../../reveal.js/plugin/notes/notes.js', async: true, condition: function() { return !!document.body.classList; } }
]
});
</script>
</body>
</html>