Public Page
2022-12-13 Architecture Meeting Minutes
Public Page
Date: Dec 13, 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
Moving BMS to CAPIS Data Dictionary
Meeting Minutes
Antitrust Accepted
Meeting minutes reviewed and accepted
Mike attended a Swaggerhub webinar, and they will have support for API 3.1 first quarter 2023
They have 2 new products
Ready API that will consume an open API spec and create all the test suite
Pack Flow is a tool for developers where it will create both the client and server and test the API
It's good to have Stop light, SmartBear/Swaggerhub and Postman.
There is a tool we have not used yet, Oxygen XML that Andy uses because it is written in JAVA and its platform independents, runs on Windows and Linux and Mac.
http://json-schema.org/blog/posts/validating-openapi-and-json-schema#without-schema-validation
When working with CAPIS, there is a need for our member companies to be able to pull the CAPIS into their system.
Describe how to embed your schema and open API pack
Provide some examples
JIRAS
Need to review JIRAS
Need to create Jira for following enumeration and making sure we follow enumeration have test instances to validate
Parts properties vs arrays
Mike showed two versions of his parts code. On one side he had the properties named and on the other he had array for those properties.
The array is flexible, but thy really not that many prices we run into an estimate, so the flatten with properties seems to work well.
Making changes that Break Previous release
At this time, we should make sure everyone is aware that CAPIS is at an alpha release, there is no concept of backward compatibility until we do a full release.
Problem with current release structure/build
JASON schemas folder that had child folders for schemas and definitions and then the schemas folder made references to the definitions and the definitions folder as dot dot back slash definitions back slash name of resource file.
When we put out the release, the JASON schema folder and it has schemas, bundles, definitions and the schemas, so with the new folder structure, the definitions reference does not work.
Building up our support page
We want to direct members to go to the support page and ask questions about implementation of CIECA Standards.
For example, above when Dan was talking about how to pull the CAPIS standards into his company coding tools, this would be great to share with everyone and we can have examples of how to with the different tools we are using.
However, I don’t want to be the only author of the questions, so when the each of you run into issues or think there is a great point, if you can add it to the Support Help page, we can build a good repository.
This is our Last Meeting of the Year! Have a happy and safe Holiday Season. Merry Christmas and Happy New Year.
Up Next
Network/Welcome
Antitrust
Review Meeting Minutes
Review JIRAS
Action items
Decisions
Participants
Paulette Reed
Paul Barry
Andy Bober
Mike Hastings
Dan Webster
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