rather than give you the signal. Okay. All right, I'll set. All right, thanks. Good morning. Today is Monday, February 26th, 2024. I'm Alina Bryant. I'm one of the commissioners of the Gaming Commission. This is the 14th convening of the screening committee for the executive director search. We are doing this using, the meeting using remote collaboration technology. So I'm gonna do a roll call. Commissioner Maynard. Good morning. Commissioner, oh, I just promoted you. CFO Lennon. Good morning. I'm here. And director Muldrew. Good morning. And I'm here. So all four of the members are present. We have a quorum. So the second item on the agenda, we have a number of the meeting minutes to go over. I think they were forwarded for review. Unless anybody has comments they wanna make now, can take a motion on the meeting minutes. I'm happy to make a motion. I'm going to actually read all the dates in. If something is up, someone stop me and let me know. Madam chair, I move that the screening committee approve the minutes from the November 13th, 2023, December 4th, 2023, December 12th, 2023, December 21st, 2023, January 3rd, 2024, January 4th, 2024, January 16th, 2024, January 17th, 2024, January 22nd, 2024, January 25th, 2024, and February 5th, 2024, screening committee meetings that are included that have been passed around, what we'll call a commissioner's packet that have been included in the packet subject to any necessary corrections for typographical errors or other non-material matters. Second. Did you mention the 14th of February as well, or? Those haven't been provided yet. Those haven't been provided yet? I don't think that we've completed those. No, we haven't sent those along yet. Okay. So I guess the agenda mistakenly has them on there. That would be my error on the 14th. All right, so February 5th. Fifth, okay. So commission, if anyone have any questions, comments or corrections right now? No? No. So commissioner Maynard. Aye. CFO Lennon. Aye. Director Muldrew. Aye. And I am aye, so 4-0 approving those minutes. And then the two items to go into executive session today, item three, review and consideration of selected first round candidates for the position of executive director. The committee anticipates that it may meet an executive session in conjunction with the initial screening process to review and consider specific first round candidates for the position of executive director in accordance with general law chapter 30A, section 21A8. The chair declares that an open meeting would have a detrimental effect on obtaining qualified applicants for the position. Committee anticipates the open session of this meeting will not reconvene at the conclusion of this executive session. Do I have a motion? Second. I move. I'm sorry. That's okay. I move that we go into executive session for the reasons and the matters articulated by the chair. Second the motion. Okay, any questions or comments? Okay, commissioner Maynard. Aye. CFO Lennon. Aye. Director Muldrew. Aye. NIMI, so 4-0 to go into executive session on 3A. And then 4A, we have a number of minutes for executive session to also go in. So I will read the necessary language. The commission anticipates that it will meet an executive session to review the minutes from the following 12 executive sessions. And I may be mistaken that's probably 13 because 14 is on here as well. So 13 executive sessions as discussion and open meeting would frustrate the intended purpose for which the executive sessions were convened in accordance with general 3A subsection 21A8 which was to obtain qualified applicants for the position of executive director. Public session of the commission meeting will not reconvene at the conclusion of this executive session. Is there a motion? Madam chair, I move that we go into executive session for the reasons and the matters articulated by you. Second. Any questions or comments? Commissioner Maynard. Aye. And CFO Lennon. Aye. Director Mildrew. Aye. And I am aye, so 4-0 on 4A. And before we go into executive session, is there any other business that was not anticipated that you wanna bring up that we could not anticipate at the time of the posting? Okay, so seeing none, that would conclude the public portion of today's meeting. We'll now go into executive session and thank everyone who is in attendance this morning.


Welcome to the ITU studio in Geneva. I'm very pleased to be joining the studio today by Mr. Muhammad Al-Ramsey, who is Executive Director of Regulatory Affairs for the Telecommunications Regulatory Authority, the TRA in the United Arab Emirates. And he's also, of course, Chair of WTIS-18. Hello. Nice to meet you. Welcome to the studio. Now, I'd like to start talking to you a little bit about this event. How important do you think is WTS in the overall development of the telecommunication and ICT industry? You know the ICT industry, actually, it's a very rapidly changing industry. And it generates a lot of data, a lot of indicators. For sure, I mean, you need some mechanism to capture this data, to measure it, and also to be a reference for your development. So decision makers in each country, they can rely on those indicators and see how they're developing in terms of economic and social development. So when we have an event like at WTIS that gathers all expertise from different sectors, from ICT, from policymakers, from the industry, from academia, they be in one place and they share their experience and how to gather this data, how to properly measure it, how to use it as a reference for policy development. Absolutely. This is a very, very required event. And all countries need to participate in it. Now WTIS is all about tracking the evolution of the ICT sector. From your country's perspective, how easy is it to track this fast evolving sector? Well, in our country, I mean, it was actually inherited in the vision of the country. So we have a vision 2021 for UAE in which they have different indicators and they have assigned it to different entities. So ICT is actually put for the regulator there. So we have a specific ICT that we are looking at it, how to gather data, how to monitor its development year after year. So this is actually inherited in our vision and our strategies as well. Now, the figures came out last week. Approximately 51.1% of the global population is now using the internet, is now connected to the internet. What more do you think countries can do to bring more people online? I think three issues that we need to consider on it. And I think two of them, we are all countries that are working at affordability and availability. And I think we are doing very well in those two factors. The third one, which I think we need to put more effort in it, is to availability of content. We need to develop content for other people so that they will be bound to have internet connection. In addition, how to utilize ICT to provide services to for education, for health sector, for example. And if we do this, we will increase the percentage of people who will be connected to the internet. Raul Katz, who was sitting where you were sitting today this morning, said Wikipedia, for example, the majority of the content there is in English. So we really need much more content in Arabic, for example. Exactly. Finally, what key messages will participants be taking away from this year's symposium, do you think? I think they will realize the importance of indicators and how we can work collaboratively how to collect this data, properly analyze it, and provide those data for organization like an ITU. This is for their own benefits. They can track their development. And I think this is the major key that we want to deliver out of WTIS. Well, we wish you the very best of luck with the rest of the conference. And thank you very much for joining us in the studio today. Thank you very much. Thank you.


