- From: Eric Korb <eric.korb@accreditrust.com>
- Date: Tue, 22 Mar 2016 18:35:09 -0400
- To: Steven Rowat <steven_rowat@sunshine.net>
- Cc: Credentials Community Group <public-credentials@w3.org>
- Message-ID: <CAMX+RnDu5ADgVm4uAT3_xqkE1SYzgWvQrGSt7Nj2PvnSMDen6Q@mail.gmail.com>
+1 Eric <https://mail.google.com/> On Mon, Mar 21, 2016 at 4:39 PM, Steven Rowat <steven_rowat@sunshine.net> wrote: > On 3/21/16 11:46 AM, Shane McCarron wrote: > >> Information in >> the page indicates where on the vendor's site to find their claim >> about security, and the extension can retrieve the claim and >> verify it. [snip]... >> You can imagine many similar scenarios for >> other verticals (verify physician credentials, check whether a school >> is accredited, etc.) >> > > +1 > Agreed, would be a great improvement in the current UI. I know I've > wanted it recently. Millions of people probably wish for something like > this every day. :-) > > One thought: IMO it could lead to complex privacy questions -- > > Example: on a Health Site, a doctor is writing the site supposedly. The > user checks this, and the credential exists, but...what kind of doctor? > Educated where and when and with what specialty? > > The doctor's verifiable credentials could then include year graduated, > what university, what specialty -- but the doctor may not want all that > available on the site. Meanwhile the site user may feel they need to know > certain levels of the information in order to trust the site. (Do I trust > what a Neurosurgeon says about nutrition? Or what a GP says about > neurosurgery?) > > I believe this granularity is already under the scope of the Credentials > Goals in the Editor's Draft, as "Composability of verifiable claims to > express an aspect of one's identity in a granular way." > > So the use-case overall looks like it's well worth doing...and perhaps > would be complicated in some scenarios, requiring a back-and-forth with the > site viewer. > > Steven Rowat > > >
Received on Tuesday, 22 March 2016 22:35:57 UTC