Merge branch 'main' into dev

SteeringCommittee/Minutes Steering Committee No.4 - 9 March 2023.md

@@ -30,42 +30,42 @@ SC members:
 ## Notes
 
 * Update on Fellowship program
-    * Introduced fellows and range of experience. From masters people to experienced with ADB and others. Reasons for 2 fellows in Philippines. Isabelle assigned a project in CB working on detect exposure data, support from SwissRe Foundation, ground truth validation. 
-    * Will provide summary of fellows to SC, to share profiles, and potentially set up bilateral meetings to discuss projects/relevant experience.
-    * TR: what happens to fellows at the end of the program: encourage them to maintain a relationship beyond the project, increasing talent and exposure is a nice thing to do, and good to grow that talent and see where they can get to. PC: will be STC and meet WB staff so have a change to explore that.
+    * Introduced fellows and range of experience. From masters people to people experienced with ADB and others. Reasons for 2 fellows in the Philippines. Isabelle was assigned a project in CB working on detecting exposure data, support from SwissRe Foundation, ground-truth validation. 
+    * Will provide a summary of fellows to SC, to share profiles, and potentially set up bilateral meetings to discuss projects/relevant experience.
+    * TR: what happens to fellows at the end of the program: encourage them to maintain a relationship beyond the project, increasing talent and exposure is a nice thing to do, and good to grow that talent and see where they can get to. PC: will be STC and meet WB staff so have a chance to explore that.
     * NM: How can we propose to or explore opportunities with Fellows, before they start considering other opps? E.g. GRMA opportunity for work. PC: there are workshops, and we welcome presentations on the initiatives you’re working on, to do show those opportunities.
