2023-07-18 Architecture Meeting Minutes

Public Page

Date: Jul 18, 2023

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

• CONNEX

• Referral API Demo

• Pros and Cons of Bundling

• Release numbering. Semantic Versioning 2.0.0

• Review Mikes Changes

Meeting Minutes

• Antitrust Accepted

• Dan skipped out on us to have a vacation.

• Meeting Minutes Reviewed Accepted

• CONNEX

  • Andy will not be able to attend CONNEX

  • There is not a separate technical track at CONNEX, we have too many technical folks that are also business that have to pick which presentations they want to attend if we have different tracks. Therefore, we do have technical presentations sprinkled into the normal line up, just not a specific technical track.

  • The theme is connected car and the connected cities. We are having a speaker from a city in Georgia that is set up as a connected city and going to do a presentation on how that works, we have a few speakers talking about connectivity within the vehicles and the EV.

  • The Technical presentation is going to be a panel discussion where we have questions, and a panel can discuss the topics to answer.

• Referral API Demo

  • EHI is working with the Referral Committee to create a new API and they did a demo last week of the work. I wanted to share this with the Architecture team to show our committee an example of a CIECA Member using API.

    • EHI is developing schemas and endpoints using JSON.

    • In the Referral message there was other objects such as Renter.

      • The naming convention of the properties and objects looks similar to CIECA.

      • The example shows they are not using BMS.

      • The JSON was very flattened.

    • Paul like the clean design of the webpage and thought we could use a similar approach to CIECA.

      • Mike noticed they were using a couple different tools to present the endpoint services.

        • Swagger

        • Postman

        • Proprietary Enterprise

• Pros and Cons of Bundling

  • There is definitely value in bundling, but it would be good not to focus on the bundling until the schemas are complete.

• Release Numbering

  • Is everyone okay with the next release being 0.1.0 and following the semantic versioning pattern?

    • Yes everyone is good with this numbering pattern for the releases.

• Mike Demo changes.

  • GitHub branches

    • We can delete the CAPIS release one that had no work

    • We want to keep the Hyperjump branch because it has a lot of work and concepts.

  • Decided to wait until Dan was back to go over the changes for review.

    • To show the differences, GitHub has a tool, but Mike has been using IntelliJ from a company out of Russia.

      • Tool has plugins for Microsoft and Visual Studio

  • Mike has a clean build and test instances working.

    • The sync to stoplight is good.

    • we would like to see if we can get our code to work with Swagger now that they have updated to support the most recent version of JSON Schema and Open API.

• Next Steps

  • Fix the Release order of the folders

  • Working on the order of objects in the BA Data Dictionary

• Open API 3.1

  • Open API 3.1 you know and there was a question about did we jump the gun or are we trying to push the edge you know too much did you guys continue talking about that last week or are we just kind of good with where we are and we're going to move forward or because it's still an open top?

    • We did discuss and we all like the idea that you brought up of having different versions because we're not using any fancy features of 3.1 specifically. It should be relatively easily because what we're doing is kind of simple, but we didn't want to really have that conversation or sort of make any decisions without Andy being part of the conversation. But yes, we all like the idea of being able to potentially produce multiple versions just as a service to the CIECA members, but we didn't really want to do a whole lot without you because we felt like you're pretty much expert.

    • Andy is glad everyone's still open t, looking at that and he did verify that there's a really nice Open-source package that does convert from the different versions between the different versions.

    • Hopefully Andy will have something that I can present, if not next week, maybe the following week.

  • There's data types that they added in the 202012 schema release that supports new formats and we're using some of those formats.

    • We may want to be able to target different schema releases because kind of what we're finding is the tools.

    • It's hard to find a tool that supports the 202012 all the schema Features.

      • Java to POJO has worked in the past.

    • Maybe the things we can do to in the build to provide better support for the tools, you know, based on the schema versions.

Great Work everyone, we wrapped up 11 min early because Dan was not in attendance

Up Next

• Network/Welcome

• Antitrust

• Review Meeting Minutes

• Review Work Changes

Action items

Decisions

Reference

Participants

• Paulette Reed

• Mike Hastings

• Andy Bober

• Paul Barry

• 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