-
Notifications
You must be signed in to change notification settings - Fork 4
/
content.xml
982 lines (950 loc) · 52.8 KB
/
content.xml
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
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
<?xml version="1.0" encoding="UTF-8"?>
<content>
<index>
<div>
<p>Nomisma.org is a collaborative project to provide stable digital representations of numismatic concepts according to the principles of <a
href="http://www.w3.org/DesignIssues/LinkedData.html">Linked Open Data</a>. These take the form of http URIs that also provide access to
reusable information about those concepts, along with links to other resources. The canonical format of nomisma.org is RDF/XML, with
serializations available in JSON-LD (including geoJSON-LD for complex geographic features), Turtle, KML (when applicable), and HTML5+RDFa
1.1.</p>
<p>While the URIs provided by nomisma.org are stable, the project is in progress and subject to constant expansion and ongoing correction. This is
particularly the case for the information provided about each nomisma.org identifier.</p>
<p>The information provided by nomisma.org has been provided by a wide community of scholars and insitutions.</p>
<p>The project is steered by a committee currently consisting of:</p>
<ul>
<li>Rahel Ackermann, Swiss Inventory of Coin Finds</li>
<li>Florence Codine, <a href="https://www.ephe.fr/">Ecole Pratique des Hautes Etudes</a></li>
<li>Karsten Dahmen, <a href="http://ww2.smb.museum/ikmk/">MK Berlin</a></li>
<li>Frédérique Duyrat, <a href="http://www.bnf.fr/">BnF</a></li>
<li>Ethan Gruber, <a href="http://numismatics.org">ANS</a></li>
<li>Sebastian Heath, <a href="http://isaw.nyu.edu/">NYU ISAW</a></li>
<li>Jerome Mairat, <a href="https://www.ashmolean.org/">Ashmolean Museum, Oxford</a></li>
<li>Andrew Meadows, <a href="http://www.new.ox.ac.uk/">New College, Oxford University</a></li>
<li>Ulrike Peter, <a href="http://www.bbaw.de/en/">Berlin-Brandenburg Academy of Sciences and Humanities</a></li>
<li>Karsten Tolle, <a href="http://www.dbis.informatik.uni-frankfurt.de/">DBIS, University of Frankfurt</a></li>
<li>David Wigg-Wolf, <a href="http://www.dainst.org/en/department/rgk">DAI RGK</a></li>
</ul>
<p>Nomisma.org also hosts the <a href="https://github.com/ewg118/NUDS">Numismatic Description XML Schema</a></p>
<p>There are two Github repositories associated with the project. The application code is available in <a
href="https://github.com/nomisma/framework">https://github.com/nomisma/framework</a>. The RDF/XML data and ontology versions are in <a
href="https://github.com/nomisma/data">https://github.com/nomisma/data</a>.</p>
</div>
<div>
<h3>Example Nomisma.org URIs</h3>
<p>Nomisma.org focuses on URIs for concepts that are unique to numismatics or which have a distinct meaning within the discipline. Examples are:</p>
<ol>
<li><a href="http://nomisma.org/id/axis">http://nomisma.org/id/axis</a>. The 'axis' is the angular relationship between the obverse and reverse
of a coin.</li>
<li><a href="http://nomisma.org/id/ephesus">http://nomisma.org/id/ephesus</a>. The 'mint' at Ephesus. Nomisma relates this numismatic concept to
other URIs such as <a href="http://dbpedia.org/resource/Ephesus">wikipedia</a>, <a href="http://pleiades.stoa.org/places/599612"
>Pleiades</a>, <a href="http://vocab.getty.edu/tgn/7002499">Getty thesauri</a>, and the <a
href="http://collection.britishmuseum.org/id/place/x107267">British Museum</a>.</li>
<li><a href="http://nomisma.org/id/quinarius">http://nomisma.org/id/quinarius</a>. Nomisma.org maintains lists of Roman and other denominations.
To indicate that “quinarius” is a concept within Roman numismatics, the Dublin Core property "dcterms:source" relates this URI to <a
href="http://nomisma.org/id/roman_numismatics">http://nomisma.org/id/roman_numismatics</a>.</li>
</ol>
</div>
</index>
<nuds>
<div>
<h1>Numismatic Description Schema (NUDS)</h1>
<p>The Numismatic Description Schema is a codified XML schema based on numismatic database fields proposed by Sebastian Heath and Andrew Meadows.
These fields, called the Numismatic Description Standard, are detailed at <a href="http://www.greekcoinage.org/nuds.html"
>http://www.greekcoinage.org/nuds.html</a>, and were originally published on Nomisma.org. The NUDS XML schema is based on this field list
and Ethan Gruber's preliminary work mapping coins to Encoded Archival Description, which was detailed in a 2009 Computer Applications in
Archaeology paper, <a href="http://proceedings.caaconference.org/paper/14_gruber_caa2009/">"Encoded Archival Description for Numismatic
Collections."</a> It is also influenced by the structure of <a href="http://www.tei-c.org/index.xml">TEI</a> and <a
href="http://www2.archivists.org/groups/technical-subcommittee-on-eac-cpf/encoded-archival-context-corporate-bodies-persons-and-families-eac-cpf"
>EAC-CPF</a>, common standards in the Digital Humanities, library and archival domains. Ideally, a NUDS record should implement XLink
attributes to integrate URIs from external Linked Open Data vocabulary systems, such as concepts defined on Nomisma.org itself. It allows for
the optional namespacing of <a href="https://sourceforge.net/p/epidoc/wiki/Home/">EpiDoc TEI</a> elements for legends and descriptions for more
complex tagging of inscriptions and prose.</p>
<h3>Resources</h3>
<ul>
<li>
<strong>Schema (stable):</strong>
<a href="http://nomisma.org/nuds.xsd">http://nomisma.org/nuds.xsd</a>. The current stable version of the NUDS XSD schema is hosted by
Nomisma.org at a permanent URI. It can be linked to from NUDS documents for validation. </li>
<li>
<strong>Schema (Github):</strong>
<a href="https://github.com/ewg118/NUDS">https://github.com/ewg118/NUDS</a>. All versions are available through Github. </li>
</ul>
</div>
</nuds>
<documentation>
<page stub="sparql" label="SPARQL examples">
<h1>SPARQL Examples</h1>
<p>This page contains a collection of basic SPARQL examples which can be applied to data in Nomisma.org. It is not intended to be an introduction to
SPARQL as a whole, but a good <a href="http://jena.apache.org/tutorials/sparql.html">tutorial</a> can be found on the Jena site.</p>
<ul>
<li>
<a href="#e1">List of all Roman Emperors</a>
</li>
<li>
<a href="#e4">All weights of Augustan denarii</a>
</li>
<li>
<a href="#e5">Average weight of Augustan denarii</a>
</li>
<li>
<a href="#e6">Coins of RIC Augustus 1A and 1B</a>
</li>
<li>
<a href="#e7">Average Diameter of RIC Augustus 1A</a>
</li>
<li>
<a href="#e8">All findspots for RIC Augustus 1A</a>
</li>
<li>
<a href="#e9">All coins found in Northamptonshire, ordered chronologically by issue</a>
</li>
</ul>
<h2>Querying within Nomisma.org Concepts</h2>
<div id="e1">
<h3>List of all Roman Emperors</h3>
<pre><![CDATA[PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
PREFIX nm: <http://nomisma.org/id/>
PREFIX nmo: <http://nomisma.org/ontology#>
PREFIX org: <http://www.w3.org/ns/org#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
SELECT ?uri ?label WHERE {
?uri a foaf:Person ;
skos:prefLabel ?label ;
org:hasMembership ?membership .
?membership org:role nm:roman_emperor .
FILTER(langMatches(lang(?label), "EN"))
} ]]>
</pre>
</div>
<h2>Querying Coins linked to Nomisma.org Concepts</h2>
<div id="e4">
<h3>All weights of Augustan denarii</h3>
<pre><![CDATA[PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX nm: <http://nomisma.org/id/>
PREFIX nmo: <http://nomisma.org/ontology#>
SELECT ?type ?weight WHERE {
?type nmo:hasAuthority nm:augustus ;
nmo:hasDenomination nm:denarius ;
dcterms:source nm:ric.
?coin nmo:hasTypeSeriesItem ?type .
?coin nmo:hasWeight ?weight
}]]>
</pre>
</div>
<div id="e5">
<h3>Average weight of Augustan denarii</h3>
<pre><![CDATA[PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX nm: <http://nomisma.org/id/>
PREFIX nmo: <http://nomisma.org/ontology#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
SELECT (AVG(xsd:decimal(?weight)) AS ?average) WHERE {
?type nmo:hasAuthority nm:augustus ;
nmo:hasDenomination nm:denarius ;
dcterms:source nm:ric.
?coin nmo:hasTypeSeriesItem ?type .
?coin nmo:hasWeight ?weight
}]]>
</pre>
</div>
<div id="e6">
<h3>Coins of RIC Augustus 1A and 1B</h3>
<p>This will also gather measurements data, source collecton (with English label), and thumbnail/references images.</p>
<pre><![CDATA[PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX nm: <http://nomisma.org/id/>
PREFIX nmo: <http://nomisma.org/ontology#>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
SELECT ?object ?type ?diameter ?weight ?axis ?type ?collection ?obvThumb ?revThumb ?obvRef ?revRef ?comThumb ?comRef WHERE {
{?object nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A> }
UNION { ?object nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1B> }
?object rdf:type nmo:NumismaticObject .
OPTIONAL { ?object nmo:hasWeight ?weight }
OPTIONAL { ?object nmo:hasDiameter ?diameter }
OPTIONAL { ?object nmo:hasAxis ?axis }
OPTIONAL { ?object dcterms:identifier ?identifier }
OPTIONAL { ?object nmo:hasCollection ?colUri .
?colUri skos:prefLabel ?collection FILTER(langMatches(lang(?collection), "EN"))}
OPTIONAL { ?object foaf:thumbnail ?comThumb }
OPTIONAL { ?object foaf:depiction ?comRef }
OPTIONAL { ?object nmo:hasObverse ?obverse .
?obverse foaf:thumbnail ?obvThumb }
OPTIONAL { ?object nmo:hasObverse ?obverse .
?obverse foaf:depiction ?obvRef }
OPTIONAL { ?object nmo:hasReverse ?reverse .
?reverse foaf:thumbnail ?revThumb }
OPTIONAL { ?object nmo:hasReverse ?reverse .
?reverse foaf:depiction ?revRef }
}]]>
</pre>
</div>
<div id="e7">
<h3>Average Diameter of RIC Augustus 1A</h3>
<pre><![CDATA[PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX nm: <http://nomisma.org/id/>
PREFIX nmo: <http://nomisma.org/ontology#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
SELECT (AVG(xsd:decimal(?diameter)) AS ?average) WHERE {
?object nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A> ;
nmo:hasDiameter ?diameter
}]]>
</pre>
</div>
<div id="e8">
<h3>All findspots for RIC Augustus 1A</h3>
<p>This will query all coins with individual finds and all coins linked to hoards or hoards with contents containing Augustus 1A. This query
makes use of the current Nomisma findspot data model (implemented April 2020). See <a href="http://nomisma.org/documentation/contribute"
>documentation</a> for further details.</p>
<pre><![CDATA[PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcmitype: <http://purl.org/dc/dcmitype/>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX nm: <http://nomisma.org/id/>
PREFIX nmo: <http://nomisma.org/ontology#>
PREFIX geo: <http://www.w3.org/2003/01/geo/wgs84_pos#>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX crm: <http://www.cidoc-crm.org/cidoc-crm/>
SELECT ?object ?title ?findspot ?placeName ?hoard ?hoardLabel ?lat ?long ?type ?burial WHERE {
{ ?object a nmo:NumismaticObject ;
nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>}
UNION { ?broader skos:broader+ <http://numismatics.org/ocre/id/ric.1(2).aug.1A> .
?object nmo:hasTypeSeriesItem ?broader ;
a nmo:NumismaticObject }
UNION { ?contents a dcmitype:Collection ;
nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A> .
?object dcterms:tableOfContents ?contents }
?object dcterms:title|skos:prefLabel ?title .
{ ?object nmo:hasFindspot/crm:P7_took_place_at/crm:P89_falls_within ?findspot }
UNION { ?object dcterms:isPartOf ?hoard .
?hoard a nmo:Hoard ;
skos:prefLabel ?hoardLabel ;
nmo:hasFindspot/crm:P7_took_place_at/crm:P89_falls_within ?findspot .
OPTIONAL {?hoard nmo:hasClosingDate ?burial . FILTER isLiteral(?burial)}
OPTIONAL {?hoard nmo:hasClosingDate ?closing .
?closing nmo:hasEndDate ?burial}}
?findspot rdfs:label ?placeName ;
geo:location ?loc .
?loc geo:lat ?lat ;
geo:long ?long .
OPTIONAL { ?object rdf:type ?type FILTER (?type != skos:Concept)}
OPTIONAL { ?object nmo:hasClosingDate ?burial . FILTER isLiteral(?burial) }}]]>
</pre>
</div>
<div id="e9">
<h3>All coins found in Northamptonshire, ordered chronologically by issue</h3>
<p>This query uses property paths to look for children of (crm:P89_falls_within) of the Wikidata URI for Northamptonshire, England
(http://www.wikidata.org/entity/Q23115).</p>
<pre><![CDATA[PREFIX crm: <http://www.cidoc-crm.org/cidoc-crm/>
PREFIX dcmitype: <http://purl.org/dc/dcmitype/>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
PREFIX geo: <http://www.w3.org/2003/01/geo/wgs84_pos#>
PREFIX nm: <http://nomisma.org/id/>
PREFIX nmo: <http://nomisma.org/ontology#>
PREFIX org: <http://www.w3.org/ns/org#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
SELECT ?coin ?type ?date ?place WHERE {
?coin nmo:hasFindspot/crm:P7_took_place_at/crm:P89_falls_within ?place ;
nmo:hasTypeSeriesItem ?type ;
a nmo:NumismaticObject .
?place crm:P89_falls_within+ <http://www.wikidata.org/entity/Q23115> .
?type nmo:hasEndDate ?date .
} ORDER BY ASC(?date) LIMIT 100]]></pre>
</div>
</page>
<page stub="contribute" label="How to Contribute Data">
<h1>How to Contribute Data</h1>
<p>In the spring of 2013, we took a new approach in establishing links from RIC types in <a href="http://numismatics.org/ocre/">OCRE</a> to physical
coins and hoards which reference those types. The model has evolved over time to be compliant to the new Nomisma ontology. The following models
are required before contributing data into the Nomisma triplestore for use in <a href="http://numismatics.org/ocre/">OCRE</a>, <a
href="http://numismatics.org/crro/">CRRO</a>, and other coin type projects.</p>
<p>The first basic prerequisite for participation is that each object you wish to contribute be accessible to the web with a distinct URI. This is
the core standard for Linked Open Data. After this, there are essentially two required elements for contributing data to a Nomisma-affiliated
project, influenced by the requirements for <a href="https://github.com/pelagios/pelagios-cookbook/wiki/Joining-Pelagios">joining</a> the <a
href="http://pelagios-project.blogspot.com/">Pelagios Project</a>: an RDF data dump (which also much be accessible by URL) and some metadata
about this dump, in <a href="http://www.w3.org/TR/void/">Vocabulary of Interlinked Datasets (VoID)</a> RDF.</p>
<h2>VoID RDF</h2>
<pre><code class="language-markup"><![CDATA[<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:void="http://rdfs.org/ns/void#">
<void:Dataset rdf:about="http://coins.lib.virginia.edu/">
<dcterms:title>The Fralin | UVa Art Museum Numismatic Collection</dcterms:title>
<dcterms:description>The Fralin Museum of Art at the University of Virginia numismatic
collection contains about 600 coins of mainly Greco-Roman origin.</dcterms:description>
<dcterms:publisher>University of Virginia Library</dcterms:publisher>
<dcterms:license rdf:resource="http://opendatacommons.org/licenses/odbl/"/>
<void:uriSpace>http://coins.lib.virginia.edu/id/</void:uriSpace>
<void:dataDump rdf:resource="http://coins.lib.virginia.edu/nomisma.rdf"/>
</void:Dataset>
</rdf:RDF>]]></code></pre>
<p>The void:Dataset should include the URI for your project, and this URI should be linked from each individual object (physical coin, coin type, or
hoard) within the data dump using the void:inDataset property (see examples, below). The dcterms:title, dcterms:description, dcterms:publisher,
and dcterms:license are all required. The title and description must be textual strings, but the publisher and license may be URIs. In fact, the
license <i>should</i> be a URI designating the dataset under an open license, such as those published by <a href="https://creativecommons.org/"
>Creative Commons</a> or <a href="http://opendatacommons.org/">Open Data Commons</a>. A literal rights statement (dcterms:rights) may be
made instead of a dcterms:license link.</p>
<h2>Data Dump Model</h2>
<p>The data dump model should conform to the standards established by Nomisma.org, including the use of the Nomisma ontology where applicable.</p>
<div class="section">
<h3>Physical Coins</h3>
<pre><code class="language-markup"><![CDATA[<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:void="http://rdfs.org/ns/void#"
xmlns:nmo="http://nomisma.org/ontology#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
<nmo:NumismaticObject rdf:about="http://coins.lib.virginia.edu/id/1991.17.140">
<dcterms:title>Antoninianus of Gallienus, Rome, 254-255. 1991.17.140.</dcterms:title>
<dcterms:identifier>1991.17.140</dcterms:identifier>
<nmo:hasCollection rdf:resource="http://nomisma.org/id/uva"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/ocre/id/ric.5.gall(1).143fA"/>
<dcterms:replaces rdf:resource="http://coins.lib.virginia.edu/display-uva?id=n1991_17_140"/>
<nmo:hasAxis rdf:datatype="http://www.w3.org/2001/XMLSchema#integer">6</nmo:hasAxis>
<nmo:hasDiameter rdf:datatype="http://www.w3.org/2001/XMLSchema#decimal">22</nmo:hasDiameter>
<nmo:hasWeight rdf:datatype="http://www.w3.org/2001/XMLSchema#decimal">2.86</nmo:hasWeight>
<dcterms:isPartOf rdf:resource="http://nomisma.org/id/olivers_orchard_hoards"/>
<nmo:hasObverse rdf:resource="http://coins.lib.virginia.edu/id/1991.17.140#obverse"/>
<nmo:hasReverse rdf:resource="http://coins.lib.virginia.edu/id/1991.17.140#reverse"/>
<void:inDataset rdf:resource="http://coins.lib.virginia.edu/"/>
</nmo:NumismaticObject>
<rdf:Description rdf:about="http://coins.lib.virginia.edu/id/1991.17.140#obverse">
<foaf:depiction rdf:resource="http://coins.lib.virginia.edu/images/coins/screen/n1991_17_140_obv.jpg"/>
<foaf:thumbnail rdf:resource="http://coins.lib.virginia.edu/images/coins/thumb/n1991_17_140_obv.jpg"/>
</rdf:Description>
<rdf:Description rdf:about="http://coins.lib.virginia.edu/id/1991.17.140#reverse">
<foaf:depiction rdf:resource="http://coins.lib.virginia.edu/images/coins/screen/n1991_17_140_rev.jpg"/>
<foaf:thumbnail rdf:resource="http://coins.lib.virginia.edu/images/coins/thumb/n1991_17_140_rev.jpg"/>
</rdf:Description>
</rdf:RDF>]]></code></pre>
<p>The title, publisher, and identifier are required, as is nmo:hasTypeSeriesItem. nmo:hasCollection is recommended for physical specimens.
Before submitting your data to nomisma, please contact the administrators to create a URI for your collection. A physical specimen must be
carry the nmo:NumismaticObject class. Finally, each object must contain a void:inDataset property linking to the URI of the void:Dataset in
the VoID metadata RDF.</p>
<p>There are several fields which are particular to physical objects (and not hoards): nmo:hasAxis, nmo:hasDiameter, nmo:hasWeight, and
obverse/reverse thumbnail and references images (to be added as necessary). Thumbnails and reference images that represent sides of coins
should be contained in the data objects linked with the nmo:hasObverse and nmo:hasReverse properties. If they are not contained in the
nmo:hasObverse or nmo:hasReverse, it is assumed that the images include both the obverse and reverse sides of the coin. None of these fields
is required, though the measurements can be used for quantitative analyses. The measurements should be associated with xsd:decimal for
weights and diameters, xsd:integer for axis (unless the source data uses fractional numbers for axes). The dcterms:isPartOf property is used
to link a coin to a coin hoard that has a published URI.</p>
<div class="section">
<h4 id="iiif">IIIF Integration</h4>
<p>The Nomisma RDF model has been extended to follow the Europeana Data Model <a
href="http://pro.europeana.eu/files/Europeana_Professional/Share_your_data/Technical_requirements/EDM_profiles/IIIFtoEDM_profile_042016.pdf"
>specifications</a> for defining IIIF images and services. Essentially, this requires additional triples about the reference image
(foaf:depiction), which should be defined as an edm:WebResource. This edm:WebResource should link to a JSON-LD IIIF manifest or
information object (dcterms:isReferencedBy) and the URI for the service (with the svcs:has_service property). The service should include
several triples that defines it as a IIIF image service.</p>
<p><strong>Note:</strong> The JSON-LD IIIF link in the edm:WebResource should be either:</p>
<ul>
<li>If the image represents either the obverse or reverse, the link should point to the info.json for the image</li>
<li>If the image depicts both the obverse and reverse simultaneously (as is the standard for British Museum and Harvard Art Museums
photographs), the link should be the full IIIF manifest.</li>
</ul>
<pre><code class="language-markup"><![CDATA[
<edm:WebResource rdf:about="https://rucore.libraries.rutgers.edu/api/iiif/image/2.0/rutgers-lib:45878;PTIF-1/full/600,/0/default.jpg">
<svcs:has_service rdf:resource="https://rucore.libraries.rutgers.edu/api/iiif/image/2.0/rutgers-lib:45878;PTIF-1"/>
<dcterms:isReferencedBy rdf:resource="https://rucore.libraries.rutgers.edu/api/iiif/image/2.0/rutgers-lib:45878;PTIF-1/info.json"/>
</edm:WebResource>
<svcs:Service rdf:about="https://rucore.libraries.rutgers.edu/api/iiif/image/2.0/rutgers-lib:45878;PTIF-1">
<dcterms:conformsTo rdf:resource="http://iiif.io/api/image"/>
<doap:implements rdf:resource="http://iiif.io/api/image/2/level1.json"/>
</svcs:Service>]]></code></pre>
<p>Be sure to include the following XML namespaces/prefixes in your RDF:</p>
<kbd>PREFIX edm: <http://www.europeana.eu/schemas/edm/></kbd>
<br/>
<kbd>PREFIX svcs: <http://rdfs.org/sioc/services#></kbd>
<br/>
<kbd>PREFIX doap: <http://usefulinc.com/ns/doap#></kbd>
</div>
<div class="section">
<h4>Findspot</h4>
<p>The findspot model is based upon the ARIADNE archaeological specification, using a combination of existing Nomisma RDF properties and
classes in combination with CIDOC-CRM properties. A coin is found by an event which may have occurred on a known date or date range and
a place. In an archaeological excavation or a find reported to an portable antiquities service, the very specific coordinates by be
presented. Regardless of whether the specific coordinates are known or able to be made public, the findspot occurs <i>within</i> the
place defined by a Gazetteer URI. Allowable gazetteers are Wikidata, Geonames, the Getty Thesaurus of Geographic Names, Ordnance Survey,
and the Pleiades Gazetteer of Ancient Names. Upon ingestion into Nomisma.org, these URIs will automatically be reconciled to Wikidata
Entity URIs, when applicable, and the geographic coordinates, hierarchy, and skos:closeMatch URIs will also be extracted via SPARQL from
Wikidata.</p>
<p>When the findspot conforms to one of the aforementioned URI schemes, the crm:E53_Place and its spatial extent do not have to be
explicitly included in the RDF export, since these will be programmatically extracted from Wikidata.org to improve consistency across
harvested datasets. The crm:E53_Place that defines the gazetteer URI includes two properties (in the WGS84 geo ontology and CIDOC-CRM)
pointing to the same node for the spatial expression, which bears two RDF classes. This model is dually compatible with CIDOC-CRM and
the more common WGS84 geo ontology.</p>
<pre><code class="language-markup"><![CDATA[<nmo:NumismaticObject rdf:about="https://finds.org.uk/database/artefacts/record/id/1018642">
<nmo:hasFindspot>
<nmo:Find>
<crm:P7_took_place_at>
<crm:E53_Place>
<rdfs:label xml:lang="en">Hollingbourne</rdfs:label>
<crm:P89_falls_within rdf:resource="http://www.wikidata.org/entity/Q9199209"/>
</crm:E53_Place>
</crm:P7_took_place_at>
</nmo:Find>
</nmo:hasFindspot>
</nmo:NumismaticObject>
<crm:E53_Place rdf:about="http://www.wikidata.org/entity/Q9199209">
<rdfs:label>Hollingbourne</rdfs:label>
<crm:P89_falls_within rdf:resource="http://www.wikidata.org/entity/Q737114"/>
<skos:closeMatch rdf:resource="http://sws.geonames.org/2646748"/>
<skos:closeMatch rdf:resource="http://data.ordnancesurvey.co.uk/id/4000000074547229"/>
<skos:closeMatch rdf:resource="http://sws.geonames.org/7295882"/>
<skos:closeMatch rdf:resource="http://data.ordnancesurvey.co.uk/id/7000000000018330"/>
<geo:location rdf:resource="http://www.wikidata.org/entity/Q9199209#this"/>
<crm:P168_place_is_defined_by rdf:resource="http://www.wikidata.org/entity/Q9199209#this"/>
</crm:E53_Place>
<geo:SpatialThing rdf:about="http://www.wikidata.org/entity/Q9199209#this">
<rdf:type rdf:resource="http://www.ics.forth.gr/isl/CRMgeo/SP5_Geometric_Place_Expression"/>
<crmgeo:Q9_is_expressed_in_terms_of rdf:resource="http://www.wikidata.org/entity/Q215848"/>
<geo:lat rdf:datatype="http://www.w3.org/2001/XMLSchema#decimal">51.2675</geo:lat>
<geo:long rdf:datatype="http://www.w3.org/2001/XMLSchema#decimal">0.641111111</geo:long>
<crmgeo:asWKT rdf:datatype="http://www.opengis.net/ont/geosparql#wktLiteral">Point(0.641111111 51.2675)</crmgeo:asWKT>
</geo:SpatialThing>
</nmo:NumismaticObject>]]></code></pre>
<p>The above model can be described as follows:</p>
<p>A coin was found (nmo:hasFindspot, repurposing an existing property to stand in for crmsci:O19i_was_object_found_by from ARIADNE), which
is represented by the event of an nmo:Find (equivalent to crmsci:S19_Encounter_Event). <i>From this point, the model conforms to
CIDOC-CRM</i>. The Find took place at (crm:P7_took_place_at) a place (crm:E53_Place). This place is often amorphous. We don't
necessarily know the precise place on earth where the coin was found. In the event that we do, we can insert the
crm:P168_place_is_defined_by and geo:location properties here to point to precise coordinates. The rdfs:label can be any human-readable
label, such as "Farmer Jones' field." Usually the rdfs:label is the gazetteer preferred label. This blank node of an E53_Place exists
within the broader geographic concept defined by the gazetteer URI (crm:P89_falls_within). This gazetteer URI can be the
lowest-geographic level known, from a Pleiades URI for a temple to the country.</p>
<ul>
<li>The nmo:Find can accommodate any other CIDOC-CRM properties available to a CRM Event class, such as dates.</li>
<li>In the event that two coins were found during the same finding event, it may be necessary to give the nmo:Find a reusable URI,
instead of using a blank node that will not be able to connect multiple coins found at the same time.</li>
</ul>
</div>
</div>
<div class="section">
<h3>Hoards</h3>
<pre><code class="language-markup"><![CDATA[<rdf:RDF xmlns:nmo="http://nomisma.org/ontology#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:void="http://rdfs.org/ns/void#"
xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
xmlns:skos="http://www.w3.org/2004/02/skos/core#"
xmlns:dcmitype="http://purl.org/dc/dcmitype/"
xmlns:relations="http://pelagios.github.io/vocab/relations#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
<nmo:Hoard rdf:about="http://numismatics.org/chrr/id/SCU">
<dcterms:title xml:lang="en">Scurta (Romania; SCU)</dcterms:title>
<nmo:hasFindspot>
<nmo:Find>
<crm:P7_took_place_at>
<crm:E53_Place>
<rdfs:label xml:lang="en">Scurta, Romania</rdfs:label>
<crm:P89_falls_within rdf:resource="https://sws.geonames.org/663431/" />
</crm:E53_Place>
</crm:P7_took_place_at>
</nmo:Find>
</nmo:hasFindspot>
<nmo:hasClosingDate rdf:datatype="http://www.w3.org/2001/XMLSchema#gYear">0014</nmo:hasClosingDate>
<dcterms:tableOfContents rdf:resource="http://numismatics.org/chrr/id/SCU#contents"/>
<void:inDataset rdf:resource="http://numismatics.org/chrr/"/>
</nmo:Hoard>
<dcmitype:Collection rdf:about="http://numismatics.org/chrr/id/SCU#contents">
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-252.1"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-276.1"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-278.1"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-286.1"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-350A.2"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-362.1"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-393.1a"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/crro/id/rrc-463.3"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/ocre/id/ric.1(2).aug.541"/>
<nmo:hasTypeSeriesItem rdf:resource="http://numismatics.org/ocre/id/ric.1(2).aug.340"/>
</dcmitype:Collection>
<crm:E53_Place rdf:about="https://sws.geonames.org/257598/">
<rdfs:label>Matala (Greece)</rdfs:label>
<crm:P2_has_type rdf:resource="http://vocab.getty.edu/aat/300008347" />
geo:location rdf:resource="https://sws.geonames.org/257598/#this" />
<crm:P168_place_is_defined_by rdf:resource="https://sws.geonames.org/257598/#this" />
</crm:E53_Place>
<geo:SpatialThing rdf:about="https://sws.geonames.org/663431/#this">
<rdf:type rdf:resource="http://www.ics.forth.gr/isl/CRMgeo/SP5_Geometric_Place_Expression" />
<crmgeo:Q9_is_expressed_in_terms_of rdf:resource="http://www.wikidata.org/entity/Q215848" />
<geo:lat rdf:datatype="http://www.w3.org/2001/XMLSchema#decimal">46.10391</geo:lat>
<geo:long rdf:datatype="http://www.w3.org/2001/XMLSchema#decimal">26.19728</geo:long>
<crmgeo:asWKT rdf:datatype="http://www.opengis.net/ont/geosparql#wktLiteral">POINT (26.19728 46.10391)</crmgeo:asWKT>
</geo:SpatialThing>
</rdf:RDF>]]></code></pre>
<p>Like physical coins, the dcterms:title, and dcterms:identifier are required, and the resource must carry the nmo:Hoard class. Similarly, the
void:inDataset property is required in the nmo:Hoard object to link to the void:Dataset URI.</p>
<p>Presently, the hoard model is very simple and does not contain all the information stored in the database or NUDS XML record. The nmo:Hoard
object should link to a dcmitype:Collection, which merely contains a list of associated TypeSeriesItems (linked with the
nmo:hasTypeSeriesItem property). These records are meant to facilitate basic mapping and timelines in OCRE and CRRO. We anticipate enhancing
the hoard model over the coming year.</p>
<p>The nmo:hasClosingDate is optional, but if it is a year, it should conform to the rdf:datatype, xsd:gYear (four digit number, padded with
zeroes. Negative numbers represent B.C. dates).</p>
<p>The nmo:hasFindspot should be expressed like the example of an individual find, above.</p>
</div>
</page>
</documentation>
<apis>
<h1>Documentation</h1>
<p>This page contains documentation for using web services provided by Nomisma and how to access machine readable serializations through REST and
content negotiation.</p>
<p>Note that all APIs, including the SPARQL endpoint, are also accessible securely through https URLs. HTTP URLs are not automatically forwarded to
HTTPS due to unpredictable downstream effects by Nomisma data and web service consumers.</p>
<ul>
<li>
<a href="#apis">APIs</a>
</li>
<li>
<a href="#reconciliation">OpenRefine Reconciliation Service</a>
</li>
<li>
<a href="#access">Accessing Data</a>
</li>
</ul>
<div id="apis">
<h2>APIs</h2>
<table class="table">
<thead>
<tr>
<th style="width:50%">API</th>
<th>XML</th>
<th>JSON</th>
<th>Turtle</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<a href="#avgAxis">avgAxis</a>
</td>
<td>
<a href="apis/avgAxis?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>">XML</a>
</td>
<td>
<a href="apis/avgAxis?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>&format=json"
>JSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#avgDiameter">avgDiameter</a>
</td>
<td>
<a href="apis/avgDiameter?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>">XML</a>
</td>
<td>
<a href="apis/avgDiameter?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>&format=json"
>JSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#avgWeight">avgWeight</a>
</td>
<td>
<a href="apis/avgWeight?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>">XML</a>
</td>
<td>
<a href="apis/avgWeight?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>&format=json"
>JSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#closingDate">closingDate</a>
</td>
<td>
<a
href="apis/closingDate?identifiers=http://numismatics.org/crro/id/rrc-385.4|http://numismatics.org/crro/id/rrc-409.2|http://numismatics.org/ocre/id/ric.1(2).aug.1A"
>XML</a>
</td>
<td>
<a
href="apis/closingDate?identifiers=http://numismatics.org/crro/id/rrc-385.4|http://numismatics.org/crro/id/rrc-409.2|http://numismatics.org/ocre/id/ric.1(2).aug.1A&format=json"
>JSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#getLabel">getLabel</a>
</td>
<td>
<a href="apis/getLabel?uri=http://nomisma.org/id/ar&lang=fr">XML</a>
</td>
<td>
<a href="apis/getLabel?uri=http://nomisma.org/id/ar&lang=fr&format=json">JSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#getFindspots">getFindspots</a>
</td>
<td/>
<td>
<a href="apis/getFindspots?id=denarius">geoJSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#getHoards">getHoards</a>
</td>
<td/>
<td>
<a href="apis/getHoards?id=denarius">geoJSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#getMints">getMints</a>
</td>
<td/>
<td>
<a href="apis/getMints?id=denarius">geoJSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#query.json">query.json</a>
</td>
<td/>
<td>
<a
href="apis/query.json?query=query=PREFIX+rdf%3A%09<http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23>%0D%0APREFIX+dcterms%3A%09<http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2F>%0D%0APREFIX+geo%3A%09<http%3A%2F%2Fwww.w3.org%2F2003%2F01%2Fgeo%2Fwgs84_pos%23>%0D%0APREFIX+nm%3A%09<http%3A%2F%2Fnomisma.org%2Fid%2F>%0D%0APREFIX+nmo%3A%09<http%3A%2F%2Fnomisma.org%2Fontology%23>%0D%0APREFIX+xsd%3A%09<http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23>%0D%0A%0D%0ASELECT+DISTINCT+%3Fhoard+%3Ffindspot+%3Flat+%3Flong+WHERE+{%0D%0A++%3Ftype+a+nmo%3ATypeSeriesItem+%3B%0D%0A++++++++++nmo%3AhasDenomination+nm%3Atetradrachm+.%0D%0A++%3Fcoin+nmo%3AhasTypeSeriesItem+%3Ftype+%3B%0D%0A++++++++dcterms%3AisPartOf+%3Fhoard+.%0D%0A++%3Fhoard+a+nmo%3AHoard+%3B%0D%0A+++++++++++nmo%3AhasFindspot+%3Ffindspot+.%0D%0A++%3Ffindspot+geo%3Alat+%3Flat+%3B%0D%0A++++++++++++geo%3Along+%3Flong%0D%0A}"
>geoJSON</a>
</td>
<td/>
</tr>
<tr>
<td>
<a href="#query.kml">query.kml</a>
</td>
<td>
<a
href="apis/query.kml?query=query=PREFIX+rdf%3A%09<http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23>%0D%0APREFIX+dcterms%3A%09<http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2F>%0D%0APREFIX+geo%3A%09<http%3A%2F%2Fwww.w3.org%2F2003%2F01%2Fgeo%2Fwgs84_pos%23>%0D%0APREFIX+nm%3A%09<http%3A%2F%2Fnomisma.org%2Fid%2F>%0D%0APREFIX+nmo%3A%09<http%3A%2F%2Fnomisma.org%2Fontology%23>%0D%0APREFIX+xsd%3A%09<http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23>%0D%0A%0D%0ASELECT+DISTINCT+%3Fhoard+%3Ffindspot+%3Flat+%3Flong+WHERE+{%0D%0A++%3Ftype+a+nmo%3ATypeSeriesItem+%3B%0D%0A++++++++++nmo%3AhasDenomination+nm%3Atetradrachm+.%0D%0A++%3Fcoin+nmo%3AhasTypeSeriesItem+%3Ftype+%3B%0D%0A++++++++dcterms%3AisPartOf+%3Fhoard+.%0D%0A++%3Fhoard+a+nmo%3AHoard+%3B%0D%0A+++++++++++nmo%3AhasFindspot+%3Ffindspot+.%0D%0A++%3Ffindspot+geo%3Alat+%3Flat+%3B%0D%0A++++++++++++geo%3Along+%3Flong%0D%0A}"
>KML</a>
</td>
<td/>
<td/>
</tr>
<tr>
<td>
<a href="#getRdf">getRdf</a>
</td>
<td>
<a href="apis/getRdf?identifiers=rome|augustus|av|aureus">RDF/XML</a>
</td>
<td>
<a href="apis/getRdf?identifiers=rome|augustus|av|aureus&format=json">JSON-LD</a>
</td>
<td>
<a href="apis/getRdf?identifiers=rome|augustus|av|aureus&format=ttl">RDF/TTL</a>
</td>
</tr>
</tbody>
</table>
<div class="highlight">
<a name="avgAxis"/>
<h2>Average Axis</h2>
<p>Get average axis for given SPARQL query.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/avgAxis?<br/>
<b>Parameters</b> : constraints (following predicate - object format. multiple contraints separated by ' AND '. See examples below), format
('json' or 'xml', default 'xml')<br/>
<b>Result</b> : returns a decimal number in a response wrapper.<br/>
<b>Examples</b>: <a href="apis/avgAxis?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius"
>http://nomisma.org/apis/avgAxis?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius</a>
<br/>
<a href="apis/avgAxis?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>"
>http://nomisma.org/apis/avgWeight?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A></a>
</p>
</div>
<div class="highlight">
<a name="avgDiameter"/>
<h2>Average Diameter</h2>
<p>Get average diameter for given SPARQL query.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/avgDiameter?<br/>
<b>Parameters</b> : constraints (following predicate - object format. multiple contraints separated by ' AND '. See examples below), format
('json' or 'xml', default 'xml')<br/>
<b>Result</b> : returns a decimal number in a response wrapper.<br/>
<b>Examples</b>: <a
href="apis/avgDiameter?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius"
>http://nomisma.org/apis/avgDiameter?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius</a>
<br/>
<a href="apis/avgDiameter?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>"
>http://nomisma.org/apis/avgDiameter?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A></a>
</p>
</div>
<div class="highlight">
<a name="avgWeight"/>
<h2>Average Weight</h2>
<p>Get average weight for given SPARQL query.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/avgWeight?<br/>
<b>Parameters</b> : constraints (following predicate - object format. multiple contraints separated by ' AND '. See examples below), format
('json' or 'xml', default 'xml')<br/>
<b>Result</b> : returns a decimal number in a response wrapper.<br/>
<b>Examples</b>: <a
href="apis/avgWeight?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius"
>http://nomisma.org/apis/avgWeight?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius</a>
<br/>
<a href="apis/avgWeight?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>"
>http://nomisma.org/apis/avgWeight?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A></a>
</p>
</div>
<div class="highlight">
<a name="closingDate"/>
<h2>Closing Date</h2>
<p>Get the closing date of a hoard based on coin type URIs provided in the request parameter.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/closingDate?<br/>
<b>Parameters</b> : identifiers (coin type URIs divided by a pipe '|'), format ('json' or 'xml', default 'xml')<br/>
<b>Result</b> : returns an integer which represents the year. Negative numbers refer to B.C. dates.<br/>
<b>Examples</b>: <a
href="apis/closingDate?identifiers=http://numismatics.org/crro/id/rrc-385.4|http://numismatics.org/crro/id/rrc-409.2|http://numismatics.org/ocre/id/ric.1(2).aug.1A"
>http://nomisma.org/apis/closingDate?identifiers=http://numismatics.org/crro/id/rrc-385.4|http://numismatics.org/crro/id/rrc-409.2|http://numismatics.org/ocre/id/ric.1(2).aug.1A</a>
</p>
</div>
<div class="highlight">
<a name="getFindspots"/>
<h2>Get Findspots</h2>
<p>Get all individual find spots for a given skos:Concept defined by the id parameter or for a given coin type (nmo:TypeSeriesItem) defined by
the coinType parameter<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/getFindspots?<br/>
<b>Parameters</b> : id (of Nomisma ID) OR coinType (full URI for a coin type) OR symbol (full URI for a symbol [monogram, mint mark, etc.])<br/>
<b>Result</b> : returns geoJSON for features (points or polygons)<br/>
<b>Examples</b>: <a href="apis/getFindspots?id=denarius">apis/getFindspots?id=denarius</a>, <a
href="apis/getFindspots?coinType=http://numismatics.org/crro/id/rrc-408.1a"
>apis/getFindspots?coinType=http://numismatics.org/crro/id/rrc-408.1a</a>, <a
href="apis/getFindspots?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1"
>apis/getFindspots?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1</a>
</p>
</div>
<div class="highlight">
<a name="getHoards"/>
<h2>Get Hoards</h2>
<p>Get all hoards associated with a given skos:Concept defined by the id parameter or for a given coin type (nmo:TypeSeriesItem) defined by the
coinType parameter. If the skos:Concept is a hoard, then only one point is returned.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/getHoards?<br/>
<b>Parameters</b> : id (of Nomisma ID) OR coinType (full URI for a coin type) OR symbol (full URI for a symbol [monogram, mint mark, etc.])<br/>
<b>Result</b> : returns geoJSON for features (points or polygons)<br/>
<b>Examples</b>: <a href="apis/getHoards?id=denarius">apis/getHoards?id=denarius</a>, <a
href="apis/getHoards?coinType=http://numismatics.org/crro/id/rrc-408.1a"
>apis/getHoards?coinType=http://numismatics.org/crro/id/rrc-408.1a</a>, <a
href="apis/getHoards?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1"
>apis/getHoards?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1</a>
</p>
</div>
<div class="highlight">
<a name="getMints"/>
<h2>Get Mints</h2>
<p>Get all minting locations (may be nmo:Mint or nmo:Region) associated with a given skos:Concept defined by the id parameter. If the
skos:Concept is a mint or region, then only one point or polygon is returned.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/getMints?<br/>
<b>Parameters</b> : id (of Nomisma ID) OR symbol (full URI for a symbol [monogram, mint mark, etc.])<br/>
<b>Result</b> : returns geoJSON for features (points or polygons)<br/>
<b>Examples</b>: <a href="apis/getMints?id=denarius">apis/getMints?id=denarius</a>, <a
href="apis/getMints?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1"
>apis/getMints?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1</a>
</p>
</div>
<div class="highlight">
<a name="getLabel"/>
<h2>Get Label</h2>
<p>Get the label of a Nomisma ID given its URI and language code.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/getLabel?<br/>
<b>Parameters</b> : uri (of Nomisma ID), lang (two-letter ISO language code), format ('json' or 'xml', default 'xml')<br/>
<b>Result</b> : returns the label in given language, or English as default.<br/>
<b>Examples</b>: <a href="apis/getLabel?uri=http://nomisma.org/id/ar&lang=fr">apis/getLabel?uri=http://nomisma.org/id/ar&lang=fr</a>
</p>
</div>
<div class="highlight">
<a name="query.json"/>
<h2>Get GeoJSON for SPARQL Query</h2>
<p>Get a GeoJSON response for a SPARQL query that contains coordinates (SELECT, CONSTRUCT, DESCRIBE)<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/query.json?<br/>
<b>Parameters</b> : query (URL encoded SPARQL query)<br/>
<b>Result</b> : GeoJSON<br/>
<b>Examples</b>: <a
href="apis/query.json?query=PREFIX+rdf%3A%09<http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23>%0D%0APREFIX+dcterms%3A%09<http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2F>%0D%0APREFIX+geo%3A%09<http%3A%2F%2Fwww.w3.org%2F2003%2F01%2Fgeo%2Fwgs84_pos%23>%0D%0APREFIX+nm%3A%09<http%3A%2F%2Fnomisma.org%2Fid%2F>%0D%0APREFIX+nmo%3A%09<http%3A%2F%2Fnomisma.org%2Fontology%23>%0D%0APREFIX+xsd%3A%09<http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23>%0D%0A%0D%0ASELECT+DISTINCT+%3Fhoard+%3Ffindspot+%3Flat+%3Flong+WHERE+{%0D%0A++%3Ftype+a+nmo%3ATypeSeriesItem+%3B%0D%0A++++++++++nmo%3AhasDenomination+nm%3Atetradrachm+.%0D%0A++%3Fcoin+nmo%3AhasTypeSeriesItem+%3Ftype+%3B%0D%0A++++++++dcterms%3AisPartOf+%3Fhoard+.%0D%0A++%3Fhoard+a+nmo%3AHoard+%3B%0D%0A+++++++++++nmo%3AhasFindspot+%3Ffindspot+.%0D%0A++%3Ffindspot+geo%3Alat+%3Flat+%3B%0D%0A++++++++++++geo%3Along+%3Flong%0D%0A}"
>(click for full URL)</a>
</p>
</div>
<div class="highlight">
<a name="query.kml"/>
<h2>Get KML for SPARQL Query</h2>
<p>Get a KML response for a SPARQL query that contains coordinates (SELECT, CONSTRUCT, DESCRIBE)<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/query.kml?<br/>
<b>Parameters</b> : query (URL encoded SPARQL query)<br/>
<b>Result</b> : GeoJSON<br/>
<b>Examples</b>: <a
href="apis/query.kml?query=PREFIX+rdf%3A%09<http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23>%0D%0APREFIX+dcterms%3A%09<http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2F>%0D%0APREFIX+geo%3A%09<http%3A%2F%2Fwww.w3.org%2F2003%2F01%2Fgeo%2Fwgs84_pos%23>%0D%0APREFIX+nm%3A%09<http%3A%2F%2Fnomisma.org%2Fid%2F>%0D%0APREFIX+nmo%3A%09<http%3A%2F%2Fnomisma.org%2Fontology%23>%0D%0APREFIX+xsd%3A%09<http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23>%0D%0A%0D%0ASELECT+DISTINCT+%3Fhoard+%3Ffindspot+%3Flat+%3Flong+WHERE+{%0D%0A++%3Ftype+a+nmo%3ATypeSeriesItem+%3B%0D%0A++++++++++nmo%3AhasDenomination+nm%3Atetradrachm+.%0D%0A++%3Fcoin+nmo%3AhasTypeSeriesItem+%3Ftype+%3B%0D%0A++++++++dcterms%3AisPartOf+%3Fhoard+.%0D%0A++%3Fhoard+a+nmo%3AHoard+%3B%0D%0A+++++++++++nmo%3AhasFindspot+%3Ffindspot+.%0D%0A++%3Ffindspot+geo%3Alat+%3Flat+%3B%0D%0A++++++++++++geo%3Along+%3Flong%0D%0A}"
>(click for full URL)</a>
</p>
</div>
<div class="highlight">
<a name="getRdf"/>
<h2>Get RDF</h2>
<p>Aggregate RDF for Nomisma ids. The default stream is in RDF/XML, but Turtle and JSON-LD are available.<br/>
<b>Webservice Type</b> : REST<br/>
<b>Url</b> : nomisma.org/getRdf?<br/>
<b>Parameters</b> : identifiers (Nomisma ids divided by a pipe '|'), format ('xml', 'ttl', 'json'; default 'xml')<br/>
<b>Result</b> : RDF/XML, RDF/TTL. Other RDF formats will be supported eventually.<br/>
<b>Examples</b>: <a href="apis/getRdf?identifiers=rome|augustus|av|aureus">apis/getRdf?identifiers=rome|augustus|av|aureus</a>
</p>
</div>
<hr/>
</div>
<div id="reconciliation">
<h2>OpenRefine Reconciliation Service</h2>
<p>
<strong>Service URI:</strong>
<a href="http://nomisma.org/apis/reconcile">http://nomisma.org/apis/reconcile</a>
</p>
<p>Nomisma supports the following reconciliation services for OpenRefine:</p>
<ul>
<li>Main Reconciliation Service</li>
<li>Preview API</li>
<li>Entity Suggestion API (for autosuggest on matching terms)</li>
</ul>
<p>All API responses are in JSON. Please see the <a href="https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-Api">API
documentation</a> and <a href="https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation">usage documentation</a> for more details. The
blog post, <i><a href="http://numishare.blogspot.com/2017/10/nomisma-launches-openrefine.html">Nomisma launches OpenRefine reconciliation
service</a></i>, contains further information about this particular implementation in Nomisma.</p>
<hr/>
</div>
<div id="access">
<h2>Accessing Data</h2>
<div>
<h3>Individual Records</h3>
<p>Numishare supports delivery of individual records in a variety of models and serializations through both REST and content negotiation.
Content negotiation (with the accept header) requests should be sent to the URI space http://nomisma/id/. Requesting an unsupported content
type will result in an HTTP 406: Not Acceptable error.</p>
<table class="table">
<thead>
<tr>
<th>Model</th>
<th>REST</th>
<th>Content Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>HTML</td>
<td>http://nomisma.org/id/{$id}</td>
<td>
<code>text/html</code>
</td>
</tr>
<tr>
<td>KML</td>
<td>http://nomisma.org/id/{$id}.kml</td>
<td>
<code>application/vnd.google-earth.kml+xml</code>
</td>
</tr>
<tr>
<td>RDF/XML</td>
<td>http://nomisma.org/id/{$id}.rdf</td>
<td>
<code>application/rdf+xml</code>
</td>
</tr>
<tr>
<td>Turtle</td>
<td>http://nomisma.org/id/{$id}.ttl</td>
<td>
<code>text/turtle</code>
</td>
</tr>
<tr>
<td>JSON-LD</td>
<td>http://nomisma.org/id/{$id}.jsonld</td>
<td>
<code>application/ld+json</code>
</td>
</tr>
</tbody>
</table>
</div>
<div>
<h3>Search Results</h3>
<p>Search results (the browse page) are returned in HTML5, but Numishare supports Atom and RSS via REST, as well as Atom and raw Solr XML via
content negotiation of the browse page URL, http://nomisma.org/browse. The REST-based Atom feed sorts by the Lucene syntax 'timestamp desc'
by default, but the sort parameter may be provided manually to alter the default field and order.</p>
<table class="table">
<thead>
<tr>
<th>Model</th>
<th>REST</th>
<th>Content Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>HTML</td>
<td>
<a href="http://nomisma.org/browse">http://nomisma.org/browse</a>
</td>
<td>
<code>text/html</code>
</td>
</tr>
<tr>
<td>Atom</td>
<td>
<a href="http://nomisma.org/feed/">http://nomisma.org/feed/</a>
</td>
<td>
<code>application/atom+xml</code>
</td>
</tr>
<tr>
<td>Solr/XML</td>
<td>N/A</td>
<td>
<code>application/xml</code>
</td>
</tr>
</tbody>
</table>
</div>
<div>
<h3>Pelagios RDF Dump</h3>
<p>Data dumps conforming to the <a href="http://pelagios-project.blogspot.com/">Pelagios 3</a> model are linked on the index page. At present,
these files are only available in RDF/XML.</p>
<ul>
<li>
<a href="pelagios.void.rdf">VoID RDF</a>
</li>
<li>
<a href="pelagios.rdf">Dump RDF</a>
</li>
</ul>
</div>
</div>
</apis>
</content>