Closed eddie-knight closed 4 months ago
This issue will be closed as stale in 7 days. Please update this issue if it is still needed.
@smendis-scottlogic I'm going to close this issue, but ask that you keep this phrasing consideration in mind as appropriate in the future. 🙇♂️
Problem
Currently, there is a lack of clarity surrounding the term "taxonomy," with contributors using the phrases "top-level taxonomy" and "service-level taxonomy" due to a lack of clarity regarding the terminology intent.
Proposed Solution
According to a cursory search:
Extending this definition, I propose that we use the term "taxonomy" strictly for the purposes of describing the complete list of services covered by this project. The taxonomy will contain multiple service categories, such as "Compute" and "Storage". Subsequently, each "Service Category" will contain a list of features that are common to that category.
Where the
README.md
will contain a comprehensive overview of the taxonomy of services, and each sub-directory is a "Service Category." Within each subdirectory will be entries for each subsequent "Service Type."For example, the corresponding directory structure could be:
Concluding, I suggest that a glossary be provided with the following definitions, and the codebase be adjusted accordingly: