2022-05-03 Architecture Meeting Minutes

Public Page

Date: May 3, 2022

Agenda

• Antitrust

• Committee Welcome

• Meeting Minutes Review

• Review Mikes Homework for $Ref

• Continue Flattening discussion for Vehicle

Meeting Minutes

• Antitrust Accepted

• Welcome

• Meeting Minutes Reviewed and Accepted

• Mike reviewed his work and provided the Proof of Concept for $Ref and bundling

  • The issues that XML Spy was warning about was corrected after the schemas were bundled.

  • XML Spy can reference lower than one level when bundled.

  • The Proof of concept is that you can have a Vehicle Large, Vehicle Med and Vehicle Small by using the same Vehicle by referencing.

• How do we pronounce CAPIS?

  • Lapis Definition & Meaning | Dictionary.com

    • lap-is, recommended we pronounce cap-is

  • Other ways of pronouncing is Kay-p-is

  • Agreement that as a standard we should all pronounce the standard the same; using cap-is.

  • We have received a few Avatar submissions for our CAPIS project, however, most are logo related and not a character.

• Vehicle Common type

  • We are going to continue to work through the Vehicle Info BMS aggregate for the CAPIS Vehicle, when that is completed we want to review Claim Info and Parties.

  • NICB is where we left off last week and began the discussion

    • NICB has been sold off and no longer called NICB

    • It is suggested that it is dropped from Vehicle and if someone would like it added back, they can make that proposal

    • It is believed this would be a value needed for subrogation, but nobody in this committee understands.

  • Naming and JSON Style guide

    • The naming concepts were reviewed. The largest part is that Vehicle Info can be called vehicle, but does this allow a developer to know this is a vehicle Object or Aggregate or do we need more descriptive naming? The naming is supposed to be meaningful and we do not want to concentrate on long or short. Does ‘Info’ add to the description of vehicle? It was ruled Info could be description or stuff or many other words, but its all referring to vehicle and vehicle was valid name. The same was walked through for odometer and agreed odometer was a valid name.

    • The Array object being anonymous vs named.

      • The Style Guide says array should not use enveloping and we reviewed the definition of enveloping and was good with the style guide and the descriptions.

    • The color codes have three different values for oemColor, vendorColor and customColor. It was suggested that we may be able to go to one color code, however, the committee is not familiar with these distinctions of color and do not feel like they should be removed at this time.

    • Engine and transmission have an array of options within them that adds a level of hierarchy that we have not used to this point.

      • There is discussion of engine and transmission both can have different options and each having this array is valid. It may not be required by transmission.

      • We ran out of time and will start with engine and transmission next week.

Open

Great Meeting Everyone!

Action items

Decisions

Participants

• Paulette Reed

• Dan Webster

• Andy Bober

• Chrisa Hickey

• Jeff Schroder

• Mike Hastings

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