Submind YouTube summaries
Thumbnail for CA2SIG Standards WG call - 2026/08/11

CA2SIG Standards WG call - 2026/08/11

Watch on YouTube

Video summary

The CA2SIG Standards Working Group call focused primarily on the development and refinement of a blog post outlining the vision for the Accountable Impact Commons lab under the Linux Foundation Decentralized Trust initiative. Kit presented an expanded outline designed to clarify acronyms, define long-term goals regarding impact commons, and establish the lab's identity within the broader context of W3C ontologies and decentralized trust. A key discussion point involved practical next steps for establishing a professional online presence; specifically, the group agreed that registering a memorable domain name was preferable to using lengthy GitHub links. Consequently, Kit purchased the domain accountableimpactcommons.org, which will be hosted on GitHub Pages with permission from Bri Jones, providing a stable landing page that can evolve into a full website as resources allow. The conversation also addressed community engagement strategies and technical standards for data integrity, particularly concerning carbon accounting and greenwashing prevention. Jeff highlighted his work on digital twin modeling within the coffee supply chain to demonstrate how structured ontologies can accurately track greenhouse gas emissions across complex Scope 3 scenarios involving IoT devices, shipping logistics, and agricultural practices. The group discussed integrating existing indicator and methodology ontologies developed by Jeff's team into the main lab repositories, ensuring that data units are standardized to prevent misleading claims about climate impact. This technical rigor is essential for securing funding from European institutions and banks that require verified environmental metrics before offering favorable loans or investments in green projects. Administrative matters included updates on personnel availability and meeting logistics due to external factors like severe weather. Jeff explained his absence during the current session as he was sheltering in a basement office building following tornado warnings in Chicago, while Alonso apologized for missing parts of the discussion due to illness but confirmed he would return after two weeks. The team decided to defer certain detailed planning sessions until later dates to accommodate these absences and ensure productive collaboration when all members are present. Additionally, they resolved communication channels by connecting on Discord rather than creating a new Telegram group, aligning with existing Linux Foundation practices for project support and direct messaging within the decentralized trust community.
Read the full video transcript
Hello kid. Hi. Hi. Okay. How are you? >> Oh, I'm good. Zoom Zoom just offered to take notes, so I was saying yes. And uh we'll see what happens. >> Okay. I think the um Yes, the the I think the the the the LF LFDT setup also does that. >> Oh, really? Oh. Oh, yeah. >> If it's because you click someone clicks every time, but let's let's see how that works. >> Okay. Yeah, at the top of my screen I have a this meeting is being transcribed message. >> Yes. >> So maybe that's LFTT or maybe that's me. I'm not sure. But hi Alonso. >> Hi Alonso. Uh I must just apologize for Alex. He just let me know he has a terrible migraine headache. So, he's going to take some pills and get into bed. >> Oh, >> but he asked us to carry on to carry on without him. Uh, he did send agenda. So, I think we can just uh we can just look at that. >> Yes. Um, well, I think maybe let's let's let's let's get on. We don't have to take the full hour if if if we if we don't uh we don't have to. So, let's let's just see if um what we have. Can I can I share my screen? Um um I think this this first one is something that Alex put on the agenda. I'm not sure if you saw the correspondence. >> Yes. Um but I think he he is he's if he could join today unfortunately can't. So Alex arranged to speak to him what is our time 3:00 on Friday but I think it will just be a a a preliminary discussion. So, we'll we'll just meet with him and then and then see where it goes. If anyone of you two would like to join, I can just uh include you in that. Uh I'm not sure if it's even needed. I don't think it's uh um but you can say I can I mean I can if if if it looks like 4:00 p.m. GMT + 3 which I think is a bit early on your side also kit maybe that's okay for you. Yes, on Friday >> Turkey as well, >> right? Well, I could possibly join that. >> Okay. You know what? Let let me let me let me just if there's a if there's a um I see he and Alex, they are corresponding. So, let's just see if it's finalized. Uh you know, you'll I'll just make sure that you also have the invite. But I think Alex will will will take the lead in that one. So, let's let's um let's let >> It looks like a nice opportunity. >> It it does. Yes, it it it does. Um I think the the the we have to think about the practicalities and and who can do what. But but it it does. I mean if uh it's the type of thing that we wanted is that that that people use our framework and build on that and so forth. So that is actually what we were after. Um so let's see how that develops. Um >> Alonsu >> I I cannot find the correspondence for for that. I believe >> uh I I I saw you being included. I wonder if it on I'll tell you now on what it's on your me.com email. Um >> I think you were CC there. >> No, it's I I don't I don't see it. But anyway, um I'll I'll look for it afterwards. Okay. If if if there's a if there's a a meeting, I'll I'll just forward you the invite >> and if you can if you can join, you know, if it's I think it's early on your but if you can join then then do so and then >> it's done. I fored it. >> Okay. Thanks. Uh, thanks uh, Kit. >> Thank you. >> Okay, I think Kit you, uh, worked on the on the blog post, so maybe we can look at that now. Do you want to do you want to take the screen? Um, sure. I'll uh, let me see. How should I do this? Um, >> I'm stopping on this side. >> Okay. Um, let's see. Let me >> Does it allow you to to to share the screen? >> Um, well, let me try that first. Yes, it does. Um, well, let me move some windows around because I actually have it on a very large window. Let me move it to my laptop and that will work better. And so now if I share Okay, here it goes. >> Okay. Um, this is that uh that rise up site that I I told you about. And I mean, actually, here are uh settings. I always have my stuff in dark mode, but maybe it's better to switch to light mode for this. >> Yes, I I can see the screen, but there's there's nothing on the screen. >> Ah, okay. Then now I that's what I was afraid of. Uh, hang on a minute. Let me >> That's what you call dark mode. Yeah, that is dark mode, isn't it? Um, okay. You are screen sharing. Can I change? One moment. No. I see. Okay. Well, then hang on. Let me stop share for a moment and move this back. It seems to want to share my big screen. So, uh, >> okay. So, now I think you see a white page with text. >> Yes. Thank you. >> Okay. Let me uh make this bigger so it's [snorts] readable. So this is the um the riseup site that uh we use for uh quick uh quick text collaboration. And um yeah here you can see my name and a color. If somebody else start editing then uh you will get a color and you can fill in your name. But it's all it's all open uh and uh it's kind of security by obscurity you could say because there's no login or anything but uh it's perfect for uh temporary texts and things. >> Yes. So below is the original outline that we wrote with some notes that I kind of expanded on and uh I sent that in an email. And then here is the uh yeah the the [clears throat] unfolded outline so to speak where uh I uh I made sure that I got every point in the outline. And so there's things like an announcement and in the announcement we expand all the all the acronyms so that they can be used uh later with an abbreviation. We talk about a date. We mention the name the impact column or impact commons which reflects our long-term goals. And yeah I don't know if we need this but we also have the uh the GitHub repositories on there. And then just for people who aren't familiar with us, there's one paragraph about the AIAO which is uh uh taken from uh the verbatim from another another document and it links to the the ontologies on W3D just so that people know uh what the larger context is. And then we go into the Linux Foundation decentralized trust. And this is a quote from them. That's what they call themselves. And so I said for us the the key word is trust. And the the provenence of our software is critically important. And here is a quote from somebody, but I don't know who. In the in the outline there's a T there. It says T. I thought well T could be trust or it could be Tim Burners Lee. I'm not sure. But I put the quote in there because it's a nice quote and yeah whoever it's from will credit them appropriately if we know. And then I yeah quickly talked about it having the it genesis under the the Linux Foundation as the uh the standards working group. Yeah. >> So then we go into why a lab and these are more or less the points that we put in the outline. It signals our intent to continue building and yeah structured collaboration and we want to support a community and this is why we chose the name accountable impact commons because we view the resources as belonging to a larger community. And then yeah, quickly mentioned that it can open up funding avenues and it's on the road to the becoming a formal project. And for the how I basically copied existing content from uh from other sources. So I I made a couple of minor modifications but this is all all known. So uh this is how it how it works, what it enables. And I also mentioned the initial release which was back in December and we'll have a a link to that. And the what is something we have to we have to think about because uh this is where we describe the products or services. And so I start by saying that some of us are available for consultancy. uh but at the same time we're working on uh documentation and user resources and they'll be under the lab and also plug the same academy which is uh in uh development and yeah we don't have our our GitHub uh pages site up and running but when we do we can link to it and we can uh show the the road map that has our plans in timeline form. And then yeah, you mentioned in the notes that we're planning on developing indicator and methodology ontologies and we'll be using uh S SSO. So that's [clears throat] in there and then there's a call to action and this will look familiar too. This is from the uh existing page. Um, and I link to the GitHub guides so that uh people can just jump immediately if they're interested. And we request that they share the results. So this will be at the uh that registration page that Alex made up. And then yeah, at the end there's a contact. And so if our website's up and running, we can link to that. I put this in there. I don't know if it's true, but if there are other LFDT members, maybe they can message you directly. And I also suggested in the email that maybe we want to set up a Telegram group. That's that's kind of common with with uh software software apps and things that there's the telegram group where people can go and uh inquire for support or something but that's to be decided as well and uh well that's the end. So yeah I mean here are the questions. >> Yeah >> I mean I also thought we could register a domain accountable impactcom.org or if we wish, which really would be better than promoting this long link for the lab because this is memorable. You can say it to somebody at a conference, but this never Oh, sorry. I switched uh switch tabs or something. Oh, actually, I clicked the link, didn't I? Yeah. One moment. So the idea of registering a a a memorable domain I think is a good idea for for our our group and the content of it would be exactly the same as this. Um it would be this. I mean it would just point at it via via the uh the GitHub pages thing. But you can you can point a custom domain at a GitHub pages site. And actually Abby and I are doing that right now for the the Shane research site. And then yeah, these are other links that I will insert later into the into the text, but I didn't want to insert them now because it makes it uh yeah, it makes it uh messy and noisy. But these are the other links that'll that'll go in. So, these are the the three IDs and the shape. >> Um, thank you, Kit, for for writing it. Okay. I' I've been out of this world the past two weeks, one in bed, and I I just couldn't uh help you as I promised. Okay. >> But thank you for doing it. It's it's it's quite good. I have uh some u recommendation with in with sema rather than than saying that it's just how is it can you move forward up where you have sema um where do they Here >> there it is. >> Okay. Rather than saying a short for semantic sema is sign in Greek. Ah sign in in Greek. Okay. Very nice. That's that's where it it it that's why I name it Sema. Okay. There are some other interpretations but they are not esoteric but but not relevant here. It's a Sufi uh ceremony in Arabic. It means to listen okay and to hear. But so it it has a whole connotation around the origin which is sign and that's that's the first comment. Second, if you scroll down to uh to the telegram recommendation. Okay, let's say that a way of messaging within LFDT well without within Linux Foundation it's a discord channel. Ah okay. So every project every group uh every lab has a channel in Discord. Okay. So we don't we don't have to to do a um a telegram group. So chat for chat >> support and direct messages is uh via the the discord channel the LFDT discord channel. Okay. And then you also had some other place the this org uh the or yeah that um something we something all of the labs at LFDT have the possibility of having their own web page. Okay. And so that would be the web page that we referred to. Okay. If >> if we register the domain, that would be a good idea to register the domain and then use that domain in a in a lab hosted in a lab web page in a GitHub lab web page. I'm looking I'm looking at that. Uh I think it's available. >> Yes, it is. I checked. Well, >> and it's about $10 a year. So, I can I can I can I can buy it for us. >> Okay. And once you have that domain, then um look at the GitHub web pages for the lab >> and then the process because we we did that for learning tokens with the domain with the understanding on how to do it. You would need some permission from Bri Bri Jones. >> Okay. Would you if he just redirects? Maybe I Maybe it's nice to do it, but I mean it's not Oh, but let's let's speak to him. >> The advantage of having it at at the at the GitHub lab site is that we don't need a server. >> Yes. Yes. Yeah. Know that is very that is very handy. Well, then yeah, you need a special uh it's not permission, but I don't remember how it's called. It's just saying to Ry, we have this page, we want to link it. Okay. And those those were my only three three comments. Sema, Discord, and the web the GitHub web page. All the rest is great, kid. Thank you for doing. >> Okay. Um, on my side. Could you uh um provide a link to the Discord channel? >> Uh I think I'm not actually I'll have to check that myself, but I I think there's a way to link to a channel with a URL. And then for anybody who does have Discord or does use Discord and has an account, then that takes them directly there. But no, no, I'm sorry. No, that's wrong. You have to join the Discord first. Okay, never mind. >> But that also means someone has to someone has to monitor that. >> Oh yes. So I mean >> why don't we use what's what's already there and what they use. Okay. It's called the Linux Foundation uh decentralized trust. Okay. And Okay. Let's see if I can invite No, I don't have you. Uh, how do I find you, Kit, in Discord? >> Um, well, my username is Kit Blake. Um, so you try that. >> Yeah, just like everywhere else. >> No, it said uh no results were f found. So, how how Yeah. >> Okay. Let me add you. No, I I'm I'm lost. I'm not operating at my full capacity which is it's it's always low but now it's lower. Okay. So basically if if you are in Discord um go to Linux Foundation decentralized trust and in that community let me see if our lab already appears or not. Because if it doesn't, then we should ask for it to be there. Uh, I'm looking at my phone. No, I don't see the labs. Okay, hang on a minute. I'm I found a a Discord. I'm trying to join it. Do you see this the discord? I'm >> No. >> No. Okay. Well, because I have multiple multiple windows and so I guess I'm only sharing one window. >> I'm seeing you doing the puzzle there. >> Oh, okay. Well, then we're in. Hang on a minute. Uh, okay. One moment. Let me get my Discord. >> And while you're doing that, I'm just paying for the domain quickly. >> Okay. We'll have to figure this out. it uh I already have I already used Discord and now it says that my address is already in use which is true. Um so there must be another way to join but I don't know what. Well, let's let's uh on once you you get into Discord, I can look for you at you as a friend and then once you are friend I can but you already found LFBT. >> Okay, I I found you Alonso. So, uh, >> okay. >> Let me good. >> Yeah. Okay. So we are now connected on g on discord alonso that's uh that's done. Okay. And probably, let's see, probably I need to these are all the labs on the left, right? I don't see I I don't see the labs. I don't either. I see lots of them. >> I see the projects. I see the projects. The incubating projects. >> I see special interest groups, community groups, and working groups. >> Okay, we'll search for it. uh should be there because in fact I just got a an email this morning saying that I have not posted recently in learning tokens and they are you know pulling my ears [laughter] for that you know being reprimanded who know but okay that's the that's the official channel of LFDT. >> Okay. >> Okay. And then in the GitHub um in our lab GitHub repo, there is the possibility of having a web page with the domain that Christian bought. >> Yes. So I've I've already got it. So, so once we have the pages up, I can just uh we can just speak to to Ry, but I think it will just work if you just give it it as the forwarding address. So, if you go to that URL, it just forwards to it just forwards to the GitHub pages >> and we can and we can have a very simple landing page for the time being and that's the one that's linked to the GitHub rep. >> Yes. because it would be host it would be hosted there and over time we can develop that landing page into what is necessary whatever is necessary >> can you remember of your head the address that that is on now >> no you're asking me I don't know the the the GitHub address of the lab. >> Um, I'll find it. Uh, I'll find it. Can Can you look at that? Okay. You have the accountable impacts, >> right? >> Oh, it was it was G semantic frameworks. GitHub. >> Not anymore. >> Not anymore. It's been updated. So we have it that's that's very good. We have it in the GitHub and in the lab name accountable impact comments. Good. >> Exactly. >> And so there the domain that you bought is exactly the same name just.org, right? >> Yes. Yes. >> Good. >> That's great. So let's let's build a very simple landing page for that domain and once we have it then we ask how do we connect it here. Okay. Let me just put the address in the chat here. I found it >> everyone. account impact-com uh yeah so GitHub pages so opening the uh to so setting up the GitHub pages is the next technical thing maybe Alex or myself can look at that at some point um and and then uh connecting the connecting the the domain I've just I've just purchase this the domain. So I think that's a that's a clear path here. I just want to this transcription is going to make a note. So let's let's update when the transcription comes. Um >> great. >> Yeah, this is from my side. Thank you. I I think it's it's uh uh it's it's it's it's well written. It's like to the point, but everything is there. Um, yeah, I really like your your your concise uh but effective style. Uh, it's uh I'm I I I tend to be long- winded, so uh it's refreshing to see someone get to the point uh in such a nice way. Um >> yes, >> would you would you mind just uh I think I'm sure I remember you you you shared the um the uh the link to that to that page in the email, but would you mind just putting it in the chat? Um so maybe maybe after if >> Thank you. If there's just a um a word here or there or something that that one of us can put in then then we've got it. Um okay. Um Ali, you you mentioned you were you were sick. Are you feeling better now? There's a very strange flu here. A lot of people have it. And uh I was in bed for two weeks ago, I was in bed for the whole week. >> Yeah. >> And past week, I'm I'm up, but I never take medicines, but so I have to take them and they they really slow me down. Okay. So, just what what I did for the logo, that was the last thing I was able to do. >> Okay. Yeah. So, I'm I'm late in in all my my uh >> Yeah, but we're not going to pull you We're not going to pull your ears like some other [laughter] remember I had an a German grandmother [laughter] [clears throat] >> and she used she used to do that and I don't know how you call this. >> How do you call this? >> Oh, yeah. >> Knocking. Yeah. Knocking. [laughter] >> Yes. Yes. Yes. >> Knock your head. >> Omar would do that. >> Always. Okay. But that's the way some are. >> Fine. >> Okay. Let's see if we can if we can analyze a few of these other of these other points. We spoke about the LFX crowdfunding. I haven't paid any further attention to that. I'm not sure if Alex has. Um, let's just keep it on the on the agenda. C, can we just remind ourselves what we said were the next were the next step there. What I think was the next step, it it follows like we're doing with burning tokens because uh this came from uh our la our mentorship. Um and we're working on it and and we're late. Um what we have to do is we have to budget what we're going to ask. >> Oh yes. >> For the crowdfunding. >> We have to budget and and link that budget to the liberals. >> Yes. Yes. I remember that. And that and that that also uh the this the the the road map step is also related to that >> the step the item five. >> Yes. Just in terms of practicalities, in the next month, I'm going to go away at the end of the week and I'm going to be traveling for two weeks and I'm not even taking my computer with me. So, I'm I'm I'm out of circulation basically for the next Yeah. for for for for two, let's say, for three weeks. Um Okay. And um so I'm also going to miss the next the next the next meeting in two weeks. I I think Alex is here so you you can go on without me but so I'm not going to be able to give to pay attention to this for about a month. Um well and and and and and I know um yeah so so if we can keep it on the agenda um if someone wants to to run with that but I think the um what we maybe should do is then let's say in in in in four weeks from now that we take a part of that planning in this meeting and that we just do a do it bit by bit or maybe that we just get a get a outline and then we just uh someone does a little bit of homework and then we come back again. Um so those because those deliverables and that road map all of that goes together but realistically for for me I can I can I can look at it in a month from now. Um so if we just uh you know if we can erase like that um Alonso was there any communication around that ISO or is that's also one of >> let's just keep let's just keep it there and when the opportunity arises we communicate >> please. Um, and I'm sure these other things as well. The next the the Sema Academy. Um, the the Sema Academy has a lot of of uh general descriptions about potential courses that I did some time ago. So, the the the proposals are there. Okay. Maybe what I would suggest is that we select which is the first >> course to to to work on and I can take those frameworks and with AI turn them into something more uh concrete. No, but we have to go through that proposal and say yeah let's go this way or that way among the possibilities that are there I think there were at least uh I don't know remember six or nine >> should is it is it worth discussing in 10 minutes now or should we >> maybe just look at them and as we did with the with the logo Let's vote on on on which one to to explore. >> Okay. So So we we we take that one on on on um >> Yes, please. >> on the email as well. >> Please. >> Okay. And then I think that that that C will will will will um resolve itself when we get there and then ask Jeff to give overview. Okay. When Jeff is back, we can we can arrange with him. He's here. >> No, I'm here. >> Oh, Jeff. Sorry. Sorry. >> I came in a half hour late. >> Yeah. If you have We [clears throat] were in the basement of the office building because another tornado. >> Oh, no. >> Another one. >> Yeah. Look on Look on US Radar Chicago. You see a It's the weather here is ridiculous. I'm moving. >> Look for the yellow brick road. >> Yeah. It's just every day there's storm warnings. But yeah, be on your get internet look at US radar and then just look at the Chicago area and you'll see these horrible storms that just came through. So we're in the basement for a half hour in the office. >> Horrible. >> No, I was referring to the Wizard of Oz. >> Yeah, I like the Wizard of Oz. But yeah, >> that's that's where the tornado would take you. >> That that'd be that would be fun. Get get your black your red shoes and and be ready those >> to to meet them. [laughter] >> Well, you you have to be a pope for our gender our gender. The only one the only one that uses the red shoes >> was the pope, you know, >> for the previous >> Oh, we're gonna I was listening to Yeah, it keeps Yeah. zoom into the National Weather Service and you'll see um horrible weather. I'm not seeing anything on this thing. What is this? >> Yeah, I I'm looking Yeah, I I see it here on my side. It looks uh >> Yeah, there we are. >> Yeah. Yeah. >> All that red horrible storms. >> Sure. But but but but Jeff, while you're here and we're thankful. >> I was listening to you. I've been on here a few minutes. I I listen to you guys what you're talking about about the boat and everything. So yeah. So whenever you if if whenever you're ready for uh for um if you want to if you want to uh you know speak about your your implementation again then then you know we'll just schedule some time for that when so I [clears throat] I redid some of the architecture and there's a demo written in Python that does a few things but um um it's kind of getting into the summer so I was gone for a couple weeks in Northern Michigan away from this weather but um um I can there's a couple presentations one I can do the architecture which I kind of did once also um I was going to submit this I it e um have you seen that blockchain um >> yes Yes. Yes. >> So, um I got a bunch of stuff going on in assets, but it's still just me. But I'm afraid right now to put out on our website a call for people interested in it programming and so forth because I'm not organized enough yet. But um the ontology piece um is so important. Although I did have to change the model the data model last week as it's built out that data model is changing. So relationships between data are changing because of um the way carbon accounting wants to store data and the blockchain. Um you know as you're getting IoT data long story short getting IoT data every 1 second or so forth they can't store blockchain obviously everybody on this call knows why. So how do you aggregate it and put it in? What are the standards? What are the audit standards? So there's a lot going around and that's also part of the ontology. So, I would s think in the middle, a month from now, the middle of September, uh, when it's cool here and I don't have to hide in the basement all day. Um, do you want me to do a presentation to this group? I prefer to do one to this group first focused on the ontology aspects of the digital twin and then um then the architecture. I don't want to go too deep in architecture because um there's also the Linux Foundation is looking at this and saying can you in your um architecture can you make it less generic or have a generic copy and then have one that shows the advantages of using LFDT products fabric for your blockchain all the security and so on and so forth. So, um, anyway, I'm doing that. I took a portion of it. I put on, uh, I'm the manager of some LinkedIn sites. Some of the LinkedIn sites have over a million members. I stuck it out on this one site and it got 620 downloads. >> Sure. >> I don't know where it's going. I track it, but it was it was probably like a fifth of what um what it's going to be. And I saw a bunch of mail in my mailbox. We had about 15 or 16 which is unusual. So it's probably people asking questions about that. But um I don't want to divulge much in the ontology. Is that a correct approach until we're um well that's a question that I have for everybody is as I'm building this digital twin out and I get questions about it and people want to see it. Do I promote the ontology at this point or do I just steer away from it at this time? >> I think you I think since we've since we've we've published what we've published, I think you can you can you can safely say you've used that as a basis or you've made reference to that. Uh and and um I think the the lab is the lab is out there, the um the accountable impact comments lab. So I think you know you can you can safely refer to that and to I mean it's it's it's your your interpretation of that or your use of that. So that is that is for you to decide how to how to share that. But but for the for the work you know that that we have done we we we welcome you know we welcome sharing and reference and and so forth through that. Um, >> okay. Did you see the ver did you see the um copy that myself and Alex put together a few months ago where we have all the data from the digital twin mapped and we showed ontology reference and a graphical form and knowledge graph and then we then I made a copy of that and placed into that all the Linux I mean the digital twin data and all the relationships and myself and Alex put that together a while ago I remember that. is. >> So, that's been changed a little bit, but um that's that's more of a knowledge graph. It's not um in a written format. Actually, I don't even know how to write it in a written format to be honest with if anybody's interested in how that works, get it to me. But, um I'm going through it on different levels, the ontologies and all the relationships. And so um you know I think with carbon accounting just from a carbon accounting standpoint that's sig there's a lot going on out there with it e about data and properly reporting data standardizing data um making sure that units are correct everything that has been describing you know our last our meetings over the last year there's still a lot of concern around the data especially around um accuracy of data to prevent people from greenwashing. Um there are a lot of especially European companies and banks who will give um lower interest rate loans or or uh >> fund funding of things around climate change but um they're having issues with um keeping units straight. I still see stuff that I get on some online stuff saying supply chain did this with their trucking operations and they've removed um 20 and I go 20 what? 20 CO2 tons of CO2 CO2 equivalent. Is it all just CO2? That doesn't make sense. What about methane? What about nitrous oxide? Especially nitrous oxide. Um and well is that so has that been normalized to one unit or not? So um especially coffee digital twin is reflecting coffee farmers from Ethiopia, Canyon, Colombia and the farm itself has a big greenhouse gas emission footprint from use of soil and use of fertilizers which release N2O which is a I think it's remember 300 times more potent than CO2. And so >> and so um a lot of that's still going on right now but um I've forgone the Python build out. The Python buildout right now is just a screen that collects a lot of IoT data puts the data model together. You can create the data model. So um I get hold of David Boswell and Tomas. You know you guys know Tomas, right? >> Yes. >> He's in Europe. Yeah. Yes. >> So, so Jeff, if I mean if when when you are when you are ready for for to to show us some of those concrete work then you can just uh you can just for the upcoming meeting just put that on the agenda. >> Okay. and then you know for whatever upcoming mean just put it in the agenda you know and then we'll we'll we'll we'll you know it'll be great for us to discuss that just from myself and Alex side um we are we are working quite hard right now in a in a in an application that we are building and for that we've developed with with our colleagues we've developed an indicator ontology and a methodology ontology that are aligned with with I and with impact on and with claim on. So >> um so basically building you know because because I think claim on has the the idea of an indicator and then we we we we built that out further to say okay um you know what ex how in detail does an indicator function and then a methodology is something that calculates the the value for an indicator. If your if if your indicator is something like ton CO2 equivalent avoided per year, >> Mhm. >> then >> that's a that's an indicator. It's a way of describing some something and then a methodology is how to calculate that for a specific let's say for soil a specific >> from a source >> conversion technology compared to something else um and and and we we we built out the semantics of that so I think in the past we've discussed whether we can bring that in to the accountable impact commons Um, >> so maybe I'm I'm going to those those are public repos. So maybe what I'll do after this is I'll share just the GitHub addresses with you with all of you and then we can just uh discuss in the future whether we we can bring those in um as as sub you know as as repos under this and de develop it it in the same in the same context. um also get the the W3 ID um uh name spaces and everything so that that we build out the suite >> into because that flow directly from what we've done >> and but we had the need to do it you know to be very specific around those things and um and we built that out. So that is something that that we I think we talked about it we mentioned it in the past in passing but I think uh we would like to formally u discuss with you all you guys whether we want to bring that in. So I'm going to share an email with you tomorrow. So just with those addresses and then we can keep we can put it on the agenda um for when we meet again uh which for you guys will will can be in two weeks but for for me will be in a month from now. >> Y that sounds good because that's you again this digital twin the key [clears throat] function in the digital twin is modeling. So you had the supply chain. So we currently have a supply chain with about 20 players in it from a coffee field all the way to New York Harbor, the grinding operations. And so you're you're doing your your greenhouse gas baseline on the supply chain, but now you're going to model it and show how you can reduce it and get credits, get payments. And that's where this becomes with the units and having a structured data uh process to say this is legitimate. We're doing this. We're doing this with soil. We're doing this with solar panels. We're modernizing trucks. Um, and this is what we're going to save. And the get down to net zero. And so that conversion over to showing what we're doing modeling that that's where that standard data is really key. Otherwise, that's that's where greenwashing takes place right there. >> Yeah. It's I I I Yes. But it's also I think Jeff you you picked a really difficult I mean let's say a complex problem because there are so many moving parts but maybe that is is also a worthwhile problem if you >> yeah that makes it more it's difficult you've got you're right you got many moving parts but you also have different cultures working so you got African cultures you got African truckers you've got global oceangoing freighters you've got >> New Yorkers um that's enough said there but um you Yeah. So I we picked this on I picked this on purpose. We did a supply chain mockup of it about with the supply chain group maybe a year ago and picked this one. So there's [clears throat] a lot of there's a lot in this one there. There's a lot of sources. You know, just a coffee field has got off the top of my head. It's got fertilizer. It's got trucks moving things around. It's got process to get the beans out. There's different ways to get the beans out of the pulp. The bags themselves. There's plastic bags. There's bags called Joot which are more natural fiber reusable. So I go on down the list of just carbon sources from a opportunities to reduce carbon emissions just in the field. Beside then the trucking operations to go so many miles to either uh the port which is 800 miles or to Kenya has got a train system that'll take them over there and save a lot of greenhouse gases. So showing differences in countries. Same with Ethiopia. You know, these are all small farms that get conglomerated together. So, um I've actually talked to those folks in the supply chain, Eth folks that run what's called the Ethiopian Coffee Exchange, ECE. Um who there's thousands of small farmers [clears throat] and all that gets collected by them and it gets auctioned in these auction houses in Africa, Kenya. Um and so there's lots of opportunities for um greenhouse gas reduction. It dumps a lot the coffee in your cup. You'd be amazed how much that's another reason why you know it it when you show these demos you can show how much how much greenhouse gas goes into that cup of coffee sitting on your desk. It's amazing especially dark roast and the roasting process and shipping it overseas which shipping it on a transport boat is one of the lowest segments of the supply chain that gives up. does gas emissions, you think it'd be the most, but because of the freighter size and what else is put on there, um, you know, there's a lot of there's a lot of standards out there in the world about climate exchange and one of them is if you're putting this many square feet or pounds on an ocean vessel, this is your greenhouse gas emissions. I don't know where they calculate those things from. So [clears throat] those are kind of standardized ones, but trucking with all the IoT um and again we're what's called scope 3 emissions which is the most baffling thing out there in 2026 and 2027 companies in America, Australia, Europe. So we have to work on scope three emissions and so I'll focus on that a lot. >> Okay, I think I see we are on time. Alonsu you have to drop. Um thank you. >> Hope you get better Alonso. Hope you feel better. So, >> um then I'll I'm going to see you guys then in a month from now. So, uh but I'll I'll I'll I'll send an email then tomorrow and um and uh Kit, if I have some comments, I'll I'll make that on that on that site that you gave us. >> Yes. Just go ahead and edit away and uh have a good vacation. >> Thank you. Thank you. Yeah. And I hope you stay safe, Jeff. Uh um [clears throat] >> yeah, I'll start doing the calls from the basement. So in the office build, well, it's a big office building. And you got remember tornadoes in the United States, they have a there's advanced weather radar here. And so if they see any kind of spin up in the clouds, they call that a tornado now. They don't wait for it to hit the ground. >> So you get these warnings and it doesn't mean that there's one there really is one on the ground and doing any damage. They seem to spin in the atmosphere. It's very and they just give these warnings out. So we were in the basement for like 45 minutes. We did have winds about 70 miles an hour >> straight like wind. So the Midwest US is not a fun place to live in the summer. Very violent. >> Um well where I vacation up in Michigan is much cooler up there. So they don't have that kind of stuff up there. It's middle of summer. You have coats on upper Michigan. So, >> okay. Thanks, guys. >> Y >> see you. >> Bye.