2023 06 28 Aries Working Group

2023 06 28 Aries Working Group

Show Video

Stephen Curran: All right. Welcome to the Stephen Curran: June 20 eighth. A is working group. Call 23. a number of things on the agenda, slightly out of order. But I'll get that in what we get into the topics. we'll start with the marketing group update, and then I've got a pile of Rfcs. Pr. That I'd like to merge if we can get to that, and then we'll see what else we can get to. Stephen Curran: this is a Linux Foundation meeting and a hyper leisure meeting. So the antitrust policy of the Linux Foundation is in effect, as it's the Hyper Ledger code of conduct.

Stephen Curran: It is not the 20 first of June, so we've got to edit that. There we go. Stephen Curran: please add your name to the list of attendees. I put it the link to this in chat. So feel free to add your name. Stephen Curran: If anyone would like to introduce themselves or make announcements. The mike is now open for anyone to take that feel free to step up Stephen Curran: for introductions, for those new to the community that want to introduce themselves and talk about what you're doing in this space. We welcome that Stephen Curran: all right. Stephen Curran: this announcement we're going to talk about in a bit, I believe. So I'll defer that until the discussion topics. If that's okay.

Stephen Curran: release statuses. Stephen Curran: areas, cloud, Asian python, r, C. One of release 0 8 2 has been released. Stephen Curran: there is probably one more Pr to emerge into that. So we're holding off on a final 8 to release Stephen Curran: we do have an issue with Github actions related to a move to Python 3.9. basically, we're in a situation where we've got a couple of the integration tests that we're fine on 3, 637 and we're fine on 3, 8, and 3, 9 locally. But but hang on Github actions 3.8 and 3.9 without any Stephen Curran: feedback at this point. So we're couple of people that have been looking at are at a loss. We're stuck. If anyone can help out on that, we'd really really appreciate it. So let me know if you're able to help out or willing to help out. Stephen Curran: We really need to get that one resolved. we'll take some other actions. But

Stephen Curran: we need some new eyes on that one. Which is, it's just a weird one and very, very frustrating. Stephen Curran: any other announcements about frameworks or any other releases, release updates and so on. Stephen Curran: couple of things to know Ares Asian test harness. failed last night to run. I don't think any of the tests ran, or very few. So I'll be investigating that in a bit this morning. So heads up on that Stephen Curran: Aries Mediator service. We'll talk a bit about this. But we really it would be super useful to have this updated with socket, Doc, so Stephen Curran: that'd be a nice project that people are interested in in a and are looking for something to do.

We have something that we're least even. Stephen Curran: What's that Jason Leach: we when you were asking about framework releases. We did integrate if J. 0, 4, 0 by fold last week. So that's a huge win. Jason Leach: thanks to all the hard work from our friends at animal it seems to be working great. We've got one thing that we forgot to fix ourselves. But yeah, it's working great. Jason Leach: That's this, of course, got all the new shared components in it. We we're not using in the SDK anymore. We're using all the rest libraries like ask. So we asked car to interact with the ledgers and the wallet, and and on credits rs, and all those other shared components we're using as well, which work great. Stephen Curran: That's awesome. Stephen Curran: Yeah, that was The the fact that it ran, you know, even with small issues, that it ran on on a first go was amazing. So nice work on that.

Stephen Curran: Thanks, Jason. Stephen Curran: All right. Discussion topics. Stephen Curran: Helen, Alex, do you guys want to take over the screen and talk about what you're doing, or just talk about what you're doing. Helen Garneau: we can just talk about what we're doing. That'd be fine. Helen Garneau: So the first official meeting of the Aries marketing committee took place yesterday. This is I think we're gonna meet just once. Monthly. to talk about

Helen Garneau: Updating all things Aries branding, messaging, etc. So, please, you know, starting off, please encourage anybody on your team who might be interested in this effort to join us. the it is on the the groups. I/O like calendar Helen Garneau: reminders, or whatever. So folks should should get them all the information there. we also have a wiki page. just if you click backwards a couple of times you'll see it. So anyways, it's It's it pot and the Ares it. You know a a branch of the areas, Wiki. Helen Garneau: So all the information there to join, please folks join we will be inviting some speakers to come and and clarify a few topics for us. we're looking at sort of how to explain Aries externally to non people that are like not really familiar with the project or self starving identity, or what a credential is like. Kind of you know how to how to explain things

