2022-08-16 Architecture Meeting Minutes

Public Page

Date: Aug 16, 2022

Agenda

• Antitrust

• Network/Welcome

• Review Previous Meeting Minutes(s)

• CONNEX/QA Face to Face Update

• Homework Updates

• Thank You Everyone for all the work this last week

• Review/Prioritize/Assign Next Steps

• Review Jira Board

Meeting Minutes

• Antitrust accepted

• Meeting minutes reviewed/accepted

• CONNEX Reminder

  • September 13, day 1 of the event is full of presentation by industry experts to discuss topics on emerging trends

    • NABC Recycled Rides event

  • September 14, day 2 of the event, we will have more presentations and end with an Open Member meeting

    • The Open Member meeting will replace the monthly SAB meeting and a chance for all the chairs to speak.

    • Dan and Mike will speak and present Architecture and the work on capis

    • A tour of Hunter Engineering

  • September 15, CIECA Board meeting is at 9am and we will start an Open Technical session to work on capis in the morning. After the Board Meeting concluded, we will have our 2022R2 QA meeting.

  • For a complete list of presenters for CONNEX, CIECA CONNEX 2022 - Agenda (zohobackstage.com)

• Homework

  • Bundling Portion of the build process is completed.

    • Next steps validation

  • Fixes to current schemas

    • All schemas were using the deprecated “definitions” keyword rather than “$defs”. This is what caused all the yellow underlines.

    • Several schemas included “title” and “description” properties containing details from prior automated xsd to json-shema conversion.

    • cpaisPropertiesDictionaryDefinitions.json had a typo in addressType commQualifer spelling that was fixed

    • capisPropertiesDictionaryDefinitions.json had a typo primaryPoi pointOfImpactType should be pointOfImpact was fixed

    • capisClaimSchema.json had claimInfo and $ref referencing claimInfoType should be claim and $ref should reference claim was fixed

    • cpaisPartiesShcema.json had typo in all properties referencing party but only partyType is available in capisPropertiesDictionaryDefinitions. swithced these to partyType so the bungling would work but Andy does not think this is what we want, we need to define party. This was only a partial fix

    • capisVehiclePartiesClaimSchema.json was referencing claimInfo instead of claim and had same issue with party.

  • Things we need to discuss

    • All the schemas in the json-schema/schemas directory are using "anyOf" at the root.  This is a holdover from the automated conversion that I do not think we want to keep.  The purpose of this was to expose all the individual aggregates contained in the file for testing.  In our hand coded stuff, I believe we should abandon the "anyOf" at the root altogether.

  • Summary of Build process:

    • A build directory is re-created with each run.

    • A log of each run named capis.log is generated in the build directory.  This contains more details than what is shown at the command line.

    • Any schema in the json-schemas/schema directory is run through the bundler.

    • Bundled schemas are placed in the json-schemas/bundles directory - not build because I think we're planning to commit the bundles, right?  Otherwise, they should go to the build directory.

    • Yucky YAML versions of the bundled schemas are also put in the build directory.

  • Validation of vehicle was completed

  • Tip: Don’t forget to do a ‘git pull’ go get the latest changes and reduce the conflicts at check-in.

• Review/Prioritize/Assign Next Steps

  • Finalize Claim (Excel review showed some flattening or removal possibilities)

    • deductibleBasedOnPercentageMethod we think we can remove for zero based ruling, but we will give a week to let everyone to review.

    • Inspection review to see if we want to bring it up.

  • Review quotedPart/part

  • create party from homework

  • Get more Test Instances for vehicle, claim, party, part

    • Valid and Invalid

  • Documentation

• Work Done in meeting

  • Changed partyType to party due to partType being an ENUM property and not the full party

  • We have an object Model for Vehicle and Claim, however we removed that for Party.

    • Now when we are including all of party, we have to include each one of these, this means in the above work of changing partyType to party, we had to do it multiple times

    • Need to look at Party some more to see if we need object of party.

  • Schema bundling concept, do we have schemas that will have all the individual (Vehicle, Party, Claim) and then one that includes all of the schemas together.

    • There was a thought that we would only have the individual to do testing

    • Not sure at this time and good topic to revisit.

  • Issues with the pattern of arrays in the current schema need to be corrected

    • Set up a working meeting later this week to go over these changes and get sync executed

    • Paulette and Dan will stay online after meeting to work on GitHub

• GitHub review

  • Showed how the different checkins showed up and how it compared the versions.

    • Reviewed the changes that Andy made showing the ‘Definition’ being changed due to it being deprecated.

    • Looked at the code for anyOf.

• Next, we will review part that Mike has prepared.

Action items

Decisions

1. Remove anyOf from the schemas.

Participants

• Paulette Reed

• Dan Webster

• Jeff Mueller

• Brad Broerman

• Mike Hastings

• Paul Barry

• Phil Martinez

• Jeff Schroder

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