https://cieca.atlassian.net/wiki/spaces/ARCH/pages/125304911/2020-08-04+Architecture+Meeting+Minutes

1. It is okay for the BMS and the Implementation Guide descriptions to remain out of sync.
2. Dan confirmed that the top one is correct: the capital “F” is because “arrange for” is two words; the lower case “u” is because the noun form of “pickup” (defined as “an act of collecting a person or goods, especially in a vehicle”)  

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/158826531/2020-08-25+Architecture+Meeting+Minutes

1. Damage Type asterisk(*) will remain and Z is no longer going to be added to 2020R2.

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/565641284/2021-01-12+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/579633157/2021-01-19+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/616660993/2021-01-25+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/690815014/2021-02-16+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/640712727/2021-02-2+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/640712707/2021-02-2+Architecture+with+RP+I+ROE+Code+List+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/717258793/2021-02-23+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/674005013/2021-02-9+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/728498254/2021-03-2+Architecture+Meeting+Minutes

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/759136376/2021-03-9+Architecture+Meeting+Minutes

1. TimeStamp Data Type will be dropped and not used in the APIs.

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/830701657/2021-04-06+Architecture+Meeting+Minutes

1. Decision that we will have a validating schema; we will not worry about speed; but we want to make presentable for ease of implementations.

1. Version of CIECA API is 3 parts. 1 version breaks existing code, 2 change with no break, 3 patch

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/863633443/2021-04-13+Architecture+Meeting+Minutes

1. All JSON types will start lower case
2. All of the types that are part of the json build have been dropped from our simple types (boolean, integer, date, time, uri, email)
3. phone number is a type in json schema with a pattern.
4. All Char Types from the BMS was added as well as decimal ranges and integer ranges.
5. JSON schema naming.

1. Json Rules(s)

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/906887207/2021-04-27+Architecture+Meeting+Minutes

1. It was decided to move forward with OpenAPI 3.1 and JSON 2020-12

1. At this time, we do not plan to use SwaggerHub because it does not support the version of JSON we will be developing.

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/943358136/2021-05-11+Architecture+Meeting+Minutes

1. It was decided that Char_# and Decimal_Range_, and Integer_Range_ values would not be used in OpenAPI development, that we would use the JSON values String, Decimal and Integer.

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/976093212/2021-05-18+Architecture+Meeting+Minutes

1. Criteria for Common Property , must be used more than once

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/1035730988/2021-06-8+Architecture+Meeting+Minutes

1. DocmentInfo does not need object in schema
2. BMS Version will not be needed in JSON and do not see a Version being needed in JSON Schema, may just be able to use URL path
3. Document Version is still needed, but not needed for FNOL; it would be required for estimate

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/1130692651/2021-07-13+Architecture+Meeting+Minutes

1. At this time we will have the VIN in the schema be 17, if a need comes up later for the length to be longer, it can be requested. The minimum value will be 1.

1. The Required fields for Vehicle Info will be VIN or Year/Make/Model

1. The four fields we keep from DocumentInfo to be rolled up are Version, CreateDateTime, PassTrhoughInfo and VendorCode.

https://cieca.atlassian.net/wiki/spaces/ARCH/pages/1307148289/2022-03-29+Architecture+Meeting+Minutes

1. The complete flattened object was rejected, and we agreed to stay with named objects.
2. Not to use the Chile Model because it is not supported by tools.
3. Guiding Principles is when we have properties that need to go together, they should be an Object and introduce a level of hierarchy
4. Guideline to always make sure that you are referencing the property definition. Look at the structure that it is in and determine the properties you want with best judgement.
5. Guiding Principle for Naming Convention that Desc should be used for property that describe something in a string.
6. Guiding Principle is no extraneous layers, layers that do not add value to the thing being transmitted instance schema. For an example the OrgInfo or Party Aggregates in the BMS.
7. Array Rule - Property naming should be plural
8. Promote VehicleDesc to the root of VehicleInfo, flattened and promoted.
9. Promote Body to the root of VehicleInfo