Feedback Template
Source ID/Section | Comment | Feedback Type | Jira Issue |
|---|---|---|---|
4.3 - Interactions with other BBs | In the table in this section, suggest a couple of changes: ID Building Block - this relationship is not clear. I assume the Consent BB will query the ID BB to verify a foundational ID as is shown in the diagram Digital Registries - can we also indicate that the consent may be stored either in a digital registry or in an app-specific data store/database (per TC conversation last week) | Now | Create issue only once comment has been reviewed |
4.4 - Functionalities | The links in this section should go to govstack.gitbook.io rather than app.gitbook.com | Now | |
5 - Cross-cutting requirements | I like the table outlining requirements from other building blocks. Could you provide a brief description of what this table is? Also in this section, there is one link to the security requirements. This link should be to http://govstack.gitbook.io rather than http://app.gitbook.com | Now | |
6 - Functional Requirements | Could we change the format to reflect the template here: https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/ugHOCsaCJ3B29gavXcd8/6-functional-requirements Also, could we use REQUIRED, RECOMMENDED, OPTIONAL instead of MUST/MAY. We are trying to move to this language across all BBs | Now | |
9 - Internal Workflows | Link to Workflow specification goes to Google docs. Can we update to point to the Workflow spec at govstack.gitbooks.io | Now | |
9 - Internal Workflows | Is the Workflow BB necessary for all Consent interactions, as shown here? Can an application access the Consent API directly or are we mandating the use of Workflow BB? | Next |