Helen Garneau: at a very kind of, you know, basic fundamental values based way. And then also how to explain to those developers kind of who are in the open source community who are more familiar with it, and that kind of thing so kind of both sides. Because I think that there's some we, you know, we've sort of decided that there's some some things that one side would want and not the other, and and vice versa. Helen Garneau: So, Alex, I'll turn it over to Alex here in a minute to talk about the questionnaire. But we would love to get some feedback from the community on this. It shouldn't just be coming from Alex and myself and But So we're hoping to get some some feedback and a simple questionnaire. So, Alex, do you want to explain what that processes and what the goals are with that effort. Alex Metcalf: Yeah, thank you. I think you said most of it. Very well. So we got the question there, out. If you see anything where there was something a question there was a survey coming away. Please take the hopefully 2 and a half minutes it will take to complete right there and then I'd be much, much appreciated. What you achieve is to is to flesh out

Alex Metcalf: understanding Alex Metcalf: all the things that you guys know in your daily interactions by Aries. So when Alex Metcalf: a person, you know is comes along, where do you point them? And one of the most important things to be telling other people about areas right now. And maybe what the challenge is people are facing when they hear about they are, what's the resistance you're face? You're you're hearing about it. And it sounds like a lot of things go into. So down some very targeted questions, probably a ranking question with a free tech space. You can just give us your thoughts and get the Alex Metcalf: core proposition of Aries together, because it's still very clear that. this clarity about the lack of clarity that we that we need to get Alex Metcalf: one solid core understanding of what the areas proposition is. Right now Alex Metcalf: I know that's quite broad, and then we can specialize it in depending on the target audience for someone looking at this. It's this, it's for exact as this, if it's for develop on boarding to to leverage it or contribute to this.

Alex Metcalf: So yeah, short version is, I think he'll he'll think it'll be next week. time scale sub to change, maybe. See a questionnaire of survey across your path, please. Alex Metcalf: You'll be very quick to complete, and we'd really appreciate your input. and they'll start to that. Helen Garneau: I would just say one of those questions that will be on there. I out sort of alluded to it is any links to videos, meet ups, recordings, blogs, papers, pages on your company's websites like anything that you that has been created to explain Aries specifically, that you links that you send to people. Maybe new developers. Come on your team and you send them. Helen Garneau: You know, a handful of links. We're hoping to create kind of a Helen Garneau: like a dashboard of sorts, a community bulletin board of like helpful resources. so start or start getting those together, organizing those? because I think those will be really valuable, that just as an ongoing effort to always kind of be updating, hey, we just had this Helen Garneau: cool event. I spoke it identverse. And this is the record, whatever like you, you know, we just just keep kind of on going. yeah, Bolton, Bart. Board of sorts with resources public facing resources. So start getting those links together. But we'll be organizing and collecting those in that as well, so if you want to be featured on kind of the main Aries page with that, with your information. that's another kind of added benefit to filling out the questionnaire.

Stephen Curran: Excellent! Stephen Curran: There's quite a lot of those in the community that's for sure having them organize with me. Helen Garneau: Yeah, like we we realize there's so much content that's already made by everybody on this call. that, let's you know. Let's maximize it and maximize visibility on it. Stephen Curran: Excellent! All right. any questions, comments for Alex or Helen. Stephen Curran: All right. Stephen Curran: Okay, next topic is, Aries, our Fc, ours. This is something we do regularly that haven't done in a while. So there's a long list of Pr's in the Stephen Curran: in the community to be reviewed. have I got it right? Okay, you can. People can see when I scan back and forth across my screens.

Stephen Curran: Say, yes. Stephen Curran: yeah. Good. Thank you. Sorry about that. I just wanted to make sure Zoom was working the way I thought. Stephen Curran: let me do one thing before I can share this Stephen Curran: Change anything to an editor copy link. and I'll put this in chat as well, in case anyone wants to go through it, and I'll add it to the really quickly Stephen Curran: should have done this before. Sorry about that, but I want to get it into the notes, so we don't lose it. Okay, Stephen Curran: alright. So we're gonna play. Let's merge. I'm gonna keep in this view because I've got links and things to show 7 89 at clarify. So I'm gonna what I'm gonna do is, just list these off and then go through them. What I'd like to do is get to some sort of resolution on these. and ideally we either merge them, close them or identify questions to go back. Stephen Curran: So definitely need your feedback and and input as we do this.

