Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
🔓 Public Page
CIECA 500 Westover Dr #11617; Sanford, NC 27330
Date
| Info |
|---|
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
Antitrust and Meeting minutes acceptance
Review Dan and Mikes Style Guide and messages and implement the Google Revisions and other revisions
Versioning of CIECA API
Meeting Minutes
Antitrust Accepted
Meeting Minutes Accepted
Reviewed Mike’s capiesSimpleType.json
all json types start in lower case
All of the types that are part of the json build have been dropped from our simple types (boolean, integer, date, time, uri, email)
Date and time follow date and times RFC in Common Global Types
phone number is a type in json schema with a pattern. We talked about having a number and an international phone number. Need to discuss how we want phone number.
All Char Types from the BMS was added as well as decimal ranges and integer ranges.
Indicator has the ^ added.
Need test instances to test all these simple types
JSON schema naming.
XML had schema types with .xsd to identify them as schemas
JSON the only way to identify them as schemas is to but schema in the name
We should remove all the _ values so char_5 would be char5
JSON Rule(s)
When you are using a pattern; you do not need to have min and max
when the file is an include file; you do not need the definition section.
Reviewed JSON Style Guide that Dan worked on
Paulette will put the Style guide in Confluence for everyone to review before next meeting.
Additional Properties is recommended to turn on; this will allow companies to add new fields without breaking the schema and make it expandable.
The XML used a Custom Field Value to allow this.
Versioning look at Simple Versioning 0.1 | SimpleVersioning (simver.org) semver.org
The JSON version would start at 0.1.0 or 1.0.0?
🤓 Great Meeting Everyone!
Up Next
Antitrust and Meeting minutes acceptance
How do we want Phone Number (Formatted, straight numeric, multiple formats for number vs international, just international)
Finalize and vote on SimpleTypes; we would like everyone to attend to make verify the guidelines being established
Review and vote on Style Guide
Versioning of CIECA API
Action Items
Decisions
- All JSON types will start lower case
- All of the types that are part of the json build have been dropped from our simple types (boolean, integer, date, time, uri, email)
- phone number is a type in json schema with a pattern.
- All Char Types from the BMS was added as well as decimal ranges and integer ranges.
- JSON schema naming.
XML had schema types with .xsd to identify them as schemas
JSON the only way to identify them as schemas is to but schema in the name
We should remove all the _ values so char_5 would be char5
- Json Rules(s)
When you are using a pattern; you do not need to have min and max
when the file is an include file; you do not need the definition section.
Participants
Dan Webster
Chrisa Hickey
Paulette Reed
Brad Broerman
Aaron Daniele
Mike Hastings
Paul Barry
Jeff Schroder