...
Other example of the third case are lists of options such as the reason for a loan, say: education, car, house. One could create classes CarLoan, HouseLoan and EducationLoan. OR, one could create an instance of fibo-fnd-arr-cls:Classifier called LoanReaons with instances ((using an agreed naming convention): "_LoanReason_Car", _LoanReason_House", and "_LoanReason_Education". There are other ways to classify loans, for example: ConformingLoan, NonConformingLoan, USDA_Loan, VA_Loan and FHA_LOan. We could create classes for these too. But then should we also create a class for every valid combination? This can result in an exponential number of classes, which should generally be avoided.
...