 Okay. So, we think of you guys as the other RDA, and I'm sure you feel the same way about us. But this is the RDA that I've been working with. It's a library standard. And my business partner John Phipps and I have been working on it since 2008, although not paid for all that time, sadly. So, I have a couple of, let's see, I have some slides, texty slides like this, but I also have some images that I can't, I don't really have time to go all the way through, but I thought it might be useful for people who, you know, to go through them later on because there's some stuff that you can't easily get at if you're not, if you're not me or John. But this is kind of what our goals are. And we're talking primarily public vocabularies at this point, although we, at some point I think we will be able to manage private vocabularies as well. And we have a couple of services that are associated with what we're doing. It's, we cover both, you know, structural vocabularies, element sets, whatever you want to call them, everybody has a different name, and also value vocabularies or Scotts vocabularies as people sometimes call them. So, it's a slightly different kind of panoply than the, than your RDA does, but it's all absolutely necessary for what the, this RDA or our RDA needs, because we're transitioning off a world of Mark. And really, there was no other way to do it. Okay. So this is kind of the, we call what we're doing kind of a three-legged stool, and I'll show you the picture later. First one is the open metadata registry. And, and that one you can get by, if you want to look at it while I'm talking is the, it's metadata registry.org, metadata registry is the whole word. And that's really the heart of the thing. And we started working on the open metadata registry, which was at that time called the NSDL registry. About 2004, something like that. The OMR is kind of the central leg, if you will. Although, as I said, we've been working on it for a long time and it shows its age in some ways, mostly with the user interface, which is kind of kluji, but you know, it still works. And we're in the background, trying to rewrite it. It's, it's using old, old software and things like that, but we've kind of built on it, which is fine, but, but we have to kind of go back and make that part work better. But one of the things we started doing, which when we first began working on this was we, we record detailed history of all changes. And it, and, and the provenance, you know, who did it, when they get it, etc. And this, it's the, it has along with it a specialized vocabulary server, which kind of takes a little of the burden off the old software. But it, and we have a lot of services that go along with that. And I'll get to some of those. All right, leg two is get and get hub, which I assume some folks are using or familiar with. But that's where our version management comes in a lot of our issues tracking and the documentation that we have for the RDA registry, although not, not yet with with the with the open metadata registry. Okay, so the third part is the specialized RDA vocabulary management, which is the part that it really doesn't have a user interface. It's really intended to for people to use to, to, to read information or to access information. But it doesn't have a separate user interface because the OMR is really the only woman that is important in terms of what we're doing. So it does make available downloads and all different kinds of viewable data. The, when it says aggregated RIMF data, that's from a bit of software that we interact with, which is a very, a very cool little cataloging thing that allows you to work sort of an isolation. We're trying to get some money together to, to allow it to be a web tool, but we're not there yet. So the lexical aliases are kind of interesting because we've, we're doing a lot of stuff with translations and I'll show you kind of how that works when we, when we take a look at some of those. So our workflow is pretty, you know, kind of goes all over the place, but I have a picture after this and you can see how, how it relates to all these three, these three legs. So it, we're working primarily now with not with direct input, although that's still allowable in the OMR. And our major users do use that, but we're, we're trying to make it possible to do a lot of import export using spreadsheets of various kinds. And that's been, that's been what we've been working on pretty, pretty much for the last year and a half or so. So, we only have one user that is now enabled to do that and that's Gordon Dunsire, who, who does all the data work for, for the RDA. So, let's see. This management workflow kind of goes all over. I'll show you what the picture. So the OMR and the vocabulary server are, you know, from, from the outside sound like different things, but they're actually pretty much the same thing. The vocabulary service that's behind the OMR, the OMR has the user interface, etc. And so these numbers are for those workflow things that I did that has numbers. So you can see that that there's a fairly complex interaction between these things because they all have slightly different functions. But anyway, I decided not to put any, any arrows in there because I thought nobody be able to read that but you know this is kind of for for further reference you can take a look at that. And here, here are the links that are I think the most important to look at as I'm going through the rest of these but I thought I'd give you those up front. So if you want to, if you want to look at some of that, well, while I'm talking, feel free. And it will be on the presentation. So you'll be able to see it at any time. Okay, this is, this is part of our newish stuff, which has, the Google Sheets import. And this is Alie publishing, which is our major user. And so you can see that that that all of this information, you know, when it was exported when it was last imported, when it was edited within the OMR all of those have separate columns. It really requires a fair amount of setup to do this. But we've, since we have our one major project, it's been, they've been doing pretty much all the testing and all the pain with the testing to this is a view of the OMR data. So you can see the element sets. It manages all of the information about the history and imports and maintainers who's allowed to get in there and work on this stuff. And we have all kinds of, as you can see, we're working fairly heavily on the, on the language, the multilingual parts of it. So it looks, it's a little hard to, to deal with, but this is the, the RDA work properties, RDA is based on Ferber, which is now LRM, the library reference model. And so there's all kinds of pieces to that, that are used to describe each element. So, at this point, you can export that data. And then work on it offline and then import it back. That's, that's really what we're, what we're working on at the moment. Here's a list of exports for one property. These are just screenshots and I'll leave you to look at them in a, in a better way. I think the important thing is that all of that stuff reflects the fact that we are keeping track of every transaction on these list of vocabularies. It's a huge amount of data, but it's really important. So here's the, here's that this little box tells you what, what happens when you look at the updated on that column. And it tells you that the previous action was, was added. So that was the first time it appeared. And this is, I think this is German. And the status is, is new published old published. So it started out as published. It didn't change its status as part of this update. This is, this is again from directly from the OMR, and it, and it gives you the history information about a particular property. And, and who, who did it. And, and the last column says import. So you know, you have a numbered import that you can look for to, to figure out if something went wrong. So this is kind of in there so that we can, we can really problem solve a lot of this stuff, which is really hard to do once you get outside of the, the box. So this is the RDA registry, which is that, that part that is the basically read only we don't, we don't manage the data through this, but we manage the data itself, you know, make the downloads available. Allow you to get information in a variety of different language. And it gives you some, some of the extended information down, down at the bottom. So the, when you look at the left column under curie, you see RDAW and then a number that's we do all of our URIs are set up like that. So that you have RDAW, which means work properties. And then the number allows you to have a number that is that works for every language because that's the, that's the, the basic URI the languages have what we call lexical aliases. In other words, they also have additional URIs that are in the language that the, that translation is in. But they all point in the data back to that original, that original curie. Okay. Here's a, here's one from a value vocabulary carrier type, which of course is this gossip. And these are are handled pretty much the same way you can see this one's in Chinese, I believe. And, and, and there's a lot of information there in in Chinese. Because you have all the, all the information about what it's reflected. You can, you can see it in any language, you can see under the languages in the front there, there's a red box around Chinese. Okay, this is part of an example spreadsheet and there's a link there if you want to take a look at it. So, again, we're working very heavily on the multilingual versioning for both the element sets and the value of tabulars. This is proved to be a really interesting challenge because English is the primary language. So everything, every translation is based on the sort of the or language here. But the translations are done by independent folks who are working within the within the group, and they don't necessarily. They don't necessarily get to a translation or they don't necessarily update it at the same schedule so we're having to deal with that that there is the, the version of the primary language English. And then there are, there are versions that are inherent in the, in the addition of the different languages. So we have issues about when the language of the, of the, of the, when, when the information of a particular language results in a change, even if the English didn't change. But we always have to kind of go back, link back to the, to the version that was being used in the translation anyway. So this, this all gets pretty crazy. We're, we're working on trying to figure out if there's a better way to do it. And the bottom bullet says moving the each language into a separate GitHub repo and version independently is one of the things we're looking at we haven't quite made a decision that. So this is, this is kind of where we're intending to go what we're trying to do where we are with it. And the custom application profiles is based on how, how you design your data, basically, and, and so we have application profiles within the OMR. And other people can make application profiles for their data and we're starting to get to the point where we would like to be able to store them and use them for output. Anyway, so we're on a, we're on the beta version of the OMR at this point, but nobody is allowed to use it except us. But that because you can't get people to test stuff like that unless they know what's going on. So we're, we're kind of at the point where we're doing a lot of it testing internally and not ready for prime time. Okay, you may notice this is this is one of my favorite slides that there are two cars there with the same license plate, except one is New York and the other one is Ontario. So that's our, that's our business logo. Very good. So the same same words in a different context and they different license plates. Well, John is very proud that the Ontario license plate says yours to discover. You know, mine says Empire State. Well, what does that mean?