Per #1 this is a proposal to add unlinkability and unobservability as a chapter. So far they are only referenced as "Recommended to allow for implementations where either the local regulation or the specific use case requires they are not implemented." however we should be able to describe at the technical level how are these 2 functionalities implementable and the tradeoffs a decision-maker should know to choose them.
I am further asking this be moved to an Building block extension where it can be properly described and its requirements described in a Functional Requirements chapter instead of a cross-functional one in accordance with GovSpecs 2.0 specification.
I am providing a draft proposal outline on unlinkability for discussion by the working group to start the discussion:
https://govstack-global.atlassian.net/wiki/x/A4CXhg
Per #1 this is a proposal to add unlinkability and unobservability as a chapter. So far they are only referenced as "Recommended to allow for implementations where either the local regulation or the specific use case requires they are not implemented." however we should be able to describe at the technical level how are these 2 functionalities implementable and the tradeoffs a decision-maker should know to choose them.
I am further asking this be moved to an Building block extension where it can be properly described and its requirements described in a Functional Requirements chapter instead of a cross-functional one in accordance with GovSpecs 2.0 specification.
I am providing a draft proposal outline on unlinkability for discussion by the working group to start the discussion:
https://govstack-global.atlassian.net/wiki/x/A4CXhg