Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Dan 🔓 Public Page
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
Network/Welcome
Antitrust Statement
This meeting is subject to the terms of our anti-trust statement shown here. In addition, this meeting may be recorded.
Review Meeting Minutes
Continue with Contact
CAPIS BADD
Meeting Minutes
Antitrust Accepted
Meeting Minutes Reviewed Accepted
Contact
Email from Jeff I wanted to provide the math I was talking about in last weeks meeting regarding the number of options encapsulated in the current CAPIS 01 release using the phoneNums Object. There are 12 phoneNums enum for the type(communicationsQualifierEnumType) and each one can have an object with a preferredInd indicator being true or false. This gives 24 (12X 2) options with the combination of communicationsQualifierEnumType and preferredInd. Each one of the 24 combinations can have a phone number property (phoneNum) and a phone number extension (phoneExt); therefore if we were to enumerate all of the combinations of the phone number and phone number extension properties in the BAD (instead of using our current object structure), we would have a total of 24 X2 = 48 properties in BAD.
Having an array of objects to encapsulate the complexity of the enumeration combinations in the object instead of enumerating in the BAD, seems like a good (and clear choice). Where that enumeration of properties in between 1 and 48 lies is a different question and does take some "anticipation" of future needs of related properties.
I just wanted to clarify the math we discussed last week when comparing email properties vs phone number properties.
CAPIS BADD
Great Discussion everyone
Up Next
Network/Welcome
Antitrust
Review Meeting Minutes
Action items
Decisions
Reference
| View file | ||
|---|---|---|
|
Participants
Paulette Reed
Dan Webster
Jeff Schroder
Andy Bober
Mike Hastings