Homeowners Workstream: August 11, 2025
Time/Date:
August 11, 2025 - 2:00pm ET
Zoom Link:
Call Recording: <update>
Notices:
This specification creating group operates under the Linux Foundation Community Specification License v1.0.
Antitrust Policy: https://www.linuxfoundation.org/legal/antitrust-policy
Code of Conduct: https://events.linuxfoundation.org/about/code-of-conduct/
Meeting Attendees:
Related Specifications and Repositories:
Meeting Agenda:
Did everyone have a chance to consider what additional artifacts they'd like reviewed as part of this process / did everyone successfully access the shareable doc
Review of the initial project plan outline / and proposed data standard to build out (see project plan below)
Discussion and feedback on the plan
Next steps
We’re also including a draft outline of the project plan, which we’ll walk through during the call. We welcome your input and suggestions during or ahead of time:
Draft Project Plan
Step 1: Identify a focused subset of the homeowners model to use as the basis for the data standard.
Mike Payne made a recommendation here.
Step 2: Review the artifacts contributed by Cloverleaf and others, specifically for the chosen subset.
Step 3: Review and align on standard naming conventions.
Step 4: Review applicable codes associated with the subset.
Step 5: Confirm a logical format/structure for the data standard.
Step 6: Expose Standard in Draft form to key stakeholders for feedback.
Step 7: Finalize and publish Standard.
Notes:
Housekeeping
Choosing report to show the data that comes in can fulfill that report (data in-report out)
Discuss validations, how to round out the smallest part that logically means we understand how this all works
Reports that MP provided, baseline, “exhibit to create and calculate” - HO and policy form, doesnt inc other HO fields (construction type, etc.) - have this report to fill out, can come up with ALL the possible codes added to a similar report (so we can do different reports)
Hand in hand but not seem to be related - dont need to be sequential, once standards are ready can modify/create new exhibits
Are there diff people in this workstream who want to work on one vs the other - up to the individuals on this call
support on drilling down into items for specific people, this week to next week there are things to work on
#1 goal - find gaps in what we have right now - if we find there arent really gaps speed up, and if we find gaps we can dig in
Do it as extensions, for the most part reinsurers will look at similar attributes for risk, so will brokers for pricing
RFI to Oasis (JH) to see if there are additional docs/stakeholders
see if we collect any new info between now and next week
Cat model things - beyind the scope of this first effort
from a foundational perspective, what we may/may not think about
a lot of elements in Oasis that are relevant but not all components
limit fields with code, maybe oasis has opinions
oasis comes into play whne looking at codes
Suggestion for name of what we should call the first standard - thoughts?
do we want one overarching name for the standard and extensions will be “dot-something” or every one has a different name
dont want to stray too far away from cloverleaf conventions
take a look and propose? for next meeting
Clarify on roles and responsibilities
policy forum, second lead on the workstream? need someone from CL ?
validators of what we are saying
heavy AAIS team, representation from actuarial and product
and other external parties
will make sure MikeP gets support, convo w/ RobC (CL)
include JT on MP bandwidth
Action Items / ToDo: