-
Notifications
You must be signed in to change notification settings - Fork 1
/
USGINMetadataJSONschemav3.2.json
2909 lines (2871 loc) · 172 KB
/
USGINMetadataJSONschemav3.2.json
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
{
"$schema": "http://json-schema.org/draft-04/schema#",
"comment": "this section is start at making compatible with JSON-LD. see https://www.w3.org/TR/json-ld",
"@context": {
"jmd": "http://resources.usgin.org/uri-gin/usgin/schema/json/3.1/metadata",
"@vocab": "http://json-schema.org/draft-04/schema",
"@base": "http://resources.usgin.org/uri-gin/usgin/schema/json/3.1/metadata",
"foaf": "http://xmlns.com/foaf/0.1/",
"dct": "http://purl.org/dc/terms/",
"skos": "http://www.w3.org/2004/02/skos/core#"
},
"description": "A metadata record has two sections, one with information for management of the metadata itself, and one that describes some individual resource. Each metadata record describes exactly one resource. The metadata record can be considered a representation of the resource, but it has an identity that is distinct from the identity of the described resource. There may be more than one metadata record in the system describing a single resource, these should have distinct metadata lineages. specifications followed here- JSON pointer--http: tools.ietf.org/html/rfc6901; JSON schema Core--http://tools.ietf.org/html/draft-zyp-json-schema-04; JSON schema validation--http://tools.ietf.org/html/draft-fge-json-schema-validation-00. Some integration of JSON-LD, more to come hopefully... http://www.w3.org/TR/json-ld/. FOAF for person, organization--http://xmlns.com/foaf/spec/. DCAT--http://www.w3.org/TR/vocab-dcat/, and DublinCore--http://dublincore.org/documents/dcmi-terms/. still need to do integration work figuring out how to link elements in this metadata vocabulary with the other schemes.",
"skos:HistoryNote": "2015-10-09, add /2.0 to schema element base URI, review; make metadataSpecification id the spec for the metadata instance, not the harvestedsource; still need to set upreferences to the objects defined in the definitions section. Revise so will validate with http://www.jsonschemavalidator.net/ and http://jsonschemalint.com/draft4/# using the draft 4 version of the json schema schema. Note that http://www.jsonschemavalidator.net/ cannot process this schema to use to validate instance docs. Jsonschemlint.com will work to validate instances. 2015-01-20 v3.0 integrate lookup concepts from ADIWG ISO metadata JSON implementation. Contacts array at top uses ContactID as lookup for repeated values. Add some coverage info elements other adjustments to aling with ADIWG. V3.1 2016-04-29 add all MD format properties, make linkformat type an array; add extentTypeCode as enum on extent spatial geometries. 2017-02-01--Fix metadata lineage section; it referenced LineageObject, which has been deprecated. Need to harmonize metadata record history/lineage with CINERGI usage; best approach is probably a JSONLD encoding of W3C prov. 2017-03-11 - make provenanceLink same ranke as lineage, not nested in process step; remove lineage scope--in this schema lineage is about entrie resource (see note on lineageStatement); convert translation to 'search_paths' to encode mappings from this schema to ISO, DataCite or other scheme",
"version": "3.2",
"dct:identifier": "http://resources.usgin.org/uri-gin/usgin/schema/json/3.2/metadata",
"type": "object",
"search_paths": [
{
"schema": "ISO 19139",
"path": "gmd:MD_Metadata"
},
{
"schema": "DataCite v3",
"path": "resource"
},
{
"schema": "ADIWG",
"path": "metadata"
},
{
"schema": "ISO 19115-2",
"path": "gmi:MI_Metadata"
}],
"required": [
"jmd:metadataInfo",
"jmd:describedResource"
],
"properties": {
"jmd:contacts": {
"type": "array",
"description": "An array of contacts (Agent elements) to be referenced throughout the metadata. Any contact used in the metadata record must be stored within this array and referenced by contactId. Items in array may be used 0-n times throughout the record.",
"search_paths": [{
"schema": "ISO 19139",
"path": "//gmd:CI_ResponsibleParty"
},
{
"schema": "ISO 19115-3",
"path": "//cit:CI_Responsibility"
},
{
"schema": "FGDC CSDGM",
"path": "//cntinfo"
},
{
"schema": "ISO 19115-2",
"path": "//gmd:CI_ResponsibleParty"
}],
"required": ["jmd:contactID", "jmd:agent"],
"items": {
"type": "object",
"properties": {
"jmd:contactID": {
"description": "identifier used for references to the Agent element. References to contacts defined within this document SHALL be prefixed with a '#'; references to contacts defined in external registries SHALL be prefixed with 'http://'. ",
"type": "string"
},
"jmd:agent": {
"$ref": "#/definitions/jmd:AgentObject"
}
}
}
},
"jmd:metadataInfo": {
"type": "object",
"description": "keys providing documentation on the origin and provenance of this metadata record",
"required": [
"jmd:metadataIdentifier",
"jmd:metadataLastUpdate",
"jmd:metadataSpecification",
"jmd:metadataLanguage"
],
"properties": {
"jmd:metadataIdentifier": {
"type": "string",
"description": "uri that identifies this metadata record (as distinct from the resource it describes), default is UUID type URN, in which case the URN:UUID: prefix is left off. If some other identifier scheme is used, an appropriate prefix should specifiy the identifier scheme (e.g. DOI, ISSN, ARK...)",
"format": "uri",
"search_paths": [{
"schema": "ISO 19139",
"path": "//gmd:fileIdentifier/gco:CharacterString/text()"
},
{
"schema": "DataCite v3",
"path": "missing"
},
{
"schema": "ADIWG",
"path": "metadata > metadataInfo > metadataIdentifier"
},
{
"schema": "ISO 19115-2",
"path": "//gmd:fileIdentifier/gco:CharacterString/text()"
}]
},
"jmd:metadataLastUpdate": {
"description": "exactly 1. This is time stamp for most recent change to metadata content in this record. Update history should be in metadataLineage; this is a convienence property",
"type": "string",
"format": "date-time",
"search_paths": [
{
"schema": "ISO 19139",
"path": "//gmd:dateStamp/gco:Date"
},
{
"schema": "DataCite v3",
"path": "missing"
}
]
},
"jmd:metadataContacts": {
"description": "contact information to report problems with the resource tdescription content. jmd:metadataContacts maps to ISO19115 metadataContact",
"type": "array",
"search_paths": [
{
"schema": "ISO 19139",
"path": "//gmd:contact)"
},
{
"schema": "DataCite v3",
"path": "missing"
},
{
"schema": "ADIWG",
"path": "metadata > metadataInfo > metadataContact"
},
{
"schema": "ISO 19115-2",
"path": "//gmd:contact"
}],
"mappingNote": "the //gmd:contact/CI_ResponsibleParty element content is mapped to AgentObject in contactRef",
"minItems": 1,
"items": {
"$ref": "#/definitions/jmd:contactRef"
}
},
"jmd:metadataSpecification": {
"description": "Identifies the specification & profile for this metadata instance. Instances of this json schema should be identified using the id property of this schema",
"type": "object",
"$ref": "#/definitions/jmd:ReferenceObject",
"schemaMapping": [
{"jmd:referenceLabel": {
"search_paths": [
{
"schema": "ISO 19139",
"concat": [
{
"path": "//gmd:metadataStandardName/gco:CharacterString"
},
{
"delimiter": "||"
},
{
"path": "//gmd:metadataStandardVersion/gco:CharacterString"
}]
},
{
"schema": "DataCite v3",
"path": "missing"
}]
}
}
]
},
"jmd:parentMetadata": {
"description": "Identifier of the metadata to which this metadata is a subset (child). Use referenceObject in place of citation, the linkLabel is the citation title, and Link provides URL for parent record.",
"translation": {
"ISO 19115-2": ["MI_Metadata > parentIdentifier"]
},
"$ref": "#/definitions/referenceObject"
},
"jmd:metadataMaintenance": {
"description": "this element provides information on metadata maintenance process, interval or frequency. See metadataLineage for documentation of changes to the metadata record; the metadata update documentation there will need to be shoe-horned into the maintenance section of the metadata record in ISO19139 or ISO19115-3 encoding.",
"translation": {
"ADIWG": ["metadataInfo > metadataMaintenance"]
},
"$ref": "#/definitions/jmd:MaintenanceObject"
},
"jmd:metadataLanguage": {
"description": "Language of metadata content. Default is eng if no value is specified. ",
"search_paths": [
"gmd:language"
],
"$ref": "#/definitions/jmd:LanguageObject"
},
"jmd:metadataRecordLineageItems": {
"description": "documentation of update history for this metadata record. An array of processing steps or a link to an external provenance trace. First step in lineage should record harvest or creation via form. Metadata creation date goes in here with eventType = creation. USGIN has been putting this information in the metadata maintenance section. Originally defined by #/definitions/jmd:LineageObject, but that object is deprecated. Ideally probably want some kind of Prov encoding; see https://provenance.ecs.soton.ac.uk/ and https://www.w3.org/Submission/prov-json/",
"translation": {
"ISO 19115-2": [""],
"FGDC CSDGM": [""],
"ADIWG": [""]
},
"type": "array",
"minItems": 0,
"items": {
"type": "object",
"required": ["jmd:stepDateTime", "jmd:metadataUpdates"],
"properties": {
"jmd:stepSequenceNo": {
"description": "integer provided to sort processing steps in chronologic order. If sequence numbering is inconsistent with the stepDateTime, the time stamp takes precedence",
"type": "integer"
},
"jmd:stepLabel": {
"type": "string",
"description": "text to characterize,identify this step for user interface listing"
},
"jmd:stepProcessors": {
"description": "0..N parties responsible for processing step",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:AgentObject"
}
},
"jmd:stepSoftware": {
"description": "reference that specifies software used in this process step",
"type": "object",
"properties": {
"$ref": "#/definitions/jmd:ReferenceObject"
}
},
"jmd:stepProcessTypes": {
"type": "array",
"description": "concepts to categorize the kind of processing executed in this step e.g. ",
"items": {
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
},
"jmd:stepProcessDescription": {
"description": "free text description of what processing was done",
"type": "string"
},
"jmd:stepDateTime": {
"type": "object",
"description": "only allow single time stamp",
"properties": {
"$ref": "#/definitions/DateObject"
}
},
"jmd:metadataUpdates": {
"type": "array",
"description": "object that defines the changes made to the original record by this processing step. Content TBD for CINERGI. originalValue and newValue are escape-encoded JSON text; these might are each key value pairs; the values might be simple (string or number), or JSON objects. This is an array because a component in a metadata processing pipeline might effect multiple elements in the metadata record.",
"items": {
"type": "object",
"allof": [
{
"oneOf": [
{
"required": ["jmd:deletePath"]
},
{
"required": ["jmd:updatePath"]
},
{
"required": ["jmd:insertPath"]
}
]
},
{
"oneOf": [
{
"required": ["jmd:newValue"]
},
{
"required": ["jmd:originalValue"]
}
]
}
],
"properties": {
"jmd:deletePath": {
"type": "string",
"description": "JSON path identifying the location in this record where a key value pair was deleted. OriginalValue should record the content that was deleted."
},
"jmd:updatePath": {
"type": "string",
"description": "JSON path identifying the location in this record that was updated. originalValue records the content as is was, newValue records the updated value."
},
"jmd:insertPath": {
"type": "string",
"description": "JSON path identifying the location in this record where new content was inserted. newValue records the inserted content."
},
"jmd:originalValue": {
"type": "string",
"description": "escape-encoded content that was originally at that location. use 'NULL' if there was no content there before processing"
},
"jmd:newValue": {
"type": "string",
"description": "escape-encoded content of the updated content at that location. For deletion"
}
}
}
}
}
}
},
"jmd:metadataConformanceTests": {
"type": "array",
"description": "an array of test names and results, used to indicate quality of record",
"items": {
"type": "object",
"properties": {
"jmd:conformanceTestName": {
"type": "string"
},
"jmd:conformanceTestURI": {
"type": "string",
"format": "URI"
},
"jmd:conformanceResult": {
"type": "string",
"description": "either Pass or Fail"
},
"jmd:conformanceTestDate": {
"description": "time stamp for when the test was run",
"type": "string",
"format": "DateTime"
},
"jmd:conformanceTestNote": {
"type": "string",
"description": "output from conformance test; if test fails this should provide information about what went wrong"
}
}
}
},
"jmd:metadataUsageConstraint": {
"description": "documentation of any restrictions on access to or usage of the metadata record.",
"$ref": "#/definitions/jmd:UsageConstraintObject"
},
"jmd:harvestInformation": {
"type": "object",
"description": "this is information about the harvest origin of a record, only necessary when this JSON scheme is used as a document format in a metadata management system, generally not necessary for metadata interchange",
"required": ["jmd:harvestURL", "jmd:harvestDate"],
"properties": {
"jmd:harvestedFileIdentifier": {
"type": "string"
},
"jmd:harvestedMetadataFormat": {
"description": "Identifies the specification & profile of the source metadata harvested to construct this metadata object",
"$ref": "#/definitions/jmd:ReferenceObject"
},
"jmd:harvestRecordId": {
"type": "string"
},
"jmd:harvestURL": {
"type": "string"
},
"jmd:harvestDate": {
"type": "string",
"format": "date-time"
}
}
},
"jmd:SourceInfo": {
"type": "object",
"description": "identification of the source of the harvested metadata, used for internal processing",
"properties": {
"SourceID": {
"type": "string"
},
"ViewID": {
"type": "string"
},
"Name": {
"type": "string"
},
"DataSource": {
"type": "string"
}
}
},
"jmd:collections": {
"type": "array",
"description": "list of collection identifiers that this resource is a member of. Property only generally needed if this JSON scheme is used as a document format for metadata management.",
"items": {
"type": "string"
}
},
"jmd:published": {
"description": "true if the metadata record should be visible in the catalog; probably need to generalize to a policy object (like Fedora) to allow more granular access control. Only necessary for JSON docs in a metadata management system, not needed for interchange",
"type": "boolean"
}
}
},
"jmd:describedResource": {
"description": "exactly 1. what the metadata record is about",
"$ref": "#/definitions/jmd:ResourceDescription"
}
},
"definitions": {
"jmd:ResourceDescription": {
"description": "metadata that documents a resource. Basic requirement is title and access information to support the most basic discovery scenarios. The various optional elements provide capabilities for extensive resource documentation and inforamtion for machine interoperability.",
"dct:identifier": "http://resources.usgin.org/uri-gin/usgin/schema/json-metadata/3.0/ResourceDescription",
"type": "object",
"required": ["jmd:resourceTitle", "jmd:resourceAccessOptions"],
"properties": {
"jmd:resourceTitle": {
"description": "Title that identifies the resource for human users. Ideally the title would be unique to the described resource.",
"type": "string",
"net.cnri.repository": {
"preview": {
"showInPreview": true,
"isPrimary": true
}
}
},
"jmd:resourceAbstract": {
"description": "Free text description of the resource. May summarize intellectual content, as well as describe various metadata aspects such as physical expression, lineage, quality, use constraints, maintenance.",
"translation": {
"ISO 19115": ["MD_DataIdentification > abstract"],
"FGDC CSDGM": ["idinfo > descript > abstract"],
"ADIWG": "[resourceInfo > abstract]"
},
"type": "string"
},
"jmd:resourceIdentifiers": {
"description": " Array of scoped identifiers with an optional authority associated with each identifier. Scoped Identifier(s) for the resource, e.g. ISBN, ISSN, Dewey Decimal system numbers, or other URIs determined by the publishing authority.",
"type": "array",
"items": {
"type": "object",
"oneOf": [{
"required": ["jmd:resourceURI"]
}, {
"required": ["jmd:scopedIdentifier"]
}
],
"properties": {
"jmd:resourceURI": {
"description": "identifier string that conforms to RFC 3986. If identifier uses different syntax or conveintions use scopedIdetifier. Unique identifier conforming to IETF URI syntax (RFC 3986). Resource may have multiple identifiers; the identifier in this element is the preferred identifier recommended by the resource steward. The resourceURI is intended to identify the resource at the FRBR work level.",
"type": "string",
"format": "URI"
},
"jmd:scopedIdentifier": {
"description": "Identifier code with optional codespace and authority",
"type": "object",
"properties": {
"$ref": "#/definitions/jmd:ScopedIdentifierObject"
}
}
}
}
},
"jmd:citationResponsibleParties": {
"description": "Citation information for the resource: contributing agents (author, publisher, editor, compiler, etc., intellectual originator and contributors to content and presentation of the resource that metadata record describes.",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:contactRef"
}
},
"jmd:citationDates": {
"description": "pertinent dates that may be useful in searches for the resource or for identifying it,Each date should scope a different origin event",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:EventDateObject"
}
},
"jmd:citationAlternateTitles": {
"description": "alternate titles by which the resource may be known",
"type": "array",
"items": {
"type": "object",
"required": ["jmd:altTitleText"],
"properties": {
"jmd:altTitleText": {
"type": "string"
},
"jmd:altTitleContext": {
"$ref": "#/definitions/jmd:ReferenceObject"
}
}
}
},
"jmd:citationRecommendation": {
"description": "a suggested full text citation to use when citing the resource; include standard bibliographic content like edition, publisher, series title, series issue, page numbers, other information appropriate to the described resource. a recommended full citation text to use for citing the resource. ",
"type": "string"
},
"jmd:citationDetails": {
"type": "object",
"description": "Information to identify and locate published resources for which a formal bibliographic reference is appropriate. If the resource is a published work, other standard bibliographic information goes here. Publication details will only apply if the described resource is an frbr:manifestation or frbr:item (see https://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records). Linkage to online items should still be through distribution linkage elements.If the resource is a work or manifestation,then expressions and items will be distributions of that resource. Tricky...",
"properties": {
"jmd:edition": {
"type": "string",
"description": "identifier for edition"
},
"jmd:editionDate": {
"description": "in ISO model this is a date or dateTime, uses xsd types; map to string",
"type": "string"
},
"jmd:series": {
"description": "identifier (with other reference properties that specifies the series within which the described resource is published, e.d.g a DOI for the journal",
"$ref": "#/definitions/jmd:ReferenceObject"
},
"jmd:seriesName": {
"description": "name for the series; would map to the serice/referenceLabel; convienence property",
"type": "string"
},
"jmd:seriesIssue": {
"type": "string",
"description": "identifier for issue in series; syntax should follow some bibliographic standard, but depends somewhat on the kind of series."
},
"jmd:page": {
"type": "string"
},
"jmd:publicationDescription": {
"type": "string",
"description": "free text with other details specific to this particular manifestation of the resource. might add physicalDistribution and physical extent (dimensions) elements here for library usage..."
},
"jmd:publicationPresentationForm": {
"description": "codelist item, for compatibility",
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
}
},
"jmd:resourceTypes": {
"description": "0..N. ResourceType is a specially recognized keywordTheme that categorizes the resource; at least one type category should be specified, as the type will guide processing of other parts of the metadata record. Resource categorization can be done on many axes. Some example schemes include Functional Requirements for Bibliographic Records (FRBR) entity, which include _work_,_expression_,_manifestation_, and _item_ (see http: en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records#FRBR_Entities), frbr form here as well ( e.g., novel, play, poem, essay, biography, symphony, concerto, sonata, map, drawing, painting, photograph, etc.), gmd:HierarchyLevel ISO scopeCodes, and gmd:HierarchyLevelName that type resources. The different category schmes can be disambiguated by their VocabularyURI values, but concepts in each should have URIs that are sufficient.",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
},
"jmd:resourceStatus": {
"description": "Term that specifies the development status of the resource (in review, published, draft....)",
"translation": {
"ISO 19115-2": ["MD_DataIdentification > status [MD_ProgressCode]"],
"FGDC CSDGM": ["idinfo > status > progress"],
"ADIWG": "[resourceInfo > status]"
},
"$ref": "#/definitions/jmd:ControlledConceptObject"
},
"jmd:resourceContacts": {
"description": "link to party to contact for additional information about the resource. Each relatedAgent has an associated role; various parties may be associated with the resource in different roles.",
"translation": {
"ISO 19115-2": ["MD_DataIdentification > pointOfContact"],
"ADIWG": ["resourceInfo > pointOfContact"]
},
"type": "array",
"items": {
"$ref": "#/definitions/jmd:contactRef"
}
},
"jmd:resourceBrowseGraphic": {
"description": "Link to a graphic resource that provides a visualization of the resource.",
"$ref": "#/definitions/jmd:LinkObject"
},
"jmd:resourceTemporalExtents": {
"description": "This is the time instant or interval to which the resource content applies. Extent using named time ordinal eras (e.g. geologic time) should be specified using temporal keywords (vocabulary is a time scale). use ISO8601 encoding for intervals with the format <start>/<end> where start and end are 8601 dateTime strings. see http://en.wikipedia.org/wiki/ISO_8601",
"type": "array",
"translation": {
"ISO 19115-2": ["EX_Extent > temporalElement "],
"ADIWG": ["resourceInfo > resourceTimePeriod"]
},
"items": {
"type": "object",
"description": "each extent array element is only one of an instant, a period, or a reference",
"oneOf": [{
"required": ["jmd:timeInstant"]
}, {
"required": ["jmd:timePeriod"]
}, {
"required": ["jmd:temporalExtentReference"]
}
],
"properties": {
"jmd:timeFrameURI": {
"type": "string",
"description": "identifier for temporal reference system/frame,",
"translation": {
"ISO 19115": ["EX_TemporalExtent > extent > TimeInstant @frame",
"EX_TemporalExtent > extent > TimePeriod @frame"]
}
},
"jmd:timeInstant": {
"type": "object",
"required": ["jmd:timeInstantTimePosition"],
"additionalProperties": true,
"properties": {
"jmd:timeInstantId": {
"type": "string",
"description": "A unique identifier for the timeInstant.",
"translation": {
"ISO 19115-2": ["EX_TemporalExtent > extent > TimeInstant @id"]
}
},
"jmd:timeInstantDescription": {
"type": "string",
"description": "A brief description providing relevant information about the date and time.",
"translation": {
"ISO 19115-2": ["EX_TemporalExtent > extent > TimeInstant > description"]
}
},
"jmd:timeInstantTimePosition": {
"translation": {
"ISO 19115-2": ["EX_TemporalExtent > extent > TimeInstant > timePosition"]
},
"$ref": "#/definitions/jmd:DateObject"
}
}
},
"jmd:timePeriod": {
"type": "object",
"description": "A span of time represented by a starting date-time and an ending date-time.",
"additionalProperties": true,
"properties": {
"jmd:timePeriodId": {
"type": "string",
"description": "A unique identifier for a time period.",
"translation": {
"ISO 19115-2": ["EX_TemporalExtent > extent > TimePeriod @id"]
}
},
"jmd:timePeriodDescription": {
"type": "string",
"description": "A brief description providing relevant information about the time period.",
"translation": {
"ISO 19115-2": ["EX_TemporalExtent > extent > TimePeriod > description "]
}
},
"jmd:timePeriodBeginPosition": {
"description": "Starting date, or date and time.",
"translation": {
"ISO 19115-2": ["EX_TemporalExtent > extent > TimePeriod > beginPosition "],
"FGDC CSDGM": ["idinfo > timeperd > rngdates > begdate"]
},
"$ref": "#/definitions/jmd:DateObject"
},
"jmd:timePeriodEndPosition": {
"description": "Ending date, or date and time.",
"translation": {
"ISO 19115-2": ["EX_TemporalExtent > extent > TimePeriod > endPosition"],
"FGDC CSDGM": ["idinfo > timeperd > rngdates > enddate"]
},
"$ref": "#/definitions/jmd:DateObject"
}
},
"allOf": [{
"title": "beginPosition required",
"required": ["jmd:timePeriodBeginPosition"]
}, {
"title": "endPosition required",
"required": ["jmd:timePeriodEndPosition"]
}
]
},
"jmd:temporalExtentReference": {
"description": "reference to a temporal extent defined in some register",
"$ref": "#/definitions/jmd:ReferenceObject"
}
}
}
},
"jmd:resourceCharacterSet": {
"description": "character set for described resource content",
"translation": {
"ISO 19115-2": ["MD_DataIdentification > characterSet [MD_CharacterSetCode]"],
"ADIWG": ["resourceInfo > characterSet"]
},
"default": "UTF-8",
"type": "string"
},
"jmd:resourceLanguages": {
"description": "Language of resource content. Multiple languages may be specified. Use Nil not applicable if there is no text in the resource. Use ISO three letter language code (Each language SHOULD be expressed as a language tag, as defined by RFC 3066); provide option to use a jmd:reference if need some other kind of language scoping to a particulr community, dialect, or country",
"skos:exactMatch": "dc:language",
"translation": {
"ISO 19115-2": ["MD_DataIdentification > language"],
"ADIWG": ["resourceInfo > language"]
},
"default": "eng",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:LanguageObject"
}
},
"jmd:resourceSpatialExtents": {
"description": "specification of the geographic footprint of the described resource content. Array allow multiple extents for non contiguous resource, e.g. map of US coasts, and ExtentObject allows various representations of extent.",
"type": "array",
"minItems": 1,
"items": {
"$ref": "#/definitions/jmd:ExtentObject"
}
},
"jmd:resourceSpatialDescription": {
"description": "Properties characterizing the spatial aspects of the resource, if applicable.",
"type": "object",
"properties": {
"jmd:resourceSpatialRepresentationTypes": {
"description": "term specifying the nature of the geometric representation, e.g. vector, grid, tin, voxel. More complete information on spatial representation (like ISO19115 spatial representation MD_SpatialRepresentation package) is not included here; use extensions in the description details group",
"type": "array",
"translation": {
"ISO 19115-2": ["gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType/gmd:MD_SpatialRepresentationTypeCode"]
},
"items": {
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
},
"jmd:resourceSpatialReferenceSystems": {
"description": "identifier and link to definition of spatial reference system used for location information contained in the resource content. ",
"translation": {
"ISO 19115-2": ["gmd:referenceSystemIdentifier/gmd:RS_Identifier"]
},
"type": "array",
"items": {
"type": "object",
"required": ["jmd:resourceSRSCode"],
"properties": {
"jmd:resourceSRSCode": {
"description": "",
"type": "string"
},
"jmd:resourceSRSCodeSpace": {
"description": "",
"type": "string"
},
"jmd:resourceSRSCodeVersion": {
"description": "",
"type": "string"
},
"jmd:resourceSRSAuthorityName": {
"description": "",
"type": "string"
}
}
}
},
"jmd:resourceSpatialResolution": {
"description": "specification of resolution, either as a scale denominator, or as a distance(with unit of measure) specifying the smallest distance in the Earth between resolvable points in the data",
"type": "object",
"anyOf": [{
"allOf": [{
"required": ["jmd:resolutionDistanceValue"]
},
{
"required": ["jmd:resolutionUOM"]
}
]
},
{
"required": ["jmd:resolutionScaleDenominator"]
}
],
"properties": {
"jmd:resolutionScaleDenominator": {
"description": "resolution of spatial data specified as the design scale denominator for protrayal of the data.",
"type": "integer"
},
"jmd:resolutionDistanceValue": {
"description": "resolution of spatial data specified as the minimum distance between resolvable locations in the location data",
"type": "number"
},
"jmd:resolutionUOM": {
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
}
}
}
},
"jmd:resourceIndexTerms": {
"description": "an array of objects, each of which is a set of keywords scoped to a particular keywordType or keywordReference value. Only one object in the array should have neither keywordType or keywordReference, and keywords in this element will be treated as free-form tags.",
"translation": {
"ISO 19115-2": ["MD_DataIdentification > descriptiveKeywords > MD_Keywords"],
"FGDC CSDGM": ["idinfo > keywords"]
},
"type": "array",
"minItems": 1,
"items": {
"type": "object",
"required": ["jmd:keywords"],
"properties": {
"jmd:keywordType": {
"description": "Categorize this group of keywords; corresponds to CSDGM and ISO19115 theme. Typical values: include place, temporal, thematic, ISO topic category etc...",
"$ref": "#/definitions/jmd:ControlledConceptObject"
},
"jmd:keywords": {
"description": "words associated with the resource to improve search accuracy. if no keywordReference is provided, these will be treated as tags. The keyword reference should provide a mapping from the labels that appear as strings in the keywords array here to URIs that uniquely identify the keyword (if such URIs are defined)",
"type": "array",
"minItems": 1,
"items": {
"type": "string"
}
},
"jmd:keywordReference": {
"description": "identifies a thesaurus, controlled vocabulary, ontology, etc. in which the assigned keywords are defined for people and/or machines",
"$ref": "#/definitions/jmd:ReferenceObject"
}
}
}
},
"jmd:resourceAccessOptions": {
"description": "describes how to access the resource described by the metadata. Corresponds to ISO19115 distribution. Each object in the accessOptions array contains the offerings from a particular distributor. If no distributor is specified, assume that the resource contact is the distributor. Note that distributions are grouped by distributor, and Formats are associated with LinkObjects for online access and with the offline access. OrderingInstructions and turnaround are associated with Offline access procedures",
"type": "array",
"minItems": 1,
"items": {
"type": "object",
"anyOf": [{
"required": ["jmd:accessLinks"]
}, {
"required": ["jmd:offlineAccess"]
}
],
"properties": {
"jmd:distributor": {
"description": "agent responsible for making the resources accessible at the associated URLs or offline locations",
"$ref": "#/definitions/jmd:contactRef"
},
"jmd:accessLinks": {
"description": "online location that provides some kind of access to the described resource. The link properties are used to characterize the nature of the resource at the specified location, e.g. if only particular spatial representation or spatial reference system types.",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:LinkObject"
}
},
"jmd:unitsOfDistribution": {
"type": "string",
"description": "explanation of the units of distribution; from ISO19115"
},
"jmd:accessInstructions": {
"type": "array",
"items": {
"type": "string",
"description": "free text description of how to get resource; Include turnaround time and business hours information, turnaround time, and any other necessary information, including density, density units, number of volumes, software or hardware requirements, etc. Allow arrsy because ordering Instructions in ISO19115 are 0..* on MD_Distributor"
}
},
"jmd:offlineAccess": {
"description": "information describing offline distribution, involving some sort of physical media. Note distinction of medium format and file format",
"type": "array",
"items": {
"jmd:offlineMediumType": {
"description": "specification of the physical media that contains the distribution of the resource. This may be one of a variety of digital media (magnetic tape, hard disk, CDROM, DVD, thumb drive), or various legacy physical media (paper sheet, book, film transparency, rock specimen...)",
"translation": {
"ISO 19115": ["gmd:MD_Medium/gmd:mediumFormat/gmd:MD_MediumNameCode"]
},
"$ref": "#/definitions/jmd:ControlledConceptObject"
},
"jmd:offlineMediumFormats": {
"description": "Medium format is used in this scheme to specify the low-level formatting of information on a physical media.",
"translation": {
"ISO 19115": ["gmd:MD_Medium/gmd:mediumFormat/gmd:MD_MediumFormatCode"]
},
"type": "array",
"items": {
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
},
"jmd:offlineFileFormats": {
"description": "File format is used in this scheme to specify file formatting analogoous to mime type for offline distributions. Formats are typically associated with particular applications that can open the file (e.g. .doc, .xls) or are generic file types that can be opened by various applicaitons (e.g. text, tiff, csv...). Specific community profiles are necessary to specify the syntax and vocabulary for file format information.",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
},
"jmd:offlineMediumNote": {
"description": "Additional information about the medium--density, number of volumes, other information",
"type": "string"
},
"jmd:transferSize": {
"type": "string",
"description": "number of bytes to transfer to get the resource. From ISO19115; the transfer size should be associated with each online or offline option, but ISO model puts it on collection all online and offline options for a given transfer option"
}
}
},
"jmd:fees": {
"type": "string",
"description": "text explanation of any payment required to access resource"
},
"jmd:availableDateTimes": {
"description": "identify dates or date ranges where there may be restrictions on access. 'event' term on each date should make it clear what the restriction is, e.g. business hours , offline for maintenance , discontinued after...",
"type": "array",
"items": {
"type": "string",
"format": "dateTime"
}
}
}
}
},
"jmd:resourceLineageStatement": {
"type": "string",
"description": "Summary statement for lineage. Lineage documents the provenance of the described resource, might include a single summary statement (this element), a link to an external Provenance resource using some other scheme (e.g. w3c prov), or a collection of processing steps ordered by a sequence property (based on ISO19115 lineage). The lineage information this scheme is interpreted to have a scope applying to the entire documented resource, thus there is no lineageScope property. To describe lineage of different parts, create separate resources."
},
"jmd:provenanceLink": {
"description": "a link to a provenance resource maintained externally; provides a URL that will retrieve the complete provenance trace for this record from the PROV service; alternative to recording process steps in the metadata document",
"$ref": "#/definitions/jmd:LinkObject"
},
"jmd:resourceLineageSteps": {
"description": "The lineageSteps array in this scheme is interpreted to have a scope applying to the entire documented resource. To describe lineage of different parts, create separate resources... LineageSteps is an array of Process steps-Summary statements for processing steps in resource processing; This schema allows construction of the history using processing steps described by statements, or as complete ISO19115 Lineage/processStep elements.",
"type": "array",
"minItems": 1,
"items": {
"jmd:stepSequenceNo": {
"description": "integer provided to sort processing steps in chronologic order. If an ISO19115",
"type": "integer"
},
"jmd:stepLabel": {
"type": "string",
"description": "text to characterize,identify this step for user interface listing"
},
"jmd:stepProcessors": {
"description": "0..N parties responsible for processing step",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:contactRef"
}
},
"jmd:stepProcessTypes": {
"type": "array",
"items": {
"$ref": "#/definitions/jmd:ControlledConceptObject"
}
},
"jmd:stepProcessDescription": {
"description": "free text description of what processing was done",
"type": "string"
},
"jmd:stepInputResources": {
"description": "reference that identifies the resource(s) that are input into the process step",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:LineageSourceObject"
}
},
"jmd:stepOutputResources": {
"description": "reference that identifies the resource(s) that are output from the process step",
"type": "array",
"items": {
"$ref": "#/definitions/jmd:LineageSourceObject"
}
},
"jmd:stepDateTimes": {
"type": "array",
"items": {
"$ref": "#/definitions/EventDate"
},
"description": "allow array, may have beginning, end, intermediate times..."
},
"jmd:stepRationale": {
"type": "string",
"description": "discussion of why the process step was done"
},
"jmd:stepComputerProcessing": {
"type": "object",
"properties": {
"jmd:processSoftware": {
"$ref": "#/definitions/jmd:ReferenceObject"
},
"jmd:processRunTimeParameters": {
"type": "array",
"items": {
"type": "object",
"properties": {
"jmd:processParameterName": {
"type": "string",
"description": "name of parameter"
},
"jmd:processParameterValue": {
"type": "string",
"description": "parameter value; profiles will need to define syntax for encoding units and non-scalar parameter values"
}
}
}
}
}
},
"jmd:stepProcessExtents": {
"type": "array",
"items": {
"$ref": "#/definitions/jmd:ExtentObject"
},
"description": "0..N scope process to a particular geographic location/locations. Only applicable to geospatial located dataset"
},
"jmd:stepAffectedElements": {
"type": "array",
"description": "references that identify dataset, entity, attribute instances affected by this process step",
"items": {
"$ref": "#/definitions/jmd:ReferenceObject"
}
}
}
},
"jmd:resourceQualityItems": {
"type": "array",
"items": {
"$ref": "#/definitions/jmd:ResourceQualityObject"
}
},
"jmd:resourceUsageConstraints": {
"type": "array",
"items": {
"$ref": "#/definitions/jmd:UsageConstraintObject"
}
},
"jmd:resourceMaintenance": {
"$ref": "#/definitions/jmd:MaintenanceObject",