2022-06-21 Architecture Meeting Minutes

🔓 Public Page

Agenda

• Antitrust

• Committee Welcome

• Meeting Minutes Review

• Discuss Face to Face Meeting Poll results and Next steps

• Review New API Guidelines and Help page for cieca.com

  • This has the email that Dan provided in the last meeting, so it can be reviewed/approved

• Meeting for CIECA Product Committees to review Vehicle is scheduled for June 29

• Review vehicle examples for detailedVehicleOptions to confirm new fields work for other business segments

• Review Excel for Vehicle to show the differences from the last review to be in sync with new schema presented at last meeting

• Review Excel for Party

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Review and Accepted

• Architecture Committee Face to Face Meeting

  • Reviewed the Feedback from the Survey that was sent out.

    • Chrisa is not available due to projects until later in August. Committee decided that they wanted to get together in July so we had more time before CONNEX to get things into the build and ready for QA.

      • 2 Day Session

      • July 12 and 13

    • We had one possible host and one confirmed host from the survey.

      • Entegrel, out of Wisconsion has hosted in the past but hosting for this session was not confirmed.

      • Car-Part.com, out of Kentucky offered to host and it was decided to help move the process forward to get travel arrangements that we would have the Face-to-Face in Kentucky.

        • Address: 1980 highland Pike, Fort Wright, KY, 41017

        • Best Airport: Cincinnati/Northern Kentucky Int’l Airport (CVG)

        • Hotel: Holiday Inn Cincinnati Airport, 1717 Airport Exchange Blvd., Erlanger, KY 41018, (859) 371-2233

          • $119/night last room availability (includes breakfast)

          • When making reservations via phone request the Car-Part.com rate.

    • We want to draw people to technical sessions so we want them to know the meetings are fun.

      • Take pictures to show the business side, but also have fun things to do as a group that can shared to draw interest.

        • Possible things to do would be ballgame if Cincinnati Reds are in town, Distillery or Brewery tours, Ax throwing and go carts.

• New cieca.com page review of API Development Recommendations

  • Remove the mention of this being a draft page

  • Mention we are using version 3.1 of JSON

  • Question about the “Maximize JSON Schema's features that allow extensibility, in particular set the additionalProperties property to true and don't use required enumerations for version numbers.” section under the JSON Schema Guidelines.

    • This was to allow the additional properties to be set to true to allow for expandability by adding values to the schemas without causing errors.

    • If you have required property, you would increment the numeration to insure if someone is using an older version that it would cause an error and they could not publish, however, this would go against our concept of extendibility.

    • We do not want to validate version number.

  • In the email section add on bullet that discusses bringing your work to CIECA to start the process of review, we want to mention it as the committees can make recommendations and assist, instead of mentioning that we will publish because this may allow those unfamiliar with our process to think we will publish their work as Standards.

• Publishing CAPIS Standards

  • We want to get a version published ASAP to help everyone with development concepts.

    • Vehicle has been completed; the meeting will be June 29 with all of the committees that are interested in VehincleInfo.

      • We will have our Excel documents to show how Vehicle Info looks in the BMS and how Vehicle looks in JSON

        • This will show flattening concept

        • This will show the removal of unnecessary objects/fields for backward compatibility

        • This will show new fields that have been identified during this work.

      • Committee’s will make recommendations and approve, then Architecture can publish

        • How do we want to publish? We agreed in the past that we did not want implementation guides and Word documents as we have today with the BMS.

        • Commenting in the Open API would be recommended reference for the implementation.

        • First version would be 0.1

• Reviewed Car-Part.com instances using detailedVehicleOptions

  • The examples showed that the concept of detailedVehicleOptions works to share the data.

    • The selected order can be used to show order in a drop down list or it can be used to show importance. If you want to use it to show order or importance, you would use the numeric system of 1,2,3. If you have no order or importance, you can not populate the field because it is optional, or you can use the same number 1, 1, 1.

• Reminder that in the last meeting we decided to break out Engine Options and Transmission Options from the Options list

  • Do we make this change to the BMS Code List? Unanimous decision of No, we leave the BMS code list alone.

• Reviewed the changes that was made since the last review of Vehicle in Excel

  • This showed the most recent deletions and added fields

  • Purple was used on fields that were moved in the Excel document to show they were moved. This does not impact the schema because it does not have to be in an order.

    • The purple was reference for this review only and will be removed.

  • It may be nice to have purple in Column C to help show how the BMS objects were flattened.

• We will start with Party next week, Paulette will share all documentation for Party so everyone can prepare questions and/or concerns.

  • Excel document from Dan and Myself for CAPIS flattening and usage of the BMS and Party Example;

💻 Thanks everyone, Remember Phil will be out next week, so if you have any work you would like to assign him, please let me know.

Action items

Decisions

• BMS Code List for Options will not be changed to match the CAPIS