Currently the data API has categories, franchises, equivalences classes, and subequivalences classes. I wonder if this is all needed. The distinction between category and equivalence class is difficult to manage. It seems only equivalence classes are used by the rest of the system. I would like to propose:
That instead of equivalence class and category, we simply collapse "equivalence classes" into a single category upon loading the data, and only work with the resulting categories.
To rename the franchise to root categories.
Any comments on this? If this is a feasible change I'll retag this issue as a maintenance issue for release 0.3
prmr
commented
10 years ago
Currently the data API has categories, franchises, equivalences classes, and subequivalences classes. I wonder if this is all needed. The distinction between category and equivalence class is difficult to manage. It seems only equivalence classes are used by the rest of the system. I would like to propose:
Any comments on this? If this is a feasible change I'll retag this issue as a maintenance issue for release 0.3