 Welcome to You Bet Your Assess, Case for Drupal and Visual, Audio Visual, and Video Congratulations. And this was my original screen before I realized that they stand in this. My undergraduate work was in Engineering and Math, which led to a graduate degree in Education, and I worked in higher ed for some time, after which I became an educational media producer. And then discovered that HDTV standards were developing. So I aligned myself with those for quite a while and worked in digital video and eventually repositories in digital programming. And that led to Drupal five years back in 2010. And that's why I mentioned open source productization. If there's a better term, I'm gonna start using that. I've been with Drupal since 7-Eleven. Overview and Turnology. Digital Audio Visual Media Preservation is not damp. Not an acronym, and it's not damp. Maybe today it's damp. It's not exclusively film or video. It could be in other assets, print media, who knows what, but my domain right now is mainly digital audio visual. And I like to say it's non-trivial in terms of detail or scope. It's not a small project. And it's also not ideally standardized. And you will see that the role of standards comes into play soon enough. Digital audio visual media preservation needs love. That's not an acronym, that's what it needs. Interdisciplinary attention and focus. Lean or meaner standards and dog fooding. For example, the Society of American Archivists sounds impressive, doesn't it? Universal preservation format. When I went to search for it, you got a 404. So put your money where your mouth is, folks. That's just one of many. So these are my personal motivation points and pivots. Originally it was to use Drupal to represent one of today's top standards in preservation. For various reasons, I branched away and that will become apparent through the rest of this. The first step really was to switch gears and try to taxonomize this damn corpus. Which means, and you'll see again, it will show that there is a lot of different competing standards and practices and publications and entities having to do with preservation. And so I had to confront Scope Creek and then I pondered and this took some time. And then I collected insights, or I'd like to collect insights. This is a pivot. I would like to collect insights to influence the Drupal project itself. I think that we stand to gain best practices by looking at some of these other existing standards and existing initiatives. Remember, this is about assets. Here's some terminology. An asset would be defined as exploitable content. And I think we lose grasp of that when we talk about a content management system. Is the content worthy? In other words, does it have value either monetarily or sentimentally or instructive-based content? Any of those criteria would probably meet the requirements, but this is my concern about content. Content equals essence plus metadata. Essence would be the raw image, footage, audio, whatever you are recording, in other words. And then metadata, which will become the prevailing theme here. You can't have content without the metadata. Otherwise, you would have a file name. You wouldn't have anything else other than the essence, which would make it completely inaccessible. I'm using this definition of metadata, descriptive or contextual information, which refers to or is associated with another object or resource. This usually takes the form of a structured set of elements, which describe the information resource and assist the identification, location, and retrieval of it by users while facilitating content and access management. I can't emphasize enough how much it means to see that they mentioned both structure and retrieval and management all in that definition. I think this is one of the best ones going. Here's another one, though. Metadata is structured information that describes, explains, locates, or otherwise makes it easier to retrieve, use, or manage an information resource. Metadata is often called data about data or information about information. Now this one happens to be from a standards organization itself. And part of my gripe is that there is no one accepted de facto definition of metadata. Now digital preservation, again, it's a mouthful here. The series of managed activities necessary to ensure continued access to digital materials for as long as necessary. Digital preservation is defined very broadly and refers to all the actions required to maintain access to digital materials beyond the limits of media, failure, and technological change. Those materials may be records created during the day-to-day business of an organization. Born digital materials created for a specific purpose if you're teaching resources or the products of digitization projects. Now, again, digital preservation itself is very broadly defined, but in our case, it becomes apparent that it's all about the metadata. This is what I call a digital value cycle that becomes apparent. When we have essence plus metadata, that leads to our exploitable assets, which leads to the need for standards around those assets, which becomes the catalyst for preservation. And then you just repeat because one feeds the other. You can't have preservation without the original essence and metadata. And you can't have essence and metadata for long without preservation. So this is my own little device that I'm using to show bare minimum logic of this. In other words, assets count on preservation. Preservation counts on assets. Good. Here we go. Remember this? Not trivial in terms of detail or scope. In other words, we have immense needs to cover all digital preservation aspects. And not ideally standardized. There's no bona fide solutions across different repositories. So already we're running into constraints from three minutes ago when I said that it wasn't trivial and that it wasn't ideally standardized. And when I say yet, they're working on a standard. So we'll get to that. Okay, preservation, description, information. This is a very popular term in the business. Here we go. We have access rights, authenticity, content, fixity, integrity, provenance, quality, and reference. Every single one of these eight terms has made it into the pending standard which we'll see in a moment. Obviously it has to do with the, I can't say integrity because that's one of the eight elements, but it has to do with the validity of your assets. Without access rights specifically stated, you run into difficulty monetizing the content and essence. The authenticity is important to know that if you're dealing with multiple copies that it is not a fake, it is not a bootleg, any of those things. The content itself, it speaks for itself, fixity, integrity, and quality all run into each other. But it has to do as I said again with the veracity of what you have. And then provenance as well. We have to be able to trace it back and make sure that it is the original content if it's being recorded to be that. And reference, again, self-explanatory. All these eight make their way into a standard. So it's not trivial. Here we go. And this is from an excellent little paper that I had read. A standard is needed that defines the content and format of multimedia preservation description information in order to facilitate interoperability between preservation systems, ensure accurate understanding of the resources, exchanges, and reduce the risk of corruption both in the exchange and thereafter. So in other words, we have to preserve not only the assets, but the metadata, the preservation information about the assets. So again, we're already getting into another layer of complexity. And we haven't mentioned Drupal yet, but think about Drupal as I'm delving into this. Now, as I mentioned, it's part of a standard that's under development. You ready? The ISO IEC discussed standard 23,000, Part 15, Information Technology, Multimedia Application Format, otherwise known as MPEG-A. Part 15, Multimedia Preservation Application Format. Commonly known as MPAI. What the heck? So, already, we're getting into a level of complexity and nuance that seems at first glance overkill, but you'll see that it's necessary, not trivial yet. So here's an example of a typical document from the ISO. And since this one is pending, unfortunately, I'm unable to share the content publicly. There are normative references that are mentioned within it, no less than 25,000, and they are indispensable. So these are other standards that this is built on top of. So this is not the only game in town. As I said, it's under copyright control, so I can't really show you these 25 normative references, but they comprise other ISO, I can see standards and external resources. And all, every one of them merits classification within an open schema, so that if this is under copyright control and isn't publicly accessible, at least we should know which standards it relies on and be able to access those in an open format. And again, think ahead for Drupal and how that could be accomplished with rights management, with content types and all the rest. I think Drupal could be a viable solution. Now here's some personal observations. Close standards make even a simple taxonomy of this tricky. So-called normative references may or may not be open themselves. Standards need standards. It's as simple as that. Just like metadata about metadata. And standards need a unified data model and content type. This is what I've discussed with myself a few times and distilled it to the bare minimum. And here's a sidebar, taxonomies and stuff. Reality check. Are Drupal taxonomies the right tool for this use case? In other words, I'm trying to taxonomize the damp corpus. Remember Jeremy, you were in here when I said that. We're calling it damp for digital audio, visual media preservation. Well, to use a Drupal taxonomy is one thing, but I discovered that mind mapping is the minimum viable diagram because you have a signable progeny of standards and other resources. All the descendants of those particular standards or groups or whatever can be graphically denoted in a mind map trivially. Very simple to do. It offers its own, if simplistic, metadata provisions. So you'll see that in a moment. But unfortunately, a mind map is static and it has no semantic data. So here's an example of an application that I use online for free called Mind 4.2. And you can see in the center of it, it has the mind map, which looks like a little bit of a binary network, starting on the right where it says mind4.2.com and that rectangle moves to the left with features and then it splits into three and then that splits off into its own little descendants. So there's your mind map and you can see a bird's eye view of it, just the upper right of it. And all those icons are the so-called metadata. So you can assign your own symbolic or text metadata to each one of these and you can see one of them where it says icons has light and bulb, which means something and it also has a document. So here's an example of Mind 4.2 in action with my own mind map of all of these different standards in play. So see what I did? The central stalk on the left side of the upper portion has all sorts of branches. And each one designates its own standard. And I've used the badge, which is in yellow, to signify that it's a standard or a pending standard. And the check mark is just that it stands out that it's one of the more popular ones. And as you can see on the upper frame as well, I've highlighted the one right there, ISO slash IDC under discussion, et cetera, et cetera. That's the one that we just visited a moment ago. It's part 15 of many parts. It couldn't be up to 20 or more parts. And then you can see on the left, the MPAA standard initially launched in 2007. So this is sort of a chronological view of just the standards that I've accumulated by my own research. And already it's becoming quite a short. And oh, I'm the bottom, that's what I did. I highlighted it so you can read it. Any questions so far? Yeah. Why are they closed standards right now? Like a question like open, like, you know, you do all this work and then you publish it and say, well, let's see this happen and this is what you do all this work and do it. Right, the question is why are they closed standards? Well, initially some of these organizations make money off of selling the final document. So they can be closed not only for copyright control, but also because it's under discussion and hasn't been elevated to the status of a standard that's still mutable. So if that answers your question, there's some of them are open standards, some of them are not. Now, what if we had more of an in-house solution using Drupal? Graph line is or was a Drupal-based hierarchy with Google. Unfortunately, the last bit was two years ago. And they're looking for a call maintainer and there's no Drupalate development. So this is the closest I can find to something like the mind map we just saw. And as you can see, there it is from 2009. And here's an example. It looks pretty robust, similar to mind map or mind 4.2. But as I say, it's out of commission as far as Drupal, which now with the Drupalate. So more observations. A mind 4.2 like map via Drupal seems out of reach. An optimal inventory would be semantic, dynamic and open. When you think about it, I would have to be updating this 24-7 with newly researched info. Why not get it straight from the source if they embedded their own semantic data within their own links and I can pull that down from the author's page would be ideal. Crowd source could help speed up the input. And finally, scope creep sets in again. The sheer number of damp related players and initiatives out in a while. And when I say damp, that again, that just means digital audio media or audio visual media preservation, which isn't a standard, it's just my own acronym. Part three, digital preservation organizations and bodies. Now this gets complex fast. Here's another mind map and this is just a slice of it or it's bots. This map is only a work in progress. I keep adding to it. There are 45 groups so far, a few of them collaborate but most are purely independent. It almost seems as though not one group realizes that all the rest of them exist. And I perceive that as a problem. And then there is overlap. There are groups working on extremely similar cases. And here's another example of a mind map I made close up of it. So the blue icons denote that it's a Drupal site and there are more above and below us. I just couldn't fit it all on the screen. So Presto Center is one, Society, Narc Narcimus is another. They've been around since 36. Some of these I don't have metadata on. Obviously I don't know what year they were formed. I'd probably call them up and find out a few others. It's a D, which I am a member of and digital creation exchange. So I call it academia and Drupal stuff. It's just getting ridiculous folks. We need a better way of identifying these entities. Okay, key players. You ready? Here we go. AMWA, ANSI, CCSDS, which is interesting because it was for space data. It's collected by satellite or rover or whatever. And they became one of the major players. DuraSpace, as I mentioned, DuraSpace is Drupal. They are headquartered, I believe, in Diffenheim. And EBU, very popular European broadcast. There's more. The IDC, as we've heard. The ISO, as we've heard. The ITU and the LOC. So this is not a raptor. Oh, and then MPEG again. It's a Drupal site. All of them. And finally, another page. ESO, Presto Center, which is a European Drupal site. SMPTE, which is a US Drupal site. W3C, we all know. So where are my observations? Those who appear to have their shit together have Drupal sites. Is that a coincidence? I don't think so. Remember, leaner, leaner standards, I have a feeling that those who have already decided to go with Drupal realize that standards are important. And they stand out. An honorable mention, even though it is not a standards group, watch this, it's called Artifactual Systems. Here's their homepage with a revolver on it. Free and open source standards and client software solutions. Digital preservation, archival description, discovery and access. This is hitting every single key point anyone could want. And they're moving on. It's open source. What could be better? And here's another one of their pages. We believe the open source model is the best way for archived libraries and museums to reduce costs, facilitate collaboration, crew standards adoption, and raise professional. And they're preaching the choir. So I would like to start working with them in some capacity, even though they're not Drupal. Okay, documents, recommendations, standards. This is very similar to the organization of bodies that we just covered. It's just a different part of my mind now. Here we go. Again, it gets so complex. It's also work in progress. It demands a more modern solution than this. What about dynamic graphs? What about data visualization? What about something else? And it's still a game with a bunch of unwielding. Why has nobody tried to do this? There must be a list somewhere, whether Gardner or somebody who's put it together of all these different entities. If not, then I can't believe I'm the only one. It doesn't make sense. And here's a close-up of that list. So here are a few of the guidelines, frameworks, standards, data models, different criteria. Trustworthy Digital Archives is another buzzword. CIFTY has a VC2 standard for compression. It came out in 2012. All these facts should be accessible in order to create better value for digital preservation. But we don't have a means of coordinating it. There's no central nervous system in terms of Drupal that can handle it yet. So I have these again now and we're sure exactly the same. There are very solid differences in these standards. Okay, here are a few sample and data entries. So MPEG 21, MPEG 7, OAIS. This is a reference model that, again, came from the Space Systems Center. A metadata framework, which becomes important. And the OCLC is a library committee that only goes by its acronym. It doesn't even, you can't even find its own name anymore. It's just too long. The German one here with Tomer. And premise, again, the Library of Commerce, our Library of Congress, rather, has a premise, which seems to be one of the ongoing standards today, especially libraries. And then a little bit of caricature here. Oh, yeah, MPAF, MPEG format for the Multimedia Preservation, as we've seen before. That shows up on the list. So observations, acronyms do become useful after all because there are so many subtleties. You have to have a difference between all of these. Here we go. MPEG 21, MPEG 7, OAIS, premise, MPEG A, and MPAF. All of these, including MPAF, are in continual use. So the metadata standards need their own metadata. There's no doubt that Drupal could come and play. An ideal world would have standards for abstracts, too, just to know what is behind each one of these standards. Whoa, hello. What's this? The idea has been around. It's a guideline for abstracts. There is a standard out there for writing abstracts. And look, it has its own abstract. Drupal could be using this. So every single project page, every single theme, everything could have its own little abstract with it if we wanted to, and there aren't standards for it. That's just one of the spin-off ideas that I have. But the idea is that we don't need to incessantly reinvent the wheel when people have standardized, even if it's interdisciplinary, this may be for library or academia or whatever, it couldn't have a different ownership. But we still can incorporate series of practices for our own in-house use. So this is from an ISO.org, which is also, again, very prominent in the standards field. Okay, we're getting to the meat of this. It's a meat of presentation. The role of Drupal in the future. So let's see what we have. What if Drupal did go beyond an inventory or a diagramming tool like our MindFortune had? What would that look like? How about a harmonization engine? Have you ever heard of that term, harmonization? Or a crosswalk management system, another CMS. I'd like to consult this one. Issues in crosswalk and metadata standards. It's a great little document. Here it is. So 1998, okay, so that precedes Drupal. Crosswalk basically means mapping. When you have metadata, it could have different vocabularies depending on which institution you are or which end use you're intending for. Therefore, what happens when somebody de-accesses a collection in a library or when someone wants to purchase assets or transfer them in any way or transfer them to a new storage medium. All the metadata in the source and the destination has to match up somehow. So crosswalk is the simple terminology for mapping the old metadata to the new one. Oh, there we go. Harmonization. So harmonization means combining the metadata. If you have two different versions of metadata, why not combine the best of both worlds into one cohesive unit? So crosswalk would mean transferring of mapping. And I guess you could say it's almost like a field manipulation, a field model, whereas harmonization would be combining them into one body that could be exploited down the road. It would be all inclusive. So these are two of the different strategies and in use all the time for metadata. Problem is, and you'll see in a minute, there's not just one metadata standard. But first, here's a good document called understanding metadata, obviously. Metadata is key to ensuring the resources will survive and can you continue to be accessible into the future? So this is from 2001. Again, it's an advantage of Drupal and all of this has already been discussed at Nozio. Yet it appears that it has still not reached a standard. Remember that MPAF, it's still a pending standard. So here we go. When I said there were metadata standard, there was a key. Look at this. Just a few. And this is from 2010, so there may be more now. If anyone wants to consult the link, is it? So you can see there's obviously a need for a way of corralling all of these different competing standards or complementary standards. So, Drupal's role, how about this? Why not have Drupal serve as a manifold that aggregates or manages the Zulu standards? That's absolutely to me. Remember this how I mentioned? My original motivation, zero, was to use Drupal to represent one of today's top standards. I'm not gonna tell you which one of those standards it was or whether it was a different one. That's not important. But I wanted to incorporate the logic and the terminology and all the different nuances of that particular standard within Drupal itself so that I could make it a distribution. That way anyone could get an open source version of that standard implemented. It would be a perfect representation that would be the technical term for it. Drupal would be the representation of that standard that you buy and own. So how about Drupal's role? What if we step back and instead of managing that, we only manage the metadata. That's the only concern that we would have. That could be one of the potential use cases. Or if we stepped up, we could say what about handling the metadata plus the content? Imagine that. Not only would Drupal be central in managing the metadata, but the content itself could become just another content type, which would require men's storage. But if you had a motion picture archive, imagine using Drupal as the central means of organizing and accessing and preserving all of that information according to the metadata preservation standard. So again, more of Drupal's role. Somebody called these edge cases for Drupal and I just had a conversation last night with a librarian expert and he said, people dismiss Drupal. Why? Well, it may not be performant enough. You may find a more elegant, slicker solution under the hood. But in my case, I'm saying not necessarily, it's not necessarily an edge case because Drupal 8 is going progressively more standardize. For instance, we have the WAI area accessibility standard 1.0. It's a completed, they call it a recommendation, the W3C, but it's technically a standard in their eyes. The same goes for HTML5 in front of that with Drupal 8 considered a standard. So we're definitely going in the right direction compared to any of the previous releases. More of Drupal's role. As I said, performance may not expect much of other open source projects. And here's some examples. Blacklight is a discovery platform framework, which is Ruby on Rails. Hydra in a box is a term key repository of discovery, interoperability, and reuse built on Fedora. And this is not the Fedora that we know from Linux. This is a previous Fedora from one of those other organizations that has to do with storage of multimedia. And Solar and Blacklight again. So Hydra in a box is not yet out, but there was, I believe it was a $2 million grant recently completed to advance the cause. And finally, Islandora, which is a digital asset management and a discovery solution based on Drupal. And then enhanced with the Java and Python. So Fedora itself would be the Java and Python, but the notion that these are all open source should put us on warning that if we wanna do something, we would have to be up against these competitive products that are already established in the market. All right, here's some other information about Drupal 8. It no longer uses RDF mappings from anything but schema.org. You guys are probably aware of that? Is that an issue? Well, it does promote the notion of unified and shared vocabulary, which I think is a good thing. It gets rid of a lot of those contentious issues that we had before with the zoo of standards for metadata. So is it a problem or an opportunity? I don't know. There is a project you may have heard about called RDF UI, a user interface. They could map fields and content types to schema.org from within Drupal. And did you know that, here it is. It was a Google summer code project by an undergraduate. Now, I think she was still in high school. Her name was Sachin Haram. And that's her page. So if anyone is interested, she also has another one that can automatically generate content based on those parameters. So I guess it works both directions. But to think that we could have a user interface written by a high schooler is inspiring to say the least. So think about the role that this could have in the standardization of the metadata, competing standards that I mentioned, or the vocabulary, is we could do some of that conversation and crosswalk between all of them by means of Drupal, since this is already essentially doing that. It's mapping the metadata through the fields. It's right here. For Drupal 8 exclusively. And I guess it has, what did it say? This module enables you to specify the parameters between content, types, and fields with types and properties of Cineba.org, respectively. So this is a really useful little idea. And I think it could take off if we exploit it right. I think there's a version of this in 72. Not according to this. Because this just came out last year. I just love something very similar. Well, that's great. Oh, I didn't know. I'll look it up. I'll look it up. OK. But yeah, this was, like I said, a student in summer code, which kind of hearts back to Angie Byron getting her stroke. Anyway, more observations. Finding a place for Drupal will take effort, but it will lock in longevity. Imagine if we cemented ourselves as a community into the space program, or into the Library of Congress, or into any of these other entities that aren't already using Drupal as their web presses. I think it could perpetuate Drupal in a very solid manner. And I don't know if Dries or any of the board is on board with it. But as an end user, I don't see why they could. It seems to me like it's a definite opportunity. But who will advocate it? I don't know. Is it worth it? Is it worth advocating on a developer level, or do we need to get an OQI involved, or what do we need? And here are some other unspoken considerations that came up to my mind when I was doing this. What about creative comments? I never hear the notion of standards being released with creative commons, parameters. It seems as though it's a match made in heaven. And it would be something to investigate. Maybe it's already done, but I haven't seen it. And then also YouTube. This is probably the biggest digital repository out there. And you never hear anything about standards. You never hear anything about metadata. You don't know which vocabulary they may or may not be using. I don't know if it's proprietary. So all of these are good questions to cultivate down the line. This is all brand new research for me. This all just happened the past few weeks. So I'm spitting out basically everything that I've accumulated, like a bird. But anyway, the digital community can take views from certain initiatives. As I mentioned, to me, it seems as though even just standardizing the notion of an abstract, or standardizing the metadata of vocabularies for our own projects, could get us way ahead of the competition, way ahead of the rest of the web in terms of being able to document. So that if all of our semantically rich descriptions were embedded already in every project, in every theme, in every distribution, then all that data could be pulled from the horse's mouth, so to speak. It would be sucked down and populate all the different documentation on the web, all the different resources, so that everything is always current, dynamic, up-to-date, thanks to the semantic shared data, the linked data. And I think Drupal, since it already has that part parcel of its underpinnings, why not start using it for something like this? So I think we could follow the standards, and maybe they could follow us, too. And this is the last bit, spin-off potential. Did this induce any ideas among you? And is anything here wrong? Is anything here incomplete? This is just an overhead view, and I committed myself to following the item description in the schedule. So that's the last point I had to make. I'll open the floor and see if anyone has any contributions, especially if you're in the library realm or in any of the preservation fields. But that's it. Thank you. I know that there was a case study on Islamdora on Drupal that somebody just did, and I can't remember which company, but they used Islamdora as a back end for archiving information. Because they said that was pretty much a big post to be a good standard to follow when it comes to archiving. And they used the baseball hall fame. Yeah, I got it right here. OK, I remember that it was a company called Kagaap, COGAPP. I believe it's on an email. Pretty sure that. They did baseballcall.org. They did the Qatar Digital Library online using the same thing. And I believe one other. But again, this is all pretty semi-exhaustive research to try to find any link I could between, however you say it, Islamdora is the door. It's a Drupal initiative. It's based on Drupal to try to find any links between Drupal and digital preservation. And there are few in far between. I think we've conquered most of them between Presto Center in Europe, which has a pretty decent established sense in that picture. And what else? There were a few other ones that I mentioned on there. The ones from DuraSpace, which is based outside of Cornell University. Drupal is part of their web presence, but I don't think it's part parcel of their strategy. And for reasons that I mentioned, it may not be performing. It may require a solar infrastructure that's much faster. You have all that data, and you're needing to access it so quickly. Drupal may choke. So that may be a valid consideration. But I'll look into the Baseball Hall of Fame and see if their performance needs are being met by Drupal. And if they have any concerns about it. I think that's a great idea. Thanks for sourcing it. Jeremy, I appreciate it. Yeah, they use that as their back. And then they have another people site that's pulling from that archive. And they said they were trying to implement best practices. I don't know what you're going to do with that. Thank you for showing me here. They're quite happy. They don't know what it is, and they don't understand it. I'm not sure if there is one for that particular use case. But again, it almost means the community's voice to bring that up and create a forum for it. Because with all of its features that they've been hitting on between the serialization of the data and who knows what, the services, all those different selling points in Drupal would be great to have a use case associated with them that has a standard bath in it. That's an arbitrary little lottery site or something like that. We want something that's really going to hit it out of the park. And I think we're halfway there. I think that between some of the established ones and these emergent standards, if we could lock in and match our content types to all of these different metadata fields or whatever it takes, I think we could secure ourselves a future. That's just my hunch. You spoke with anybody at schema.org about creating a schema for digital assets. Because that's something that even Google is sort of pushing people forward to have structure data. And so, but in order to have structure data, you need a schema for it. So, but there's lots of reasons why people don't want them. Because they want to have their own proprietary repository information. That's exactly the crisis that we're running into. And to have an ability to both harmonize and crosswalk between different standards is essential. Otherwise, we're going to have that sheet of 100 or 200 different items. So, I think schema.org, I haven't contacted schema.org yet, which is obviously, it's a glomerate. It has a consortium of what, Krupul, Yambu, and who else? Microsoft's part. Yeah, but I just don't know if having that unified vocabulary is the ideal solution since there's so many existing metadata vocabulary is out there all right. Having a way of bridging them, and as I said, if Drupal were used as a manifold, it could bring in or ship out any variant of any metadata standard so easily. These are simple data models that we can construct and then have it dynamically updated if they change, you know, you could always import out a new version of it on the fly. I just think that nobody's ever implemented that, let alone made a list of all the different metadata standards that are out there, except for that one that's three years old. I don't know if anyone's done anything since. There's a color version of that chart, too. Remember that one that I showed that? It had, you know, oh, I have it right here in traffic. Here, it says glossary of metadata standards. The print was so small, my laser printer was choking on it, it almost crashed because there are so many tiny different entries on this list. And it's in there, I've got the notes, slides that are in there, and there's a link to it. But I just think that we have metadata, what I call it, Nervosa or something. I made up a term, or the acronym. Yeah, it's almost a point where there are too many cooks in the kitchen, and we need somebody to clear it through and do this sort of schema.org method that would consolidate and improve the system by measuring schema.org is sufficient. I don't know if it itself will be luminous enough to contain all of the substaterials. Well, it may not be, but I really like the idea that Steven, or anybody like that, had us, came up with a standard for, you know, a particular type of, you know, whatever. That way, you know, if you're getting information from the internet, you don't have to go anywhere. You can just, when you receive it, it's gonna be just like however you wanna have it in, you know. It's like a good example of recipes. You don't have a name, you have the ingredients, and you have how to bake it. And everyone who has a recipe card, it's universal. And so the same with any other kind of digital information could be that same way. So that you always receive the information the same way. So if you just wanna look at, you know, fishing recipes or fish recipes, you could do it, it doesn't matter what site you go to, it would always standard it. This, the way it is now, you have to guess. There's no structure to content, really. In that fashion, you know, another one is research documents. So that's kind of one area that they are trying to develop schemas for. It's so bad if a scientist talks to something. That as, if you're looking for that information, you shouldn't have to search on the page, you should just be able to search in a minute from a computer or something. That's just what we get it all. I've heard of an issue, so much of that. So stay tuned. Well, I know Harvard is working on it too, because the system that they're trying to introduce is, you know, it's pay-as-you-go kind of thing. That's not what, you know, it's not universal, it's the primary, you know, it's just... Anything else, folks? Can you subscribe on the kind of scenario of the future, like where all of this, let's say it exists, what a user would do with it? Who's gonna use it and what would they do with it? That's a nice little question. In the future, what sort of user would use it and what would they do with it? I think it's nebulous for now, but I'm sure there will be massive educational times. And monetization of old content that we didn't know existed, simply because there was never any metadata with it. Almost like finding, I'm not gonna compare it to finding, you know, another Kennedy assassination reel, but along those lines, there may be content out there that's never been associated with any other content because there's no metadata there. Or the metadata isn't sufficient or it's in a different format. And I think that there's just going to be more of a harmonization, as I mentioned, in the lingo that they use to combine all the metadata from all these various standards or all these various vocabularies into a cohesive way of searching. And I don't know if Google is really ambitious enough to do that. Well, I mean, they're indicating that that's what they want to do. Right, right, but I mean- Because they're even giving you points to have structure data. No, I know that. And there's something called rich snippets and that's what I hinted to before. If Drupal itself were to incorporate semantic data within and it's already associated because every content type corresponds to another of what is at the resource, all those different things are mapped within Drupal 8 such that as soon as you set up your normal data structure within Drupal 8, it's automatically tied in and ready to be serialized and put out on the web. Google Rich Snippets will pull that and even without any special request will post that information right there in your search result. So that's not anything earth-shattering or new. However, the implementation of it is what's lacking. So it's sort of the same thing with this. We have a lot of this data, we have a lot of standards and we even have ways of crawling the web or spidering it to find other things. I mean, there are projects in here that will go through and determine whether the footage is legitimate. Remember those eight different criteria for whether it's authentic, whether it's quality, all those things like if there's a video dropout from a VHS take, it will notice that and there is, I have a data sheet here that talks about that, the metadata will represent it down to that granular level to say, hey, this is not the cleanest copy of this content, but there may be a cleaner copy in some other repository somewhere else that no one ever knew existed because it's under a proprietary silo. No one knows that it's there. So I just have a feeling that it's a bigger project than just one concern can take on. But if Drupal were there, since Drupal is so scalable, it could unify all those separate concerns and at least have a network for lack of better work. Well, which snippets is exactly what I'm referring to? Right. I mean, traffic data, the good is basically the same, but I totally agree with it. I mean, it could be phenomenal if it's size. Yeah. But the Drupal 8 is only OutputScheme.org now. It's not going to be a calculator, really. There are ways of overwriting that, I'm sure, but I think the foundation is in place already and we just have to find a house to build on.