Proposal: Component Taxonomy is insufficient - can Pack Datasheets fill a gap?

[jkrech]

This issue is to capture feedback to the idea of extracting a human readable document Pack Data Sheet from the pdsc.
Today we render searchable device and board pages from pdsc files but not for packs (software).

PackDataSheet.pdf

From Meeting: https://linaro.atlassian.net/wiki/spaces/CMSIS/pages/29036806164/Open-CMSIS-Pack+Technical+Meeting+2023-10-17

[ReinhardKeil]

A possible example of a datasheet content is here: https://github.com/ReinhardKeil/lwIP/tree/patch-1#readme

Weakness: Provided Interfaces (API header files)

PackDataSheet.pdf highlights Provided Interfaces as a weakness. This is exemplified by lwIP where multiple header files are used to define various interfaces. In addition, the header file name also contains a sub-pathname:

#include "lwip/tcp.h"    // defines the tcp API of lwIP

See also Open-CMSIS-Pack/lwIP#1

We may need to consider also how API header files are exposed to the user. In uVision this is done in the editor dialog only (the current dialog is overloaded on complex applications):