I’ve never had a problem with using consumer or consuming. Verifier may work although but as Shane said, verifying isn’t consuming but may be part of consuming. Evaluate doesn’t really work as it assumes assessment. > On Feb 15, 2016, at 8:51 AM, Shane McCarron <shane@halindrome.com> wrote: > > Hmm. But a "consumer" might not be the one doing the verification. A consumer is the one that needs the claim to be true (presumably). Requestor is more accurate in the case where we are talking about the entity that is asking the holder for the claim. > > On Mon, Feb 15, 2016 at 2:20 AM, Adrian Hope-Bailie <adrian@hopebailie.com <mailto:adrian@hopebailie.com>> wrote: > Verifier seems appropriate given that these are "verifiable" claims > > On 15 February 2016 at 00:59, Steven Rowat <steven_rowat@sunshine.net <mailto:steven_rowat@sunshine.net>> wrote: > On 2/14/16 1:44 PM, Manu Sporny wrote: > I'm happy with 'evaluators', but wonder what our colleagues in the > education industry think? ...[snip] > > Credential/Claim Requestor and Credential/Claim Verifier could also work? > > IMO any of Requestor, Verifier, or Evaluator would be preferable to Consumer. > > Except, Requestor could be confused with 'holder', the person/entity asking for the original issuing, since at the start they are 'requesting' that a credential be issued for them -- which they then take elsewhere to be Evaluated or Verified (or, currently, Consumed). > > But as you noted, with multiple possible systems in play -- finance, education, payments, government -- it's going to be hard not to cause at least some confusion somewhere. > > > Steven > > > > > > -- > -Shane
Received on Tuesday, 16 February 2016 08:56:06 UTC