2021-11-30 Architecture Meeting Minutes

   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Nov 30, 2021

Agenda

• Antitrust and Meeting minutes acceptance

• Review Vehicle bundle concepts

Meeting Minutes

• Antitrust Accepted

• Meeting Accepted

• Mike reported an issue to Stoplight and he did receive support with the Required Fields issue. It is not resolved at this time, but he is in communication.

• Recap of last week:

  • The process to achieve the proof of concept was covered in the last meeting and the meeting minutes captured it well. In short, we took the BMS and converted it to JSON, then created the JSON Style Guide and used that to name the fields and create the initial schema, then we flattened the schema by removing the hierarchy of the data aggregates, then we removed some fields that were not seen as needed to make the vehiclelite object smaller, then we used the bundling concept to bring in Simple Types and Custom Fields.

• Next Steps

  • We need to provide examples of how we can use bundling to achieve a VehicleLite, VehicleMed, VehicleLg and not have numerous Vehicle Files that will cause confusion in standards.

  • The Schema of Vehicle does not have bundling; the reference is in YAMAL and Open API (BMS Message).

  • We need to continue having Instance Files that test/validate the schemas.

    • Mike will add instances to Stoplight

  • We need to add the reference documentation to Stoplight, for example the javascript that does the bundling.

    • We want the best and easiest information in Stoplight that will help developers understand the CIECA API standards and how to use them.

    • We have information for QA, such as spell-checking documentation that does not need to be part of the standards and will remain in Architecture.

  • GitHub and Stoplight are synced, so do we want to allow users to access in GitHub or Stoplight?

    • The Schema Examples for API is embedded in Stoplight and the clean presentation.

  • Model Year; Why is it a String instead of an Integer?

    • Original BMS Year was an Integer

    • In researching JSON standards the new USO standard has it a string that works well with Timezone and allows the developer not to have to convert year to get a timezone.

    • The W3C standard is also using date with a timezone

    • How often will date be used with a timezone? Is it necessary?

    • Dan is going to do more research on Year and timezone to provide to the committee.

  • One of the properties removed from Vehicle was Odometer, for an example in coming presentations, we will present how to include Odometer with No Named object.

  • Andy is going to present on Automation next week and the committee is excited to see this presentation.

• Vehicle Present and Review Proof of concept

  • We need examples that are clear with instances that validate the proof of concept.

  • Add Repair Facility may be a good example of a simple API?

  • We need examples of all the JSON Verbs (Post, Get, Delete)

  • We have vehicleLite, now we need to prove how we can build it back up with.

Great Meeting

Up Next

• Antitrust and Meeting minutes acceptance

• Andy presentation on Automation

• Vehicle Proof of Concept building back up to Vehicle Large

Participants

• Paulette Reed (Scribe)

• Pete Sheehan

• Dan Webster

• Mike Hastings

• Jeff Schroder

• Phil Martinez

• Paul Barry

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