Public Page

2021-09-28 Architecture Meeting Minutes

Owned by Paulette Reed
Oct 07, 2021
3 min read

Public Page

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

 

Date

Sep 28, 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 Oct 5 11-3 CST

  • Options Code from Emerging Tech for 2020R2 Approval

  • Phone Number format examples of errors and proposed fix

  • GraphQL Demo/Bundling Concepts

  • Get Vehicle proof of concept

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Accepted

  • QA will be October 5 11-3 CST for 2021R2 Release

  • The Emerging Technology Committee removed the Codes that were duplicates of existing Codes.

    • Architecture Approved the Options Codes additions

  • Phone Number examples were not available for this meeting.

    • The CAPIS Schema is international

    • The BMS has International concept, so if it is causing issues we need to look at the number.

    • Examples will be brought to the next meeting.

  • GraphQL Discussion and Demo

    • When you have a lot of clients using data but all needing different data needs, GraphQL can help.

    • Data fetching, single API calls pulling specific data

    • Fixed Rest would need multiple calls to duplicate the same specific data as Data Fetching.

    • GraphQL is self docmented, no Swagger or Stoplight.

    • All JSON Schema

    • CIECA did a CIECAST on GraphQL, we can look through old presentations and review.

    • Does CIECA Standards look at one base standard for API or Multiple?

      • We can build multiple versions, but we have to focus on 1 for the start.

    • Why is GraphQL better for microservices?

      • REST would need different services and endpoints, GraphQL provides middleware server to get data based on client needs.

      • Middleware server is easier to manage

    • Is there Tools that take GraphQL that creates server side code?

      • Server Side Code you build schema

    • GraphQL we do not define Requst and Response. We create body of data, we do not have to generate data.

    • To Date all of EICEA standards have been based on existing standards like XML.

    • GraphQL is not a standard, it is open source tool.

    • CIECA should be providing API Standards and the tools can be recommendations.

    • CIECA would only do common Types and aggregates model and not worry about messages; members could build messages with the data standards set by CIECA.

    • GraphQL is not replacement proposal for the current JSON

    • CIECA will conclude building current API and then work on GraphQL for second version.

Great Meeting

Up Next

  • Antitrust and Meeting minutes acceptance

  • Phone Number format examples of errors and proposed fix

  • GraphQL Demo

  • Work on Data Aggregate Breakout with Bundling Concepts

 

Participants

  • Paulette Reed (Scribe)

  • Paul Barry

  • Dan Webster

  • Chrisa Hickey

  • Mike Hastings

  • Andy Bober

  • Tapas Sarangi

  • Jeff Schroder

  • Brad Broerman

  • 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