Char Howland: Alright, welcome everyone to the identity implemented is working group call for March 24 2022 This is our second meeting after a bit of a hiatus so Thank you everyone for joining us today, my name is Dr Holland i'm a software engineer at indicia tech.
Char Howland: last meeting Steve led the agenda as usual and introduced me as a new co moderator with the group, in addition to heather doll the CEO of indie CEO and so, in case you missed that meeting Steve is stepping into additional responsibilities and rolls his head and myself becoming co moderators.
Char Howland: The purpose of this group is to keep track at a high level of what's going on and all the different working groups, and in the Community, hopefully, providing helpful entry points.
Char Howland: For people looking to get involved, but wanting to understand the overall landscape of the groups as a whole.
Char Howland: So this is a place that aggregates links and notes and recordings from all the many media and, since it would be very challenging to attend every single one of them.
Char Howland: So today we'll plan to cover some working group status updates in the second half of the call, we will hear a presentation from Cuba shot skin on the kodiak project and last week's cody interrupt with on.
Char Howland: I will share my screen as well with the agenda.
Char Howland: Alright, and so, as usual, this is a hyper ledger call, so the anti trust policy and hyper ledger code of conduct or an effect.
Char Howland: This means that we are collaborators in this space and we make sure that anything under pen protections or mbas or anything confidential proprietary.
Char Howland: stays out of this call, however, anything, of course, that doesn't fall under some sort of confidentiality agreement.
Char Howland: And that you would like to share with the group, you are more than welcome to, and if you have an idea for a presentation we can definitely.
Char Howland: Book you for a call sometime in the future, we would really appreciate that this call is being recorded and will be posted on this meeting page later today.
Char Howland: And with that we can move on to introductions would anybody.
Char Howland: Like to introduce themselves.
Char Howland: If you're new or rejoining or just would like to say hi.
Keela Shatzkin @KeelaRShatzkin: Well, this is my first time here, so I can do a quick introduction, my name is kyla shad skin, I am a consultant at raskin systems in the health it space i've been doing this for a long time, but my.
Keela Shatzkin @KeelaRShatzkin: foray into identity and verifiable credentials is relatively new.
Keela Shatzkin @KeelaRShatzkin: But not new enough that I didn't manage to become a Co Chair of the Cardio working group, which is what i'll be presenting on later today so very happy to be here, see some friendly and familiar faces.
Char Howland: are so glad you're here, thank you.
Char Howland: Would anyone else, like to introduce themselves.
Char Howland: and other notes if.
Char Howland: If you're able to click the link the links in the chat and put your name under the attendees list that would be great so that we can keep track of who's attending our calls.
Char Howland: So I think we can now move on to our announcements, I want to start off by asking heather to introduce herself as.
Char Howland: A co moderator.
Char Howland: This group self esteem you heather.
Heather Dahl: And hi welcome everyone i'm happy to be a Co Moderator of this group i've been in this space for about 12 years now and.
Heather Dahl: I love the mission of this group because we're really talking about actual we're rubber meets the road and the challenges and also lessons learned in the successes of using hyper ledger.
Heather Dahl: code for verifiable credentials, so I want to thank Steve for asking us to come in and help support this group, so we continue on and bring a variety of perspectives and people involved in our Community, to present, so thank you sure.
Char Howland: Thank you heather.
Char Howland: All right.
Char Howland: Another announcement is the I w or the Internet identity workshop, which is in person in mountain view California on April 26 to 28 and so you can register at the link, provided there.
Char Howland: Another announcement, I believe, Stephen current announced this on yesterday's areas working group call there's a call out from hyper ledger for a revamp and the organization of documentation so it's a Google funded.
Char Howland: program connecting Open Source projects with with technical writers.
Char Howland: So Google will pay a technical writer to work with an open source community, the deadline is tomorrow so it's a bit last minute, but if you're able to get an application and i'm sure they would really appreciate it.
Char Howland: And there's more information at the link there and then Lastly, this has been announced, several times already, but just to reiterate the move from hyper ledger rocket chat to discord I believe that tomorrow is the deadline.
Char Howland: That should be 25th I believe that tomorrow is the deadline when rocket chat will be archived so last chance to make that move over.
Char Howland: Are there any other announcements that i've missed or anything anybody else wants to add before we jump into working group reports.
alright.
Char Howland: Alright, so there's a lot going on in the many working groups and, of course, we can only go into so much detail because there's so many so.
Char Howland: we'll do a brief overview and there are links provided, if you would like to investigate further we doesn't want to make sure kayla has enough time for her presentation on this call.
Char Howland: And if you attended any of these mediums you are more than welcome to jump in and give an update on the main points discussed them.
Char Howland: So let's see we can start with the main identity working group.
Char Howland: As i'm not totally sure if the meeting cadence now they've started meeting again but looking through their list of meeting notes I don't I don't believe they've met since.
Char Howland: Their February 16 meeting when Robert wiki from the human classes foundation presented on micro lectures as Steve reported in our last call.
Char Howland: let's see.
Steve McCown: I think the main identity group tends to meet about monthly give or take.
Char Howland: Okay.
Char Howland: And I think in our next call, we will hear a new update for them so thanks for that note Steve.
Char Howland: All right, for the hyper ledger in the contributors call did anybody attend that who wants to give a brief update.
Lynn Bendixsen: I was on a call but there wasn't any I don't remember anything.
Lynn Bendixsen: super significant happening there's there's a timezone issue where some people attended that call that that were intending to attend the did indie call so reiterate that the dead end collars the started.
Lynn Bendixsen: half hour earlier than the the indie contributors call used to start, and it goes for an hour and then the new contributors call as a half hour.
Lynn Bendixsen: later than it used to start only goes for half an hour, because a lot of the things I talked about her that did indie stuff the progress continues on trying to get a update to indy node so that we can do network upgrades from.
Lynn Bendixsen: ubuntu 1604 to 2004 so they keep working on that thanks.
Char Howland: thanks for that update land.
Char Howland: And yeah thanks for mentioning in the did indeed method call as well, which is held back before we're working on the implementation of the final feature.
Char Howland: Which is often self certification otherwise working on cleanup minor key factors for fantastic coverage and it's coming on well and we'll be done within the next.
Char Howland: couple weeks.
Char Howland: let's see areas working group.
Char Howland: called does anybody attend that who would like to give an update.
Char Howland: Alright, it looks like on yesterday's call the main things that were discussed, where did exchange signatures looks like PR and issue were discussed for that and then did all three credential.
Char Howland: Which is really to proving did ownership when issuing a json ld credential so I linked to a half empty document from team of glass jar in case you'd like to learn more.
Char Howland: And then on the call before that last week looks like the main discussion was on out of band invitation compression and I think hacking D from kimmy bird on that.
Char Howland: How about the areas by field user group.
Char Howland: Anybody attend that one.
Char Howland: looks like they talked mainly about development roadmap planning, specifically for reputation and continue to discussion on out of band invitations transitioning to that.
Char Howland: For the acapella group.
Char Howland: I attended that one we talked about getting ready for this year, seven for release, for you know which PRS will be included in that, and then.
Char Howland: heard from Shen Jen Gil about adding persistent queues in occupy and the future briefly about multi tenancy and using an endorser for multi tenant agents.
Char Howland: And then here's some some updates on areas shared libraries links if you'd like to learn more and investigate further.
Char Howland: Did anybody attend to areas framework go.
Char Howland: looks like they've been they went over.
Char Howland: Work updates from the previous week related to wacky work.
Char Howland: How about the FDA meeting.
Char Howland: They mainly talked about out of band and did exchange and then the 0020 release of F G F G and there's a list from their notes with items that they're resolving for the release.
Char Howland: here's some links to testing tools as well.
Char Howland: Did anybody attend the latest hyper ledger ursa working group, I guess, I guess, they haven't met as far as I can tell, since we last met.
Char Howland: Since their last meeting was February second and Steve reported on that last time.
Char Howland: All rights in the trust over IP foundation.
Char Howland: They had an all Members median on march 16 so this meeting consisted of updates from the other working groups here's a link there's a link to the White Paper.
Char Howland: as well that they are working on.
Char Howland: The steering committee as far as I can tell the last met on February 23 so there's a link to the slides and.
Char Howland: Agenda for that meeting.
Steve McCown: let's see so i'm on the Steering Committee we actually met yesterday.
Steve McCown: Oh, and I can I can get a link for for that page.
Steve McCown: And we kind of went off.
Steve McCown: We discussed a bunch of goals and priorities, but one of the things that i'd like to point out, for this group and i'll drop the link in the chat.
Steve McCown: Let me do that right now I can't talk and chew gum at the same time.
Steve McCown: let's see.
Steve McCown: What what's going on in California is there's a senate bill.
Steve McCown: That is talking about introducing digital identity credentials for high school students, so that they can then assert those credentials of transcripts and so forth, to California, universities and.
Steve McCown: So this is at the planning stage and this came out this was a discussion in the trust over IP Steering Committee yesterday, and I think this one's relative relevant to everyone.
Steve McCown: kind of their timeframe for what's going on, is it looks like before July of next year.
Steve McCown: They want to have outlined a pilot and then.
Steve McCown: By the one year later, after let's see by January 1 of 2024 they want to have.
Steve McCown: Their trust framework and best practices and so forth outlined, and so I don't know what technology that is I don't know that if that that's you know the.
Steve McCown: The four layer stack, as we know it here, or what they're planning to use, but the fact that California has a bill up to make that a reality should be of note.
Steve McCown: For those in the US you kind of know that whatever California does tends to migrate its way across the nation and.
Steve McCown: So then that's something of note that the US is doing just wanted to point that out.
Steve McCown: I don't know if they're asking for request for comments or anything at this stage I know.
Steve McCown: Trust over IP was asked for a couple of comments on it and feel free to end but you would, the more people we get commenting on stuff like that to bring our flavor verifiable credentials into into play with the better that that is so there's that link right there.
Char Howland: Thank you for sharing that.
Char Howland: And for jumping that link.
that's great to know.
Char Howland: Alright, so the Communications Committee, they met last week, and mainly discussed blood related updates the governance stack working group.
Char Howland: They met in February they're developing foundational documents to help illustrate their principles and they're also working with the utility foundry group group on layer specific governance framework templates.
Char Howland: The technology stack working group is focused on their white paper design principles governance deck specification and technological specifications and they're currently working on the tip.
Char Howland: Technology architecture specification.
Char Howland: utility foundry group Linda do you want to give an update on this one.
Lynn Bendixsen: yeah love to so.
Lynn Bendixsen: we've been spending, most of our effort, these days, working on our new document that we're trying to produce we we we had a great baseline and then we.
Lynn Bendixsen: have a lot of suggestions that have come in, and you can start tweaking and the tweaks that were small became a little bit more heavy and so we're not quite there yet on our document but we're trying to.
Lynn Bendixsen: Add into our layer one utility guide document a rubric so that people that want to.
Lynn Bendixsen: choose an existing layer one utility can look at all these suggestions we have of how to evaluate in and a guide for evaluating layer one utilities and a rubric that will help them to to choose one and.
Lynn Bendixsen: This document is got the the I, as you mentioned up the governance working group, and they have a meeting today and they have invited us, they want to.
Lynn Bendixsen: The governance, they want to start with, looking at later when utilities and they think some of the stuff we've written in that document will help and so.
Lynn Bendixsen: we'll be chatting, hopefully with some of us from that utility group today on their call for the governance work and so.
Lynn Bendixsen: that's probably enough for an overview, oh no, we have a speaker coming up, we have George gervin from velocity networks coming and they built to layer one utility called the velocity network and.
Lynn Bendixsen: The idea that is unleashing the future of careers and they'll be talking at our next meeting, and next Tuesday the 29th.
Lynn Bendixsen: that's.
Lynn Bendixsen: It Thank you.
Char Howland: that's it look forward to hearing.
Char Howland: Those updates in our next call that sounds really interesting.
Char Howland: Alright, and i'm also looking at the time.
Char Howland: So the ecosystem foundry working group they had a presentation from rightly hears from traffic, they also talked about ecosystem classification matrix.
Char Howland: That details difference differences between builders and users tools and services against the operation on perspective needs of business bottles.
Char Howland: The inputs and semantics working group.
Char Howland: is working on the alignment of dynamic data economy models concepts and technologies with the more familiar SSI.
Char Howland: The concepts and technology working group is focusing on discussing language and how to meet the audience with language that works closely with mental model.
Char Howland: That the audience already has, and then the good health pass working group.
Char Howland: This this group has several subgroups that needed different cadences so.
Char Howland: So the the link there can take you to more information on that.
Char Howland: And then moving on to the diff did anybody attend the did come working group that would like to give an update.
Steve McCown: Yes, and.
Steve McCown: We had a discussion on PR to 68 about service in points we talked about.
Steve McCown: What those need to look like we had a discussion about.
Steve McCown: Compatibility between how did comes being laid out right now and interfacing with microsoft's eye on and a lot of technical formatting issues about how all that fits together we believe it's.
Steve McCown: strategically important to be compatible with Ion and so we're we're looking basically there's.
Steve McCown: specification that we're both drawing from and we're looking at it two different ways, and so we are trying to figure out how to make that compatibility happen.
Steve McCown: Probably i'm not going to go out on a limb, because it hasn't fully been decided yet, but probably what's going to happen as well make a couple of very minor the significant.
Steve McCown: Notable changes to to did come, they should be formatting wise very, very minor but they'll move things around a little bit to where Microsoft likes them and so.
Steve McCown: Then, that will help with a compatibility and we think that's an important step for us to take so we had a discussion on that among a few other things as well.
Char Howland: Great, thank you for that update.
Steve McCown: alright.
Char Howland: We have also the different users group, this is new and it's they don't have a synchronous meeting where everybody meets at the same time it's held over a 24 hour period where people can.
Char Howland: work at whatever time they would like.
Char Howland: here's the discord like if you'd like to.
Char Howland: see more about that group.
Char Howland: let's see the diff interoperability Group looks like they had some time zone confusion last week but met yesterday and heard from trust alliance, New Zealand.
Char Howland: Sovereign foundation if anybody has any of these meetings that would like to give a quick report.
Jim St. Clair: I didn't go to any of those meetings, but I can give a report on another working group and sovereign that's interested, the group to me a chance.
Char Howland: yeah if you want to go ahead now that'd be great.
Jim St. Clair: yeah so the only sovereign foundation meeting that i'm able to make any more as Michael shay's SSI and iot working group we've been together for about 18 months and, quite frankly, I think it has been tremendously exciting.
Jim St. Clair: And and kind of represents the next frontier for decentralized identity and we call it SSI and iot but it's really about decentralized identity management at the nonperson entity device level.
Jim St. Clair: This to me is gaining tremendous momentum, and I think because of the number of head nodding, I have had talking about specifically medical device security and device security.
Jim St. Clair: efforts under the president's executive order for software bills material and the idea that if you're implementing zero trust architectures in an iot environment that means I don't trust you and you don't trust me.
Jim St. Clair: So it's a natural play I think for verifiable credentials and and cta what we're working on and starting to get into demonstrable.
Jim St. Clair: proofs of concept is what types of devices can leverage json objects and verifiable credentials for the trust framework.
Jim St. Clair: How you'd set those up with various devices things like the the industry consortium IPC has a new standard IPC 1783 which talks about device level authentication which we had a demonstration from a company that was actually building vcs in to do that.
Jim St. Clair: And then i'm carrying the conversation on in the medical iot device space as well, so I think some exciting stuff coming out of that working group and welcome everybody participating.
Char Howland: Great, thank you for that update that's really helpful.
Steve McCown: Just a quick tidbit on on sovereign the TGV and steward Council meetings, their their remaining separate groups but.
Steve McCown: We tend to meet together.
Steve McCown: These days, and there was some discussion about.
Steve McCown: pricing and features and some housekeeping things so that's.
Steve McCown: Nothing too much of a lot of discussion there.
Char Howland: Great Thank you.
Char Howland: And I will add another line for the SSI and iot group as well, so that we can keep getting this update, so thank you, thank you both.
Char Howland: For the wbc standard did anybody attend this group that would like to give an update.
Char Howland: I wasn't able to see if they had met since.
Char Howland: Since this February meeting Monday discuss did ID and did carry methods.
Char Howland: I, there are other updates or working groups anything else that i've missed that anybody would like to share on.
Jim St. Clair: i'm sorry I was juggling two meetings before but did we happen to just touch upon the wallet security working group in in depth, because they've been very active to OK.
Char Howland: OK, I will I will look into that and.
Char Howland: added a line on.
Our notes for that, so thank you.
Char Howland: Alright, if there are.
Char Howland: No other updates from the working groups, we can move into keyless presentation Thank you again so much for joining us, I know you introduced yourself at the beginning, but.
Char Howland: just wanted to give you a little introduction again since it's all such an impressive experience so keeler chef skin is a lead consultant at checks can systems.
Char Howland: and has been focused on improving health information exchange, since 2010 she's consulted for various ha ease across the US specializing in.
Char Howland: Data architecture engineering data exchange solutions workflows and operations she's involved in several state and national committee's discussing policy and technology in the HR space.
Char Howland: and more recently she's become involved in verifiable credentials and serves as the co Chair of the cardiac.
Char Howland: work group, which is a project under the Linux foundation, public health, which he is going to tell us about today so thanks again for joining us kayla and with that I will pass it off to you.
Keela Shatzkin @KeelaRShatzkin: All right, so um I think we have lots of friendly faces in our group today so.
Keela Shatzkin @KeelaRShatzkin: This hopefully.
Keela Shatzkin @KeelaRShatzkin: Not much of this will be too surprising, let me just get sharing here and we'll jump in to the presenter mode.
Keela Shatzkin @KeelaRShatzkin: Okay, are you guys still with me.
Dan Bachenheimer (Accenture): Excellent yeah yes.
Keela Shatzkin @KeelaRShatzkin: Okay, so um so as we discussed right cardiac is a project under the Linux foundation, public health, it was launched through collaboration and effort with sita who participated in donated code in conjunction with in DC out to sort of get this on under.
Keela Shatzkin @KeelaRShatzkin: Under the Linux foundation and what exactly is it and and what is it trying to accomplish so it's.
Keela Shatzkin @KeelaRShatzkin: Being able to create digital health credentials that are privacy, preserving and allow most almost, most importantly, allow the.
Keela Shatzkin @KeelaRShatzkin: The patient or the person right in every context they have a slightly different name to control the access and dissemination of their information and what's you know who they preserve it with.
Keela Shatzkin @KeelaRShatzkin: Who, excuse me who they share it with and and what exactly they're sharing and so being able to control that is really important, and also to manage the.
Keela Shatzkin @KeelaRShatzkin: Privacy across the different agencies that may also work with that individual.
Keela Shatzkin @KeelaRShatzkin: So what exactly is the network, and how does it all work I think most of you are probably familiar with the trust triangle, at this point, but just to do a quick walkthrough here.
Keela Shatzkin @KeelaRShatzkin: The the trust triangle starts with.
Keela Shatzkin @KeelaRShatzkin: The an issue or have a credential it may start with a person asking for something to be issued, but.
Keela Shatzkin @KeelaRShatzkin: In general, you need to have a verifiable credential to kick off this flow and in that scenario and in the Cardio workflow this is, for example, a lab.
Keela Shatzkin @KeelaRShatzkin: Right and most of the work in the last couple of years has been really focused on the code use case so that's what we talked about a lot, we will talk about some other use cases and a little bit here.
Keela Shatzkin @KeelaRShatzkin: But in this case, this might be a lab that did your coven test or or has spun your coven test it may also be an organization that has your vaccination credentials, for example, and they are going to verify an identity layer here, which is sort of outside the immediate realm of the cardiac.
Keela Shatzkin @KeelaRShatzkin: Focus, but is certainly a critical component here so assuming that we verified the identity of the individual, the lab or other health issuer is going to issue a credential to the in this context patient.
Keela Shatzkin @KeelaRShatzkin: And that data is issued in a verifiable credential schema that has been defined by the Cardio working group and is available on our get those credentials schemas could be further defined to contain other health data as well.
Keela Shatzkin @KeelaRShatzkin: That, then, enables the patient who in this trust triangle is often referred to as the holder to choose, with whom they are going to share that data and that might be a security tsa kind of agency, it might be the government of the country in which they'd like to travel, it may be.
Keela Shatzkin @KeelaRShatzkin: A restaurant that they want to go eat dinner at, and they can then engage by scanning a qr code, for example.
Keela Shatzkin @KeelaRShatzkin: Security connection with that verifies.
Keela Shatzkin @KeelaRShatzkin: and choose which data points that they're going to share right the verify or may have a request for certain data points that they require, and then the the holder is authorizing for that to happen.
Keela Shatzkin @KeelaRShatzkin: And all of this is based on the ability of that verify to check the authenticity of the issuer that it was issued by a trustworthy source.
Keela Shatzkin @KeelaRShatzkin: So if we go into a slightly more specific use case around Kar Diya the Kar Diya.
Keela Shatzkin @KeelaRShatzkin: Group has created several agents, as part of the ecosystem, there is a health enterprise agent a government agent verify your agent and a holder agent.
Keela Shatzkin @KeelaRShatzkin: So in the workflow that we've been solving most sort of discreetly, the health agent again this might be the lab.
Keela Shatzkin @KeelaRShatzkin: Issues a health credential to the patient that patient may present it to the government that they'd like to travel to.
Keela Shatzkin @KeelaRShatzkin: and say look I do meet your criteria i've been tested within a certain timeframe or here's my vaccination status i've also been boosted, whatever their requirements may be.
Keela Shatzkin @KeelaRShatzkin: The government agent can then say can then turn around and issue another derivative credential that says this person is now welcome to enter the country, there are a trusted person to to travel here.
Keela Shatzkin @KeelaRShatzkin: And so, that is a derivative credentials, so this government agent can act both as a verify or end and issuer.
Keela Shatzkin @KeelaRShatzkin: And the and then another verify or might be, for example, as we said that sort of gate agent that lets the person sort of off the plane or or through security so that they know that that they're allowed they meet the criteria of the thing that they're trying to do.
Keela Shatzkin @KeelaRShatzkin: And again, the the mobile agent and the the holder, in this case patient slash traveler is controlling with whom they share their data.
Keela Shatzkin @KeelaRShatzkin: The piece of the puzzle that we've added to this diagram is the schemas that I mentioned so Kar Diya has.
Keela Shatzkin @KeelaRShatzkin: implemented several schemas to support these initial use cases there, they are designed to be eXtensible beyond a specific code use case so we've been very careful and this is where there's my health.
Keela Shatzkin @KeelaRShatzkin: Expertise has come into to make sure that we're not just talking about coded.
Keela Shatzkin @KeelaRShatzkin: But there is a so there's a lab result schema there's an lab order schema if knowing that the there started the process of getting tested is important.
Keela Shatzkin @KeelaRShatzkin: There is a vaccination schema again neutralized to support any vaccine and any number of vaccines that may be required.
Keela Shatzkin @KeelaRShatzkin: There is a medical release credential to help support the idea that a patient may need to authorize the release of their information to the APP.
Keela Shatzkin @KeelaRShatzkin: That they're using and and then the last one is this concept of a trusted traveler credential and.
Keela Shatzkin @KeelaRShatzkin: As we discussed in a meeting earlier this week that specific name may may trigger some connotations for people that have existing meaning so.
Keela Shatzkin @KeelaRShatzkin: In this case, the requirements of what become a trusted traveler are all part of machine readable governance, which is another layer in the cardiac ecosystem.
Keela Shatzkin @KeelaRShatzkin: So the machine readable governance is what's controlling, for example, what are the acceptable lab tests, does it have to be negative, if it's positive does it have to be a certain number of days old or.
Keela Shatzkin @KeelaRShatzkin: or who issued the data right, that was the lab test issued by a quote unquote trustworthy partner, and that is managed, all within this machine readable governance that says sort of what is acceptable and what would pass or not pass.
Keela Shatzkin @KeelaRShatzkin: And so, this is also a component of the media ecosystem that we've been working on it was included in our latest interruption, which I will spell out for you all in just a little bit and so those are.
Keela Shatzkin @KeelaRShatzkin: Between the agents that we have on the screen here the schemas and the machine readable governance that represents what we've been building in the cardiac ecosystem.
Keela Shatzkin @KeelaRShatzkin: If we just sort of move on to what are, what are we accomplishing were allowing the patient or holder to control and.
Keela Shatzkin @KeelaRShatzkin: and actively consent to what's happening with their data and that's really important in the health sphere.
Keela Shatzkin @KeelaRShatzkin: Right and there are some additional regulations that are happening, specifically in the US that are helping to enable this specific use case where.
Keela Shatzkin @KeelaRShatzkin: patient is entitled and and should be assured access and ownership of their own information, of which they are the subject, it also is helping to provide.
Keela Shatzkin @KeelaRShatzkin: defenses against tampering so one of the participants of the cardiac ecosystem, has said that they believe up to 60% of their.
Keela Shatzkin @KeelaRShatzkin: There lad or vaccination information they're receiving from people have been altered and are frauds and so the idea that you would be able to verify that the credentials issued by a trustworthy known.
Keela Shatzkin @KeelaRShatzkin: partner and ecosystem would help eliminate that and then, of course, reducing the paper, which is how you get to tampering because photoshop is something, many people have access to, and so this allows for some defenses against that.
Keela Shatzkin @KeelaRShatzkin: When we talk about use cases and sort of expanding the the initial use case that really got us moving at a much faster rate is the covert use case and travel and tourism and kind of getting back to normal life.
Keela Shatzkin @KeelaRShatzkin: But that isn't the only use case, and there are plenty of others that we've been focused on and trying to keep things sort of neutral as.
Keela Shatzkin @KeelaRShatzkin: An ecosystem that can support a bunch of things those include, for example, entertainment venues that might maybe affiliated with the coven use case or not.
Keela Shatzkin @KeelaRShatzkin: Clinical research and being able to support those those really difficult consent requirements about clinical research would be one very clear use case there's another around sports and athlete management right, and so, for example, if you're.
Keela Shatzkin @KeelaRShatzkin: If you're in the athlete combines or you have your stats as an athlete and you're trying to get recruited that might be a really good way to have that data be verifiable.
Keela Shatzkin @KeelaRShatzkin: and have the trust layer affiliated with that and then.
Keela Shatzkin @KeelaRShatzkin: What I see as a really natural transition here is also around educational, health requirements, so we we already have in the US requirements around vaccination for school age children.
Keela Shatzkin @KeelaRShatzkin: That they need to prove to the education system that they have met those requirements or have appropriate exemptions and that just reminded me that we have an exemption credential drafted, although we have not used that one extensively.
Keela Shatzkin @KeelaRShatzkin: And so those health care health proving sort of health status to be able to tend your educational spheres, whether it's lower education or higher education, I think, is a really valid use case for these verifiable credentials.
Keela Shatzkin @KeelaRShatzkin: So one.
Keela Shatzkin @KeelaRShatzkin: trial that has been completed successfully has been on the island of Aruba again sita who was pivotal in helping to incubate and subsequently donate the code for Kar Diya.
Keela Shatzkin @KeelaRShatzkin: In heavily back to work by the CEO who's been leading the charge here as well on this pilot was implemented both on island, but also in trying to.
Keela Shatzkin @KeelaRShatzkin: Control acceptance into the island right, so they had set guard rails around requirements for traveling to Aruba.
Keela Shatzkin @KeelaRShatzkin: and improving your health status those have been fluid definitions throughout the lifecycle of code here and part of what's interesting about this implementation is that.
Keela Shatzkin @KeelaRShatzkin: The machine readable governance allows for the flexibility dynamically without upgrades to control those evolving standards so in our first implementation of this trial, for example, we had set the vaccine machine readable governance to use a field called series complete.
Keela Shatzkin @KeelaRShatzkin: Meaning did this, that the shot series might be two shots that's where we started coven, and so we might know that the series is complete if they got their second shot.
Keela Shatzkin @KeelaRShatzkin: Once boosters came onto the scene, that was no longer good enough for the machine readable government governance and so it's shifted to a model where we actually need to know each shot individually.
Keela Shatzkin @KeelaRShatzkin: And the machine readable government should analyze the package of shots because you know Johnson and Johnson plus one other may be considered fully vaccinated in certain definitions.
Keela Shatzkin @KeelaRShatzkin: were in other definitions, you need three to be considered fully vaccinated and so the machine readable governance layer really allowed us to dynamically support the trial in Aruba as things were changing and sort of shifting sands underneath us so this trial again was as part of their.
Keela Shatzkin @KeelaRShatzkin: allowing people to come on the island, but then also allowing people to do things once they've arrived in Aruba So if you wanted to participate in certain tourism activities being able to then.
Keela Shatzkin @KeelaRShatzkin: verify that that patient or excuse me traveler in this in this context had met the criteria and was considered safe to travel, that means that they had gotten the results of their covert tests, they had met all of that criteria and were allowed to engage in those activities.
Keela Shatzkin @KeelaRShatzkin: So we have held our second interrupt Python very excitingly it was held just last week on the 17th.
Keela Shatzkin @KeelaRShatzkin: And it was open to all, but we really highlighted being able to engage the hyper ledger areas community as well as the Cardio community, and that is partially because of the out of band protocols that are mentioned earlier.
Keela Shatzkin @KeelaRShatzkin: Because there is a target for the areas community to implement sort of their phase one support for out of band connections by the end of this month, and that phase one is simply to be able to accept out of band connections, as the bar, and so we wanted to make sure that.
Keela Shatzkin @KeelaRShatzkin: That Cardio was compliance with that goal and that anybody who was preparing to also be compliant in there, in whatever they were doing.
Keela Shatzkin @KeelaRShatzkin: could use our interrupts on as an opportunity to verify that component, so we had some people come to test that and some people come to test the larger Cardio workflows as well as the first.
Keela Shatzkin @KeelaRShatzkin: interrupt testing of the machine readable governance and we focus specifically on who issued the credential and who's allowed to verify a credential and that would that's sort of the first.
Keela Shatzkin @KeelaRShatzkin: level of what to control inside that machine readable governance sort of who who can play what role within the ecosystem.
Keela Shatzkin @KeelaRShatzkin: And so, this was a fun learning experience interrupt pythons.
Keela Shatzkin @KeelaRShatzkin: As i'm new to them, but i've learned that you know it's part of a hackathon kind of style here where we're not only trying to get through some issues.
Keela Shatzkin @KeelaRShatzkin: But also understand different setups and how those might interplay with each other, and so we had provided both the opportunity for.
Keela Shatzkin @KeelaRShatzkin: Anybody attending to test against reference code that had been released for Cardio but also to test between each other as participants to make sure that there was that interoperability that's really important, and I think.
Keela Shatzkin @KeelaRShatzkin: will be presenting a little bit more on on the lessons learned and things that were exposed at that interrupt Python but certainly one thing that was notable to me, which makes me giggle as a technical person right is.
Keela Shatzkin @KeelaRShatzkin: We had one thing come up where it's like well, it says it in the yeah that's what the standard is.
Keela Shatzkin @KeelaRShatzkin: But we we interpreted it a little bit differently, and so that interpretation of standards results and things, maybe not working correctly and that's the challenge around technical standards is there should only be one and everybody should follow them but isn't always the case.
Keela Shatzkin @KeelaRShatzkin: So this was rather successful, we had a quite a few people sign up we had ended up having about six different organizations engaged in participating and testing, which is great again they came for different reasons and tested.
Keela Shatzkin @KeelaRShatzkin: different components, some of them just wanted to test out of band, some of them wanted to test everything that we had to offer which was wonderful.
Keela Shatzkin @KeelaRShatzkin: And I think that the other thing I just wanted to cover again we're among friends here, but for your recording and others who might follow and.
Keela Shatzkin @KeelaRShatzkin: How to how to engage and participate in cardiac so i've put the URL for our website, which has all of the information we've been really trying to lower the bar for what, for what it means to engage, but we have a group say oh we're on the lf pH slack and Twitter.
Keela Shatzkin @KeelaRShatzkin: And our schedule for our working group meetings is the first Thursday of the month we spend as sort of a welcoming new people trying to ease the conversation into general topics around Kar Diya and covering.
Keela Shatzkin @KeelaRShatzkin: Things so that new people can come learn, and then the second and fourth meetings are technical deep dives with the third.
Keela Shatzkin @KeelaRShatzkin: Thursday of the month, focused on marketing and communications and sort of engaging more people in this Community.
Keela Shatzkin @KeelaRShatzkin: And we haven't had a fifth Thursday, since we implemented this schedule, this will be our first month with a fifth Thursday very exciting.
Keela Shatzkin @KeelaRShatzkin: So that one's a little bit of a wild card i'm just trying to set up that agenda, maybe we'll get to sneak in some demos from our intro Python participants so that would be exciting.
Keela Shatzkin @KeelaRShatzkin: And I think with that that covers sort of high level introduction, for what we've been working on, we are starting to lay out some some other.
Keela Shatzkin @KeelaRShatzkin: roadmap items that are important and those have to do with some of the things that are mentioned and happenings and other groups that impact cardiac.
Keela Shatzkin @KeelaRShatzkin: And we're hoping that we'll be able to continue to host and drop pythons.
Keela Shatzkin @KeelaRShatzkin: You know around once a quarter, we took a little longer between our first in our second but hopefully now that we're here will be able to increase that cadence a little bit as they're really helpful for everybody participating.
Keela Shatzkin @KeelaRShatzkin: So with that.
Any questions.
Jim St. Clair: I would just add to that, beyond you know the discussion around credentials for.
Jim St. Clair: health information, you and I, of course, are involved in project unify which is looking at social services data and the relationship in the social services ecosystem child welfare agencies incarceration.
Jim St. Clair: behavioral health etc and clinical information and how do we broker that exchange of information, involve credentials for patients identity as well as consent so.
Jim St. Clair: In this world of social determinants of health i'm seeing my doctor my doctor needs to understand my housing security issues, as it relates to.
Jim St. Clair: care at home or economic security issues for a 14 my medication, they may evolve a State Agency that hat or community based organization that has information that.
Jim St. Clair: isn't in my clinical record that has to be facilitated, to be shared and how Kar Diya can be a machine readable governance framework built on state regulations to say.
Jim St. Clair: This doctor can get this information from the cbl where I can send to have this information shared or you can get my health records from the Department of corrections, etc.
Keela Shatzkin @KeelaRShatzkin: Absolutely, I think that the consent use case is probably a.
Keela Shatzkin @KeelaRShatzkin: Cross sector really widely applicable use case that we could implement using the cardiac ecosystem, to help support that Dan you have your hand up do you have something you want to say.
Dan Bachenheimer (Accenture): yeah yeah face this is good we're in a bit bit more each time I won't go over the trusted traveler death in the contention with us programs but.
Dan Bachenheimer (Accenture): I did you know, since the last presentation look at your site, and you know you do reference the good health past collaborative where Jim and I and others spent a lot of time, so i'm just wondering in the interrupt.
Dan Bachenheimer (Accenture): Your the interrupt a thon I guess if you're talking about one of the things that we we tried we you know the whole blueprint was around interoperability.
Dan Bachenheimer (Accenture): And, and it boiled down to format protocols with signatures so i'm wondering if you if you and I believe you you I saw that graph which I love the tick boxes, where you take compliance to the good health past collaborative but but in terms of interoperability, did you.
Dan Bachenheimer (Accenture): Or are you using like in Aruba the recommendations of protocols signatures and formats that.
Dan Bachenheimer (Accenture): That was put forth, and if you are then you basically get interoperability so i'm just wondering what, what do you can what parameters you consider in the interoperability challenge, and how are you dealing with those.
Keela Shatzkin @KeelaRShatzkin: Well i'm gonna do my best to answer, but I am slightly more health focus than.
Keela Shatzkin @KeelaRShatzkin: i'm newer.
Dan Bachenheimer (Accenture): yeah.
Keela Shatzkin @KeelaRShatzkin: But, but I think that the.
Keela Shatzkin @KeelaRShatzkin: You know the interruptions on around when you say signatures you mean on the credentials.
Dan Bachenheimer (Accenture): yeah exactly yes, I was thinking more than a verifiable credentials, but I did as soon as you said, from the health aspect, then it becomes interoperability terms of the data that's.
Dan Bachenheimer (Accenture): well.
Keela Shatzkin @KeelaRShatzkin: Okay, oh it's both right we're trying what we're what we basically done in this in this example is is to take health data and write it as a verifiable credential.
Keela Shatzkin @KeelaRShatzkin: In us using a schema that I helped to design, based on my my background in health care, but the idea that the the credentials are signed by a trusted issuer right and that trusted issuer has been has also been anchored to the ledger.
Keela Shatzkin @KeelaRShatzkin: That issuer would have been listed in the machine readable governance as an authorized, you know authorized to be an issue or trustworthy issuer.
Keela Shatzkin @KeelaRShatzkin: to verify our side who knows, to accept them, and so I think those components absolutely were part of the interrupt Python.
Keela Shatzkin @KeelaRShatzkin: And so i'm not sure if there's a specific thing about the signature piece i'm happy to take your question and circle back with you um when i've corralled the the technical gurus on that.
Dan Bachenheimer (Accenture): No, I mean yeah.
Dan Bachenheimer (Accenture): So it was basically described in that document is your json ld plus with with bbs signatures and and things like that using wacky Pex exchange.
Keela Shatzkin @KeelaRShatzkin: So the ones that were using are a non creds.
Dan Bachenheimer (Accenture): Right okay right not json ld, and the reason is.
Keela Shatzkin @KeelaRShatzkin: That you can control the each data point at a more granular level than you can in a json ld token there, excuse me.
Keela Shatzkin @KeelaRShatzkin: schema so that allows for the support of predicate proofing on specific fields, so if you only need to know like I issue a credential that has a ton of stuff as the health.
Keela Shatzkin @KeelaRShatzkin: sphere and the holder engages with the verify or in the verify only needs to know, are you over a certain age if that's the use case right.
Keela Shatzkin @KeelaRShatzkin: And then, using a non creds you can restrict to only share a thumbs up yes they're over your age criteria or not you don't even have to share the date of birth.
Keela Shatzkin @KeelaRShatzkin: In the non credit model.
Keela Shatzkin @KeelaRShatzkin: So that's why those are I mean they they can use the other formats certainly and we've talked about that right so in trying to be interoperable in other ways, they just have some.
Keela Shatzkin @KeelaRShatzkin: downsides around being able to hit that privacy mark that we're really trying to get to.
Dan Bachenheimer (Accenture): Yes, supposedly and that's what in our like ke VI we use not credits because well that's what was available, and I understand that the bbs plus was still evolving, but that is supposed to and i'm.
Dan Bachenheimer (Accenture): Not a developer, but that's supposed to be able to support your knowledge proofs and that's why, when we were writing that.
Dan Bachenheimer (Accenture): The good health pass collaborative blueprint that's why we specified that specifically for the reasons that you stated before zero knowledge proofs and yeah because they support predicates and stuff anyhow I know we're getting into the technical deep dive that you have scheduled but.
Keela Shatzkin @KeelaRShatzkin: i'm treading and treading water I hope.
Very good, thanks.
Char Howland: Any other last quick questions I guess we're we're pretty much to the end of the time I know a lot of us probably have needed to the top of the hour, so want to give a few minutes of wiggle room.
Char Howland: But thank you again to you so much for this great introduction to the cardiac projects and i'm sure everyone watching the recording will really appreciate it too so.
Keela Shatzkin @KeelaRShatzkin: Thank you all for joining us.
Char Howland: yeah Thank you.
Jim St. Clair: Well done, thanks.
Jim St. Clair: Thank you.
Steve McCown: Thank you, great job.
Heather Dahl: Thank you, everybody hi.
Char Howland: Thank you.