Introducing product categories

[akoshunyadi]

Problem description Currently our APIs are organized into sub-projects, later it might be changed to working groups with the related APIs, but there's still no organization of the APIs from the product view, what the developers will see when using Camara APIs.

Possible evolution I'd like to propose the introduction of product categories, like device, home, network etc.

• They could be used for naming the APIs as a prefix, e.g. device-connectivity.yaml, device-geofencing.yaml.
• The category could be also added to the info field of the OAS, like x-category: device
• Also for naming the events the short product category name could be used instead of the long API name

Alternative solution

Additional context

[jgarciahospital]

HI Akos. At product level there is a category proposal followed by Use Cases, which i'm pretty sure that will not be valid for CAMARA where the names are more specifying the functionality implemented by the API than the service that is solved with it.

Additionally, APIs are evolving in some cases, changing their scope (e.g. mobile to also fixed), not sure how this will evolve and be maintained over the time.

I'd propose that, for the time being, we fix the already open and even agreed discussions in the particular APIs, e.g. https://github.com/camaraproject/DeviceStatus/issues/125, for been able to get solutions on existing issues asap.