2021-10-26 Architecture Meeting Minutes

   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Oct 26, 2021

Agenda

• Antitrust and Meeting minutes acceptance

• Meeting Cancelled for Next week for CIC/SEMA

• Congrats Dan - CIECA Chairperson’s Award for Outstanding Leadership in 2021

• Phone Number format examples of errors and proposed fix

• Review documentation of Proof of Concept

Meeting Minutes

• Antitrust Agreed

• Meeting Minutes Accepted

• Meeting is cancelled next week for CIC/SEMA

  • Congratulations to Dan Webster for being selected CIECA’s Chairperson Award for Outstanding Leadership in 2021

• Phone Number with blank spaces was the issue in the phone number examples provided by Andy.

  • Andy experienced Microsoft Teams issues and was not able to join the call.

  • It seems that the spaces are common for International phone numbers, but we will sideline the conversation of changing the BMS or Open API format until Andy can join and add more information.

    • International phone numbers have dots and dashes in the phone # as well as blanks

    • Google Phone API uses just digits and google determines how to display the format

    • Schema has Regex pattern and the API has International phone format

    • Its proposed to change the BMS format to more common

      • Is current BMS pattern Valid for International phone numbers?

    • Proposed the use of International Phone number format E.164

    • Simple pattern may be removing the pattern and allowing 1-15 characters.

• JSON API Guidelines states no Comments but we have description now

  • comments are different than Descriptions, the Descriptions from the BMS is okay in the Open API Schemas.

• The Documentation sample needs to have illustrative examples instead of just ‘string’ and ‘number’

  • Question was raised what is Manufacturer under Vehicle. Manufacturer was a new data element added to Vehicle.

• The Vehicle we are looking at now, should it be viewed as a subset of a lite version

  • At this time it is lite version

  • Other elements need to be added to it for full messages, for example an assignment will also need license info

• Concern that Vehicle is a Leap and not a true proof of concept

  • The VIN Decoder is a Vehicle and not a VIN Decoder, it was named that and we recommended changing it in the past. The example is vehicle lite, which is the physical vehicle attributes. The Vehicle workflow data would need to be added to complete a message that needed more than just vehicle.

  • What is the Proof of Concept we want to share

    • New standard will replace some messages

    • We can have new messages that are not related to BMS messages

  • Would renaming to Vehicle Information Request or Response be better?

    • VIN for Build sheet Data

    • VIN for Policy

    • VIN for mileage

• The Committee went over in length by 5 min and members had to drop due to other meetings, we will pick up with the documentation in our next meeting.

Members have experience crazy weather the past week, everyone stay safe and those going to CIC/SEMA; see you next week.

Up Next

• Antitrust and Meeting minutes acceptance

• Phone number review and propose a solution

• Review Documentation and provide feedback

• Decide what’s next, Dan worked on a number of Data aggregates, think we should finish them.

Participants

• Paulette Reed (Scribe)

• Paul Barry

• Dan Webster

• Mike Hastings

• Chrisa Hickey

• Tapas Sarangi

• Phil Martinez

• 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. https://cieca.atlassian.net/wiki/spaces/ARCH