RE: Support for Verifiable Claims

> Accessibility Use Cases (many of which were moved out the document,

Please help me understand this.  Many of the endorsements on this thread come from people stressing the value for disabled people, but the use cases document doesn’t mention accessibility or disability.  How does the proposed charter to standardize a data model and syntax address these saved use cases?  And why were they moved out of the use cases document?

> so I am not sure why some folks think this looks like is a solution in search of a problem.
I suspect Tantek is referring to the “solution” of creating a working group, not technical solutions to the use cases.  Long experience in W3C has taught many of us that unless there is a vibrant ecosystem that understands the specific problem they are trying to solve and generally agrees on what a solution looks like, creating a WG seldom leads to a successful standard.  If such an ecosystem exists for verifiable claims, and all it really needs to function better is the standardized data model and serialization syntax the proposed VC WG charter has in scope, point us to the details.

From: Katie Haritos-Shea [mailto:ryladog@gmail.com]
Sent: Tuesday, November 1, 2016 11:53 AM
To: Steven Rowat <steven_rowat@sunshine.net>; public-webpayments-comments@w3.org; w3c-ac-forum <w3c-ac-forum@w3.org>
Subject: RE: Support for Verifiable Claims


Steven,

I tend to agree with you. My business interest is in the Accessibility Use
Cases (many of which were moved out the document, but saved), some of which
I helped write. Along with those where disability and web payments
intersect. My personal interest lays in the Privacy and Payments use cases.

In the Accessibility arena, there are very real problems for people with
disabilities being able to independently verify themselves to enable access
to government and private programs, while maintaining their privacy.

​​Having worked in banking I can tell you that the web payments problems of
independent interoperable verifiable claims are paramount, so I am not sure
why some folks think this looks like is a solution in search of a problem.

* katie *

Katie Haritos-Shea
Knowbility Board Member and Advisory Committee Representative to W3C
Senior Accessibility Standards Architect (WCAG/Section 508/ADA/AODA)

Affiliation: Knowbility | Board of Directors | Austin, TX |
Katie@Knowbility.org<mailto:Katie@Knowbility.org> | 703-371-5545 | @Knowbility

Personal: 703-371-5545 | ryladog@gmail.com<mailto:ryladog@gmail.com> | Oakton, VA | LinkedIn Profile |
@ryladog

-----Original Message-----
From: Steven Rowat [mailto:steven_rowat@sunshine.net<mailto:steven_rowat@sunshine.net>]
Sent: Thursday, October 27, 2016 2:00 PM
To: public-webpayments-comments@w3.org<mailto:public-webpayments-comments@w3.org>
Subject: Re: Support for Verifiable Claims

On 10/26/16 4:40 PM, Tantek Çelik wrote:
> I want a verified pony as much as the next person, but at some point
> the framing starts to look more like a solution looking for problems
...> Tantek Çelik
> AB member
> Web Standards Lead, Mozilla

You've used the passive voice in '...starts to look more like...', but I
think you mean "the framing starts to look [to me] more like a solution
looking for problems"....

And, your perception of what is a problem (and what isn't) is colored by
your own specific position relative to the web (and society as a whole),
necessarily. For example, by your signature line, I'd speculate that, at
least in part, that position will be the position of Mozilla.

And so is my perception colored by my own position. I'm not in Mozilla. So
we're likely to identify different problems. And so with a lot of other
people, in other points of view.

The Use Cases document has evolved, first from the Web Payments group, over
a period of perhaps ten years, maybe longer.
https://w3c.github.io/webpayments-ig/VCTF/use-cases/ . Many people have
contributed. It currently holds 25 specific examples split into Finance,
Education, Healthcare, Retail, Professional Credentials, and Legal Identity.
There could be many more, but that could overwhelm prospective readers of
the document. These illustrate the breadth of what is being attempted, and
give a series of real-world stories to it.

I'm personally only strongly interested in two or three of those cases, in
the sense that they would make the work that I do easier.
For the rest, I can see that most of the rest would be good to have for
society; and I suppose somebody must feel strongly about them or they
wouldn't have made it. I've watched them being added by various people from
various life-roles that I know little or nothing about.
I'm willing to accept that these people have their reasons. And I'll stay
involved, as long as the ones I'm interested in are still accepted as valid
goals.

I agree about your example of the Web of Things and the current attack
problem. That could be included as a use case, in my opinion, and an
interesting one.

But that doesn't make the other 25 cases any less important; it just adds to
them.

Steven Rowat







>
> [1] I.e. I assume y'all have seen:
> https://krebsonsecurity.com/2016/10/hacked-cameras-dvrs-powered-todays

> -massive-internet-outage/
>
>
> On Mon, Oct 24, 2016 at 1:35 AM, Rinke Hoekstra <rinke.hoekstra@vu.nl<mailto:rinke.hoekstra@vu.nl>>
> wrote:
>> Dear All,
>>
>> The Vrije Universiteit Amsterdam also supports the Verifiable Claims WG
>> Charter, and is looking forward to contributing.
>>
>> Best regards,
>>
>> Rinke Hoekstra
>>
>>
>>
>>> On 21 Oct 2016, at 20:20, j.j.spaanderman@dnb.nl<mailto:j.j.spaanderman@dnb.nl> wrote:
>>>
>>> +1 to the Verifiable Claims WG charter on behalf of DNB.
>>>
>>> Best regards,
>>> Jurgen
>>>
>>> Van: Hakkinen, Mark T
>>> Verzonden: vrijdag 21 oktober 2016 20:08
>>> Aan: w3c-ac-forum@w3.org<mailto:w3c-ac-forum@w3.org>
>>> Cc: public-webpayments-comments@w3.org<mailto:public-webpayments-comments@w3.org>
>>> Onderwerp: RE: Support for Verifiable Claims
>>>
>>> +1 to the verifiable claims working group charter
>>> +http://w3c.github.io/webpayments-ig/VCTF/charter/

>>>
>>> Educational Testing Service supports this charter and looks forward to
>>> contributing to the work of the group.
>>>
>>> Mark
>>>
>>> --
>>> Markku (Mark) T. Hakkinen, PhD
>>> Managing Sr. Research Developer
>>> Accessibility, Standards, and Assistive Technology Research Group
>>> Center for Cognitive, Accessibility, and Technology Sciences
>>> Educational Testing Service Rosedale Road Princeton, New Jersey
>>> 08541 USA
>>> +1 609 734 5014
>>> mhakkinen@ets.org<mailto:mhakkinen@ets.org>
>>> http://www.ets.org

>>>
>>>
>>> This e-mail and any files transmitted with it may contain privileged or
>>> confidential information. It is solely for use by the individual for
>>> whom it is intended, even if addressed incorrectly. If you received this
>>> e-mail in error, please notify the sender; do not disclose, copy,
>>> distribute, or take any action in reliance on the contents of this
>>> information; and delete it from your system. Any other use of this
>>> e-mail is prohibited.
>>>
>>>
>>> Thank you for your compliance.
>>>
>>>
>>>
>>>
>>> De informatie verzonden met dit e-mailbericht is vertrouwelijk en
>>> uitsluitend bestemd voor de geadresseerde. Indien u als
>>> niet-geadresseerde dit bericht ontvangt, wordt u verzocht direct de
>>> afzender hierover te informeren en het bericht te vernietigen. Gebruik
>>> van informatie door onbevoegden, openbaarmaking of vermenigvuldiging is
>>> verboden en kan leiden tot aansprakelijkheid.
>>>
>>> De afzender is niet aansprakelijk voor schade die verband houdt met
>>> risico's verbonden aan het elektronisch verzenden van berichten. De
>>> e-mails en eventueel bijgevoegde bestanden zijn volgens een
>>> standaardprocedure gecontroleerd op computervirussen. Deze controle kan
>>> aanwezigheid van malware, zoals virussen, echter niet geheel uitsluiten.
>>>
>>> The information sent in or enclosed with this email is confidential and
>>> intended solely for the addressee. If you have received this email but
>>> are not the intended recipient, please notify the sender immediately and
>>> delete the message. Please be advised that the unauthorised use,
>>> disclosure, dissemination or distribution of information is prohibited
>>> by law and may entail liability.
>>>
>>> The sender cannot be held liable for damage in connection with risks
>>> inherent in electronic message transfer. The sender has taken standard
>>> precautions to verify no computer viruses are present in this email or
>>> any attachments it may contain. However, the presence of malware, such
>>> as viruses, cannot be ruled out.
>>>
>>
>>
>>
>
>