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
Work Session
Meeting Minutes
Antitrust Accepted
Meeting Minutes Accepted
Working Session
Reviewed JSON Style guide
JSON should not have extraneous layers of hierarchy
Distinguish Bundling from Reference and shared resources
Bundling is to be able to have similar file structure that we had with the BMS with referenceable and usable objects
BMS was costly and large and hard to use. When trying to use in the JSON we would get warnings about these references are not used.
The Tools caused the warning, not the Open API
Bundling we can reference only the objects we need and will use.
Different Concepts
getting rid of things, we don’t need, things that we are never going to use. Obsolete and will Never be used.
Second effort, hypothetical, Vin Decode is there is a subset being used and we know there are more. How will we have others for same elements with different subsets for the same thing (Vehicle, Vehicle Med, Vehicle Large) concept
When we need a Subset do, we pick only our items, or do we have to worry about the other Subset?
We have the master and then have subsets
Concept of Common Properties Schema
Could include Vin and the Common Aggregates
Reference in JSON Schema is just copying your named section of your reference schema into the one that referenced it. It does not need to be named object.
Anonymous arrays are coined named for those repeating list of elements that were not named anything but just repeating
Review Vin Decode in current state
Common Types
Instead of having one large Common Aggregate we would have smaller common types so Vehicle would have Vehicle Common Types would be smaller
Working on the Reference and how to use it without a name
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
Public Page