In the Eiffel protocol we can describe requirement of dependencies via compositions and validity checking. The describes does not describe the result but only the requirement.
Motivation
Today the protocol does not specify how to describe dependencies between artifacts and source changes.
Exemplification
Some ideas to elaborate the problem
Either Eiffel introduces a way to describe dependencies between artifacts and source changes in some similar manner that SBOM formats does it. E.g. CONTAINS or DEPENDS_ON in the SPDX relations
Let Eiffel refer to a SBOM format that handles dependencies between artifacts and source changes
Benefits
A good dependencies description between artifacts and source changes will help the user of Eiffel to understand dependencies.
Description
In the Eiffel protocol we can describe requirement of dependencies via compositions and validity checking. The describes does not describe the result but only the requirement.
Motivation
Today the protocol does not specify how to describe dependencies between artifacts and source changes.
Exemplification
Some ideas to elaborate the problem
CONTAINSorDEPENDS_ONin the SPDX relationsBenefits
A good dependencies description between artifacts and source changes will help the user of Eiffel to understand dependencies.
Possible Drawbacks
None that I can think of