Versions Compared
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
Antitrust
Committee Welcome
Meeting Minutes Review
Next Weeks Meeting
Proposal from Members starting JSON messaging
Review proposals of Option Types for Vehicle, Engine and Transmission
how to handle arrays and validation of different values in arrays
Review analysis on valuation fields.
Meeting Minutes
Antitrust Accepted
Welcome
Meeting Minutes Accepted
Arrays Flattening
Code list needing to be broken up and fields for better validation.
Proposal for new members starting JSON before Architecture is complete
Allow members to work on JSON Open API’s and bring back to committee(s) and architecture for review.
Dan will work on a document to share when these request are made.
Tags and data definitions with XML
Hybrid - Use CIECA XML to transport to JSON
Documents Needed for new generation of code
Wordlist, tag list, JSON Style guide
Simplified Schema
Common Code List
Discussed CIECA BMS Color
OEM Color code
Vendor Color Code
Custom
Array for Powertrain
We will have an array of Powertrain that will have an engine and transmission.
Do we need a code list to go with Engine and Transmission instead of option?
Examples of CIECA Vehicle Options and Manufacture or Other Source Option Codes
Mike showed examples of ciecaVehicleOptions Array that has the Option Code and Option Description that would use the current CIECA Options Code list and compared that to a manufacturereVehicleOptions code that has an Option Code, Option Description and an Option Code Type.
Dan reviewed the BMS Color aggregate
Discussed CIECA BMS Color and all aggregates are optional
OEM Color code
Vendor Color Code
Custom Color Code
ARA Color Code, that should be ARA but just named ColorCode
looked at CIECA BMS Options
option has optionCode
Option Description
Then we have a little brother that has DetailVehicleOptions (Not in current BMS)
Detailed Option Description
Detailed ID
Detailed Category
or we can have a new array called detailedVehicleOptions
DetaledOptionSource
detailedOptionId
DetailedOptionSelectedOrder
detailedOptionDesc
👥 Great Meeting Everyone
Up Next
Antitrust
Committee Welcome
Meeting Minutes Review
Action items
- We will have Powertrain array that will have Engine and Transmission and Configuration.
- Transmission Option and Engine Option code will break up Options Master Code list to have one for Engine Option, one for Transmission Option and one for everything else. Transmission and Engine will follow the engine option array and detailedEngineoption array.
- Vehicle Option will have a ciecaVehicleOptions and a detailedVehicleOptions that has new fields detailedOptionSource, DetailedOptionId, detailedOptionCategory, detailedOptionSelectedOrder, detailedOptionDesc.
Participants
Paulette Reed
Dan Webster
Mike Hastings
Jeff Schroder
Jeff Mueller
Paul Barry
Brad Broerman