Stephen Curran: so looking forward to that is is what I'm looking for. So 789 is adding a clarification to it to the thread Rfc. About the handling of an empty thread decorator. So basically, this is a a clarification Stephen Curran: as noted. some frameworks may send over a till the thread empty. Stephen Curran: which causes Stephen Curran: other frameworks, possibly to crash, to, to throw on exception, or even to reject a message when a when an empty thread decorator comes in. the simple messages don't do that. Don't send those over. If you're gonna have an empty one, just don't even send it. But if if someone does happen to send one over. Stephen Curran: The framework should be defensive in their handling of it. Shouldn't reject the message. Simply ignore the the decorator. So that's the advice in that. So if I come over here to look at the change. Stephen Curran: it's it's a simple clarification, saying it's not recommended. may send an empty thread. Aries agents, receiving a message with an empty thread, must gracefully handle such a message. So that's the the clarification any comments or any questions about merging this.

Stephen Curran: We've had some conversation on this couple of suggestions that maybe to make. If you're going to put a thread in, then you have to put the thread id in but we don't want to make that a required as noted. So we think all of the 3 of the frameworks. Now handle this at least a Vcx and go. We're not sure of their status. Stephen Curran: Any concerns about merging this one. Stephen Curran: All right. I'm going to go ahead and merge this one. I think this is probably the only one we'll do on the fly, because the rest will require updates. But we have at least accomplished that Stephen Curran: probably should have put in the notes.

Stephen Curran: that we what we did. Stephen Curran: Oops. Stephen Curran: Okay. I'll try to keep track of the status as we go. 7, 85 is another one that I put in based on

Stephen Curran: activities in the in in, in the day to day work going on. in this case, with by full the by full team. revise the well-known goal, codes Aries well and Aries, well, build again a clarification. Stephen Curran: relation rel is a relationship in this case. So the Ares well and Aries well, build Stephen Curran: indicate that the goal code is to build a relationship. Stephen Curran: there was a line in the in the item to say, these should not be used when just establishing a did-com relationship, but that actually happens to be exactly what we need it for. Stephen Curran: the change is just to remove that restriction, and since sometimes that is all you need. So let me get to that change. 785

Stephen Curran: shoot! I can't see the Stephen Curran: where I've got things placed. I can't see it, so I'll just Stephen Curran: to that to say. 7 85. So I stay on the I wasn't even helpful to do that. But anyway. So basically a minor change that says this should not be confused with building a Didcom channel Stephen Curran: and and in fact, it could be used for a a a Dcom connection itself is not the relationship, but would be used to carry out interactions to facilitate the relationship. And so basically, this is saying, this may be accomplished by establishing updating or deleting a Dcom message connection Stephen Curran: that provides a secure communication channel. Stephen Curran: basically saying. it's okay to use the school code for that purpose. It's not specifically banned

Stephen Curran: any questions or concerns with that Stephen Curran: right? Stephen Curran: No comments. Are we okay to merge that one? Stephen Curran: Any objections? No objections? Okay. Stephen Curran: I'll mark that as to merge Stephen Curran: Then I wanted to throw up this basically, these the goal codes and and other Stephen Curran: events are needed to Stephen Curran: deal with user experiences user experience. So the this one came about because of activities on the BC wallet. we need gold codes Stephen Curran: to fine tune the ux, so that an inventor. An event occurs that trigger some behavior in this case.

Stephen Curran: lacking a goal code on the connections. mechanism Stephen Curran: the BC wallet is now assuming that after a connection is established, something else will happen. either an offer of a credential, or perhaps a a presentation request. Stephen Curran: In this case this. This issue came up because there was no other action other than we just wanted to create a connection. But there was no events, no logic in there for the wallet to use in in making that user experience distinction. Stephen Curran: So a, we need goal codes, to help out in the user experience. So we need to define new goal codes and use them in places where they're enabled. Stephen Curran: also brings especially the concept of done in an action so that we know when we're done. This is one sticking point that we've seen. And we ask people to think about as they are developing wallets and things which is, once you get to Stephen Curran: an interaction with another party, and you get to the end of it. How do you know you're at the end of it, or

