Release/4.0.0 (RC3) #209
Open
Release/4.0.0 (RC3) #209
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MattDonovan82
approved these changes
Aug 22, 2024
* test pr list build artifact * Fix unexpected column name change * Add build step to post excel on PR's * Add script to update rel links * Update release script for test * check * Fix * release test working
Build PreviewYou can find files attached to the below linked Workflow Run URL (Logs).
|
Build PreviewYou can find files attached to the below linked Workflow Run URL (Logs).
|
Co-authored-by: sstruzik <stephane.struzik@gmail.com>
* Update ReadMe.md Updates to the cyber 'read me' * Update Liability ReadMe.md Update and edits to the liability read me - into, rationale and taxonomy descriptions. * Delete Docs/Liability/Docs/OED_Liabs_DataFields.csv Deleted the liability data fields.csv * Delete Docs/Liability/Docs/OED_Liabs_DataSpec_v1.0.xlsx Deleted the liability data spec.xlsx * Delete Docs/Cyber/Docs directory deleted the cyber 'data fields' and 'data spec' docs. * Delete Docs/Liability/Docs/ODS_Liabs_Rationale_Taxonomy_v1.0.pdf Delete the liability rational .pdf doc - this is covered in the 'read me' anyway and was mainly for distribution to the community upon original launch of liability. * Update ReadMe.md Added the correct taxonomy image * Add files via upload * Update README.md * minor edits and add 3.4.1 release link to table * fix typo and delete duplicate diagram --------- Co-authored-by: Joh Carter <johanna.carter@oasislmf.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release/4.0.0 (RC3)
OED v4.0.0 is the first version which brings together the data standards for multiple exposure classes; property, cyber, liability and marine cargo, into a single integrated specification. The set of fields supported for each class are different and allow for different required field status to be flexible enough to serve a wide range of use cases. Wherever fields are common across classes they share identical descriptions, data types, default values and conditionally required 'CR' codes.
The files and structure of the Open Exposure Data repository have also been changed since OED v3. The 'source of truth' of the specification has been moved from excel to csv, to enable better version control and transparency of changes in github. The excel specification has been retained but is generated from the underlying csv's with each release, and accessible directly from the README in the home directory, for the convenience of users.
Specification
More details of changes in the specification, documentation and data examples are summarized in the following issues.
Property
Changes that affect property and reinsurance are listed below.
Cyber and Liability
The OED v4 version of the cyber and liability specifications follow directly on from the respective v1.0.0 versions. The changes are substantial, with many fields being renamed in order to align with existing property fields that have equivalent meaning, the financial fields have been revised and many optional fields have been added for consistency of data storage across exposure classes. More details can be found within the following issues.
Marine Cargo
OED v4.0.0 for Marine Cargo is the first version of the specification for this exposure class and should be considered work in progress. It is has been added as a separate exposure class with a minimal set of fields rather than integrated into property because it is expected that there will be a lot more improvements to be made which can be made as future minor updates (additions) that will not impact the other classes.
OpenExposureData_Spec.xlsx ~ 4f91fafOpenExposureData_Spec.xlsx ~ 0cfa0ed