Public Page

2021-04-20 Architecture Meeting Minutes

Public Page

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

 

Date

Apr 20, 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

  • How do we want Phone Number (Formatted, straight numeric, multiple formats for number vs international, just international)

  • Finalize and vote on SimpleTypes; we would like everyone to attend to make verify the guidelines being established

  • Review and vote on Style Guide

  • Versioning of CIECA API

Meeting Minutes

  • Antitrust Agreed

  • Meeting minutes were updated and approved

  • Phone Number

    • Mike removed the US phone number and we only have the International Phone Number pattern in the schema now

    • Phone number extension is not part of the International phone number, however, it is a value that has use in the BMS and has recently been updated to be longer in length.

      • Team thinks it will be best to have Phone Number extension as its own property.

  • Review of schema work since last meeting:

    • Year and Year Month was changed to be its own pattern.

      • We can make Month smarter in the future; so values above 12 can not be added.

  • Common Global Types

    • Resources or components

      • To be defined as JSON; the Common Global Types will be components

  • String

    • We have went back and forth on just going with String or going with String with a min and max; its suggested to look at the Char# values to see which ones are used numerous times and a few times.

    • We have values in the BMS, such as city and address that are defined differently in different sections. We need to make sure we standardize these values moving forward.

  • Definition Schemas Vs Full Schema

    • If we only have a schema with definition; there is no way to test those definitions without including them in other messages. If we had full version; we could test all patterns with the definitions.

    • 3.1 allows the concepts that we want, but SwaggerHub and other tools are not available for 3.1 at this time;

      • Do we wait on the tools to be ready or do we move forward with 3.1

        • We looked at Json-schema.org to look at the versioning and what is available for the different versions. Please review this site to help move the conversation forward in our next meeting.

        • AJV is a Json validator built into the Git Hub build pipeline. We can use this to do automated testing for the latest version of JSON 2020-12.

        • We can use other tools besides swaggerHub if we want to move forward with 3.1. We will pick up here next week on the discussion of using 3.1 to get a consensus on the what version to use.

  • Please send Paulette your GitHub user name; if you already have a GitHub user so you can be invited to join GitHub. If you do not have a GitHub account, we will use your email to invite you.

Good Meeting! Please review the Json-schema.org website documentation to help determine if we should use OpenAPI Spec 3.1 or a previous version.

 

Up Next

  • Antitrust and Meeting minutes acceptance

  • Discuss JSON 3.1 vs previous versions for CIECA APIs

  • Finalize and vote on SimpleTypes; we would like everyone to attend to make verify the guidelines being established

  • Review and vote on Style Guide

  • Versioning of CIECA API

 

 

Participants

  • Paulette Reed

  • Dan Webster

  • Mike Hastings

  • Brad Broerman

  • Aaron Daniele

  • Mike Hastings

  • 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. Architecture Committee