Stephen Curran: or that the other party is going to continue on with some other step, and so coming up with the concept of done is something. that the the BC wall team has been thinking about and trying to figure out how to accomplish, particularly with goal codes. Stephen Curran: any feedback on that would be of of interest in any other experience in in developing. And too many user experiences would be good. Stephen Curran: Okay. Stephen Curran: they vote for anyone comments and we'll jump to 784.

Stephen Curran: Oh. Stephen Curran: just so that one while we go. Stephen Curran: this is a a an interesting one. basically, as you can see what it does is there's a table in the revocation, notification. V. 2.

Stephen Curran: that says, Hey, here's the type of revocation, notification. It is the the type of credential and an examples of the format. Stephen Curran: This one adds, in addition to Indian on price, as just plain and on threads and uses an example of it, did as the as the mechanism, the identifier for the credential held Stephen Curran: by the Stephen Curran: by the holder to say, Oh, this credential. This specific credential has been Stephen Curran: has been deleted or has been revoked. Sorry. So that's the purpose of Rfc. 721. Stephen Curran: it's it's hard to tell whether this is a clarification or a minor update. I would lean towards this being a clarification. note that this is still in the proposed this Stephen Curran: 7 21 is still in the proposed status, and the actual current revocation. Notification is 0 1 8, 3, which is a bit problematic. But that's for another day.

Stephen Curran: it kind of implies. If you're adding another revocation format, it implies that you're going to have a different handler for it. You're going to. You're going to get this message, and it's going to say a revocation format. And you're going to handle it with one way with an indie and on credits, and another way with an on press. so a bit of a clarification or a minor update. Stephen Curran: any comments on this one. Stephen Curran: Anyone run into this or or have an issue.

Stephen Curran: any concerns about merging this. I think this is a a pretty straightforward one. It's a doesn't really matter, since it's still in the proposed state whether it's a clarification or minor update any concerns with merging this Daniel Bluhm: no concerns with merging this, but a a comment on the subject, at least that I think we should basically just treat this like Daniel Bluhm: the did. Spec has the Method registries when there's a change to the Method registry. It doesn't change the did course. Okay. Daniel Bluhm: yeah, I think this is a similar change. So I I think we're, I think we should be good with Daniel Bluhm: making these sorts of modifications without Daniel Bluhm: needing to rep the specification for the Stephen Curran: thank you. Stephen Curran: Thanks. Okay. all right. On to the next one, which is 780. Let me jump to that one Stephen Curran: so that I'm ready.

Stephen Curran: Okay, we have a entire brand new Rfc. with this one. I think this one is pretty straightforward. We have had a few people review it. Basically, this says. Stephen Curran: when you are issuing a credential Stephen Curran: and Stephen Curran: particularly for images and perhaps other data types in those attributes that you're issuing. Stephen Curran: This recommendation is to use a data. URL, Stephen Curran: for those unfamiliar that's it. That's an image.

Stephen Curran: that's not what I want it to do. It's trying to click that button. Stephen Curran: So a data. URL, looks like this, which is, you've got an attribute called a photo. And then the data. URL looks like this. Stephen Curran: data is a hard coded. You've got the the mine type

Stephen Curran: an optional semicolon and base 64. To say that the data is base 64 and code it a comma. And then the actual data. Stephen Curran: And so this particular data, URL, is that image that I I you saw slightly earlier on the screen. So this is a itf, rfc, 2397. Stephen Curran: so I think, and I think the the There's been a few people read through the Rfc. Stephen Curran: Others are welcome, but I think it's ready to merge. Stephen Curran: Interestingly, another use of it is, Json can actually just put in this. The data type is Json, and either base 60 for it or not. but that would help in places where, for example, in a non credits, where you want to have an array. you cannot have an array in and on credits. Stephen Curran: so Stephen Curran: not not a valid not you. You can't do that because of how the and On credit signature works so you can't have an array of data elements. But you could have a single attribute. That is the array. and this would give an indicator for a holder to say, Oh, by the way, this is is Json data, and they might have a chance at being able to display it in a reasonable way rather than just dumping a bunch of Json on the screen.

Stephen Curran: So lots of flexibility in there. There was a discussion about whether this is an Aries level, or should be a credential formats. Stephen Curran: issue with the at at the specification level of credential formats, like in on credits, or the W 3 Cbc format. since those looks like I had a since those do not deal with pretty much. Don't deal with the data. I don't think it's appropriate personally that that those go in the and on credits you can put whatever you want. those and on privilege W. Threec. Doesn't care what Stephen Curran: kind of data or or or the format of the data. And you put in the attribute. Stephen Curran: so it it's really up to you. it just makes things a whole lot more flexible and easier to use, easier for things like holders to be able to display data. If a data URL is used particularly for that photo use case. I think that's one that's going to come up a lot and needs to be there

