W3C home > Mailing lists > Public > public-credentials@w3.org > June 2016

Request for terminology input - consumer/inspector/TBD Credential

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Tue, 7 Jun 2016 23:00:09 -0400
To: Credentials Community Group <public-credentials@w3.org>, Web Payments IG <public-webpayments-ig@w3.org>
Message-ID: <57578A39.3010308@digitalbazaar.com>
We discussed terminology on the Verifiable Claims Task Force call today
and left two things undecided. We really need to get this terminology
straight in order to align the prose in all of the documents. As a first
step, we need to get all of the options on the table.

-------

We have a block in our architecture block diagram that is currently
labeled as "inspector":

http://w3c.github.io/webpayments-ig/VCTF/architecture/architecture.svg

This is the entity that requests a set of verifiable claims from the
holder and examines them to determine if they are valid for the purposes
of granting access to a particular resource. Naming options include:

Consumer
Inspector
Reader
Verifier
Receiver

-------

We agreed to relabel the word "Credential" with a modifier in order to
reduce confusion with other "credential initiatives". Naming options
include:

Identity Credential
Digital Credential
Web Credential

-------

Please add to these list of options with the following caveats:

1. If you propose something, make sure that you're the champion for
   that term. Don't suggest something that you wouldn't want as the #1
   pick.
2. If you propose something, make an argument for the use of that term
   and an argument against all of the other terms.
3. Don't send "me too" emails. If you want to weigh in, please make
   sure you're making an argument that no one else has made in order to
   cut down on the number of emails sent to the mailing list.

We are going to collect input until midnight on Thursday and put up two
Generalized Instant Runoff Voting[1] polls on Friday. The polls will be
open for a week and will determine the final terminology we'll use
across all of the documents.

-- manu

[1]https://www.opavote.com/methods#instant-runoff-voting

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
JSON-LD Best Practice: Context Caching
https://manu.sporny.org/2016/json-ld-context-caching/
Received on Wednesday, 8 June 2016 03:00:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 21:19:29 UTC