Smart Data Scheme Reference Model on the Dataswyft Network
Not all proofs/assets require a smart data scheme. Proofs/assets that do not have any content data would not require a scheme. Open API systems also do not require a scheme.
When proofs are required to be of high assurance or contain sensitive underlying information. If the data coming in to your ecosystem are high assurance or sensitive data such as National ID, banking, or health records, it is likely that Dataswyft would ask for a Smart Data Scheme to be registered. This is so that the rules of execution are clear for Dataswyft to implement.
When the data profile would result in many proofs/assets issuers. A data profile provider that can spawn many proofs or badges would require a Smart Data Scheme as Dataswyft has to be clear which issuers are allowed to issue against the data profile.
When ecosystem members are vulnerable. If a data ecosystem involves vulnerable members of society (e.g. children, disabled, stateless), a Smart Data Scheme would be required.
When data flows entail risks. If data flows within an ecosystem entail cyber security, or any other risks, a Smart Data Scheme would be required so that all members are aware and accept the risks.
Check with our studio specialists on whether your data ecosystem requires a smart data scheme.
‣ (members only)
V0.1