Public Page

2022-11-15 Architecture Meeting Minutes

Owned by Paulette Reed
Dec 06, 2022
3 min read

Public Page

Date: Nov 15, 2022

 

 

 

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

  • Review Meeting Minutes

  • CAPIS Like Proposal feedback

  • Feedback of Restful services

  • Work on moving the rest of BMS Data Dictionary to JSON Schema Data Dictionary

  • Work on Parts and Procurement Services.

Meeting Minutes

  • Network

    • Andy received his award in the mail, and everyone congratulated him.

  • Antitrust Accepted

    • It was discussed in the Executive Committee meeting that in regular meetings where everyone normally attends, that we would display the antitrust on the screen and ask everyone if they agree.

  • Meeting minutes reviewed from old version and accepted

    • There was mention in the meeting notes about membership and making the intellectual property private. This was not decided to do or how, just that we need to analyze and see what can be done.

  • Holiday Schedule

    • With all the great work and the additional hours that everyone put in and the holidays, it has been decided that the next 2 weeks of Architecture meetings will be cancelled.

  • Additional Properties for the Schemas

    • If additional properties is true, basically your schema would be whatever you defined it as plus anything else you wanted to put in there, and it would simplify the job of folks who are trying to implement API contracts with trading partners.

    • The complications from additional properties being true, your test will not error because and makes testing more difficult.

    • It breaks all the rules we had in BMS XML for years.

    • Additional properties being set to false in more in line with CIECA standards.

    • BMS has Custom Fields, which is set up as an array of fields they can add without breaking the BMS.

      • Arrays and properties versus name value pairs like the ID Info.

      • Its better to have User ID and Office ID and make changes to the Schema than to add things to custom fields.

      • Its better to add the properties where the property applies.

        • employee Id, estimate ID, company ID, account number are all primary keys in the database.

    • Should we version our Schemas?

      • Versioning the schemas and versioning the APIs.

      • API REST versioned by different endpoints, the path of the endpoints will have v1 or v2. This would allow a user to use the old code by using v1 endpoints and the new v2 endpoints would not have to be backward compatible.

      • Mike will try to find some examples of the different endpoints being used for versioning.

      • `Should we be backward compatible?

Up Next

  • Network/Welcome

  • Antitrust

  • Review Meeting Minutes

  • Moving BMS to CAPIS Data Dictionary

Action items

Decisions

 

Participants

  • Paulette Reed

  • Dan Webster

  • Paul Barry

  • Jeff Schroder

  • Alan Hemmi

  • Andy Bober

  • Phil Martinez

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