Versions Compared
Version | Old Version 1 | New Version 2 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
🔓 Public Page
Date:

Info |
---|
ANTITRUST STATEMENT As participants in this meeting, we need to be mindful of the constraints of antitrust laws. There shall be no discussions of agreements or concerted actions that may restrain competition. This prohibition includes the exchange of information concerning individual prices, rates, coverages, market practices, claims settlement practices, or any other competitive aspect of an individual company’s operation. Each participant is obligated to speak up immediately for the purpose of preventing any discussion falling outside these bounds. |
Agenda
Welcome
Antitrust
Review Meeting Minutes
Review Action Items
Dan - review 3.2.22 SpecialtyVehicleDesc to look at the qty and desc use in the naming.
Mike/Jeff - Analyze the WarrantyValue and aggregates to recommend a solution.
Work on EMStoBMStoCAPIS Parking Lot
Complete 52 Aggregates on Parking Lot
Look at AI recommendations
Meeting Minutes
Antitrust Accepted
Meeting Minutes Accepted
Review or Array Rules that Dan proposed previously
We reviewed schemas with otherParties with a reference to party in the existing CAPIS Schemas
Modified the wording to Guidelines 60 and 61 to below decisions
Action item for Paulette to update all the guidelines from the Master page that was broken with this modification
warrantyValue will remain in CAPIS with a new ENUM of warrantyUnits
We made it to 51 aggregates in the parking lot, Mike has reviewed a few of these that we can go over in the next meeting
We will review SpecialtyVehicleDesc in the next meeting.
Up Next
Welcome
Antitrust
Meeting Minute Review
Action items
Decisions[5
Duration Type will not be used in CAPIS- Paulette Reed Update broken guidelines in the master tab for the array verbiage change.
Decisions
- Guideline 60: Arrays shall have plural names and their items shall be defined as a reference to a named property. The referenced property shall be defined separately, typically with a singular name matching the array's plural name. For arrays of enumerated types (code lists), the reference shall point to the appropriate definition in the separate code list definitions file.
- Guideline 61: Arrays may be defined inline, but frequently used ones should be defined as named types in the dictionary.
Reference
Participants
Paulette Reed
Dan Webster
Chris Martinez
Andy Bober
Mike Hastings
Jeff Schroder
Paul Barry