Public Page

2021-10-12 Architecture Meeting Minutes

Owned by Paulette Reed
Oct 18, 2021
3 min read

Public Page

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

 

Date

Oct 12, 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

  • 2021R2 QA was completed

  • Phone Number format examples of errors and proposed fix

  • Get Vehicle proof of concept

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Accepted

  • 2021R2 QA was completed and the Release is scheduled for October 20, 2021

  • Check Teams Settings to allow everyone to Enter Meeting Automatically so they do not have to wait in Lobby.

  • Andy Got a few examples for the phone numbers erroring, but has not had time to review them and would like to discuss at next meeting

  • Recap of Where we are at with Open API

    • We are still prioritizing Open API

      • Bundling Vs GraphQL

        • The Bundling Concept seems to work the best for what we need to do first and then GraphQL can follow

      • Vehicle has already been built with the Bundling Concept

        • Vehicle was flattened and then access baggage was removed manually

    • Dan’s idea is to make references to anonymous list of properties

      • Bundling is a list of properties without the hierarchy

      • It was recommended to use Named list and more away from anonymous list

    • Vehicle Vs Vehicle Lite

      • The Vehicle lite version will have less data

      • smaller and lighter Vehicle is the better for open APIs

    • We need to Focus on the JSON Style Guide

      • How are we going to document and what are we going to provide? Are we going to have schemas, definitions and examples like we do with BMS?

      • It was recommended that we focus on the Data and not worry about the messages because membership will be able to use the definitions and make the data for the messages they need.

      • It was agreed that the most important item to focus on was the data and not worry about the messages.

      • CIECA will provide the Building blocks and let partners build the messages, using the CIECA data standards will make the partners compliant.

      • Aggregates will be going away

      • Would like the Architecture Committee to provide examples and recommendations for Bundling.

        • We would like to have a work meeting to go over these concepts, Thursday at 2pm CST.

Great Meeting

Up Next

  • 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

 

Participants

  • Paulette Reed (Scribe)

  • Chrisa Hickey

  • Dan Webster

  • Andy Bober

  • Paul Barry

  • Jeff Schroder

  • Chris Poulos

  • Mike Hastings

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