Public Page

2021-02-16 Architecture Meeting Minutes

Owned by Paulette Reed
Feb 23, 2021
3 min read

Public Page

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

 

Date

Feb 16, 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

  • Update on SmartBear/SwaggerHub

    • Any questions we have to send to them before meeting

  • Continue to work on the CAPIS.

    • GitHub Project

    • FNOL Use Case

  • Standardize Percentage definitions question (Becky)

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes approved

  • Swagger

    • Meeting was postponed with SmartBear due to electric and internet outage.

    • Did talk to Remington and it was suggested that we could have 3-5 sign on and up to 50 APIs for a monthly price. When we needed more, we could upgrade.

    • Question of can we have users in different domains is critical to our needs. It seems from the feedback, that this would not be an issue.

    • Stoplight and Insomnia are other tools that can edit Open API and JSON.

    • Swagger is a hosting tool to allow members to see and it has development tools. Stoplight and Insomnia are development tools only and do not have hosting.

    • Can we get a token to direct members from CIECA.com to Swagger?

    • Swagger will not be used to share parts or sections, it is one for all. Today we have members that purchase a single message of the BMS, that is handled through email, and not something we want to continue to support.

    • How will we manage user?

  • GITHUB

    • Mentioned that we should create another project for Open API.

    • Porotypes in GitHub

    • Name could be cieca_api_standard all in lower case just a place to store intellectual properties

    • Who can access GitHub?

  • CAPIS

    • We don’t want arbitrary levels of hierarchy in Open API

Have a great week everyone!

Up Next

  • Antitrust and Meeting minutes acceptance

  • Continue to work on the CAPIS.

    • FNOL Use Case

      • Look at ADMIN INFO and break it into the Data Types and Aggregates that we need.

    • Do we want to add a new section to the Architecture Guidelines for CAPIS guidelines or should we have a separate document?

  • Standardize Percentage definitions question (Becky)

Action Items

Decisions

 

 

Participants

  • @Paulette Reed

  • Paul Barry

  • Jeff Schroeder

  • Dan Webster

  • Andy Bober

  • 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