...
The spec work, while being submitted to ISO, ISO is not the audience of the work. The specification's audience - or evaluators - is the data protection regulators, the customers for using the specification are the operator and industry frameworks, which they define according to regulator requirements. The users/engineers of these frameworks are the identity protocol based systems. Then in this system there customers and users, and with some standards, there can also be Certifications and 3rd party trust services, which service the system (think Me2B with an UMA License). Like a code of conduct and a badge framework for use with these systems.
The above frames the layers and the is framed by the physical /external governance layers. The aim of this spec is for an encapsulating all of these use cases in the outer- legal to encapsulate any stakeholder requirement, with this spec as a vehicle for the technical, legal, and social components required by any stakeholder. Using legal; notice, notification and consent requirement frameworkrequirements, which is globally defined in law and most often in the form of a legal ledger type model for things like notaries so people can , which is an example of creating tools for people to self certify a credential. This spec is non technical and people to law, and law to people.
...
This work is unique in Kantara, as its a spec for non-identity framework technology, which can use be used to provide notice and consent scopes too identity protocols.
Draft - Instructions for Use Case Work and flow for spec dev:
...