221 update disaster_identifier to array of Classification objects

docs/about/changelog.md

@@ -77,6 +77,9 @@ This page lists changes to the Risk Data Library Standard.
 - [#210](https://github.com/GFDRR/rdl-standard/pull/210) - Replace `resource.`url with `.access_url` and `download_url`
 - [#218](https://github.com/GFDRR/rdl-standard/pull/218) - `Vulnerability·taxonomy` removed from required array.
 - [#220](https://github.com/GFDRR/rdl-standard/pull/220) - Reorder top-level fields.
+- [#232](https://github.com/GFDRR/rdl-standard/pull/232)
+  - Convert `disaster_identifiers` to array of `Classification` objects.
+  - Add new codes to classification_scheme.csv.
 
 ### Codelists
 

docs/rdl/other-standards.md

@@ -14,11 +14,6 @@ In 2018 an international consortium led by the British Geological Survey develop
 In this standard, we developed a list of hazard type codes and process type codes which are used as a reference in the hazard, vulnerability and loss components of the standard, and facilitate matching of appropriate vulnerability functions to hazard data, for example.
 Details about the development are reported [here](https://riskdatalibrary.org/resources).
 
-**GLIDE disaster event identifier**:
-Since the beginning of 2004, GLobal IDEntifier numbers (GLIDE) are produced at (GLIDEnumber.net) for all new disaster events reported by partner institutions and those discovered by ADRC.
-A GLIDE number comprises two letters to identify the disaster type (e.g. EQ - earthquake); the year of the disaster; a six-digit, sequential disaster number; and the three-letter ISO code for country of occurrence. E.g., the GLIDE number for West-India Earthquake in India is: EQ-2001-000033-IND. This number is posted by the above organizations and in many other websites, on their documents relating to that particular disaster and gradually other partners will include it in whatever information they generate. As information suppliers join in this initiative, documents and data pertaining to specific events may be easily retrieved from various sources, or linked together using the unique GLIDE numbers. List of services using GLIDE: https://glidenumber.net/glide/public/links.jsp
-The RDL Standard uses a GLIDE number in the `hazard.event` object, to denote the historical event to which hazard event data relates, e.g., the simulated hazard intensity footprint of that event.
-
 ### Hazard taxonomies
 
 The RDL project performed a review of the most relevant hazard taxonomies and derived a classification focusing on those hazards and processes that are more often required in disaster risk assessments, while mapping and matching alternative definitions into one consistent framework. There are several existing taxonomies that could have been adopted to describe hazard data:

docs/reference/schema.md

@@ -156,7 +156,7 @@ The following diagram shows key hazard component fields, with required fields hi
         "temporal": "",
         "events": [
           {
-            "disaster_identifier": "",
+            "disaster_identifiers": "",
             "calculation_method": "",
             "description": "",
             "hazard": {
@@ -165,7 +165,7 @@ The following diagram shows key hazard component fields, with required fields hi
               "intensity_measure": "",
               "trigger": ""
             },
-            "occurence": "",
+            "occurrence": "",
             "footprints": [
               {
                 "intensity_measure": "",
@@ -1195,6 +1195,7 @@ jsonpointer: /$defs/Classification/description
 This sub-schema is referenced by the following properties:
 
 - [`vulnerability/se_category`](rdls_schema.json,/properties/vulnerability,se_category)
+- [`Event/disaster_identifiers`](rdls_schema.json,/$defs/Event,disaster_identifiers)
 
 Each `Classification` has the following fields:
 

schema/codelists/open/classification_scheme.csv

@@ -1,3 +1,6 @@
 Code,Title,Definition,Source,Category
 GED4ALL-socio-economic,GED4ALL socio-economic taxonomy,The socio-economic taxonomy defined in the Global Exposure Database for Multi-Hazard Risk Analysis (GED4ALL).,https://wiki.openstreetmap.org/wiki/GED4ALL#Socio-Economic,Socio-economic index
 MOVER_social_vulnerability_categories,MOVER social vulnerability categories,The social vulnerability categories defined in the Multi-Hazard Open Vulnerability Platform for Evaluating Risk (MOVER).,https://www.gfdrr.org/en/publication/mover,Socio-economic index
+GLIDE,Global Identifier Numbers,Identification codes generated by GLIDE since 2004 for all new disaster events reported by the Asian Disaster Reduction Center and GLIDE partner organizations.,https://www.glidenumber.net/glide/public/search/search.jsp,Distaster identifier
+EMDAT,EM-DAT International Disaster Database,"EM-DAT contains data on the occurrence and impacts of over 26,000 mass disasters worldwide from 1900 to the present day. The database is compiled from various sources, including UN agencies, non-governmental organizations, reinsurance companies, research institutes, and press agencies. The Centre for Research on the Epidemiology of Disasters (CRED) distributes the data in open access for non-commercial use.",https://www.emdat.be/,Disaster identifier
+USGS_EHP,USGS Earthquake Hazards Program,"The USGS monitors and reports on earthquakes globally, assigning each reported event a unique identifier. These event identifiers are used in the associated USGS products including PAGER, ShakeMap and DYFI.",https://earthquake.usgs.gov/earthquakes/search/,Disaster identifier

schema/rdls_schema.json

@@ -1813,11 +1813,14 @@
           "description": "A locally unique identifier for this event.",
           "minLength": 1
         },
-        "disaster_identifier": {
-          "title": "Disaster identifier",
-          "type": "string",
-          "description": "The GLIDE number associated with this disaster event. A globally unique identifier for the event, assigned by [GLIDE](https://www.glidenumber.net/glide/public/search/search.jsp).",
-          "minLength": 1
+        "disaster_identifiers": {
+          "title": "Disaster identifiers",
+          "type": "array",
+          "description": "Disaster identifiers for this event.",
+          "items": {
+            "$ref": "#/$defs/Classification"
+          },
+          "minItems": 1
         },
         "calculation_method": {
           "title": "Model calculation method",
@@ -2426,6 +2429,9 @@
       "title": "Classification",
       "description": "A classification consists of at least two parts: an identifier for the list (scheme) from which the classification is taken, and an identifier for the category from that list being applied. It is useful to also publish a text label and/or URI that users can draw on to interpret the classification.",
       "type": "object",
+      "required": [
+        "id"
+      ],
       "properties": {
         "scheme": {
           "title": "Scheme",