2022-07-19 Architecture Meeting Minutes

Public Page

Date: Jul 19, 2022

Agenda

• Antitrust

• Update on Action Items and work completed from Face to Face

Meeting Minutes

• Antitrust Accepted

• Review of Face to Face

  • Party and Claim Info was completed in the Face-to-Face meeting

  • Part Info was worked on and Car-Part.com team will propose Part

    • looking at QuotedPart

  • The BA Excel document was worked on that pulled the tags from BMS 6.5.0 and the capis tags

    • The Number, Qty, Num, NumOf tags are in this document

    • This document can be found on the Architecture Committee https://cieca.atlassian.net/l/cp/tPf1XdyV Page

  • Coordinates will remain a pair for latitude and longitude

  • ConsumerPrivacyIndicator of a Boolean can be used to allow data receiver to know this message/object has PPI

  • The SimpleType of Decimal and Currency can be removed, and we will use number.

  • Phone # is 11 characters

  • Rule to use abbreviations

    • Standardize abbreviations such as num, qty and retire property names that break the new abbreviation rule.

  • Clean up GitHub

  • Party is complete and the parties that are used by Architecture Committee members are added, a list needs to be sent to the other committees to get the Parties they want to use in json. This is in line with the zero-budgeting approach of removing things and them being added back.

  • Update Styleguide with rules and information from the face-to-face

  • Finished meeting with images and MMII discussion with not resolution.

• Meeting Notes

  • In the All CIECA Committee Review for Vehicle, there were a few fields that were questioned about being removed. These fields were added back (LicensePlateRegistrationDate, LicensePlateExpirationDate, OdometerReadingCode, OdometerReadingCodeEnumType, Package)

  • Removal of NICBInfo was brought up.

    • NICBInfo is not part of Vehicle any longer, if there is a need for NICBInfo, it can be added to the dictionary schema. The architecture committee is asking for instances of use so we can make sure the properties needed are being added and instance documents can be created to test the additions.

    • NICBInfo is used in salvage today but not sure the NICBDate is part of the BMS message

      • The NICBDate can use the extendedProperties Property to add data that is not part of the capis definition

  • SimpleTypes definitions may be able to be moved up to the capis definitions, so we do not have an extra level, but at this time the simpleTypes are in a different schema.

    • Currency and Decimal were removed as suggested in the previous meeting

  • Consistency in using Type

    • With Address we have an addressType and address, lossLocationAddress both use addressType in the definition

    • date-time is a built in format, however, to be consistant we should have a property of dateTime defined and then accidentDateTime, lossDateTime, policyEffectiveDateTime, PolicyExpirationDateTime, PolicyRenewalDateTime, PolicyStartDateTime, reportedDateTime and vehicleRecoveryDateTime would all reference dateTime, so if it was changed, it would be changed in one place and not numerous places.

    • The use of Type in the name is that for property that have more than one property included, because dateTime would not be a Type if that was the case. We need a Rule for when to use Type in the description of a property.

  • Line Endings

    • Some the line endings are different, and we all want to make sure that we're using the same line endings. And then as such we want to make sure that the tooling is configured to use the same line and needs.

    • Git uses new line

    • Unix is new line and the recommendation

  • Naming Convention

    • We still need to decide on the num, numOf, quantity, qty, number and abbreviation rule

    • It was agreed that we want consistency and we are okay with renaming BMS objects in a consistent way, homework will be to look at the BMS Properties and propose the new way.

  • GitHub Structure

    • Before this meeting the team got together and worked on cleaning up gitHub. The new structure is in place for review.

    • CAPIS/json-schema/definitions/ is definitions, simpleTypes and codeList

    • CAPIS/json-schema/schemas/ is the capisVehicleSchema, capisClaimSchema, capisPartySchema and the combined schema using the definitions

    • CAPIS/json-schema/bundles/ has the bundled vehicle

    • CAPIS/json-test-instances/ is different in structure than the BMS. There is a folder for Vehicle, Claim, Party and vehiclePartiesClaim with folders for valid and invalid. This will help people find the test instances and not be part of a large list.

    • CAPIS/open-api-spec/ was missing because it didn’t have any documents under it. gitignore was added so the folder would show up.

    • The branches were cleaned up and now we have main and schema-bundling-test. Work should be done in schema-bundling-test and checked in for the team to review.

  • PartInfo work

    • car-part.com team is about 1/3 of the way through flattening quotedPart

      • If the team wants to share the new version with Paulette, we can put it in Excel so we can have the side-by-side BMS and proposed Part.

      • Think PartInfo will be reviewed next week

  • Expectations

    • capis version 0.1 in October

    • First Version to include vehicle, parties, claim and part or quotedPart

    • Document a Cross Reference so people can see familiar EMS and BMS properties with the CAPIS properties

    • Add descriptions to definitions

Kabob Case is when words are separated with a dash: learned-something-new-today. Great job today everyone.

Action items

Decisions

Participants

• Paulette Reed

• Dan Webster

• Mike Hastings

• Andy Bober

• Paul Barry

• Chris Poulos

• Jeff Shroder

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