find ones that would be particularly good to add to that playlist. Yeah. You let me know. I'll make that happen. And hang on. I'm not saying anything. I don't want to jinx it. I don't believe in jinxes, but all right, we are alive. And now I'm going to resume recording and we're good to go. Sounds great. Thank you so much for setting that up. Oh, no worries. We're looking at ways to automate that process. So one of the challenges is we sometimes, like a meeting doesn't happen. Like it gets canceled and one person shows up and suddenly the recording starts. So we were, Ryan and I are well, Rai has done all the hard work. We're looking at how to automate this so that when you start the meeting, it just happens. Here we go. And we've got awesome. Oh, that's great. Oh, you can see my screen. It looks good. I can see your screen and I see a telegram. Sam has joined us. Wonderful. Welcome, Sam. And set char to. Co host. Thank you. Hi, Tim. Hey, Tim. Make co. All right, char, you're the co host. Thank you. If there's ever anybody else you want to add as co host, just let me know. OK, great. Good to know. I generally have a policy that we turn on co host or have someone else's host because. Internet goes down. We don't want to end because one person is, you know, the point of failure. So yeah, yeah, that happened once before. Yes. Again, super fun. Thanks, you're the best. Very fun. Although the alternatives are not even probably shouldn't say that on a recording like that. Well, let's see where our speaker today is. Clay CEO of BC Gov. So let's wait until we see him on the call. Right. Hi, Maria. Thanks for joining the call. Hi. We'll get started in just a few minutes. Perfect. Thank you. Hi, Clay CEO. Good morning. All right. Let's see. We can probably go ahead and get started already recording. So that's great. Let's see. Welcome, everyone, to the Hyperledger Identity Special Interest Group call for May 4th, 2023. Thanks, everybody, for joining us today. My name is Shar Haaland. I'm a co chair of this group with Bippin Barathon and Tim Spring. So today we will talk about. We'll talk a bit about the change of this group from a working group to a special interest group and our merge with the identity working group, which we're really excited about. We'll also go over working group status updates and we will hear a presentation from Clay CEO of BC Gov on Aries Bifold and the BC Wallet. So thanks so much for joining us today, Clay CEO. This is a Linux Foundation call. And so we are following the Linux Foundation. Antitrust policy, as well as the Hyperledger Code of Conduct, both of which are linked and written here. This call is of course being recorded and streamed on YouTube. I will post the recording on this meeting page later today and I'll. Send out this page in the chat. Let's see if you want to write your name on the attendees list. That would be wonderful. Always fun to be able to see who's attending our calls. And I think we have some new faces on the call today. Would anybody like to take a moment to introduce themselves? Say, whatever you want to say, a brief introduction of yourself. What has brought you to this space? What you're working on? So we'd love to hear from any new people on the call. Sure. Hi, everyone. My name is Chan Lu and currently I'm a research manager at a blockchain research cluster at the University of British Columbia. And before I became the research manager, I was a post-doc research fellow at the research cluster. And I have a PhD in business. Folks on strategic management and organization. My research area is blockchain adoption and health care. I'm very excited to meet everyone and learn from everyone. Thank you. Yeah, thanks so much for joining the call, Chang. Thank you. Great to have you on. Sean, it looks like your hand is up. Yeah. Hi, my name is Sean Bowen. I am a community architect at Hyperledger. I've been in and out of the Hyperledger community for the last six years. This week was the sixth anniversary of Indie being accepted into Hyperledger as a project, which is pretty weird to see pop up. And I am here. I'll be on a lot of these calls going forward now that we have an identity sig. We are live streaming this to YouTube. So folks want to watch it live. Or if they want to watch it later on, we have an identity sig playlist on the Hyperledger YouTube. And if anybody needs to reach me, you can find me on Discord. Just pop a note in community architects. I monitor that all day long. But also, you know, whether you're in the Indie or the areas of the Oncreds community, welcome. And thank you for Char for leading on this. Absolutely. Thanks. Thanks so much, Sean. Would anybody else like to introduce themselves? Let's see. A few announcements worth mentioning. There is an Oncreds workshop on May 31st. Here's the link to register. That'll be great. So definitely encourage everybody to attend. Let's see. Another announcement, of course, is our merge with the identity working group and becoming a special interest group. I think it would be nice to talk a bit about what that means, what that is going to look like. Maybe reintroduce our co-chairs within Tim and myself. But before we jump into that, are there any other announcements that anybody has or any introductions that anybody would like to make? All right. Wonderful. So Tim spring and I have been co-chairing the Hyperledger identity implementers working group call for a while. And within Barathon of DLT NYC has been leading the identity working group. So we're really excited to join forces and become a special interest group instead of a working group. This fits better what we do here where it's a roundup of community news and working group progress updates, presentations and demos, rather than a technical project that we're developing together. So we're excited to consolidate the existing communities and resources of these working groups. It's really wanting it to be an entry point for newcomers, a place to ask questions, community news. There are so many calls, too many to attend all of them. So this gives the brief updates. On what is going on. So those are, those are some of the, the main goals. Collaborating across Hyperledger identity projects and collaborating with other, other special interest groups that focus on identity as well. Leading outreach to other Linux foundation identity communities. Of course we, we track updates in the TOA. Which is great. Also bringing in speakers to talk about a deep dive of interesting topics or demos. And yeah, creating a forum for members to engage in the identity conversation within Hyperledger and yeah, have a place to, to host that conversation. So yeah, just wanting to open it up. If anyone has questions about this change. We're also always appreciating feedback. If anybody has suggestions on how we run these calls, format or content changes. Would love to hear that as well. We could also probably do a brief introduction of, of reintroduction of our co-chairs. So we're going to start with, introduction of reintroduction of our co-chairs. Tim and Bippin, if you're willing. I can, I can start. My name is Shar and I work at NDCO as a software engineer. I've been, I mainly worked on projects related to Hyperledger areas and Indy. I'm an active developer on the areas, cloudage and Python ecosystem. Developing plugins and other purpose built agents and protocols. And then I'm involved as a co-chair of the Hyperledger Indy contributors working group. And of course this one as well. But Tim and Bippin, would you like to jump in with a brief introduction of yourself? Tim, sure. Go ahead, Bippin. No, I said, you know, I'm waiting for you. All right. Hi, my name is Tim spring. I'm a marketing director at NDCO and I try to help line up speakers and do any, any help in promoting the groups. So that's kind of what I try to bring to the table. Hello, everyone. My name is Bippin Baratheon. I've been running the identity working group for quite a while. In fact, the identity working group started almost at the same time as the, you know, the Hyperledger itself. When the first meeting, first hackathon get together, we started the group. It was first chaired by one of the legends in the space. Then it got taken over. It got basically, it got orphaned and I jumped in to take it over. And we launched almost all the projects that are now flourishing. We were the mothership. Indy was launched inside the identity working group and also Aries and many others. And I'm so glad to see that it's all thriving. And we also did. We also differentiate, I mean the identity implementers working group started as a sort of a tactical group for reporting on the work in progress of all the, all the work that is going on in the identity space. In terms of the differentiation between the two, it used to be that the identity working group proper was where a strategic sort of vision was presented and specific project details were presented in the implementers working group. So I'm glad to see this new life being injected into the system. And we will take it forward from there. And hopefully we'll have some presentations that are focused more on a strategic vision, especially integration. With other projects because identity by itself is not very exciting, at least for me, because it is, it is the foundational aspect of identity for all different projects, meaning healthcare, financial markets, anything you touch has an identity component. And that's where, you know, the identity working group used to focus now identity sync will have these twin paths, but obviously not very divergent. Thanks for restarting, you know, rebooting this whole concept. To Sean, who is now our new point of contact. And that would be all. I'm eager to hear what the presenter has to say. Likewise. Yeah, thanks. Thanks for that. But if history, that's great to hear and really excited to join forces. All right. Before we jump into the agenda, does anybody have any questions about the change in the working group? Any announcements or introductions? All right. So let's jump into the agenda for the working groups that we track. Did I see a hand up? Okay. Well, feel free to jump in anytime. Let's see. So usually we spend the first part of the call going over working group updates. And then we turn it over to the speaker to give their, their presentation or demo. So we will start with these, these working groups that we track. I'll send the wiki out in the chat again for those who have joined more recently. So in the indie contributors call, we, we are making good, good progress on the sovereign node line. There. So there's been some, some branch switching happening. Maine got switched to Ubuntu 16.04 and the Ubuntu 20.04 branch became Maine. This is a part of the upgrade to Ubuntu 20.04. And so there's testing happening. There's some branch comparison work yet to finish up, but working towards an official release, which is really exciting. So we're also scoping out the top priority tests on the indie roadmap that we have developed recently. And especially repo cleanup is what we're starting with. So going through open PRs and figuring out what we want to do with them, retarget them to the right branch again or close them. So that is all going well. In the Aries working group, Sam, do you want to jump in with any updates there? Yes. Sorry, I just took a bite of food. The discussion we had is pretty relevant. We're talking about transitioning the legacy use of unqualified dids and some indie projects over to did peer method two. Also a did peer method three, which is a, which is an efficient synonym for did peer two. That that will be leveraged into, into that conversion in anticipation of our continued work on defining a IP three. That's our quick summary. Very cool. Thank you. All right. Aries by fold. Anybody attend that group who'd like to report. Clay CEO, you're probably pretty involved in that one. Yes, I do. I think we're the previous one. There hasn't been any major changes. And we're working on the component, creating more components, breaking down to more components that are reusable for different use cases and different applications. Wonderful. Thanks for that update. Let's see in the areas collision Python user group. We had an update from the industry team on our website. So we've been working on, basically code with us to upgrade. Acupy to use the hyper ledger implementation of a non cred. So we've been working on revocation support. Assess reassessing the existing revocation components to figure out what we can reuse there. So. Yeah, mainly, mainly working on revocation out to some, but next we're, we're looking at working on documentation, creating a, a non creds method plugin author guide so that there's enough documentation that people can, can create their own, own plugins. And then unit and integration tests as well. Another thing discussed on that call was talking about converting and acupy deployment to use areas ascar. So Wade Barnes talked about some, some lessons learned there, which was, which was interesting to hear. All right. In the age framework, JavaScript call, did anybody attend this one who'd like to report on their progress? Today's meeting's got canceled. So I don't think there has been any major change upgrades there. I know, as you had read mentioned in this, sorry, animal is working on, on some of those individual replacements as well. And introductions to. Removing in the SDK, replacing with individual shared, shared RS and Oscar and, and all that. That's one of the major changes going on at that space. Great. Thanks for that updates. All right. In hyperledger Ursa, bit of a big announcement here. Ursa is being end of life. There has not been so much recent development or time from maintainers. There's a, some discussion on this PR linked here, if you're interested in looking at that, but it looks like the pieces that other hyperledger projects depend on with Ursa will be moved into those projects, which are a non creds, Indy, Aries and a Roja. So the CL signatures part will go into a non creds BLS signatures going into Indy and BBS signatures going into Aries. So yeah, that's, that's a big change that's happening. Does anybody want to provide any more information there or any, any questions on that? Sure. I can, I can pitch in just a little bit. So the hyperledger staff had reached out to Ursa stakeholders over the last couple of weeks to talk about the status of Ursa, the progress of Ursa and where Ursa is going, the Ursa maintainers in a discussion that we have with them volunteered that there was a method by which they could help move the dependency components out of Ursa itself so that we're not abandoning the projects that, that leverage those components, but also end of life Ursa. As a follow on, we just had a conversation, the hyperledger technical oversight committee about how we go about this in the future. And making sure that we are not, even though the, the maintainers were the ones who volunteer the PR, we're not rushing these decisions and the possibility of going to a step before end of life. So that there is some quiet period where folks can, can coordinate and make the decisions that they need to. So yeah, so, so we're going to make some, some, we're going to make some changes, not from a governance perspective, but from an approach perspective where we have projects in the future that need to go to end of life. But at the same time, we also don't want to have projects that are hanging out there and abandoned and other people are picking them up and using them as dependencies who we may not know about. It's open source. We don't know everyone who's using our code within the hyperledger projects. So we want to make sure that the, the projects that we have are being, you know, maintained and updated. And so this is a pretty national process. We end of life four or five projects last year. This is just, you know, the grooming of the projects that we have and making sure that we have active communities that are not just being built, but ongoing. And so, yeah, there's a lot of work going on right now in a Roja, Indian areas, land to accommodate for this change. And there's a going EOL. Yeah, thanks for that, that context, Sean. Can I say something here? Sure. Absolutely. When a project reaches a certain maturity.  But if the project is being used actively, and it is actually a library. I don't understand this whole concept of end of life for that project and then pairing it apart and putting it into different, you know, different other projects. You know, there are many projects out in open source that reach a certain level of maturity. And after which they are being used all over the place. Sometimes with hidden bugs, as you know, like log project, which has been around for 14 years or so. But the point is this whole end of life concept. You know, it needs reexamining from that angle. Anyway, that's a different conversation somewhere else. But as far as Ursa goes. Is the library itself being archived in any state to be used or does it need further development? Could you repeat the question? The current. Current library, which is Ursa. Can it be used? You know, if someone wants to use the current library, they can. We're putting a big disclaimer that it is an end of life archive project with no active maintainers and not being actively maintained. So, if someone wants to use the current library, they can. If someone wants to use the current library, they can. We're putting a big disclaimer that it is an art. That we have an idea. That the people are being used by the top entertainers and not being actively maintained. Use at your own risk. What we what we're working on as a community right now is making sure that the projects that we know that have a dependency on Ursa. Specifically indy Ares and roja, Roja was using Ursa. They they. and dry. We still have folks show up in the Hyperledger Discord asking us about projects, Avalon, which were deprecated a year ago. Or someone was using something in a project, they stopped that project, now they come back and they're like, hey, how come no one's updated this? Well, we end up liked it over a year ago. That still happens and we want to be really considerate in how we approach this. And then plus one to Sam, for not rushing, you're absolutely correct. We are looking from a process perspective how to make sure we're not rushing in the future. But also, we don't want to have ticking time bombs out there that we don't know about or a situation where the maintainers have moved on. And we get a critical vulnerability report and there's a scramble to find someone to work on it. So we're going to find a balance between keeping things available and maturity, and at the same time, being good stewards and being good stewards of the projects that we have. Yeah, absolutely. We'll take it upon a separate thread, Sean. Sure. Sounds good. All right. Hyperledger and non-creds. Anybody attend this most recent working group meeting that would like to report? Looks like they are preparing for the AnonCreds workshop that I mentioned at the end of the month, and getting updates from the AnonCreds, the two working group as well, talking about AnonCreds in W3C VC and JWT formats. So lots of good work happening there. See, those are the end of our hyperledger groups that we track, so on to the TOIP, and I'll try to move somewhat quickly through this, so we make sure to have plenty of time for Clasio's presentation. As far as I could tell, there haven't been recent meetings of the all-members meeting during committee or communications committee, but feel free to jump in if I am missing information there. See, in the governance stack working group, they've been giving input on a third generation TOIP stack diagram. Looks like there are some other groups working on that as well. The Technology Architecture Task Force under the Technology Stack Working Group is also collaborating on that as well as the TOIP Glossary Workspace, which is near completion. Let's see. The Trust Registry Task Force has been focusing on EU comparisons, so comparing with the E-U-D-I-A-R-F, which is the European Union Digital Identity Architecture and Reference Framework, and then TRAIN, which is Trust Management Infrastructure. So comparisons with what's going on over in Europe. See, the Trust Banning Protocol Task Force as well has been having recent meetings and workshops, which sounds like have been helpful towards making key decisions. And they have another workshop planned today. No ACDC. I'm speaking at that one, by the way. Oh, great. Today. Today, yeah. Nice. What's the main topic for today? So I'm going to propose a hybrid between the encryption and signing stuff that Sam Smith has been working on and proposing. And the relevant pieces of the DidCom 2.1 spec that allows us to gain both the advanced crypto that is desired, but also leverage the existing work, but also in a way that allows for independent layers of the stack to be augmented or replaced later as we get smarter moving forward. So there's been lots of discussions and sort of various proposals all over the spectrum. And this is my attempt to propose what I think is the cleanest way forward, getting the benefits that we want without taking any unnecessary time or having to reinvent the universe. Yeah, absolutely. Cool. I look forward to hearing about that workshop. The looks like in the AI and metaverse technology task force, Daniel Bachenheimer has been talking about biometrics. Let's see, the utility foundry group, they're on hiatus, still working with the governance architecture task force. And let's see, I don't believe the ecosystem foundry group has met more recently than us. And the concepts and technology terminology working group has been working on their terminology engine version two, as well as that technology stack working group glossary workspace. We talked about, you know, I kind of breeze through these two IP updates. Does anybody have any more specific specifics or details to add from any of these working groups?  Did you want to add anything? All right. So moving on to the decentralized identity foundation, we've got the DECOM spec working group who, I guess it was the first Monday of the month, this past Monday. Let's see, Sam, do you want to give any updates on the goings on there? Yep. We talked a little bit about the possible work with the trust spending protocol. And that we also are finalizing and actually next hour in 30 minutes, I'll be seeking approval from the Diff Steering Committee on turning that dot one release into a defratified specification. I don't anticipate any issues there. The changes made make it easier for ION to use DECOM. There was a accident of the timeline and that ION was finalized just prior to the spec. And then DECOM ended up going a different direction for it and chose the one thing that ION doesn't support for its endpoint definitions. And so a mild expansion of the spec allows for ION to use it easier. The DECOM was spec compliant before and after, but expanding it a little bit makes it easier for that community. And so that's what the dot one releases. Wonderful. Thanks for that update. Hey, Shar. I think I've been having a lot of issues the whole day long. Can you hear me now? Yes. Yes. Thanks. So I was just going to add something on for the AI and Metaverse Task Force from PIP. So yeah, we'll meet bi-weekly over there. And we're working on just there were some conversations about bi-metrics from Dan and also from Venging. We're specifically looking into something called, like something called authenticated content from, say, Adobe and other folks, like I prove. And the focus over there has been that how do you really prove any given content, like when you see some videos, something that's authentic and it's not being fabricated, given the advanced AI technologies. I mean, that's pretty feasible these days. So that's one thing. And there's also a couple of white papers going on. In fact, one of the white papers I'm working on is that identity and game payments and gaming. And because I also had an approved mentorship project under Hyperledger MISIG, which is, by the way, getting a little free organized. And that white paper is actually the topic of identity and payments, like essentially creating a mini game and then researching identity and payments and gaming and how we can extend that. So like they can essentially obviously focus on being decentralized identity and payments. Wonderful. Thanks for those updates. Looking forward to hearing more about the white papers and great. Thank you. Absolutely. So on the white paper, just to add one 30-second thing about that is that as we're working on this mentorship project under the Hyperledger products. So I'm going to be doing some joint work with Hyperledger and also under QIP to present the research contents and what comes out of that. Wonderful. That's good that you're using the mentorship program for that. Thank you. Awesome. Thank you for those updates. All right. Let's see. In the interoperability group, they've been having speakers join to talk about use cases, hearing about pain points that they're addressing and why their technical decisions addressed specific pain points and seeking to recognize patterns and information in interoperability decision making. And they had a recent, I guess, yesterday they met and had a presentation on user adoption and interoperability from Dan Guresco. And let's see. In the IoT Special Interest Group, they've also been focusing specifically on use cases and sharing of interests and experiences for the direction of work in that group. Are there any other decentralized identity foundation updates that anybody would like to jump in with? All right. In the W3C, as far as I could tell, there haven't been more recent meetings of the did working group, but let me know if I'm wrong. And in the community credentials group, they've been having their education task force call and traceability call last week. And it looks like next week they have a presentation on digital trust infrastructure for discovery and validation. So are there any other working group updates that anybody would like to give before we turn it over to Klesio for his presentation? If I may, on the CCG thing, there was actually a bunch of presentations from Puton, from folks working in implementing DI, using SSI concepts in Puton. So I'm not going to go into details, but I think you could probably share some of those things here, like if some have some links come over here, because they're actually going live on their official government level. So that's happening soon. They're also trying to basically have the airlines work with the neighboring countries like NDI and other places to actually use the SSI for the actual IDing purposes. Yeah, absolutely. Thanks for bringing that up. It looks like the ecosystem foundry group in the TIP recently had a meeting related to that. But if you have any links related to the discussions in the CCG group that you could send my way, that would be wonderful. I can also look as well. So thank you for jumping in with that. All right, let's see. I want to make sure we have enough time for Klesio. So I will turn it over to you and give the screen share up. Okay. Can you hear me well? Yes. My microphone, okay. Let me share my screen. It looks like my team. You should be good now if you want to try again. Okay, I think I will need to restart my Zoom. Okay, just give me one second. No worries. Does anybody have any thoughts from IAW that they'd want to share? Anybody in this group attend? Klesio is back. I was able to go to IAW two weeks ago. It was my first time, so it was really fun to go and connect with people in the community. There were lots of talks about AI and governance, lots of folks from the government as well joining and excited to collaborate.  So cool. That looks great, Klesio. I can't hear you, though, if you are talking. Let's see. Are others able to hear, Klesio? Oh, it was me. Okay. Okay, perfect. Okay, can you hear me now and see me now? Yes, yes. Everything looks great. Can you just tell me that you can see a browser in the middle and have a phone on the right hand side? Yeah. Okay, so I'm sharing the right screen. That's good. Okay, so hi everyone. My name is Klesio Vargel. I work for the government of British Columbia in Canada. So we have been working on an app called BC Wallet, but we have also been working on Ares by FODE, which is the upstream project for our app. Both of them are open source. Of course, Hyperledger by FODE is open source, but also BC Wallet itself. We're also making that open source. I'd like to acknowledge and thank the community. Some of you are in this call as well. Some companies like IndiceaShar, Animal and DSR, there's a number of companies, organizations around the world, who have contributed in one way or another to either by FODE, AFJ, and a number of other projects that really enable this app to work. One of the things that I'd like to highlight, I think, as Shar mentioned in the Acapai call, there was conversations about moving to Ascar. We were struggling with the mediator particularly and how it was not scaling properly, it was not performing in a satisfactory way. We have spent a lot of time investigating and doing some load testing, performance testing. That's where we came to a conclusion that moving to Ascar would be our best direction other than come up with our new mediator service. We do have a demo. At the end, I'm going to post a link that you can see. I'm going to run from a diving environment just because there is one feature that I want to highlight, but I'll paste and chat the link if you want to follow along now or later. That is, you're welcome to do so. This is a live demo, so hopefully things will work, fingers crossed. In BC, we do have this showcase where we provide a number of use cases that are represented by those two personas. One, we have a student and a lawyer. The lawyer showcases the one that we have been working, actually working. It's in production in a limited release. We started pretty small with about 20 lawyers participating in the pilot program, and we now have reached over 200 lawyers who are participating now. We expected that within the next two or three months to extend to the reminders of the lawyers, which is a total amount of about 14,000 lawyers would potentially be using the system. Also, shout out to this demo. This demo is another work in contribution from the open source community. We borrowed this from Animo, so thank you very much.  I'm not going to go in details, but if you have the time, you can read and try it out yourself. It goes through the steps of installing a BC wallet, a little bit of background on why Loss of Side of BC is going digital, some explanation why it's important for court materials to go online. We talk about Loss of Side of BC is the organization that regulates the lawyer profession in BC. They're the issuers, and they have the authority to say who is an active, good standing lawyer who are authorized to practice law in BC. I'm going to start by getting a lawyer credential. I have my wallet right here. The same process who scan a QR code. I will see if a credential offered with my lawyer membership card. In the real production, as it is right now, lawyers currently have access to a Loss of Side of BC member portal where they are able to enter their login, their username and password that they already have, and they're able to manage their own credentials. They're able to issue a credential, revoke a credential, or re-issue a credential. It's important to highlight as well that the issuer Loss of Side of BC have implemented a business rule that there can only be one active, non-revoked credential at the time. They do apply a business rule where whenever a new credential is issued, any active credential, at least the previous one, is automatically revoked. The next step is for going through this showcase, it's to get what we're calling to a person credential. The person credential, it's based on our BC services card program. That information, we already have them. We integrate with that BC services card holder app. In a production environment, they use their BC services card app and we leverage the identity proving that has already been done. It has been going around for quite a few years. We have recently reached a milestone where that BC services card app has been installed over two million users, two million devices are currently using BC services card app. I'm going to explain a little bit why we needed the both credentials. We have here in my wallet, the Law Society of BC Member Card, which tells someone that, yes, I'm an active, good-standing lawyer authorized to practice law in BC. If at any time this change, a credential can be revoked by the Law Society of BC and the user will be informed of that right away and verifiers would then have an option to request for approved number of vocation and that's where they would potentially lose access to some systems. I'll go through the use case of going through the card services branch. Card services branch is providing access to card materials online. Currently, the service is only provided in person, so the biggest difference for lawyers is that they no longer have to drive to the courthouse and go in person to access those materials. They can do now from their own office, from their own computer anywhere they have access to the internet. This is the proof request that is going to be issued by the wallet, so once that proof request is satisfied, they then have access to the system. You can see here on the proof request is showing two credentials, one the Law Society of BC, the other one is the person credential. I'm going to notice that this proof request does not ask for all information but only what is the minimum information that is needed to access the system. One other thing that from BC we have very strong privacy laws in regard to tracking and identifiers. You notice that we have made a decision and decided to not provide any unique identifier in the person credential. The law member credential, they do have a made ID but from government right now we are not offering a unique identifier, which might change over time but this is where we are right now. Right now there was an identified a need for the services that we were enabling. I receive a proof request, I can then accept and share that information and the information is accepted on the outside of the system. Some validation process, there is some other business rules here for instance they check that the first name and give family names they match. There has been a few situations where lawyers haven't updated the records and their name there's a mismatch either because they got married or they got divorced, their names hasn't been officially updated yet. There's also situations where lawyers prefer, we've noticed as well that potentially females they prefer to go by their maiden name when they're practicing law. That's a quick demo of our showcase using the lawyer credential and the person credential. I'm going to pause here for a brief second if there is any question and I would like to do a demo of another feature, the mobile verifier that has been one that has recently been put in production. I will keep an eye for a hands up. Shar, can you let me know? Yeah, yeah, absolutely. I had a quick question too so in order to access the court records you need to use the person credential in addition to the lawyer credential, is that to match the the names or why are both needed? Correct, that's an interesting question. So the both credential mimics the currently kind of a manual in person process where in order to keep or the level of identity assurance they request to provide two pieces of ID. So that'll be the two pieces of ID. So one that is managed by the Law Society of BC, the other one managed by the government by a different party. So from a security and privacy perspective the likelihood of two identities from different issues being compromised at the same time is relatively low but also allow them to to rely on the identity-proving process on BC Service Care to App and the government issue credentials are much higher than the ones from Law Society of BC. Okay, cool. Thank you for clarifying. Okay, no problem. So another thing that I'm going to demo is our mobile verifier functionality that is recently has been we've worked with the community and it has been currently it's in by-fold. So all of these features the features that I'm talking about it's in by-fold. So if you're planning on producing your own wallet those other features are readily available. I'm going to show you a trick. So if you are going through the showcase yourself later on there is an option to enable dev mode where we have access to potentially some tech preview features. If you type the version of the app about 10 times you are unlocked. You can unlock developer options and then develop options are going to enable the functionality of user verifier capability. Their truth capability is the verifier capability. This is enable connection less proof request and they use connection vital capability. We will enable you to generate a QR code to connect and you can then provide that connection proof request as well. So I will do that but actually I need to do on the verifier phone which is on this other one. So how will we do this really quick? Okay, so once that feature has been unlocked now you're going to see those two options. One is proof request and the proof request is connection to invite. The reason being that those features are gated for now we're not entirely sure how to present that in a user friendly way. Our user researcher and user experience has been doing some research and doing some analysis and prototyping about how the users would better understand this feature. From this one I'm going to send a proof request. As proof request right now we have decided to sort of embed baked in a number of proof request templates within BC wallet. Right now in bifold there's no template so it's up to each wallet distributor to define their own. For BC wallet we've decided to create or proof request template around the credentials that we couldn't have which is the lawyer credential and the person credential. So I'm going to do perhaps zero knowledge proof that ask if someone is over 18. There's a little bit of typo here. It says over 19 but it's actually request over 18. So it generates a proof request. It generates a QR code and within with my other phone I will then scan this QR code. Oh and I use a credential that I don't have. Okay I'm going to have to get that from another wallet. Okay I will decline and I'll go through the this showcase and get another set of credentials. We're currently have been working on these features kind of very actively. So one of the questions that I want to think that we're working on is the credential branding OCA branding and one of the things that we are working on is we have a number of showcase and demo credentials is we're trying to experimenting with how to make those credentials, how to highlight that they're not for production. So that's something that is ongoing. We would generate a new QR code on the left side. Okay there we go. So now I created a proof request. I can then share that information back to the very mobile verifier on the left hand side. It takes a little bit but that information then has been received. It gives that green banner if has been again all the cryptographic signature and the requirement has been validated. Therefore it gives that green banner. It should always get. We're working with the concept of maybe this is you're working a kiosk and you're trying to validate a number of people one after the other. There's always an option to generate a next one and within the next person line can then scan a QR code, share the credential and so on. And then you always have an option to keep going, generate a QR code, validate next and so on. Okay so now I will go back. The other way that you can do that could mobile verify is I can create a connection and then I'm going to be connecting first with the device and then from here we do have the messaging available. So let me go back here. So I see the message, I can type a message one side it's going to show on the other side and so on. So from the mobile verifier if I already have a connection I can send also send a proof request from here and this one will not create a QR code it's just send a proof request. I'll do the same proof request here, send this proof request. Just going to go back a little bit. I received the proof request, I'll share that information. Now the verifier will now have that information to have the option to open and see the information that has been shared. And I'll stop here. We are almost over time and I'll give a couple minutes for questions. That was great demos. Klesio, really interesting to see the flow of using your credential to access court records and the zero knowledge proof and messaging to a very nice interface and user experience. Yeah, a user experience is something that we're very committed and we have been working quite significantly is if we want to release that to the general public it has to be very easy and simple for the average person to understand and go through the flow. Yeah, absolutely. Now we're getting to the end of the hour but does anybody have any questions in the last few minutes? I was just going to add to your point, Charles. I think this is a very good to see. Thank you very much. One quick question. Do you have any sandbox that you can let other people come and play in? Yes, so I'll paste the link in the chat. That is public available. Anybody can go and play with those flows. As far as BC wallet itself, it's public available. It's available on the app stores. Anybody can download them. Great, thanks. And I think the only thing I want to add in there is I think especially when you're talking about you showing the zero, I'm sorry. Yeah, thank you for helping me with that. So the CKPs, I mean essentially I think one thing I struggle with on there is that I'm just showing somebody's name and a lot of situations have been out there because yes, I mean if you're just going to a movie or something or you can just flash a name and maybe a picture that's in it. But I think with the combination of fake IDs and with the fake pictures and all that coming in, I think the question becomes how much additional proof you need to really show that it's like actually you. You're not really showing somebody else's face, not really showing somebody else's name and things like, oh, I'm over 18 or I'm basically admitted to this place here because well here's the binary decision on that. So from our use case perspective, we begin lawyers, they follow the rules to the T because otherwise they are subjective to getting their privilege to practice law revoked, right? So there's a number of things here. There is the trust register part or the governance side about the verifier needs to know what credential from what issue they trust. So it's not just a matter of asking for an individual name or age, it's a matter of validating that information as well or maybe ask the question about do you have the name from the member card issued by law society of BC and the same thing for the person credential. I want that name from the person credential issued by the government of BC as opposed to anybody who can create a person scheme or anything like that. So it's a little bit of the governance around that, that the verifier can codify that validation on their side. As I said, we do leverage the service BC identity proving process. So that means either you have gone through the process of validate, identify yourself that you are who you are in order to get that person credential. As I said, that's what raises the level of identity assurance. And if the person, if the person has given authority to somebody else to use their credential, that's, they're already kind of, it's almost like fraud. So again, they are subjected to the existing laws in place. Right. Now I think I'll probably get my same question because I'm sorry, I also have a hard stuff, but I do have some follow up questions I'll probably circle back. And I think maybe one of the questions, Sean, I'm assuming you're going to capture these links here and place them on a wiki. Yeah, I will do that right after the call. Thank you so much. Yeah. Appreciate it. Yeah, absolutely. Wonderful. Any other questions? Sir, can you please put my information, contact information, the agenda on the wiki? Yes, I will do that. If somebody wants to reach out, maybe they can, they can reach out to my email. Yeah, absolutely. I will make sure that that is on there. Wonderful. Well, thank you so much, Claycio, for a great demo and presentation. Super interesting to hear about. And thank you all for joining the call and for jumping in with working group status updates. And yeah, we'll see you all in two weeks. Thank you, Sean. Thank you very much.


