Open Insurance Data Standard White Paper Work Group - 2/10/25
- Nathan Southern
Attendees
Peter Antley
Jim Bamberger
Jeff Braswell
Rob Clark
Cory Isaacson
Andy Mielke
Greg Williams
Opening Logistics
Peter Antley (PA) acknowledged the Linux Foundation Anti-Trust Policy and welcomed attendees.
Discussion
PA has been working through the white paper and processing some of the comments that have been made, as follows:
Ken Sayers (KS) agreed with the title as proposed in the previous session: Free and Open Standards for Information Exchange for the P&C Industry: The Benefits and Value Proposition. He particularly lauded the SEO-favorable nature of this title.
However, PA is less than totally satisfied with the formatting of the title and wants to work with it a bit more. Feels it reads better to start with “The Benefits and Value Proposition…” etc. etc.
PA highlighted a number of elements within the paper including where "royalty free” has been updated - likewise proprietary data formats, etc.
Sean produced the content for section 4 - Peter needs to go over this with him. Also wrote a How Can I Learn More section.
Ken wrote a section on Future Prospects. The group took a few minutes in session to discuss this.
Cory Isaacson (CI) - the content is solid, but it should more strongly emphasize the idea that this project will foster innovation and competition to make the processes of data exchange easier for everyone among new vendors - to make things more efficient, more cost effective. this will keep any single large company from dominating the space (e.g., ISO, RMS, etc.)
-PA and Jeff Braswell (JB) added a series of images following a related discussion with Peter. Specifically:
A future state diagram
A series of diagrams evoking the current state, as follows:
(for the current state, PA initially planned to use a diagram they incorporated in December, but it is too large and unwieldy - and the text is too small to read).
The confusing state diagram is as follows:
PA reviewed the narrative as it pertains to the diagram--->diagram transition in the document. PA’s feeling: messy diagram is good but doesn’t quite achieve the goal of showing that everyone has their own format - so some additional work is likely warranted, here.
To better evoke the different data formats, Rob Clark (RC) suggested that Peter implement patterns into the diagram. Also possible to change the nature of the lines themselves - dotted, dashed, straight, etc. Also: because we’re showing what one party is doing with another party, and a couple of example of those between different parties, and all the work that is involved, these lines represent lots of those.
Some of the arrows should be bidirectional, but not necessarily all of them.
Peter’s team has also been working on taking some of the language in the press release by Werner Kruck and consolidating it into the white paper. PA asked Jenny for a resource that can provide more assistance in this area.
On the problem statement: PA has made the content more muscular but doesn’t feel like the statement is quite ready for prime time yet. Cory agreed to help revise it.
Action Items
Peter Antley: Wordsmith the title of the white paper over the next week or so.
Group Members: Please review the white paper document for Peter’s highlights and note any of them with which you disagree.
Peter Antley: Integrate Sean Bohan’s comment/insight about future-proofing into the paper.
Rob Clark & Team: Contribute content on core model and extensibility this week.
Peter Antley: Review Sean’s content with him and ask him to discuss this in the OIDS group on Thursday.
Peter Antley: Revise the white paper so that it more strongly emphasizes the idea that this project will foster innovation and competition to make the processes of data exchange easier for everyone among new vendors - to make things more efficient, more cost effective. this will keep any single large company from dominating the space (e.g., ISO, RMS, etc.) this can be done as a summary at the bottom of Section 2.6. After Advantages of Future opportunities (next to 'Fostering Innovation,') this can be summarized again.
Peter Antley: Remove boxes around diagrams in white paper - and establish consistency between Figure X in the text and Figure X on the corresponding figure. Do this for all three diagrams.
Peter Antley: Work on tweaking/revising messy ‘current state’ diagram - per Rob’s suggestion, evoke different data formats with the incorporation of patterns, add different kinds of lines, bidirectional arrows, etc. per the comments above. Make this diagram better before Thursday.
Cory Isaacson: Work on beefing up/revising problem statement upon receiving the link from Peter.
Peter Antley: Work on cleaning up some of the unresolved comments in the white paper.