@@ -6048,31 +6048,6 @@ <h4>Spoofing Attack</h4>
60486048to enable proof of control.
60496049 </ p >
60506050 </ section >
6051- < section class ="informative ">
6052- < h3 > Bundling Dependent Claims</ h3 >
6053-
6054- < p >
6055- It is considered best practice for [=issuers=] to atomize information in a
6056- [=credential=] or use a signature scheme that allows for selective
6057- disclosure. When atomizing information, if it is not done securely by the
6058- [=issuers=], the [=holders=] might bundle together [=claims=] from different
6059- [=credentials=] in ways that the [=issuers=] did not intend.
6060- </ p >
6061-
6062- < p >
6063- Consider a university issuing two [=verifiable credentials=] to an individual.
6064- Each [=credential=] contains two properties that, when combined, indicate the
6065- person's "role" in a specific "department." For instance, one [=credential=]
6066- pair might designate "Staff Member" in the "Department of Computing," while
6067- another could signify "Post Graduate Student" in the "Department of Economics."
6068- Atomizing these [=verifiable credentials=] results in the university issuing
6069- four separate [=credentials=] to the individual. Each [=credential=] contains
6070- a single designation: "Staff Member", "Post Graduate Student", "Department of
6071- Computing", or "Department of Economics". The [=holder=] might then present
6072- the "Staff Member" and "Department of Economics" [=verifiable credentials=] to
6073- a [=verifier=], which, together, would comprise a false [=claim=].
6074- </ p >
6075- </ section >
60766051
60776052 < section class ="informative ">
60786053 < h3 > Highly Dynamic Information</ h3 >
0 commit comments