Re: Using Email as an Identifier

Sorry folks- try this link <https://youtu.be/y3rJpbKZIWo>
Feedback welcome:)

*Leah Houston M.D <https://twitter.com/LeahHoustonMD>.*
Chief Executive Officer
Linkedin <https://www.linkedin.com/in/leahhoustonmd/> | Twitter
<https://twitter.com/LeahHoustonMD>
<https://www.linkedin.com/company/hpecid/>  <https://angel.co/company/hpec>
<https://www.crunchbase.com/organization/hpec-a109>




This electronic mail (including any attachments) may contain information
that is privileged, confidential, and/or otherwise protected under
applicable law from disclosure to anyone other than its intended
recipient(s). Any dissemination or use of this electronic mail or its
contents (including any attachments) by persons other than the intended
recipient(s) is strictly prohibited. If you have received this message in
error, please notify the sender or *webmaster@hpec.io
<webmaster@hpec.io>* immediately
and then delete the original message (including any attachments) in its
entirety. We take steps to protect against viruses and other malicious code
but advise you to carry out your own checks and precautions as we accept no
liability for any which remain. We may monitor electronic mail sent to and
from our server(s) to ensure regulatory compliance to protect our clients
and business.




On Fri, Nov 12, 2021 at 11:38 AM Leah Houston, MD <leah@hpec.io> wrote:

> Hi All-
>
> Our walle and credential issuing systemt ties DID's to Emails
> It's the only way we could make it easy for credential issuers to KNOW
> they were sending it to the right credential holder:
> Here is how it works <https://studio.youtube.com/video/y3rJpbKZIWo/edit>-->
> (old video from our staging environment - now in full production)
> Feedback on that welcome from anyone.
>
> Best
>
>
> *Leah Houston M.D <https://twitter.com/LeahHoustonMD>.*
> Chief Executive Officer
> Linkedin <https://www.linkedin.com/in/leahhoustonmd/> | Twitter
> <https://twitter.com/LeahHoustonMD>
> <https://www.linkedin.com/company/hpecid/>
> <https://angel.co/company/hpec>
> <https://www.crunchbase.com/organization/hpec-a109>
>
>
>
>
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected under
> applicable law from disclosure to anyone other than its intended
> recipient(s). Any dissemination or use of this electronic mail or its
> contents (including any attachments) by persons other than the intended
> recipient(s) is strictly prohibited. If you have received this message in
> error, please notify the sender or *webmaster@hpec.io <webmaster@hpec.io>* immediately
> and then delete the original message (including any attachments) in its
> entirety. We take steps to protect against viruses and other malicious code
> but advise you to carry out your own checks and precautions as we accept no
> liability for any which remain. We may monitor electronic mail sent to and
> from our server(s) to ensure regulatory compliance to protect our clients
> and business.
>
>
>
>
> On Fri, Nov 12, 2021 at 11:06 AM Kerri Lemoie <klemoie@concentricsky.com>
> wrote:
>
>> Hello all,
>>
>> There’s been an ongoing discussion in the Open Badges community about
>> using email addresses as an identifier when a wallet is not being used.
>> This is a dilemma particularly in the Open Badges community because it has
>> been using email addresses as recipient identifiers. Over the years using
>> emails as identifiers has been problematic in numerous ways especially
>> considering that the recipients don’t have control over their email
>> addresses and in the past has led to lost badges. Even still, it’s a
>> challenging topic especially because DIDs are a new concept and not as easy
>> to understand as email yet.
>>
>> The VC spec indicates that if an identifier is used in the
>> credentialSubject that it should be a URI. An email could be described by a
>> URI and also, from what I can tell, it wouldn’t be a huge stretch to use
>> did:web to point to an account that has an email address associated with it.
>>
>> Please note that I personally don’t support using email addresses or even
>> references to email addresses as identifiers (on the fence about the
>> did:web accounts approach as a bridge) but I’m curious to hear the
>> community's thoughts on this and wonder if there are any wallets that would
>> consider supporting email identifiers in some form should Open Badges
>> recipients want to move their badges to a wallet at a later time?
>>
>> Thanks,
>>
>> K.
>>
>> --------
>> Kerri Lemoie, PhD
>> Director, Digital Credentials Research & Innovation
>> badgr.com <https://info.badgr.com/> | concentricsky.com
>> she/her/hers
>>
>>
>>
>>
>>
>>
>>