Stephen Curran: any comments other than Colton's comments in the chat about this one. Anyone want to say anything about it? Stephen Curran: Any objections to this being merged. Stephen Curran: and that could be, you just want to be able to read it before it gets merged to make sure that the Rc. Is complete. Stephen Curran: Have to put these in capitals.

Stephen Curran: Okay. we're gonna go with that Stephen Curran: 768 is the proposed legacy peer did method. So I'll jump over to here. Stephen Curran: not going to be as easy to do this one. But let's see if I can just get rid of that and 7, 68, Stephen Curran: and see what the changes are. So this is was proposed as a way to deal with unqualified unqualified

Stephen Curran: did using. sorry. Yeah. Unqualified Ds that are being used in peer-to-peer relationships. Basically in Dcom. we since have Stephen Curran: updated. And Stephen Curran: should this should not be merged, the latest solution is we would adopted Pier 2, and did pier 3 Stephen Curran: and transform unqualified kids, which is what is talked about in this method Stephen Curran: into did pier 2. And then subsequently into did Pier 3. So in code the did do that was shared in the end, as the unqualified did, and then transition encode, that as it in Pier 2, and then subsequently encode that

Stephen Curran: period to into It did pier 3 Stephen Curran: since we already have the did, Doc. So I think this one is to be cancelled. Stephen Curran: Any objections to canceling this one? Stephen Curran: Somebody make a comment just for the fun of it. Hyperledger Community: Not even that comment. Stephen Curran: perfect! Stephen Curran: 7 55. this is a very large one. one that I think is now ready to merge. one that I've created. So And I've done a few presentations on this one.

Stephen Curran: so Stephen Curran: The background for people who have not heard. But I've talked about it. Lots is Oca is a Mecca oca for Aries uses and the overlays capture architecture, specification Oca in a way that allows us to make credentials beautiful by adding multilingual support and issue. We're branding to the display of credentials. Stephen Curran: which is particularly useful in holders, in wallets and things. So this has been incubating for a very long time. And we've been making minor adjustments as we've gone along. I've given updates presentations on what Updates have been made as for things we've learned while implementing it. Now I'll talk down at the bottom here. Stephen Curran: Since the last time I presented this, and we talked about it. Only 2 changes have been made. the addition of a display of a stacked view in the style guide itself, so that was assumed, but not actually displayed in the style guide. So that is now there. Stephen Curran: And we've added a data element called watermark to the Meta overlay, and that is used in particular, for when Stephen Curran: showing a non production.

Stephen Curran: credential, which for developers happens a lot So putting a watermark on so the difference, can a a difference can be seen between a Stephen Curran: a production and non production? Stephen Curran: credential in a wallet. Stephen Curran: how they work. Excuse me, that's gone on is Aires by full. Now has an Mpm. Model that is published on on Stephen Curran: public shared on the Npm. Repo called Hyper Ledger areas, Oca that implements the pulling in of a

Stephen Curran: an O. C. A. Bundle for giving credential and and Stephen Curran: grabbing the data and using that data for the display. Stephen Curran: and there's also a repository created in BC. Gov. Called Ares, oca bundles which implements a a a way to publish.

Stephen Curran: oca bundles. Anyone can submit a Pr Stephen Curran: of an Oca bundle with appropriate data associated with it. That data gets humanly verified gets checked out. And as long as the the Stephen Curran: yeah, the the rules are followed that it is actually Oca bundle and that the bundle points to existing identifiers. it will get merged. And anyone can use this as they wish. Stephen Curran: so with all that are we able to merge this? Any objections to merging the Oca for Aries and the seventh, and it comes along with a Rfc. 756 Oca. For area style guide. So both Rfc's are included in this Pr.

