This issue is a follow-up to the weekly Solid CG meeting of 2022-12-14 (cf. minutes).
User Stories serve as the basic input for the UCRs (Use Cases and Requirements) which give direction to TRs (Technical Reports). While we currently have a number of UCR documents linked to a specific TR (e.g. authorization-ucr, notifications-ucr, https://github.com/solid/webid-profile/pull/80), and the purpose is/was to achieve that for every TR (https://github.com/solid/specification/issues/9), the issue was raised that it might be more useful to have use cases overarching the different Solid TRs. The reasoning behind it is twofold:
The scope of Use Cases might differ from the scope of a single specification: Use Cases might require features of multiple TRs to be fully supported. In such cases the Use Case would currently have to be duplicated between the different UCR documents of each TR.
New Use Cases are currently added to a single specific UCR document, even if they require efforts in other TRs as well. Understandably, we cannot expect from each panel to rummage through the UCR documents of every other panel in order to find those Use Cases.
The question then becomes: Would it be more efficient to manage all User Stories, Use Cases, and Requirements in a single document and repository?
This issue is a follow-up to the weekly Solid CG meeting of 2022-12-14 (cf. minutes).
User Stories serve as the basic input for the UCRs (Use Cases and Requirements) which give direction to TRs (Technical Reports). While we currently have a number of UCR documents linked to a specific TR (e.g. authorization-ucr, notifications-ucr, https://github.com/solid/webid-profile/pull/80), and the purpose is/was to achieve that for every TR (https://github.com/solid/specification/issues/9), the issue was raised that it might be more useful to have use cases overarching the different Solid TRs. The reasoning behind it is twofold:
The scope of Use Cases might differ from the scope of a single specification: Use Cases might require features of multiple TRs to be fully supported. In such cases the Use Case would currently have to be duplicated between the different UCR documents of each TR.
New Use Cases are currently added to a single specific UCR document, even if they require efforts in other TRs as well. Understandably, we cannot expect from each panel to rummage through the UCR documents of every other panel in order to find those Use Cases.
The question then becomes: Would it be more efficient to manage all User Stories, Use Cases, and Requirements in a single document and repository?
Edit: Tagging @timbl and @csarven for input.