2021-09-21 Architecture Meeting Minutes

   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Sep 21, 2021

Agenda

• Antitrust and Meeting minutes acceptance

• Review Options Code from Emerging Tech for 2020R2 Approval

• Phone Number format is US and more companies are needing International phone number for XML

• Continue to discuss Bundling after everyone can review.

• Get Vehicle proof of concept

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Accepted

• Welcomed Tapas to the Architecture Committee

• A Doodle Poll was created to find the best time for QA, please fill that out ASAP.

• Reviewed Master Code List additions to Options Tab

  • All of the Codes that were not duplicates of older codes were approved.

  • All duplicates, such as APA, we will remove and leave the Code and description in the original category.

  • The question of do we need Blind Spot Monitor and Blind Spot Warning, will be taken back to the Emerging Technologies committee.

  • The question was brought up if we validated the codes being added did not duplicate existing codes.

    • Yes, Paulette did verify the new codes were unique.

    • It would be nice if the build process or QA process had a test to verify there were no duplicates. Andy accepted this challenge.

• Phone Number to be International

  • The proposal to make the BMS Phone Number international in format was proposed by Entegral.

  • The BMS format was reviewed and it was intended to be international format, however both EHI and Mitchell have experienced phone number validation errors with this format.

  • Newer developers would rather use Google to send numbers and it execute the formatting and validation.

  • Andy is going to review the errors for phone number that they have seen and come back with a proposal for the fix.

  • Also JSON phone number format will be international.

• Bundling

  • For a few weeks the committee has been discussing bundling concept.

  • Due to more member participation this week, Dan gave an overview of what work has been going on with the committee and the proposed approaches.

    • The Committee started with simple types and common aggregates for FNOL.

    • These aggerates were simplified by removing the hierarchy of elements to the upper level.

    • This still left the data aggregates very large and complex.

    • Fields were then removed that the committee did not see as being value added or needed with new implementations.

    • The JSON structuring for complex schema was still causing issues, therefore the bundling tool was looked at.

    • Bundling tool will go to the source schema in an external reference and pull back the fields needed and not the entire schema.

    • The two ways to pull in common data aggregates:

      • $id brings in the entire schema

      • The bundling tool will bring back only the necessary fields

    • At this time, Mike has been doing the bundler manually and would like a tool to automate this process.

    • Bundling Tool Documentation is at Structuring a complex schema — Understanding JSON Schema 2020-12 documentation (json-schema.org)

  • Team will review bundling and discuss more next week, but at this time, bundling is the process the Architecture Committee is recommending.

• Vehicle Info

  • Mike had some homework to add transmission back into Vehicle and we reviewed that.

  • We need to get Tapas access to Git/Stoplight and Slack

  • Do we go back to hierarchy in data aggregates, build subsets of data and reference them with the bundling tool or create different versions of common aggregates (VehicleInfo, VehicleLite)?

    • Committee wants one version of the truth, we do not want different Vehicle objects

    • We hope to not copy and only pull necessary data.

  • GraphQl will allow a model to be defined then quieris are done to get the data for the messages the customer/user wants.

    • Tapas will do a demo of GraphQl at the next meeting.

Great Meeting

Up Next

• Antitrust and Meeting minutes acceptance

• Review Options Code from Emerging Tech for 2020R2 Approval

• Phone Number format examples of errors and proposed fix

• GraphQL Demo

Participants

• Paulette Reed (Scribe)

• Paul Barry

• Andy Bober

• Tapas Sarangi

• Dan Webster

• Mike Hastings

• Phil Martinez

• Chris Poulos

• 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