Stephen Curran: I'm not hearing objections. Stephen Curran: Anyone want to comment on this whole idea, the lunacy of it Jason Leach: great. And I think we're we're also thinking about trying to make this work for the web. So we had a conversation at our last by full user group meeting. Jason Leach: Because we want to make like this, this will. This package will work in in by fold. So react native. But we also want to see about adding support for the web, so that if you're making something like traction or your own Jason Leach: a thing. You can have the same look and feel that you would get in the wallet. So you can. I understand how it's gonna look when you release your credential. Jason Leach: If you've got any interest in that, feel free to find us in the bifold channel that Keith would be Jason Leach: champion championing that endeavor. Stephen Curran: I'm just gonna show off the Oca. Explorer, but I don't have it.

Stephen Curran: Andy but but it is an example in this repository. we have a published github pages that displays it. Stephen Curran: Okay. that is to be merged which makes for an easy next one. which is 740. Stephen Curran: I did so. 7, 40 is an update of the read me of the overlays capture architecture. Rfc, 0, 1, 3. basically. On that one. Let me jump to that one. Stephen Curran: Whoa! That doesn't look right.

Stephen Curran: Or is it sorry about this? oh. there it is Stephen Curran: so this so Stephen Curran: there is a Rfc overlays. Stephen Curran: Rfc, 13 is called overlays. And basically what this Rfp or Rfc was is a definition. An early specification of Oca. Since then the specification has been moved

Stephen Curran: into the Human Classes Foundation, has its own spec, has its own repository, has its own working group. so the fact that we've got an early version of the Oca. Spec in Aries does not make a whole lot of sense. So as part of the previous one Stephen Curran: of 7, 55, and with the agreement of Paul is that I basically have updated Stephen Curran: Rfc. 13, to say, retire. and so Stephen Curran: I, there's no need to merge this pr, and we can just close it, since since the update does not make sense. The the specification is published elsewhere.

Stephen Curran: Any objections to merging this and retiring this? Stephen Curran: All right. Jason Leach: I believe that is the last one of the easy ones for me. Stephen Curran: so oca, this one was written in Stephen Curran: 2019, this Rfc. 13, as you can tell, it's very, very new. Since then, although Stephen Curran: this was there. as a, as a as an Rfc that was proposed. It basically was merged as a proposed but never updated or or never move to a higher status. Stephen Curran: Paul Knowles and collaborators then Stephen Curran: took the entire specification and just opened a new specification at Human Classes Foundation. And that's where the The Oca. Spec resides, and we've got pointers to that in the Oca. For Aries.

Stephen Curran: pr Stephen Curran: in this one, and we've got in the in the where we retire. 13. We also point to Stephen Curran: this work, has been moved to that organization in that repository. Jason Leach: Got it Stephen Curran: that makes sense cool. Stephen Curran: Next one is a a new Rfc that adds push notifications as Stephen Curran: expo protocol. So there is. this is mobile, specific push notifications between a mediator and mobile walls. Say, Hey, I've got a message for you.

Stephen Curran: There's some administrative work. If we do want to merge this one. And there was a question raised by by Sam that has not been answered. Stephen Curran: this is 745 But other than that. I am not qualified to comment on this one, and and so would suggest Stephen Curran: anyone with Stephen Curran: that expertise. Take a look at this and and add a comment on this this

Stephen Curran: does. supplement 6, 99 and 7 34, which are other forms of push notification. Stephen Curran: fcm, and atns again, I'm not. Don't know enough about it, so I I can't comment on this. Can anyone? Has anyone looked at this? thinks this is ready to merge? Stephen Curran: It looks complete to me, and so I'd be happy to merge it. As a proposed. Tim Bloomfield: I haven't actually read this, but it's a thought that jumps to my head, and probably maybe Tim Bloomfield: not correct, but Tim Bloomfield: e it for an Rfc like this is technology specific, like expo versus azure versus firebase versus. I just wonder if there should be a not, I don't know if it can be, but more more agnostic or or it's okay to have this technology specific. Rfc, so it's really Stephen Curran: yeah. It has. Has anyone implemented notifications.

Ryan Koch: Florida, but not in this. not using this for the Paul. Stephen Curran: what what do you do? Ryan Koch: We were just adding a metadata property to the Ryan Koch: did call messages that would say, if it was right or not, and then checking that it's kinda it was not a very good. Stephen Curran: This is more specifically for push notifications for a mobile app Stephen Curran: as opposed to the messaging. Colton Wolkins: So, for instance, when the mobile app is not connected to the mediator directly, then the mediator can push some form of notification to the mobile app while the app is offline. Stephen Curran: Yeah. Ryan Koch: yeah.

