Public Page

2022-04-12 Architecture Meeting Minutes

Owned by Paulette Reed
Last updated: Apr 19, 2022
3 min read

Public Page

Date: Apr 11, 2022

 

 

 

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

Meeting Minutes

  • Antitrust Accepted

  • Welcome

  • Meeting Minutes Review

    • Meeting Minutes Accepted

  • Meeting Minutes

    • Reviewed the JSON Style Guide changes from the last meeting

      • Discussion on should we use Envelope Style or not.

        • There was no conclusion to this topic and the committee would like to revisit the discussion. At this time the document will have the sentence in orange so we know we need to review.

          • The Example at the bottom of the document is showing the concept of not using Envelope Style

          • Envelope Style increases human readability

        • Moved the text ‘Always make sure that you are referencing the property definition.’ to the JSON Schema Guidelines by adding a new section for Schema Building Procedures. The statement that was moved is more in line with Schemas.

          • We will work on the website format for this documentation with the CIECA Simplified style, but at this time it is being added to Confluence.

        • All the other changes were accepted to the JSON Style Guide.

    • BMS Discussion

      • When we are converting names from BMS to CAPIS, we will need to be careful to follow the CAPIS guidelines.

        • We have a few aggregates that are named Details, which is plural but the aggregate is not plural or an array.

        • Facts is another BMS aggregate that would need to be renamed not to go against the CAPIS naming convention of Singular and Plural named values.

        • We need to be careful not to add definitions to aggregates that is not needed. An example of this, VehicleInfo could be named Vehicle. However, things like Odometer may need more information because Odometer Reading is what people would figure was Odometer.

        • Desc is for a String and not to be used in an aggregate.

        • Arrays will be plural

        • Each Camel Case word needs to add value and meaning to the name

    • New Topic

      • Should the CAPIS standards be a list of properties and allow the trading partners to use the fields as they want?

        • CIECA Standards named objects or a list of properties?

    • Issues with Referencing

      • Mike ran into some issues when using the Referencing concept

        • Mike will share his examples and issues in slack or email

        • Mike will try referencing with other Validators

Action items

Decisions

Participants

  • Paulette Reed

  • Chrisa Hickey

  • Mike Hastings

  • Dan Webster

  • Andy Bober

  • Chris Poulos

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