-
Notifications
You must be signed in to change notification settings - Fork 4
/
index.html
3798 lines (3798 loc) · 204 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
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
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="generator" content="Asciidoctor 1.5.5">
<title>Guidelines for the RDF encoding of spatial data</title>
<link rel="stylesheet" href="stylesheets/inspire.css">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/css/font-awesome.min.css">
<link rel="stylesheet" href="stylesheets/pygments-autumn.css">
<style>.admonitionblock td.icon .icon-requirement:before { content: "\f06a"; color: #b30000; }</style>
<style>.admonitionblock td.icon .icon-recommendation:before { content: "\f06a"; color: #ffcc00; }</style>
<style>.admonitionblock td.icon .icon-permission:before { content: "\f06a"; color: #009933; }</style>
</head>
<body class="book toc2 toc-left">
<div id="header">
<div id="toc" class="toc2">
<div id="toctitle">Table of contents</div>
<ul class="sectlevel0">
<li><a href="#_guidelines_for_the_rdf_encoding_of_spatial_data">Guidelines for the RDF encoding of spatial data</a>
<ul class="sectlevel1">
<li><a href="#foreword">Foreword</a></li>
<li><a href="#_scope">1. Scope</a></li>
<li><a href="#_conformance">2. Conformance</a></li>
<li><a href="#_normative_references">3. Normative references</a></li>
<li><a href="#_terms_and_abbreviations">4. Terms and abbreviations</a>
<ul class="sectlevel2">
<li><a href="#ref_terms">4.1. Terms</a></li>
<li><a href="#_abbreviations">4.2. Abbreviations</a></li>
<li><a href="#_verbal_forms_for_the_expression_of_provisions">4.3. Verbal forms for the expression of provisions</a></li>
<li><a href="#_namespace_conventions">4.4. Namespace conventions</a></li>
</ul>
</li>
<li><a href="#overview">5. Overview</a></li>
<li><a href="#general_encoding_requirements">6. General encoding requirements</a>
<ul class="sectlevel2">
<li><a href="#_application_schema_and_schema_language">6.1. Application schema and schema language</a></li>
<li><a href="#_character_encoding">6.2. Character encoding</a></li>
<li><a href="#_exchange_metadata">6.3. Exchange metadata</a></li>
<li><a href="#_transfer_unit">6.4. Transfer unit</a>
<ul class="sectlevel3">
<li><a href="#_granularity_and_structure">6.4.1. Granularity and structure</a></li>
<li><a href="#_object_identification">6.4.2. Object identification</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#input_data_structure">7. Input data structure</a></li>
<li><a href="#output_data_structure">8. Output data structure</a></li>
<li><a href="#ref_cr">9. Schema conversion rules</a>
<ul class="sectlevel2">
<li><a href="#_general">9.1. General</a>
<ul class="sectlevel3">
<li><a href="#ref_cr_general_documentation">9.1.1. Documentation</a></li>
</ul>
</li>
<li><a href="#schema_conversion_pkg">9.2. Application schema package</a>
<ul class="sectlevel3">
<li><a href="#ref_cr_pkg_name">9.2.1. Ontology name and namespace</a></li>
<li><a href="#_version_information">9.2.2. Version information</a></li>
<li><a href="#_imports">9.2.3. Imports</a></li>
</ul>
</li>
<li><a href="#ref_cr_type">9.3. Types</a>
<ul class="sectlevel3">
<li><a href="#ref_cr_mappings">9.3.1. Mappings</a>
<ul class="sectlevel4">
<li><a href="#ref_cr_mappings_iso19103">ISO 19103</a></li>
<li><a href="#ref_cr_mappings_iso19107">ISO 19107</a></li>
<li><a href="#ref_cr_mappings_iso19108">ISO 19108</a></li>
<li><a href="#ref_cr_mappings_iso19115">ISO 19115</a></li>
<li><a href="#_iso_19139">ISO 19139</a></li>
<li><a href="#ref_cr_mappings_inspireAddresses">INSPIRE Annex I - Addresses</a></li>
<li><a href="#ref_cr_mappings_inspireGeographicalNames">INSPIRE Annex I - Geographical Names</a></li>
</ul>
</li>
<li><a href="#ref_cr_alignments">9.3.2. Alignments</a>
<ul class="sectlevel4">
<li><a href="#ref_cr_alignments_inspireAddresses">INSPIRE Annex I - Addresses</a></li>
</ul>
</li>
<li><a href="#ref_cr_type_name">9.3.3. Class name</a></li>
<li><a href="#ref_cr_type_abstract">9.3.4. Abstractness</a></li>
<li><a href="#ref_cr_type_inheritance">9.3.5. Inheritance</a></li>
<li><a href="#ref_cr_type_feature">9.3.6. Spatial object type</a>
<ul class="sectlevel4">
<li><a href="#ref_cr_type_feature_alignment">Alignment</a></li>
<li><a href="#ref_cr_type_feature_documentation">Documentation</a></li>
</ul>
</li>
<li><a href="#ref_cr_type_datatype">9.3.7. Data type</a></li>
<li><a href="#ref_cr_type_union">9.3.8. Union</a></li>
<li><a href="#ref_cr_type_enumeration">9.3.9. Enumeration</a></li>
<li><a href="#ref_cr_type_codelist">9.3.10. Code list</a></li>
</ul>
</li>
<li><a href="#ref_cr_prop">9.4. Properties</a>
<ul class="sectlevel3">
<li><a href="#ref_cr_prop_mappings">9.4.1. Mappings</a></li>
<li><a href="#ref_cr_prop_alignment">9.4.2. Alignment</a>
<ul class="sectlevel4">
<li><a href="#ref_cr_prop_alignment_geometry">Geometry</a></li>
<li><a href="#ref_cr_prop_alignment_geographicalName">Geographical name</a></li>
</ul>
</li>
<li><a href="#ref_cr_prop_omission">9.4.3. Omission</a></li>
<li><a href="#ref_cr_prop_name">9.4.4. Property name</a></li>
<li><a href="#ref_cr_prop_domain">9.4.5. Domain - local vs. global</a></li>
<li><a href="#ref_cr_prop_range">9.4.6. Range</a></li>
<li><a href="#ref_cr_prop_multiplicity">9.4.7. Multiplicity</a></li>
<li><a href="#ref_cr_prop_voidable">9.4.8. Voidable</a></li>
<li><a href="#ref_cr_prop_vocabulary_reference">9.4.9. Vocabulary reference</a></li>
<li><a href="#ref_cr_prop_attribute">9.4.10. Attribute</a></li>
<li><a href="#ref_cr_prop_associationrole">9.4.11. Association role</a></li>
</ul>
</li>
<li><a href="#ref_cr_association_class">9.5. Association class</a></li>
<li><a href="#ref_cr_constraint">9.6. Constraint</a></li>
</ul>
</li>
<li><a href="#ref_instance_cr">10. Instance conversion rules</a>
<ul class="sectlevel2">
<li><a href="#ref_instance_cr_input_to_output">10.1. From input to output data structure</a></li>
<li><a href="#ref_instance_cr_resource_identifier">10.2. Resource identifiers</a></li>
<li><a href="#ref_instance_cr_considerations_on_spatial_objects">10.3. Considerations on spatial objects</a></li>
<li><a href="#ref_instance_cr_geometry">10.4. Encoding geometry</a></li>
<li><a href="#ref_instance_cr_metadata">10.5. Encoding metadata</a></li>
<li><a href="#ref_instance_cr_value_collections">10.6. Value collections</a></li>
<li><a href="#ref_instance_cr_extensions">10.7. Extensions</a></li>
</ul>
</li>
<li><a href="#annex_a">Annex A - Vocabulary examples (informative)</a></li>
<li><a href="#_bibliography">Bibliography</a></li>
</ul>
</li>
</ul>
</div>
</div>
<div id="content">
<div id="preamble">
<div class="sectionbody">
<div id="EC_logo" class="imageblock" style="text-align: center">
<div class="content">
<img src="images/EC%20logo.jpeg" alt="European Commission Logo" width="150">
</div>
</div>
<table class="tableblock frame-none grid-none spread">
<colgroup>
<col style="width: 25%;">
<col style="width: 75%;">
</colgroup>
<tbody>
<tr>
<td class="tableblock halign-center valign-top"><p class="tableblock"><span class="image"><img src="images/INSPIRE%20logo.png" alt="INSPIRE Logo" width="150"></span></p></td>
<td class="tableblock halign-left valign-middle"><p class="tableblock"><span class="inspire_headline">INSPIRE<br>
Infrastructure for Spatial Information in Europe</span></p></td>
</tr>
</tbody>
</table>
</div>
</div>
<h1 id="_guidelines_for_the_rdf_encoding_of_spatial_data" class="sect0">Guidelines for the RDF encoding of spatial data</h1>
<div class="openblock partintro">
<div class="content">
<table class="tableblock frame-topbot grid-none spread">
<colgroup>
<col style="width: 50%;">
<col style="width: 50%;">
</colgroup>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Title</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Guidelines for the RDF encoding of spatial data</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Status</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Draft</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Creator</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">ARE3NA project "INSPIRE Re3ference Platform Phase 2"</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Date</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">2017-07-17</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Subject</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">INSPIRE encoding rules for representing spatial data as RDF</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Publisher</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">ARE3NA project "INSPIRE Re3ference Platform Phase 2"</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Type</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Text</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Description</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">This document specifies an experimental encoding rule for representing spatial data sets in INSPIRE as RDF. The use of RDF is optional and does not supersede or replace the requirements regarding encoding specified in Clause 9 of the Data Specifications. This optional encoding is intended to support the e-government and open data community in Europe, which is increasingly looking at RDF to represent data.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Format</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">HyperText Markup Language (HTML)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Licence</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution (cc-by) 4.0</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Identifier</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://inspire-eu-rdf.github.io/inspire-rdf-guidelines" class="bare">http://inspire-eu-rdf.github.io/inspire-rdf-guidelines</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Language</strong></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">EN</p></td>
</tr>
</tbody>
</table>
<div style="page-break-after: always;"></div>
<!-- toc disabled -->
<div style="page-break-after: always;"></div>
</div>
</div>
<div class="sect1">
<h2 id="foreword">Foreword</h2>
<div class="sectionbody">
<div class="paragraph">
<p>The challenges regarding the lack of availability, quality, organisation, accessibility, and sharing of spatial information are common to a large number of policies and activities and are experienced across the various levels of public authority in Europe. In order to solve these problems it is necessary to take measures of coordination between the users and providers of spatial information. The Directive 2007/2/EC of the European Parliament and of the Council adopted on 14 March 2007 aims at establishing an Infrastructure for Spatial Information in the European Community (INSPIRE) for environmental policies, or policies and activities that have an impact on the environment.</p>
</div>
<div class="paragraph">
<p>INSPIRE is based on the infrastructures for spatial information that are created and maintained by the Member States. To support the establishment of a European infrastructure, Implementing Rules addressing the following components of the infrastructure have been specified: metadata, interoperability of spatial data sets (as described in Annexes I, II, III of the Directive) and spatial data services, network services, data and service sharing, and monitoring and reporting procedures.</p>
</div>
<div class="paragraph">
<p>INSPIRE does not require collection of new data. However, Member States have to make their data available according to the Implementing Rules within two years of the adoption of the corresponding Implementing Rules for newly collected and extensively restructured data and within 5 years for other data in electronic format still in use.</p>
</div>
<div class="paragraph">
<p>Interoperability in INSPIRE means the possibility to combine spatial data and services from different sources across the European Community in a consistent way without involving specific efforts of humans or machines. 'Interoperability' is understood as providing access to spatial data sets through network services, typically via the Internet. Interoperability may be achieved by either changing (harmonising) and storing existing data sets or transforming them via services for publication in the INSPIRE infrastructure. It is expected that users will spend less time and efforts on understanding and integrating data when they build their applications based on data delivered in accordance with INSPIRE.</p>
</div>
<div class="paragraph">
<p>In order to benefit from the endeavours of international standardisation bodies and organisations established under international law their standards and technical means have been utilised and referenced, whenever possible.</p>
</div>
<div class="paragraph">
<p>An open and participatory approach was used during the development of the data specifications on Annex I, II and III data themes and the preparation of the Implementing Rule on Interoperability of Spatial Data Sets and Services.</p>
</div>
<div class="paragraph">
<p>The INSPIRE data specifications are built on a development framework. The following two documents from the framework are particularly important for this document:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>The Generic Conceptual Model defines the elements necessary for interoperability and data harmonisation including cross-theme issues. Among other aspects it specifies the UML profile used to specify the INSPIRE application schemas.</p>
</li>
<li>
<p>The Guidelines for the Encoding of Spatial Data defines how geographic information can be encoded to enable transfer processes between the systems of the data providers in the Member States. Even though it does not specify a mandatory encoding rule it sets GML (ISO 19136) as the default encoding for INSPIRE, which has been used by most of the data specifications.</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>This document specifies an additional encoding rule supporting the consistent representation of spatial data sets that meet the interoperability requirements using RDF. It builds on <a href="https://ies-svn.jrc.ec.europa.eu/projects/rdf-pids/wiki/ARE3NA_RDF_+_PIDs_study">previous work</a> on this subject. All issues are raised and discussed in an <a href="https://github.com/inspire-eu-rdf/inspire-rdf-guidelines">open forum</a>.</p>
</div>
<div class="paragraph">
<p>The document has been prepared for the ISA Programme by PwC EU Services and interactive instruments GmbH as part of ISA Action 1.17, A Reusable INSPIRE Reference Platform (ARE3NA).</p>
</div>
<div class="paragraph">
<p><strong>Disclaimer</strong></p>
</div>
<div class="paragraph">
<p>The views expressed in this report are purely those of the authors and may not, in any circumstances, be interpreted as stating an official position of the European Commission.</p>
</div>
<div class="paragraph">
<p>The European Commission does not guarantee the accuracy of the information included in this study, nor does it accept any responsibility for any use thereof.</p>
</div>
<div class="paragraph">
<p>Reference herein to any specific products, specifications, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favouring by the European Commission.</p>
</div>
<div class="paragraph">
<p>All care has been taken by the author to ensure that s/he has obtained, where necessary, permission to use any parts of manuscripts including illustrations, maps, and graphs, on which intellectual property rights already exist from the titular holder(s) of such rights or from her/his or their legal representative.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_scope">1. Scope</h2>
<div class="sectionbody">
<div class="paragraph">
<p>This document specifies an encoding rule for representing spatial data sets in INSPIRE in RDF. It may be applied to spatial data sets meeting the requirements for the interoperability of spatial data sets and services specified in regulation 1089/2010 and the associated Data Specification documents for each spatial data theme.</p>
</div>
<div class="admonitionblock warning">
<table>
<tr>
<td class="icon">
<i class="fa icon-warning" title="Warning"></i>
</td>
<td class="content">
<strong>This encoding rule is an optional encoding rule and does not supersede or replace the requirements regarding encoding specified in Clause 9 of the Data Specifications.</strong>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>Supporting an RDF encoding for spatial data sets in INSPIRE is intended to support the e-government and open data community in Europe, which is increasingly looking at RDF to represent data.</p>
</div>
<div class="paragraph">
<p>In accordance with Article 7 of regulation 1089/2010, the encoding rule specified in this document conforms to ISO EN 19118:2011. In particular, it specifies</p>
</div>
<div class="ulist">
<ul>
<li>
<p>schema conversion rules for all spatial object types, attributes and association roles and</p>
</li>
<li>
<p>the output data structure.</p>
</li>
</ul>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
The encoding rule does not provide a bijective mapping between the information items defined by the conceptual INSPIRE application schemas and their RDF encoding. For example, a transformation of a spatial object from an INSPIRE GML representation to INSPIRE RDF and back may thus result in some information loss. This is acceptable, as long as the encoding rule leads to an RDF representation that is appropriate for typical uses of INSPIRE data in an RDF context.
</td>
</tr>
</table>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_conformance">2. Conformance</h2>
<div class="sectionbody">
<div class="paragraph">
<p>If these technical guidelines are adopted in the future, then conformance classes for INSPIRE RDF vocabularies and instance documents will be added.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_normative_references">3. Normative references</h2>
<div class="sectionbody">
<div class="paragraph">
<p><a id="geodcat_ap"></a>GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe v1.0.1, <a href="https://joinup.ec.europa.eu/node/154143/" class="bare">https://joinup.ec.europa.eu/node/154143/</a></p>
</div>
<div class="paragraph">
<p><a id="inspire_d25"></a>INSPIRE D2.5 v3.4, Generic Conceptual Model</p>
</div>
<div class="paragraph">
<p><a id="inspire_d27"></a>INSPIRE D2.7 v3.3, Guidelines for the encoding of spatial data</p>
</div>
<div class="paragraph">
<p><a id="w3c_locn"></a>ISA Programme Location Core Vocabulary, <a href="https://www.w3.org/ns/locn" class="bare">https://www.w3.org/ns/locn</a></p>
</div>
<div class="paragraph">
<p><a id="iso_19118"></a>ISO 19118:2011, Geographic information – Encoding</p>
</div>
<div class="paragraph">
<p><a id="ogc_gml_33"></a>OGC Geography Markup Language (GML) - Extended schemas and encoding rules, OGC document number 10-129r1</p>
</div>
<div class="paragraph">
<p><a id="ogc_geosparql"></a>OGC GeoSPARQL - A Geographic Query Language for RDF Data, OGC document number 11-052r4</p>
</div>
<div class="paragraph">
<p><a id="UML_212"></a>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</p>
</div>
<div class="paragraph">
<p><a id="owl2"></a> OWL 2 Web Ontology Language, Structural Specification and Functional-Style Syntax (Second Edition), W3C Recommendation 11 December 2012, <a href="http://www.w3.org/TR/owl2-syntax/" class="bare">http://www.w3.org/TR/owl2-syntax/</a></p>
</div>
<div class="paragraph">
<p><a id="ogc_sf"></a>OpenGIS Implementation Standard for Geographic information - Simple feature access - Part 1: Common architecture, OGC document number 06-103r4, <a href="http://portal.opengeospatial.org/files/?artifact_id=25355" class="bare">http://portal.opengeospatial.org/files/?artifact_id=25355</a></p>
</div>
<div class="paragraph">
<p><a id="w3c_rdf11_concepts"></a> RDF 1.1 Concepts and Abstract Syntax, <a href="http://www.w3.org/TR/rdf11-concepts/" class="bare">http://www.w3.org/TR/rdf11-concepts/</a></p>
</div>
<div class="paragraph">
<p><a id="w3c_rdfschema11"></a>W3C RDF Schema 1.1, <a href="https://www.w3.org/TR/rdf-schema/" class="bare">https://www.w3.org/TR/rdf-schema/</a></p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_terms_and_abbreviations">4. Terms and abbreviations</h2>
<div class="sectionbody">
<div class="sect2">
<h3 id="ref_terms">4.1. Terms</h3>
<div class="dlist">
<dl>
<dt class="hdlist1">application schema</dt>
<dd>
<p>conceptual schema for data required by one or more applications <a href="#iso_19101">[iso_19101]</a></p>
</dd>
<dt class="hdlist1">conversion rule</dt>
<dd>
<p>rule for converting instances in the input data structure to instances in the output data structure <a href="#iso_19118">[iso_19118]</a></p>
</dd>
<dt class="hdlist1">data interchange</dt>
<dd>
<p>delivery, receipt and interpretation of data <a href="#iso_19118">[iso_19118]</a></p>
</dd>
<dt class="hdlist1">data transfer</dt>
<dd>
<p>movement of data from one point to another over a medium <a href="#iso_19118">[iso_19118]</a><br>
<br>
NOTE Transfer of information implies transfer of data.</p>
</dd>
<dt class="hdlist1">encoding</dt>
<dd>
<p>conversion of data into a series of codes <a href="#iso_19118">[iso_19118]</a></p>
</dd>
<dt class="hdlist1">encoding rule</dt>
<dd>
<p>identifiable collection of conversion rules that define the encoding for a particular data structure <a href="#iso_19118">[iso_19118]</a><br>
<br>
NOTE An encoding rule specifies the types of data to be converted as well as the syntax, structure
and codes used in the resulting data structure.</p>
</dd>
<dt class="hdlist1">transfer format</dt>
<dd>
<p>structured representation of data in a file for transfer between systems<br>
<br>
NOTE Typically, a machine readable schema will document the structure of the data in the transfer
file.<br>
<br>
EXAMPLE GML <a href="#iso_19136">[iso_19136]</a> encodes the application schema in XML Schema.</p>
</dd>
<dt class="hdlist1">simple feature</dt>
<dd>
<p>feature with all geometric attributes described piecewise by straight line or planar interpolation between sets of points <a href="#ogc_sf">[ogc_sf]</a></p>
</dd>
<dt class="hdlist1">spatial data</dt>
<dd>
<p>data with a direct or indirect reference to a specific location or geographic area <a href="#inspire_directive">[inspire_directive]</a></p>
</dd>
<dt class="hdlist1">spatial data set</dt>
<dd>
<p>identifiable collection of spatial data <a href="#inspire_directive">[inspire_directive]</a></p>
</dd>
<dt class="hdlist1">spatial object</dt>
<dd>
<p>abstract representation of a real-world phenomenon related to a specific location or geographical area <a href="#inspire_directive">[inspire_directive]</a></p>
</dd>
</dl>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
It should be noted that the term has a different meaning in the ISO 19100 series. It is also synonymous with "(geographic) feature" as used in the ISO 19100 series.
</td>
</tr>
</table>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">spatial object type</dt>
<dd>
<p>classification of spatial objects <a href="#inspire_d25">[inspire_d25]</a></p>
</dd>
</dl>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
In the conceptual schema language UML a spatial object type will be described by a class with stereotype <<featureType>>.
</td>
</tr>
</table>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">transfer protocol</dt>
<dd>
<p>common set of rules for defining interactions between distributed systems <a href="#iso_19118">[iso_19118]</a></p>
</dd>
</dl>
</div>
</div>
<div class="sect2">
<h3 id="_abbreviations">4.2. Abbreviations</h3>
<table class="tableblock frame-none grid-none spread">
<colgroup>
<col style="width: 15%;">
<col style="width: 85%;">
</colgroup>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">CEN</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">European Committee for Standardization</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">GCM</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">INSPIRE Generic Conceptual Model</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">IETF</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Internet Engineering Task Force</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">INSPIRE</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">INfrastructure for SPatial InfoRmation in Europe</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">IR</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Implementing Rule</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">ISO</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">International Organisation for Standardisation</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">LOCN</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">ISA Programme Location Core Vocabulary</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">OGC</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Open Geospatial Consortium</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">SDI</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Spatial Data Infrastructure</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">SDIC</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Spatial Data Interest Community</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">TR</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Technical Report</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">TS</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Technical Specification</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">UML</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Unified Modelling Language</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">URI</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Uniform Resource Identifier</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">URN</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Uniform Resource Name</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">UTF</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Unicode Transformation Format</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">XML</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">eXtensible Markup Language</p></td>
</tr>
</tbody>
</table>
</div>
<div class="sect2">
<h3 id="_verbal_forms_for_the_expression_of_provisions">4.3. Verbal forms for the expression of provisions</h3>
<div class="paragraph">
<p>In accordance with the ISO rules for drafting, the following verbal forms shall be interpreted in the given way:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>"shall" / "shall not": a requirement, mandatory for every data specification</p>
</li>
<li>
<p>"should" / "should not": a recommendation, but an alternative approach may be chosen for a specific case if there are reasons to do so</p>
</li>
<li>
<p>"may" / "need not": a permission</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>To make it easier to identify the mandatory requirements, the recommendations, and the permissions for INSPIRE data specifications in the text, they are highlighted and have an identifier.</p>
</div>
<div id="REQ/OWL/A/B/C" class="admonitionblock requirement">
<table>
<tr>
<td class="icon">
<i class="fa icon-requirement" title="Requirement"></i>
</td>
<td class="content">
<div class="title">Requirement REQ/OWL/A/B/C</div>
<div class="paragraph">
<p>Requirements are shown using this style.</p>
</div>
</td>
</tr>
</table>
</div>
<div id="REC/OWL/X/Y/Z" class="admonitionblock recommendation">
<table>
<tr>
<td class="icon">
<i class="fa icon-recommendation" title="Recommendation"></i>
</td>
<td class="content">
<div class="title">Recommendation REC/OWL/X/Y/Z</div>
<div class="paragraph">
<p>Recommendations are shown using this style.</p>
</div>
</td>
</tr>
</table>
</div>
<div id="PMS/OWL/X/Y/Z" class="admonitionblock permission">
<table>
<tr>
<td class="icon">
<i class="fa icon-permission" title="Permission"></i>
</td>
<td class="content">
<div class="title">Permission PMS/OWL/X/Y/Z</div>
<div class="paragraph">
<p>Permissions are shown using this style.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>Specific notes are also highlighted. They do not have normative character.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
This is a note.
</td>
</tr>
</table>
</div>
</div>
<div class="sect2">
<h3 id="_namespace_conventions">4.4. Namespace conventions</h3>
<div class="paragraph">
<p>This standard uses a number of namespace prefixes throughout; they are listed in the following table.</p>
</div>
<table class="tableblock frame-all grid-all" style="width: 90%;">
<colgroup>
<col style="width: 15%;">
<col style="width: 85%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Prefix</th>
<th class="tableblock halign-left valign-top">Namespace</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">base</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://inspire.ec.europa.eu/ont/base#" class="bare">http://inspire.ec.europa.eu/ont/base#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">dcat</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.w3.org/ns/dcat#" class="bare">http://www.w3.org/ns/dcat#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">dct</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://purl.org/dc/terms/" class="bare">http://purl.org/dc/terms/</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">gsp</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.opengis.net/ont/geosparql#" class="bare">http://www.opengis.net/ont/geosparql#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">gmlowl</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.opengis.net/ont/gml#" class="bare">http://www.opengis.net/ont/gml#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">iso19150-2</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://def.isotc211.org/iso19150/-2/2012/base#" class="bare">http://def.isotc211.org/iso19150/-2/2012/base#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">locn</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="https://www.w3.org/ns/locn#" class="bare">https://www.w3.org/ns/locn#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">owl</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.w3.org/2002/07/owl#" class="bare">http://www.w3.org/2002/07/owl#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">rdf</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#" class="bare">http://www.w3.org/1999/02/22-rdf-syntax-ns#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">rdfs</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.w3.org/2000/01/rdf-schema#" class="bare">http://www.w3.org/2000/01/rdf-schema#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">sfowl</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.opengis.net/ont/sf#" class="bare">http://www.opengis.net/ont/sf#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">skos</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.w3.org/2004/02/skos/core#" class="bare">http://www.w3.org/2004/02/skos/core#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">time</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.w3.org/2006/time#" class="bare">http://www.w3.org/2006/time#</a></p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">xsd</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://www.w3.org/2001/XMLSchema#" class="bare">http://www.w3.org/2001/XMLSchema#</a></p></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="sect1">
<h2 id="overview">5. Overview</h2>
<div class="sectionbody">
<div class="paragraph">
<p>The <a href="http://inspire.ec.europa.eu/">INSPIRE initiative</a> aims at improving the sharing of spatial data and services between public authorities in Europe and in particular between the Member States and the European Institutions. INSPIRE addresses the interoperability of spatial data sets and services for the exchange of data related to one of the 34 spatial data themes defined in the INSPIRE Directive. It does so through the creation of <a href="http://inspire.ec.europa.eu/index.cfm/pageid/2">application schemas (using UML) and geospatial encodings mechanisms (using GML, plus GeoTIFF and other formats for selected data themes)</a>. Through its data specifications, INSPIRE provides a common means to describe the spatial data within the scope of all the data themes outlined in the annexes of the Directive. The GML encoding that INSPIRE uses is an open standard intended for data exchange of spatial data on the Web. It is mainly supported by geospatial technologies.</p>
</div>
<div class="paragraph">
<p>At the same time, e-government applications and tools start to use the Linked Data paradigm, based on Semantic Web languages and technologies, such as the Resource Description Framework (RDF). If INSPIRE data was available as Linked Data, these e-government applications and tools could easily link to it. INSPIRE Linked Data has potential to unlock new applications and services, not only for e-government, but also other communities following the linked data paradigm.</p>
</div>
<div class="paragraph">
<p>Moreover, the Core Location Vocabulary specified by ISA as part of the <a href="https://joinup.ec.europa.eu/asset/core_vocabularies/description">e-Government Core Vocabularies</a> is an example of where INSPIRE data (and models) can be reused in e-government in RDF, meaning that investments made in sharing data for INSPIRE can become part of key processes in online government services. This concept can in principle be extended to offer all such INSPIRE spatial data objects as RDF, thus creating a ‘base geography’ of INSPIRE data that other data (from any sector) can be linked to.</p>
</div>
<div class="paragraph">
<p><a href="https://ies-svn.jrc.ec.europa.eu/projects/rdf-pids/wiki/ARE3NA_RDF_+_PIDs_study">Previous work</a> has brought together expertise in different countries to create a draft methodology for creating the INSPIRE RDF vocabularies, explored governance issues of Persistent Identifiers (PIDs) such as URIs and has explored some of the tools that can be used to create such data.</p>
</div>
<div class="paragraph">
<p>The guidelines described in this document build on this work and include input from pilots to test draft INSPIRE RDF vocabularies and PID concepts as well as input from the community on open issues through an <a href="https://github.com/inspire-eu-rdf/inspire-rdf-guidelines">open forum</a>.</p>
</div>
<div class="paragraph">
<p>While the methodology to publish INSPIRE data as GML together with the corresponding XML schemas is well-defined, a methodology for the publication of INSPIRE data as linked data so far does not exist. This document aims at filling this gap. Consistent with the requirements for spatial data sets in INSPIRE, this document covers both</p>
</div>
<div class="ulist">
<ul>
<li>
<p>the creation of RDF vocabularies representing the INSPIRE application schemas and</p>
</li>
<li>
<p>the transformation of INSPIRE data into RDF.</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>To conform to Article 7 of the INSPIRE implementing rule (regulation 1089/2010), this document specifies an encoding rule conforming to ISO EN 19118:2011. An encoding rule describes conversion rules for transforming data from an input data structure to an output data structure. Schemas have to be described for both the input and output data structure. In this case the input schemas, the INSPIRE application schemas, use the UML profile of the INSPIRE Generic Conceptual Model, the output schemas use RDFS/OWL/SKOS. The schema for the input data structure is called an application schema.</p>
</div>
<div class="paragraph">
<p>An encoding rule specifies the following aspects:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>General encoding requirements (clause 6)</p>
</li>
<li>
<p>the input data structure (clause 7)</p>
</li>
<li>
<p>the output data structure (the "exchange format", clause 8)</p>
</li>
<li>
<p>the conversion rules, called the mapping, for converting data in the instance model to the exchange format</p>
<div class="ulist">
<ul>
<li>
<p>the schema conversion rules for mapping between the INSPIRE application schemas in UML to RDFS (clause 9)</p>
</li>
<li>
<p>the instance conversion rules for representing INSPIRE data in RDF as far as this is not described by the schema conversion rules (clause 10)</p>
</li>
</ul>
</div>
</li>
</ul>
</div>
<div class="paragraph">
<p>Sufficient examples to illustrate the rules and the encoded data are provided.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
As mentioned before, the guidelines include input from pilots to test draft INSPIRE RDF vocabularies and PID concepts as well as input from the community on open issues. The input can lead to addition and revision of examples.
</td>
</tr>
</table>
</div>
</div>
</div>
<div class="sect1">
<h2 id="general_encoding_requirements">6. General encoding requirements</h2>
<div class="sectionbody">
<div class="sect2">
<h3 id="_application_schema_and_schema_language">6.1. Application schema and schema language</h3>
<div class="paragraph">
<p>As specified by the INSPIRE Generic Conceptual Model (GCM) <a href="#inspire_d25">[inspire_d25]</a>, the schema language for modelling INSPIRE conceptual schemas is UML.</p>
</div>
<div class="paragraph">
<p>The UML Profile of INSPIRE application schemas is defined in clause 9.6.3 of the GCM. The RDF encoding rule does not require any specific extension of this UML Profile.</p>
</div>
</div>
<div class="sect2">
<h3 id="_character_encoding">6.2. Character encoding</h3>
<div class="paragraph">
<p>The format used to serialize INSPIRE RDF data sets the requirements for the character encoding. The <a href="#output_data_structure">output data structure</a> section provides further details about format requirements.</p>
</div>
</div>
<div class="sect2">
<h3 id="_exchange_metadata">6.3. Exchange metadata</h3>
<div class="paragraph">
<p>Exchange metadata is metadata about the encoded data structure. It can describe the originator of the dataset, refer to metadata information about the dataset, refer to the application schema and provide information about the encoding rule applied.</p>
</div>
<div class="paragraph">
<p>No specific metadata is defined to describe the exchange of INSPIRE RDF data. The data itself can contain metadata. In that case, the application schema defines the types and properties that contain metadata.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
<div class="paragraph">
<p>Consider the publication of metadata in one or more formats like schema.org, microdata, DCAT, and (Geo)DCAT-AP.</p>
</div>
<div class="paragraph">
<p>Choose the metadata format based upon the formats that are supported by the search engines with which you intend to make your data searchable. Annotations in HTML pages using the schema.org vocabulary is metadata that web crawlers are using. DCAT (and extensions like GeoDCAT-AP) are currently mostly used by e-government data portals.</p>
</div>
<div class="paragraph">
<p>For further information, see <a href="https://www.w3.org/TR/2017/NOTE-sdw-bp-20170511/#bp-indexable">Best Practice 2: Make your spatial data indexable by search engines</a> in the <a href="#w3c_sdw_bp">Spatial Data on the Web Best Practices</a>.</p>
</div>
</td>
</tr>
</table>
</div>
</div>
<div class="sect2">
<h3 id="_transfer_unit">6.4. Transfer unit</h3>
<div class="sect3">
<h4 id="_granularity_and_structure">6.4.1. Granularity and structure</h4>
<div class="paragraph">
<p>A transfer unit is a set of objects (a dataset or a subset of a dataset), each of which contains a set of properties.</p>
</div>
</div>
<div class="sect3">
<h4 id="_object_identification">6.4.2. Object identification</h4>
<div id=""REQ/OWL/ObjectIdentification" class="admonitionblock requirement">
<table>
<tr>
<td class="icon">
<i class="fa icon-requirement" title="Requirement"></i>
</td>
<td class="content">
<div class="title">Requirement "REQ/OWL/ObjectIdentification</div>
<div class="paragraph">
<p>Each object contained in the transfer unit shall have a unique identifier.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
Data types are not categorised as objects in the input data structure.
</td>
</tr>
</table>
</div>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="input_data_structure">7. Input data structure</h2>
<div class="sectionbody">
<div class="paragraph">
<p>As the input data structure, this encoding rule uses an instance model which is based on the generic instance model defined in <a href="#iso_19118">ISO 19118</a> clause 8. The instance model is capable of representing data described by INSPIRE application schemas expressed in UML.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="output_data_structure">8. Output data structure</h2>
<div class="sectionbody">
<div class="paragraph">
<p>This encoding rule is based on <a href="#w3c_rdf11_concepts">RDF 1.1 Concepts and Abstract Syntax</a>.</p>
</div>
<div class="quoteblock">
<blockquote>
<div class="paragraph">
<p>The Resource Description Framework (RDF) is a framework for expressing information about resources. Resources can be anything, including documents, people, physical objects, and abstract concepts.</p>
</div>
<div class="paragraph">
<p>RDF is intended for situations in which information on the Web needs to be processed by applications, rather than being only displayed to people. RDF provides a common framework for expressing this information so it can be exchanged between applications without loss of meaning. Since it is a common framework, application designers can leverage the availability of common RDF parsers and processing tools. The ability to exchange information between different applications means that the information may be made available to applications other than those for which it was originally created.</p>
</div>
<div class="paragraph">
<p>In particular RDF can be used to publish and interlink data on the Web. For example, retrieving <a href="http://www.example.org/bob#me" class="bare">http://www.example.org/bob#me</a> could provide data about Bob, including the fact that he knows Alice, as identified by her IRI (an IRI is an "International Resource Identifier" […​]). Retrieving Alice’s IRI could then provide more data about her, including links to other datasets for her friends, interests, etc. A person or an automated process can then follow such links and aggregate data about these various things. Such uses of RDF are often qualified as Linked Data.</p>
</div>
</blockquote>
<div class="attribution">
— https://www.w3.org/TR/rdf11-primer/#section-Introduction
</div>
</div>
<div class="paragraph">
<p><a href="#w3c_rdf11_concepts">RDF 1.1 Concepts and Abstract Syntax</a> defines a data model. It does not define a specific format to encode RDF data. A number of RDF formats exist, serving different purposes.</p>
</div>
<div id="REC/OWL/encoding/turtle" class="admonitionblock recommendation">
<table>
<tr>
<td class="icon">
<i class="fa icon-recommendation" title="Recommendation"></i>
</td>
<td class="content">
<div class="title">Recommendation REC/OWL/encoding/turtle</div>
<div class="paragraph">
<p>INSPIRE RDF data should be encoded in <a href="#w3c_rdf11_turtle">Turtle</a>.</p>
</div>
</td>
</tr>
</table>
</div>
<div id="PMS/OWL/encoding/other" class="admonitionblock permission">
<table>
<tr>
<td class="icon">
<i class="fa icon-permission" title="Permission"></i>
</td>
<td class="content">
<div class="title">Permission PMS/OWL/encoding/other</div>
<div class="paragraph">
<p>INSPIRE RDF data may be encoded in other RDF formats, such as <a href="#w3c_rdf11_ntriples">N-Triples</a> and <a href="#w3c_rdfxml">XML</a>.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>The schema for the output data structure that governs the structure of the exchange format is a combination of <a href="#w3c_rdfschema11">RDF Schema</a> and <a href="#owl2">OWL</a>.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="ref_cr">9. Schema conversion rules</h2>
<div class="sectionbody">
<div class="paragraph">
<p>This chapter documents the rules for converting an INSPIRE application schema to an OWL ontology</p>
</div>
<div class="sect2">
<h3 id="_general">9.1. General</h3>
<div class="paragraph">
<p>Rules for the conversion of an application schema package, the UML types it contains, and the properties of these types, are documented in this chapter.</p>
</div>
<div class="sect3">
<h4 id="ref_cr_general_documentation">9.1.1. Documentation</h4>
<div class="paragraph">
<p>The documentation of UML elements (types, attributes and association roles) in INSPIRE application schemas includes:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>A natural / human readable name</p>
</li>
<li>
<p>A definition</p>
</li>
<li>
<p>A description (optional)</p>
</li>
</ul>
</div>
<div id="REQ/OWL/documentation" class="admonitionblock requirement">
<table>
<tr>
<td class="icon">
<i class="fa icon-requirement" title="Requirement"></i>
</td>
<td class="content">
<div class="title">Requirement REQ/OWL/documentation</div>
<div class="paragraph">
<p>The natural / human readable name, definition, and description (if available) of a UML element shall be documented using properties as shown in <a href="#ref_cr_general_documentation_table">the following table</a>. The values of these properties shall be provided at least in English.</p>
</div>
</td>