Public Page

2024-03-12 Architecture Meeting Minutes

Public Page

Date: Mar 12, 2024

 

 

 

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

  • Network/Welcome

  • Antitrust Statement

    • This meeting is subject to the terms of our anti-trust statement shown here.  In addition, this meeting may be recorded. 

  • Review Meeting Minutes

  • Finalize EMStoBMStoCapis

  • Look at Referfal and API

  • Discuss Array

Meeting Minutes

  • Network/Welcome

  • Antitrust Statement & Recording

    • Accepted

  • Review Meeting Minutes

    • Accepted

  • Finalize EMStoBMStoCapis

    • The document was updated to show a single value of the proposed CAPIS values.

      • Committee members agreed to continue review offline and discuss finding next week.

  • Array

    • In the evolution of BMS we developed a practice that only applies to a small subset of things where we made an aggregate that contained only 1 repeating element (array) to be replaced with CAPIS array.

    • Different than the unbound repetitions that will be an array in CAPIS.

    • Dan provided a document of the different array wrappers.

    • CAPIS array style is that arrays will be plural, and the plural name will be the name of the items in the array.

    • Single element arrays will have a plural of the contents of the name.

  • Info

    • The auto generated names that we are looking through we did not remove “Info” from aggregate names, one of the rules in CAPIS is to remove “Info” from aggregates, such as ClaimInfo in the BMS is now Claim in Capis.

  • Referral API

    • It was discussed that Referral message is already an active API with one of our members and we should accept that.

      • Due to aggregates and elements being named different from the CAPIS recommendations, it should be taken back to the Referral Committee with recommendations to change the naming to align with CAPIS.

      • We can provide them the new document and have them update the names and have the committee propose the new API that matches CAPIS naming.

  • Reviewed the process of getting to the Architecture committee documents.

    • These documents covered today will be added to the Zoho Workdrive.

  • AI API

    • The naming of AI API is more in line with CAPIS

    • coordinateInfo was changed to coordinate but the API coordinate is different than the location/GeoLocation. We need a new name for coordinate for pictures for AI.

Great Work everyone

Up Next

  • Network/Welcome

  • Antitrust

  • Review Meeting Minutes

  • Release

  • Webinar

  • Homework

Action items

Decisions

Reference

 

Participants

  • Paulette Reed

  • Dan Webster

  • Mike Hastings

  • Paul Barry

  • Andrew 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