Public Page
2021-11-23 Architecture Meeting Minutes
Public Page
CIECA 500 Westover Dr #11617; Sanford, NC 27330
Date
Nov 23, 2021
ANTITRUST STATEMENT
As participants in this meeting, we need to be mindful of the constraints of antitrust laws. There shall be no discussions of agreements or concerted actions that may restrain competition. This prohibition includes the exchange of information concerning individual prices, rates, coverages, market practices, claims settlement practices, or any other competitive aspect of an individual company’s operation. Each participant is obligated to speak up immediately for the purpose of preventing any discussion falling outside these bounds.
Agenda
Antitrust and Meeting minutes acceptance
CIECA User Forum on http://cieca.com
Review Vehicle Concept for bundling (Invisible Container for Children) Use Cases
Meeting Minutes
Antitrust Accepted
Meeting Accepted
A brief review of last weeks meeting to walk through the process and the proof of concept proposal
A few weeks back, the concern was made about VIN Decoder being used as a proof of concept. The VIN Decoder was used because it only has one object, Vehicle, and was a concept everyone was familiar with. The VIN Decoder is the message that proves the object Vehicle will work.
Vehicle was taken from its original BMS version and the new JSON Style Guide of using camel case was applied and then the data aggregates were flattened.
The original Vehicle still had 1000s of data elements, then to simplify a Vehicle Lite was proposed. This was removing aggregates that were not needed in a VIN Decode Vehicle and then adding some fields. The removal and addition of fields would have to go through committee review before it became a standard. However, the Vehicle Lite was a good tool to prove a Vehicle and the JSON Style Guide and process was valid.
CIECA User Forum
Under the Standards section of the new http://cieca.com page, we would like to add a forum that helps people reach out with questions or best practices for implementation of CIECA standards. We think this Committee would be the best individuals to have on the forum and to help provide content. We ask everyone to review the page and think about ideas to make this work.
Reviewed the proposed concept page
It was proposed that since the CIECA Standards are for Members, that we should secure this page so only members had access. It would be possible for individuals to share sections of code/standards in the forum and we want to protect the Intellectual property.
It was proposed that we have a Security Clause added to not share your companies Intellectual property.
Review Concepts of Bundling
Dan and Mike had been working through Slack but the concepts for vehicle was not completed. Dan displayed the concept in simpler form of an Individual and a Team and how the object would reference both and the children of Individual and Team would appear, but the parent did not.
It was recommended if we did not show the Parent, that the naming of the fields would have to be more specific than first name and be player first name.
XMLSpy was used for the example
The Committee Members would like to see the object named, this brought back flashbacks to when people would write code as part of an interview
Define object at top that will use the $ref
Units of Measure is needed with engine displacement. Unit of Measure is a Global Common Type in the BMS and is used in Vehicle; so it was renamed to be specific to the engine displacement.
We want to take benefit of BMS definitions and be able to include the parts needed with different collections in the JSON schemas.
Andy will be ready in 2 weeks to present automation, need to get that on the agenda for 2 weeks.
Paulette needs to add Pete to Slack, GitHub and Stoplight.
Have a Safe and Happy Thanksgiving
Up Next
Antitrust and Meeting minutes acceptance
Review Vehicle bundle concepts
Andy presentation on Automation (2 weeks)
Participants
Paulette Reed (Scribe)
Paul Barry
Dan Webster
Andy Bober
Chrisa Hickey
Pete Sheehan
Jeff Schroeder
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