minor edits and add 3.4.1 release link to table

Docs/Cyber/ReadMe.md

@@ -5,34 +5,34 @@
 
 ### Introduction
 
-The increasing demand over the last five years, resulted in the release of the first data schema for cyber exposure data in 2022. Since then, it became obvious that only one OED data schema accommodating multiple classes of business would be more efficient than being separate.
+Growing demand over the past five years led to the release of the first cyber exposure data schema in 2022 as part of the Open Exposure Data standard. It soon became clear that a single, unified OED schema for multiple business classes would be more efficient than separate schemas.
 
-Following this, OED 4.0.0. was released in Jan 2025 and incorporates all of the fields captured in the original version of the cyber schema. There has been some changes to the names of the data fields to align and integrate with property and the original schema.
+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. It incorporates all fields from the original cyber schema, with some field names updated for better alignment with property and the main schema.
 
 Please refer to the release notes for OED v4 that includes all updates (https://github.com/OasisLMF/ODS_OpenExposureData/releases).
 
-More general information can also be found on the ODS webpage (https://oasislmf.org/open-data-standards.
+More general information can also be found on the ODS webpage (https://oasislmf.org/open-data-standards).
 
-It’s important to note that this is NOT an Oasis standard but a market initiative that is only curated by Oasis and so the success of ODS is reliant on community collaboration. The aim of ODS is not to serve or be controlled by a single entity for their own commercial benefit, but to accommodate multiple developers and users, be open and transparent for all.
+### Contributors
 
-The initial cyber data standard was developed through the collaboration of a working group throughout 2022, made up of participants from the following companies. Their time and efforts were hugely appreciated. 
+The cyber data standard v1 was developed through the collaboration of a working group throughout 2022, made up of participants from the following companies. Their time and effort are hugely appreciated. 
 
 * Allianz
 * Aon
 * Axis Capital
-* Cyberacuview
+* CyberAcuView
 * Gallagher Re
 * Guidewire Cyence
-* Guy Carp
+* Guy Carpenter
 * KOVRR
 * Oasis LMF (ODS curator/secretariat)
-* Ren Re
+* RenaissanceRe
 * Richard DeKorte (Cyber Security Independent)
-* RMS
+* Moody's RMS
 * Sompo International
 * Swiss Re
 * Waratah Analytics
-* Zurich
+* Zurich Insurance
 
  
 
@@ -42,9 +42,7 @@ The initial data schema was primarily intended to ensure a degree of consistency
 
 The cyber specific data fields are highlighted in the 'Cyber Fields Status' column in the 'OEDInputsFields.csv' where the fields can be filtered on 'R' for 'required fields', 'O' for 'optional' and 'CR' for 'conditionally required'. 
 
-The cyber specific coverages are included in the 'CoverageValues'.csv and prefixed by 'PolDed' for sub-deductibles and 'PolLimit' for sub-limits.
-
-
+The cyber specific coverage codes are included in the 'CoverageValues.csv' and prefixed by 'PolDed' for sub-deductibles and 'PolLimit' for sub-limits.
 
 ### Considerations
 
@@ -59,7 +57,7 @@ They should consider the vendors of their 'primary' or 'main' systems/servers as
 
 4. The user is responsible for populating the data fields in this schema. No fields will be linked to any external database (i.e., for industry scheme or code).
 
-5. All cyber exposure fields are captured in the acc (account) file. There are no 'required' fields for cyber captured in the loc file.
+5. All cyber exposure fields are captured in the acc (account) file. There is no need for a location file as the data standard does not currently require the capture of physical asset data with geographical locators, although there is nothing to preclude this from being developed going forward.
 
 Any feedback or suggestions should be sent as an issue in the GitHub repo: https://github.com/OasisLMF/ODS_OpenExposureData/issues
 

Docs/Liability/ReadMe.md

@@ -7,21 +7,21 @@
 
 The first version of the OED schema for liability data was released in April 2022 following the efforts of a small market working group. The release video can be found on the Oasis You Tube channel (https://youtu.be/WW9N4mlNtb8). This was the first data schema available to the market to promote the use of standardised liability data for the re/insurance industry. 
 
-It’s important to note that this is NOT an Oasis standard but a market initiative that is only curated by Oasis and so the success of ODS is reliant on community collaboration. The aim of ODS is not to serve or be controlled by a single entity for their own commercial benefit, but to accommodate multiple developers and users, be open and transparent for all.
+OED v4.0.0 is the first major release which brings together the data standards for multiple exposure classes; property, cyber, liability and marine cargo, into a single integrated specification. It incorporates all fields from the original liability schema (v1), with some field names updated for better alignment with property and the main schema.
 
  
 
 ### Rationale
 
 This data standard is primarily intended to ensure a degree of consistency in policy-level data capture and to enable efficient sharing of select data fields across the industry. Other than the benefit of reduced frictional cost, wide-spread adoption of the schema should enable portfolio managers to implement granular, accurate and robust exposure management procedures. This can, in turn, enable sophisticated risk accumulation and/or liability modelling use cases.
 
-The approach for the original schema was to make it as succinct and prescriptive as possible to ensure consistency of the data formats and to keep any ambiguity to a minimum. This schema has now been incorporated into the sole OED schema that has been released as OED v4.0.0 in January 2025. OED now supports the use of multiple classes such as property, liability, cyber and marine. The liability specific data fields still capture the same data as the original version, but the naming conventions have slightly changed to align with the current OED fields and hierarchy that have been used for property since OED's inception.
+The approach for the original schema was to make it as succinct and prescriptive as possible to ensure consistency of the data formats and to keep any ambiguity to a minimum. 
 
 The original taxonomy created for the liability data standard below is still intended to be internationally applicable and implemented across UK, European and US markets. Increased market adoption of this schema will heavily rely on it being used by the key players in the data transfer process, specifically the brokers and reinsurers.
 
 At a high level, the approach taken has aligned to the EIOPA definition of liability classes (classes 10-13 in their non-life risk classification convention), with some subdivision of the broad Other category. The benefit of linking the scope to the EIOPA definition is primarily to ensure exhaustiveness. 
 
-*Motor Liability*, *Aviation Liability*, *Marine Liability* and *Personal Liability* are all still excluded from OED 4.0.0. This is partly motivated by concerns around the sharing of personal information, but also the idea that liability exposure accumulation analysis often starts at company or industry-level. Accident & Health, which is not considered a liability class under the EIOPA convention, could be omitted for similar reasons, with a possible fringe case for inclusion being the Workers’ Compensation class of business.
+*Motor Liability*, *Aviation Liability*, *Marine Liability* and *Personal Liability* are all excluded from the data standard. This is partly motivated by concerns around the sharing of personal information, but also the idea that liability exposure accumulation analysis often starts at company or industry-level. Accident & Health, which is not considered a liability class under the EIOPA convention, could be omitted for similar reasons, with a possible fringe case for inclusion being the Workers’ Compensation class of business.
 
 It’s worth noting that in designing the taxonomy, it was decided to consider attributes of the insured, such as industry/trade/profession, separately from class/coverage. For example, medical practitioners, financial institutions, architects, engineers and lawyers can all be considered as insured attributes to be captured for the *Professional Liability* coverage class. This should lend itself to a more concise and consistent data schema.
 

README.md

@@ -63,7 +63,7 @@ Further information and community views of ODS can be found on the ODS website:
 https://oasislmf.org/open-data-standards
 
 
-***It's important to understand that ODS is NOT an Oasis standard, but an initiative developed by the market for the market.***
+***It's important to understand that ODS is NOT an Oasis standard, but an initiative developed by the market for the market.*** The success of ODS is reliant on community collaboration. The aim of ODS is not to serve or be controlled by a single entity for their own commercial benefit, but to accommodate multiple developers and users, be open and transparent for all.
 
   
 
@@ -81,6 +81,7 @@ https://oasislmf.org/open-data-standards
  | 3.2.0 | [OpenExposureData_Spec.xlsx](https://github.com/OasisLMF/ODS_OpenExposureData/raw/3.2.0/OpenExposureData/Docs/OpenExposureData_Spec.xlsx) | [OpenExposureData_Spec.json](https://github.com/OasisLMF/ODS_OpenExposureData/releases/download/3.2.0/OpenExposureData_Spec.json) | [Release Page](https://github.com/OasisLMF/ODS_OpenExposureData/releases/tag/3.2.0) |
  | 3.3.0 | [OpenExposureData_Spec.xlsx](https://github.com/OasisLMF/ODS_OpenExposureData/raw/3.3.0/OpenExposureData/Docs/OpenExposureData_Spec.xlsx) | [OpenExposureData_Spec.json](https://github.com/OasisLMF/ODS_OpenExposureData/releases/download/3.3.0/OpenExposureData_Spec.json) | [Release Page](https://github.com/OasisLMF/ODS_OpenExposureData/releases/tag/3.3.0) |
  | 3.4.0 | [OpenExposureData_Spec.xlsx](https://github.com/OasisLMF/ODS_OpenExposureData/raw/3.4.0/OpenExposureData/Docs/OpenExposureData_Spec.xlsx) | [OpenExposureData_Spec.json](https://github.com/OasisLMF/ODS_OpenExposureData/releases/download/3.4.0/OpenExposureData_Spec.json) | [Release Page](https://github.com/OasisLMF/ODS_OpenExposureData/releases/tag/3.4.0) |
+ | 3.4.1 | [OpenExposureData_Spec.xlsx](https://github.com/OasisLMF/ODS_OpenExposureData/raw/3.4.1/OpenExposureData/Docs/OpenExposureData_Spec.xlsx) | [OpenExposureData_Spec.json](https://github.com/OasisLMF/ODS_OpenExposureData/releases/download/3.4.1/OpenExposureData_Spec.json) | [Release Page](https://github.com/OasisLMF/ODS_OpenExposureData/releases/tag/3.4.1) |
 <!-- NEW VERSION TAG -->
 
 
@@ -108,14 +109,14 @@ https://github.com/OasisLMF/OpenDataTransform
 
 **Liability** 
 
-The focus for OED has primarily been on property cat business since its inception but has now expanded to support other lines of business. The initial (separate) liability data schema was released in April 2022 but has now been incorporated into the OED schema. See the 'liability field status' field here https://github.com/OasisLMF/ODS_OpenExposureData/blob/release/4.0.0/OpenExposureData/OEDInputFields.csv.
+The focus for OED has primarily been on property exposure data since its inception but has now expanded to support other lines of business. The v1 liability data schema was released in April 2022 and has now been incorporated into the main OED schema. See the 'liability field status' field here https://github.com/OasisLMF/ODS_OpenExposureData/blob/release/4.0.0/OpenExposureData/OEDInputFields.csv.
 
 
 &nbsp; 
 
 **Cyber** 
 
-The initial (separate) cyber schema was released in February 2023 bit has now been incorporated into the OED schema. See the 'cyber field status' field here: 
+The v1 cyber schema was released in February 2023 but has now been incorporated into the main OED schema. See the 'cyber field status' field here: 
 https://github.com/OasisLMF/ODS_OpenExposureData/blob/release/4.0.0/OpenExposureData/OEDInputFields.csv.