Versions Compared

Old Version 3

changes.mady.by.user Paulette Reed

Saved on

compared with

New Version Current

changes.mady.by.user Paulette Reed

Saved on

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 and Meeting minutes acceptance

  • GitHub Conflicts

  • GitHub and Stoplight sync issues

  • Working on Proof of Concept

    • Work on Dan’s Document and document example

    • Work through more flattening

      • AdminInfo

      • ClaimInfo

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Accepted

  • GitHub and Stoplight sync issue ended up being a non-issue. Mike did a quick demo of Stoplight to show where the confusion of a sync issue was occurring. The branch in the edit was going back to the Main branch, making it appear that updates and changes made to GitHub outside of Stoplight was not making it. Mike showed the Committee how to change the branch to see the changes to that GitHub branch.

  • We reviewed the Excel document that showed the JSON and BMS Aggregates for Vehicle

    • a column was added to show if the Aggregates were used outside of Vehicle. Vehicle Description is one aggregate that is used outside of Vehicle Info in the BMS. The discussion now is to prove how bundling will allow you to only use Vehicle Description or do we need to have vehicle description as its own schema?

  • Reviewed the JSON Style guide

    Removed Name Objects

    • root object (AKA CIECA Message Name) doesn’t have a name it just starts with properties

    • when you have array, it should be plural

    • naming has to be better on object and property to allow us to know what to use in the messages/services

    • Testing and Debug

    • each endpoint will have a different schema

    • add to property resource name to Json guidelines

  • GitHub/Stoplight

    • JSON Schema folder system, Stoplight uses Modules

    • Modules Models has the breakdown JSON parent that references all needed schemas with bundling.

  • Homework

    • Mike is going to work on Making Column A of the Excel spreadsheet by using the last Aggregate in Column C

    • Dan will show his work with including and excluding aggregates by using bundling.

Great Meeting! Documentation is found in Confluence page Work Documents .

Up Next

  • Antitrust and Meeting minutes acceptance

  • Review work done by members

  • Working through more examples of Flattening and the hierarchy

    • Excel Document has been updated with AdminInfo and ClaimInfo BMS information

Participants

  • Paulette Reed (Scribe)

  • Paul Barry

  • Mike Hastings

  • Dan Webster

  • Andy Bober

  • Jeff Schroder

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