-    * CH: important to Foundation that the Fellows are supported and get jobs after the initial project training. Encourage meeting them, discussing.
-* Update on technical review of the standard
+    * CH: important to Foundation that the Fellows are supported and get jobs after the initial project training. Encourage meeting them, to discuss.
+* Update on the technical review of the standard
     * Summary of technical review findings ([document link](https://docs.google.com/document/d/1dBK7dr7JzHnLwcR9RTHybjpaS8JViopu5LLGPHqpm2c/edit?usp=sharing)) 
-        * RV: By July, should have updated standard and repo, documentation site. This report informs that. Ran through the report main sections. HIghlgihted normative/… , example data, recommendations on the schema to align with JSON schema version, development environment to make it clear on how people can 
-        * General request to SC to have a look and comment on anything that raises flag, missing.
+        * RV: By July, should have updated standard and repo, documentation site. This report informs that. Ran through the report's main sections. Highlighted normative/non-normative text, example data, recommendations on the schema to align with JSON schema version, the development environment to make it clear about how people can use it.
+        * General request to SC to have a look and comment on anything that raises flags, missing.
     * Priority tasks for the review and enhancement of the RDLS - underway
         * User implementation - request on how you prepare would want to handle data:
             * PH:
-                * Metadata - any text based solution would work.
-                * Data in any text based format - any tools stop working quickly. In shp/tif, good as people can put data straight int, but how to keep together.
-                * Humans filling in data / forms - online form appropriate.
-                * Where lots of data, want to be able interrogate a db and create metadata automatically.
-            * TR: simplest things work well - think of developing countries context - multi-use mean familiarity. Dropdown menus, choices, less free text - better for consistency.
-            * EV: licences with spreadsheets, preference of google vs MS e,g. Creating things online, good but also need to create manual for each approach. Need to advocate for completion of metadata - make it less of a burden. Generic academic user may not think of adding the metadata. Would do online tool.
+                * Metadata - any text-based solution would work.
+                * Data in any text-based format - any tools stop working quickly. In .shp/tif, good as people can put data straight into it, but how to keep it together.
+                * Humans filling in data/forms - online form appropriate.
+                * Where lots of data, want to be able to interrogate a db and create metadata automatically.
+            * TR: simplest things work well - think of developing countries context - multi-use means familiarity. Dropdown menus, choices, less free text - better for consistency.
+            * EV: licences with spreadsheets, preference of Google vs MS e,g. Creating things online is good but also need to create a manual for each approach. Need to advocate for the completion of metadata - make it less of a burden. Generic academic users may not think of adding the metadata. Would do an online tool.
             * SH: make it as easy as possible, droplists to make it as easy as possible. Be prescriptive in file formats too. Many in JBA can use JSON, many don’t. 
-            * PC: helpful for us to all review the tools we’re using. We can be biased towarfds using WB tools and because we’re using the data hub.
-            * CH: some corporates to cant open Google.
+            * PC: helpful for us to all review the tools we’re using. We can be biased towards using WB tools because we’re using the data hub.
+            * CH: some corporates can't open Google Docs, etc.
 * Update on standard implementation
     * Update on the datasets being converted, uploaded - good coverage soon in the data catalog RDL Collection: [https://datacatalog.worldbank.org/search/collections/Risk-Data-Library](https://datacatalog.worldbank.org/search/collections/Risk-Data-Library).
 * Update on epicentre vulnerability database
     * MOVER-MVData presentation - past present and future. Development of MOVER to develop structured data. Massive schema. Adminimum dashboard in Heroku hosting of db. THen refactored MOVER with GEM (‘MOVER_cf’). Grouped information common >1 function type. Used TH hazard taxonomy and elaborated process types. Organised the ideal IMT per process.
-    * Now MVDat: expanding - single hazard multiple concurrent processes; single hazard, multiple sequential processes; multiple concurrent hazards; multiple sequential hazards. Including more dimensionality - from bi-dimensional, to curves in real-time / multi-dimensionality. To reduce the uncertainty in selecting and using the functions, characterising hazards and the dynamics between hazard and triggers. Working on oceanic/coastal; adding into hazard code explicit mention of the trigger (TSI, EQ_TSI, VO_TSI, LS_TSI). Adding asset schema natural resource, livelihoods, energy/power, biomedical scientific research facilities, decarbonisation, data centre/internet server farms (networks as well as industrial buildings and components).
+    * Now MVDat: expanding - single hazard multiple concurrent processes; single hazard, multiple sequential processes; multiple concurrent hazards; multiple sequential hazards. Including more dimensionality - from bi-dimensional, to curves in real-time / multi-dimensionality. To reduce the uncertainty in selecting and using the functions, characterising hazards and the dynamics between hazards and triggers. Working on oceanic/coastal; adding into hazard code explicit mention of the trigger (TSI, EQ_TSI, VO_TSI, LS_TSI). Adding asset schema natural resource, livelihoods, energy/power, biomedical scientific research facilities, decarbonisation, data centre/internet server farms (networks as well as industrial buildings and components).
     * Built almost complete registry of seismic and tsunami. LS, FL, WS functions are good. Not global but expanding.
     * Future: 
         * Would like feedback from practitioners, develop
-        * Develop out data schema - industrial components: Lots of interest. Also on socio-economic data.
+        * Develop data schema - industrial components: Lots of interest. Also on socio-economic data.
         * Move from descriptive analytics to predictive analytics.
         * Business model still to be defined. Need to build a community.
-    * SF/PC: can we find a way to link data to RDLS, and implement some of the new codes in RDLS (PH highlighted the different framing of hazards and trigger - allowing association between different triggers and hazards).
+    * SF/PC: can we find a way to link data to RDLS, and implement some of the new codes in RDLS (PH highlighted the different framing of hazards and triggers - allowing association between different triggers and hazards).
 * Alignment with ODS/RDLS
     * Workshop in 2021. Standards for exposure data that goes into industry cat models, loss estimates produced by them. Any model using the platform can use these standards - proprietary data standards have dominated the industry. We don’t have a standard H/V standard. Idea of the project to be funded under Oasis development, is to implement the RDL H/V standards in Oasis - Joh Carter leading. Would be looking to IDF funding and engage with RDL team.
-        * Please think for next time about use cases for having hazard and vulnerability standard wrapped aorund data in Oasis.
+        * Please think for next time about use cases for having hazard and vulnerability standard wrapped around data in Oasis.
     * Oasis conference flagged.
 * AOB
     * PC: Last minutes feedback received, upload to github after this call
@@ -74,5 +74,6 @@ SC members:
  - Last minutes upload to github (PC) 
 
  ## Next Meeting Agenda 
- - Date: May 11, 9am EST / 3pm pm CET
+
+ - Date: May 11, 9am EST / 3pm CET
 - Proposed agenda: Risk Data Library Standard proposed change by ODS Global Risk Data Bank by IFRC

SteeringCommittee/Minutes Steering Committee No.5 - 11 May 2023.md

@@ -0,0 +1,90 @@
+# Minutes of RDLS Fellows project Steering Committee No.5
+
+11 May 2023 / 09:00-10:30 EDT, 14:00-15:30 GMT / via Teams
+
+## Attendees
+
+Pierre Chrzanowski, Cristiano Giovando, Andrea Garcia (GFDRR) 
+Carolina Hess (SwissRe Foundation)
+Rachel Vint (Open Data Services)
+SC members: 
+- Paul Henshaw, GEM Foundation
+- Matt Donovan, Oasis/Open Data Standards
+- Stephen Hutchings, JBA Risk Management
+Invitees:
+- Johanna Carter, Oasis/Open Data Standards
+- Marcus Elten, UNDRR
+Absent:
+- Tiziana Rossetto, UCL EPICentre
+- Nick Moody, IDF/GRMA
+- Beat Aeberhardt, Swiss Re
+- Justin Ginetti, Hamish Patten, IFRC - Global Risk Databank (excused)
+
+## Agenda
+
+1.  Minutes of last meeting: https://github.com/GFDRR/rdl-standard/tree/dev/SteeringCommittee 
+
+2.  Progress on the standard:
+  * Update on revision of schema to object-oriented JSON format. We’d like to offer 1 week to review and to get SC members’ approval.
+  * Github issues available to contribute at https://github.com/GFDRR/rdl-standard/issues
+  * Data sprint:
+    * Planned for the beginning of June
+    * Will be done with RDL Fellows to create metadata and format data in pipeline.
+  * Update on standard implementation
+    * Documentation revisions ongoing, available to review in June
+
+3.  Update on Fellowship program
+  * Sharing project descriptions, review for interest in collaborating / further work
+  * Arrange a fellowship workshop, in which steering committee can share their work/projects
+
+4.  Update on aligning Open Data Standards and RDLS - Oasis team developing use of hazard and vulnerability metadata into Oasis models. Last meeting, requested use cases for having hazard and vulnerability standard wrapped around data in Oasis.
+
+5.  IFRC - Global Risk Databank - possiblity to use RDLS and data from Data Catalog.
+
+6.  Propose next SC meetings
+  * Wednesday 12 July 2023
+  * Thursday 14 September 2023
+  * Thursday 16 November 2023
+
+7.  AOB
+
+## Notes
+
+- Progress on the standard (see slides)
+  - PH: Question on taxonomy- is taxonomy naming retained in metadata?
+  - SF: Taxonomy code is remaining in the dataset but not in the metadata
+  - PH: Taxonomy source should come with version as well - SF agreed name and version should be in metadata
+  - Issues will be shared on GitHub with indications / pointers to invite specific reviewers
+  - When we have uploaded a good number of issues we will mail to update and invite comments
+- Objective is to have an approved version by the next SCM in early July
+- SF: we have been working with the World Bank data catalog team to display RDL metadata - discussion here https://github.com/GFDRR/rdl-standard/issues/51 
+- Oasis ODS can benefit from using RDLS metadata - lots of dev effort has been on preparing big model files - metadata has been a secondary consideration, and it is not compulsory - models not well derived - which perils, units, size of event set, etc, how freq defined.
+- Adopting RDL standard could be used to better describe models
+- Can adopt in ODS package - Johanna Carter checking what ODS needs, / doesn’t - what might be missing in RDL.
+- PH: Nasdaq “Key Facts” document provides a brief description of the most important aspects of a Model.  If Nasdaq were happy to share their template this might be useful since many OASIS vendors are already producing such documents for their models.
+- MD: Question on the integration of the ODS into RDLS - SF: lots we can learn from Oasis file structure - speaking with Joh.
+- PH: Humanitarian is still separated from the Insurance sector (humanitarian models often focus on data points such as fatalities, etc. while OASIS models can produce insured/reinsured losses).  RDLS has been designed to be taxonomy neutral. Don’t replicate or build new functions if existing in RLDS or ODS - re-use.
+- JC: it would make sense to have the Financial Terms in the RDLS exposure data given RLDS Loss component include ec/ins loss perspectives
+- Presentation of the Global Risk Data Bank by Marcus Elten
+- A project between UNDRR and IFRC - concept note
+  - Middle of phase 2; A first demo 2-3 weeks
+  - SteerCo includes NASA, WMO…
+  - The first step is to provide a consistent database of historical event impacts - footprints, impact. 
+  - SF: Ideal situation that GRD and RLDS represent the same information, GRD using RDLS metadata about historical events - GRD data into modellers to represent the event as best as possible; modellers share information beach to GRD on modelled impacts? Can SC propose some use cases to support this need?
+- CH: Data from Global Risk Datankbase could be used for parametric insurance product trigger setting (based on an understanding of past impacts)
+- Marcus suggested SteerCo as a place GFDRR can contribute.
+
+## Actions
+- GFDRR to share Fellowship project descriptions.
+- Have a Fellow Workshop to share info from SC members' organisations/experiences/opportunities. AG to share workshop dates, and plan agenda.
+- ODS/Stu to log GitHub issues, email SC when bulk is done.
+- Stu - set up a conversation about tax. strings. 
+- Tax type and version need to be in the metadata
+- Implementing occ/con types in separate fields - or as one string?
+- Understand how footprints in RDLS can complement historical data in ‘GRD’ - GFDRR conversation with IFRC planned.
+## Next Meeting Agenda
+- Make the next set of SC meetings more strategic focus, with a renewed focus on funding and future direction, having been focused on technical elements in the last few meetings.
+- Update on the agreed new schema version (to be agreed before the meeting)
+- Fellowship progress incl feedback from the SC sharing of experience.
+- Date: Weds 12 July 2023
+

SteeringCommittee/readme.md

@@ -1 +1,3 @@
 This folder contains RDL Fellowship Steering Committee minutes and related documents.
+
+When taking minutes, we recommend using Markdown editor https://jbt.github.io/markdown-editor/