Stephen Curran: Okay. I think the recommendation here would be to See if we can get a session. at an upcoming meeting to to discuss notifications and and where we are with this. Stephen Curran: and have somebody who knows what they're talking about. Lead that discussion. So we'll see what we can do about that. Colton Wolkins: Yeah. And the comment about the different types of protocols with like firebase, etc., makes me wonder if Colton Wolkins: I I don't know if there is. But if there should be a more generalized

Colton Wolkins: method for for, like Rfc for push notifications that allows for Colton Wolkins: the different mechanisms out there to be implemented. Stephen Curran: This is a matter of interest. How come there's 4 or or there's 3 I would have expected to see. Stephen Curran: So there's expo fcm, and and that that other one Stephen Curran: Aps.

Stephen Curran: how come 3 when there's only 2 mobile operating systems? Tim Bloomfield: Well, expose their own? that's not That's what I'm saying, that's part of that's probably react native. That's an explo native solution. Stephen Curran: Okay, it does it cover both OS's. Tim Bloomfield: I I believe, so as does as does firebase and maybe export calls to the other ones. I'm not sure. I mean the fire based. Universal azure is universal. and there's others out there, but those those are the most popular. Tim Bloomfield: I've never really looked at the expo implementation. Now.

Tim Bloomfield: I think most of the world uses Firebase. Tim Bloomfield: You can also use the. You can also use the native. If you just wanted to push notifications for apple, then you could just do that Tim Bloomfield: as well. Yeah.

Stephen Curran: okay, okay, thank you. Stephen Curran: Well, yeah, let's do this one as well. I want to get to the end of this. We've done almost enough. We're almost to the end. Stephen Curran: 744 is Stephen Curran: adding a timing capability to the mediator. anyone with mediator experience. This is is dug into this. Basically, this is saying. Stephen Curran: How long and recipient is willing to wait to receive messages as they are arriving. So the the generic Stephen Curran: pick up protocol says, give me, M. Messages that are queue, you know, whatever messages are queued up to a maximum of M. and then Stephen Curran: the mediator would say, Oh, I've got some, so I'll I'll I'll send those across. What this adds is. if there's less than M. Then I'm willing to wait, and milliseconds for more messages before

Stephen Curran: before sending. So if you've got none in the queue, I'm still gonna wait. Stephen Curran: you know, 3,000 ms to see it more arrive, because as a holder. I'm expecting more to be coming, or if there's 10 in the queue and I request 20, then wait Stephen Curran: some seconds to see if more messages arrive. Stephen Curran: I I don't know the utility of this Stephen Curran: happy to see it merge, since it's an optional one, and there is an implementation, and it was found to be useful. Does anyone else know if this is a useful feature? Colton Wolkins: Just from my perspective, this seems more applicable to when the agent is connected over Http rather than say, web sockets. Colton Wolkins: And Colton Wolkins: yeah, basically tell, informing the mediator.

Colton Wolkins: how long is my connection time out? Stephen Curran: Yeah. Stephen Curran: So it's a more graceful way of doing it rather than just having a cut. Stephen Curran: Okay? And the clients basically saying, Please give me a bigger batch, if possible. Yeah.

Stephen Curran: might help at minimum to have Stephen Curran: have that. Stephen Curran: Okay? Stephen Curran: I'm gonna skip past a couple of these Stephen Curran: the rest of the. So we've got a few more to do. perhaps next week, just to finalize these Stephen Curran: other Pr is very old. I'm gonna try to get them just close, because I just think they're too old to to look at. Stephen Curran: And last thing I want to do is a pitch for a proper Rfc website. So this is something that could go into the marketing. so alex might be useful here. I I spent some time doing the acupy.org website. basically using M. Docs, material as a default. My process was just to create a new repo, add welcome content for the repo, and then

Stephen Curran: a script that copies all relevant content. in the occupy. It was every nd file into an appropriate structure Stephen Curran: on the new static website. Stephen Curran: And then just a manual process to update that website nice to have with github actions. So Stephen Curran: the categories would be something like welcome an administrative page to say, you know, the life cycle of Rfc's and how to submit an Rfc. And what the process is. Stephen Curran: but then this is the really important a. I. P. One would actually have a list on a clickable website, not a Github Repository with a bunch of readings. But you could actually go through and see all of the A. I. P. One and a. I. P. 2.

