- From: Stone, Matt <matt.stone@pearson.com>
- Date: Tue, 29 Mar 2016 14:43:48 -0500
- To: Dave Longley <dlongley@digitalbazaar.com>
- Message-Id: <CA+w1=RR0s3UW+ZiJQ-ciYpGF3KSMdkmcfHBYQJ-TP=YqnjEkrw@mail.gmail.com>
"inquiring" and "accepting" are probably the closest verbs for what this party is doing in the transaction. Neither term is very intuitive. -- one of the aspects of "consume" that I like is that of impermanence - the claim is consumed once it's verified. If proof is needed again at a later date, it must be verified again. An achievement or attribute at a given time may be an indelible fact, but a claim that is verifiable may not be. Consumption is real in this case. -stone ===== Matt Stone 501-291-1599 On Tue, Mar 29, 2016 at 10:36 AM, Dave Longley <dlongley@digitalbazaar.com <mailto:dlongley@digitalbazaar.com>> wrote: On 03/29/2016 12:22 PM, Stone, Matt wrote: > in which document do we define this? Is the consumer, the one who > has asked the earner for proof of an achievement? in job search > scenario, it would be the prospective employer... http://w3c.github.io/webpayments-ig/VCTF/use-cases/index.html#ic-consuming-claims <http://w3c.github.io/webpayments-ig/VCTF/use-cases/index.html#ic-consuming-claims> That link talks about consumers of claims and you can click on "consumer" there and it will jump to the glossary section. A "consumer" is one who asks a holder to provide credentials containing verifiable claims so they can authenticate the holder and "consume" those claims in some way. Examples would be merchant websites that need to confirm that a person is of a certain age in order to buy a product, prospective employers that want to verify the credentials of job applicants, and loan officers that want to ensure they are lending to the appropriate person. -- Dave Longley CTO Digital Bazaar, Inc.
Received on Tuesday, 29 March 2016 19:43:49 UTC