🔓 Public Page
CIECA 500 Westover Dr #11617; Sanford, NC 27330
Date
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 and Meeting minutes acceptance
Phone Number format examples of errors and proposed fix
Discuss Topics for How to Present and Show Documentation for Download
Get Vehicle proof of concept
Meeting Minutes
Antitrust Accepted
Meeting Minutes Accepted
Welcome New Member Rocehell
Phone Numbers 0141 248 1333 and 0208 5719414 was provided for the phone numbers in error but full XML was not available
The members did not think spaces were allowed in XML
It was recommended to add the phone number with spacing to a test instance to see if they were valid for the current XML
We will discuss phone numbers more when Dan is available to attend the meeting and after testing in a test instance.
New CIECA.com and how to present Standards
The information from GitHub is what needs to be presented
The Schema needs to be the build schema’s and needs to be in the top level folder so the users do not need to drill down
The download feature in Zoho Workdrive will allow the users to get a ZIP file of the data they want (Release, Schemas, Test Instance) so we do not need to provide a ZIP file
We do need to create a Help document to allow members to know the information and how to get it.
The CIECAST on Thursday will demo the website and how to get into the standards.
Some of the Folders in the Release folder say Copy of, we need to remove these if they are a copy or change the name.
Vehicle Lite is in Stoplight - Vin Decoded Vehicle Info Type
Descriptions from the BMS needs to be added
Documentation
We have a Style Guide and need to complete
We need to provide a document of the process that was used for the prototype
flattening the BMS Aggregates
Removing unnecessary data element
Learning Yamal and Stoplight
Tool for Bundling and how to use it json-schema-ref-parser - npm (npmjs.com)
Need to Clean up GitHub
The vehicle light is the proof of concept and Architecture Committee has completed the objective of a proof of concept and after the documentation is complete, we can turn it over to the other committees.
Will Architecture be responsible for all the Common Data Aggregates?
The Committees that use these elements can work with the Common Data Aggregates and then Architecture will approve the changeds.
Architecture started work on several Common Data Aggregates, Party Type, Admin Info, Claim Info that we can finish.
Document Info was removed
Event Info would be a good data aggregate to work on next if Architecture wants to continue with the data aggregates.
Homework
Mike and Dan and Paulette will work on getting the documentation to go over for next meeting.
Great Meeting
Up Next
Antitrust and Meeting minutes acceptance
Phone Number format examples of errors and proposed fix
Review Documentation
Participants
Paulette Reed (Scribe)