Public Page

2021-05-18 Architecture Meeting Minutes

Owned by Paulette Reed
Last updated: Jul 13, 2021
3 min read

Public Page

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

 

Date

May 18, 2021

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

  • Review Style Guide Recommendations

    • Do we use Additional Properties set to True/False/Both?

    • Make sure the Property Value Guidelines are in Sync with the new version of JSON

  • Review and work on the capisCommonPropertyTypesSchema.json to identify the property types we want to define.

  • Versioning CIECA API

Meeting Minutes

  • Antitrust Accpeted

  • Meeting Minutes Accepted

    • With change to AJV where meeting minutes had AGB

  • JSON Style Guide was accepted

    • We moved the section for JSON Guidelines to a different page to be reviewed later.

  • capisCommonPropertyTypesSchema.json was reviewed after Mike made changes and it is very slim.

    • The questions is can we remove Decimal and currency since they are both defined as number.

      • Decimal was decided that it could be removed

      • Currency, Mike wants to do some more analysis to determine if we need currency.

        • New currency definitions may allow 4 positions after the decimal?

    • This is a great start, and it may change as the project evolves. When the BMS was done, there was many evolutions and it took a lot of time. We just want to make sure that we do not get as complex as we did with BMS.

    • The 20-12 version added Double and Float, so the common types allowed are Double, Float and Integer.

  • Criteria for Common Property

    • It must be used more than once.

    • The example is Vehicle Model is used once, because it is used within Vehicle

    • Property such as Name or Company Name would be examples of a property that is used more than once, and we would want to add it to common if we were changing the value to have a length of 50, because we would want all Company name Property to have the same length of 50.

  • When we design we need to think about how someone will download the APIs. Most people download the piece that they will be working on, such as FNOL or Estimate, but not All of the CIECA BMS, so when we design, we need to think that if they just want FNOL, how to make that download simpler.

  • FNOL Kickoff

    • We looked at the GitHub XML test instances to see what is needed for FNOL. We were going to take the smaller message and start, however, all the test instances have 425 lines of code.

    • The BMS Tool that converts the XML to JSON can be used. Andy will prepare a quick demo for the next meeting on the BMS Conversion tool.

    • Mike and Dan both have FNOL JSON messages, they will add these into GitHub and validate the JSON style guide that was approved is followed.

    • We can compare the versions of the messages and kick off the next meeting with reviewing FNOL.

Great Job everyone.

Up Next

  • Antitrust and Meeting minutes acceptance

  • BMS Tool Conversion Demo

  • Work on FNOL JSON messages

  • Versioning CIECA API

 

  1. Criteria for Common Property , must be used more than once

Participants

  • Paulette Reed (Scribe)

  • Paul Barry

  • Brad Broerman

  • Chrisa Hickey

  • Dan Webster

  • Mike Hastings

  • Jeff Schroeder

  • Aaron Daniele

 

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. https://cieca.atlassian.net/wiki/spaces/ARCH