Should/ can commercial offers be represented by credentials, really? (Joerg Heuer, Deutche Telekom Labs) ✪
Joerg: If we go too deeply into the shopping experience that won't be good for this group. We'll have a session and something that offers a transaction in the Web Payments work, might not need to go deeper than that.. ✪
... But a credential coud be a 'proof of purchase' to let you access content, etc. Right? ✪
... Using it as an access key - or to receive a special discount... ✪
Joerg: When talking about digital goods, you could use a digital receipt as a credential. ✪
Proposal - the subject of a purchase can be a credential - or a book or file... ✪
We don't need to take care of every kind of credentials, I think. ✪
Joerg: This looks like something in EU framework - attribute-based credentials. I might have an institution asking me to ensure that they're not making me give away my identity/credentials. I think we should support attribute-based credentials, in scope - would like to see that. Overall process around it, assuring customer that everything is being done correctly, doesn't belong in credentials work. ✪
USE CASE: Support endrosements/counter-signatures on credentials. Signatures can be either dependent on one another (chained together), or multiple signatures on original document (part of a mathematical Set).
Dave Longley is scribing.
USE CASE: Enable multiple credentials from multiple 3rd parties to be composed together to grant authorization to access a system.