Stephen Curran: in a nice published form. Stephen Curran: as well as you know, a column of other Rfcs that are, you know, in different in in proposed states. So I think this would be a much better way for people to be greeted by as Rfc. And be a much more comfortable way for them to read them. So I throw that out there. I've got it on my to do list. If anyone wants to help out or work on that with me. Stephen Curran: Let me know. I'm more likely to get it done if if someone's pushing me on it. So

Stephen Curran: I'll throw that out there. And with that we'll end this part of the discussion with just a couple of minutes left because I wanted to hit a couple of other things. Stephen Curran: Any final comments from anyone on that section? Stephen Curran: Awesome. Stephen Curran: Okay. mediators. we did have the presentation last week. Lots of good stuff in there. in Dco has

Stephen Curran: open source socket Doc. Awesome work on that which I think this is a a total game changer, and how to construct scalable mediators. so I think this is really great work. Stephen Curran: so mediator, Stephen Curran: basically turns it from being the the mediator from having to worry about website. It's just simply having to worry about sending and receiving Http messages so much easier to make completely scalable. So Stephen Curran: next will be As I mentioned Harry's Mediator Service Ams. the updated to use socket, Doc. I think that's the way to go. So we'll see how that goes if if people are doing that work, or or just or what becomes available for that. But I did want to highlight that in Dco. Has open source, that repository that we talked about last week.

Stephen Curran: encourage people to Stephen Curran: address it or or to use it. Stephen Curran: Last topic. I wanted to go over. And Alex and Andrea, I'm glad you're here. There's Stephen Curran: I like to highlight 2 things that have been commented in the did peer spec. So 2 issues were raised. So one of them was airy errors in the example. So a clarification is needed. the specification is about hex encoded shot 256 Stephen Curran: in attempting to do that it implementing. Did pier 3 in Aries vcx. This issue was raised so really good if we could take a look at that Stephen Curran: as well Daniel Bloom posted notice of a couple of inconsistencies in did. Pair 3 that I think should be resolved. Stephen Curran: I thought Daniel merch this a little quickly. We explained why, but I didn't think we had quite enough review. So it's not surprising to me. And I think it's not a problem for us to do that. But basically the the simple is removing the dots because the other methods don't have a dot

Stephen Curran: in in between the 3 of the the method number and the rest of the did. And then use multi base multi-codec hash. So we know exactly what hash algorithm is being used and hash, algorithm and and base encoding of the data. So again, I think those are are 2 wise changes to put in. Stephen Curran: Alex, you're here, or Daniel Bloom, you're here. If if one of you could put those in. I I was going to do it, but I really don't know enough about the multi base and multi-codec hash to explain it. Stephen Curran: I did notice that there are multiple shot 2 56 algorithms. And so I think we have to be more specific. Of which one. And I wonder if that's related to the other issue that was raised. Stephen Curran: So I throw that out to others.

Stephen Curran: See, Daniel's not on the call anymore. He was on earlier. But So he raised at it. Alex, thank you for taking a look at that. That'd be awesome. I'd really like to get that as clean as possible and keep that updated. I would note that Stephen Curran: One of the Pr's that was recently moved, merged in the did pierce back was to add, was to remove the Stephen Curran: big red text warning text. Stephen Curran: so that has been removed from the specification. there used to be some morning text saying, Yeah, should you really be using this? And and we really think this has the did peer Stephen Curran: spec in the did. Peer method has a lot of valid use. so we did not like the fact that there was this Stephen Curran: kind of ugly red text where no replacement was particularly available at the time, so really good to see this that update made.

Stephen Curran: and with that that covers all. I wanted to go over. Oh, highlighting one! Once more I went through this added a couple of issues. Timo posted a migration. Doc, for unqualified dids, moving them to qualified dids. again strongly encourage people to read through that. Take a look at it at comments via issues Stephen Curran: into a about the document. I. I found it a a very useful one, and and Stephen Curran: good one to review. Stephen Curran: and with that I will stop sharing and give anyone a last second to Stephen Curran: respond. Make any comments. and then we'll wrap the meeting up. Stephen Curran: Excellent. Have a great day. great rest of your day depending on where you are. Take care of folks. Bye. Jason Leach: thanks, Stephen.

Hyperledger Community: thanks, everybody.

2023-07-03 15:20

Show Video

Other news