When traffic is affected by construction, maintenance or utility operations, traffic control is needed to safely guide and protect motorists, pedestrians and workers in and through work zones. This zone is the area between the first advance warning sign and the point beyond the work where traffic is no longer affected. Most temporary traffic control zones can be divided into four areas. In this part of the training we'll look at each of the areas and examine them for one direction of travel. If the work you'll be doing affects more than one direction of travel, the same principles we cover here will apply to traffic in all directions. These are the four areas of temporary traffic control zones we'll be discussing. Accidents can occur in all of these areas if they are not properly controlled. Advance warning area, transition area, activity area and termination area. The advance warning area prepares drivers and alerts them to what's coming. An advance warning area is necessary for all traffic control zones because drivers need to know what to expect. Before reaching the work area, drivers should have enough time to adjust their driving patterns. In the advance warning area, traffic control devices may vary from a series of signs starting a mile in advance of the work area to a single sign or flashing lights on a vehicle. The advance warning area from the first sign to the start of the transition area should be long enough to give the motorist enough time to respond to the control devices. For most operations, the length can be one mile for freeways or expressways, 1,500 feet for most other roadways or open highway conditions, or one block or more for urban streets. Next is the transition area. When work is performed within one or more traveled lanes, a lane closure is genuinely required. In the transition area, traffic is channeled from the normal highway lanes to a new path which is required to move traffic around the activity area. Most often, this is accomplished with tapers to close the lanes. The transition area should be obvious to drivers. The correct path should be clearly marked with channelizing devices so that drivers will not make a mistake and follow the old path. If the existing pavement markings create confusion, interim markings should be used. A taper is a series of channelizing devices placed at an angle to move traffic out of its normal path. There are five general types of tapers used in traffic control zones. Merging tapers close the lane of moving traffic on multi-lane highways where a merge is required. The spacing for channelizing devices should not be greater than the speed limit. Lane shift tapers move traffic to a different lane where a merge is not required. Shoulder closure tapers are needed to close shoulder areas. Two-way tapers control two-way traffic where drivers are required to alternately use a single lane. These tapers are used when flaggers are present. Downstream tapers are those installed to allow traffic back into the normal path. The length of each type of taper is very important and is determined by several factors. Let's look at each of these factors in more detail. The length of a merging taper which is used to close a lane is determined by the speed of traffic and the width of the lane to be closed. The two formulas for determining the length of tapers for lane closures are discussed in the manual on uniform traffic control devices. For speeds of 45 miles per hour or greater, the merging taper length should be at least the width of the lane multiplied by the posted speed or the observed operating speed. For speeds of 40 miles per hour or less, the length of the taper should be at least the product of the width of the lane times the posted speed, times the posted speed divided by 60. This is actually the high speed taper multiplied by the factor of the posted speed divided by 60. In most tables, the equation is shown like this. Most state and local manuals include tables showing the required taper lengths for various speeds and lane widths. For example, a 40 mile per hour posted speed and an 11 foot lane requires a 295 foot merging taper. The lane shift taper is used when traffic is only being shifted and no merge is required. Therefore, the taper does not have to be as long as a merging taper. The minimum taper length is 1 half L, where L is the computed length of a merging taper for the given posted speed and width of the lane shift. When an improved shoulder having a width of 8 feet or more is closed on a high speed roadway, it should be treated as a closed part of the roadway. This is because drivers expect to be able to use the shoulder in the event of an emergency. The shoulder taper should be 1 third L, where L is the shoulder width multiplied by the posted speed. If the shoulder is used as a travel lane, however, the taper is equal to L. The two-way traffic taper is used in advance of a work area that occupies part of a two-way road when the remainder of the road is used alternately by traffic in either direction. A short taper is used to slow down traffic by giving the appearance of restricted alignment. One or more flaggers or temporary traffic signals are used to assign the right-of-way in such conditions. Two-way traffic tapers should be a maximum of 100 feet long, with channelizing devices spaced at a maximum of 20 feet to provide clear delineation of the taper. A downstream taper is used at the downstream end of the work to allow drivers back into the lane that was closed. It's placed in the termination area. While closing tapers are optional, they may be useful in smoothing traffic flow. However, they may not be advisable when material trucks move into the work area by backing up from the downstream end. If a closing taper is used, it should be at least 100 feet in length per lane. Here is a table from the manual on uniform traffic control devices that shows the lengths for the five types of tapers. Let's briefly review tapers and taper lengths. Where traffic on a multi-lane highway must merge, the required length is the function of the speed limit and the lane width. If traffic on a multi-lane road is to be shifted to a different lane, the taper is one-half the length of the merging taper length. When working on an improved shoulder, the required taper length is one-third of the merging taper length. Now, when traffic is on a two-way road and it's reduced to one lane, a taper with a maximum length of 100 feet is needed. And to let the driver know that he may return to the closed portion of the roadway, a 100-foot taper may be used. If restricted site distance is a problem, for example, a sharp vertical or horizontal curve, the taper should be moved well in advance of the obstructed view. Beginnings of tapers should never be hidden behind curves. Traffic should be observed to see if the taper is working correctly. Frequent use of brakes and evidence of skid markings are indications that either the taper is too short or the advance warning is inadequate. The activity area consists of four distinct spaces. They are the longitudinal and lateral buffer spaces, the workspace, and the traffic space. Buffer spaces are open and unoccupied spaces and provide a margin of safety for traffic and workers. Although they are optional, they should be provided whenever field conditions permit their use. The longitudinal buffer space is between the transition area and the workspace and provides room for the driver to stop his vehicle if he fails to negotiate the transition taper and before he enters the actual workspace. It is important for the buffer space to be free of equipment, workers, materials, and vehicles. The length of the longitudinal buffer space is based on the stopping distance for the speed being considered. Table 6-1 of the Manual on Uniform Traffic Control Devices provides guidelines for the length of buffer spaces for various speeds. It is measured from the end of the transition area to the beginning of the workspace. Situations occur where one lane of traffic uses a lane that normally flows in the opposite direction. In these situations, a longitudinal buffer space should be used to separate the two tapers for the opposing directions of traffic to help prevent head-on collisions. Lateral buffer spaces separate moving traffic from the workspace as well as opposing streams of traffic. The width of this space is determined by engineering judgment and is often governed by the portion of the roadway which is needed to perform the actual work. Workspace is that portion of the roadway which contains the work activity. It is closed to traffic and set aside for exclusive use by workers, equipment, and the storage of construction materials. Workspaces may remain in fixed locations or may move as work progresses. For long-term operations, the workspace may be shielded by barriers including food, traffic, and pedestrians. The traffic space is the portion of the roadway in which traffic is routed through the activity area. Channelizing devices are used to separate the traffic space from the work activity at a spacing no greater than twice the posted speed limit. Every feasible effort should be made to minimize traffic conflicts with the work area. These are suggestions. Use traffic control devices to make the travel path clearly visible to drivers. For nighttime operations, the traffic control devices must be retro-reflectorized and have a large surface area. Place channelizing devices between the work area and the traveled way. Provide safe entrances and exits for work vehicles. Flags and flashing lights should be considered on work vehicles exposed to traffic and a truck-mounted attenuator be provided whenever possible to protect work crews. The termination area provides a short distance for traffic to clear the activity area and return to the normal traffic lanes. It extends from the downstream end of the activity area to the end-road work sign. A downstream taper may be placed in the termination area. For some work operations, such as a single location utility or maintenance repair, it may not be necessary to display an in-road work sign because it will be obvious to drivers that they have passed the activity area. Avoid gaps in the traffic control at work zones that may falsely indicate to drivers that they have passed the activity area. For example, if the work includes intermittent activity throughout a one-mile section, drivers should be reminded periodically that they are still in the work zone. The primary purpose of the guide sign, road work, next, miles, is to inform the driver of the length of the work zone. It should not be erected until work begins. In mobile operations, the advance warning area may be provided by signs and flashing lights on the work vehicle. Additional advanced warning signs may be warranted depending on the volume and speed of the traffic. A shadow vehicle equipped with an error display and flashing lights may also be used. With mobile operations, the transition area actually moves with the activity area and the buffer space is the area between the shadow vehicle, if one is used, and the work crew. The termination area is usually obvious to the driver passing the work vehicle. The use of a truck-mounted attenuator should be considered for mobile operations. As a review, these are the four parts of a traffic control zone. The advance warning area alerts of the driver that there's something ahead that demands his close attention. In the transition area, traffic is shifted or moved to eliminate interference with work activities. The length of the taper should be computed or obtained from a table. The activity area is set aside for the actual work to be performed to provide for the movement of through traffic and to offer a margin of safety for both workers and motorists. And the termination area tells the motorists that they are out of the construction area and may resume normal driving. This concludes the review of the four basic parts of a temporary traffic control zone and their function. In the next session of the series, we'll be reviewing some typical applications that you'll be using in your work.