 Okay, here we go. My name is James Pitt and this is about semantic Ethereum and When you talk about semantic or some semantic technologies like the semantic web It starts with metadata So you so what is metadata? It provides context to the data that you have and so when you're marking up HTML your your Creating context for the data that you've included in your web page and it in that context can run very deep and Regular metadata that we usually deal with as HTML developers It it's it's a bit of a burden when you do it But if you want to go to something like the semantic web it has it's a quite a big endeavor so the semantic web was proposed by Tim Berners-Lee who created the web and When the person who created the web proposed Proposes a new idea a new concept a new set of standards We're inclined to pay attention to him because we're grateful and it's he's a genius so a Lot of people got very excited and I drunk the Kool-Aid myself I got extremely excited about it and so he started with web of content Which is the current web and then he would he expanded it to be a web of data and a web of trust And as we all know, we're solving the trust aspect of this and The deeper sense of what he's talking about is that Once you establish all this context and once you know the source of the context you You you create something that's almost a not so much of a thinking being but something that is Meaningful that that all the information is connected together in a very formal way And that can make that made a lot of people very excited and a w3c which Which maintains its standards of the web develop the standards of the semantic web and many many tools came out standards Lots of interesting diagrams like that to describe how things connect together But it largely failed and You'll find many articles about how the semantic web was a complete bust But the thing is there there's there's a lot of standards that are out there but They just weren't useful for people and they're a bit of a burden to work with And famously Corey Dr. Rowe even before the semantic web was really formally a set of standards He actually took on just metadata itself the whole concept. He said it's met a crap and Very snarky, but it was very insightful, too He talked about insurmountable obstacles Lies laziness stupidity impracticality And it's a great article if you look it up the seven straw men of meta utopia We ourselves are utopians in a way so we can learn a lot from people who just simply say things like that Perhaps Tim Berners-Lee should have listened to that a little bit But the thing is even though semantic web is a failure or perhaps not to people who are still working on it Metadata is ubiquitous anyone who's worked with web pages knows and the simple fact is apps share data and that data has important context and Much of the data as as web developers know is is embedded in HTML and that's the standard micro data API calls are out there and the documentation behind a fight API calls can be considered metadata And that's in it. It's one of the reasons why we must maintain great documentation And much of this of the semantic web is out there Not really forming a full semantic web not really forming something that everyone uses, but it's out there in it It's useful. For example, Wikipedia has been converted into a database and you you can so wiki data You can go in there and pull a lot of data relate things together. It's very useful So often we use metadata without really realizing it for example the emails that you receive and Gmail about your flight actually contain Tags metadata micro data in there and that's what Google will generate from those from that micro data and GitHub actions Often when you do search results, you'll see these little info boxes, which are somewhat controversial Google grabs this data from various places and actually creates a summary much like Wikipedia and Yeah, those are called info boxes So the thing about there's sort of a conundrum about metadata in general is if if you're if you're too loose about it It it's you're not clear right a famous lawyer said what you know what is is what is the definition of is Sometimes we can be unclear So and it can lead to ambiguity And if you over structure data, of course, it's burdensome And here's some well-known connect to characters If you think about the personality people who keep correcting you and saying you can't say it that way, you know this You can't do it that way Too much structure is annoying and developers don't want to deal with it, right? So Let's go look at what the semantic web is right highly formalized metadata. So It's it's very strict. So whether something conforms to to What what your ontology is or not is really clear It's layered on top of the open web But lots of standards data and tools And here's the things that it provides. It's really important is There's linkage and There's lots of reference through your eyes the other one is the descriptions like how what things are and Like somebody is a person What is a person? Well, you might have a resource that describes what a person is sounds ridiculous But if you want to do something more automated, it might be good to know that this object is a person and this object is an airplane And the deeper side of it is reasoning That you structure your data in a way that something can reason about it And so here's why this is what Tim Berners-Lee Wanted and this is what he was proposing. This is why we all go through this This work to build a semantic web, which many people didn't and ideas saw for agents. That's a big one That the notion was that if we all have the structured data out there something could comprehend it and create Automated services for us a range air plane flights agents things like that and I think I think one of the more interesting aspects of it was like an ecosystem of value chain of data if all the data is More formally connected you can you can build things on top of it reliably and in a way That's one of the great benefits of smart contracts So I'll give you that I'm gonna go over an interesting example some others a tool called protege and that's how you create ontologies and protege that people did protege did really humorous ontology called pizza and this this pizza ontology will help you bake the Perfect pizza data and you can't violate it like you can't put a hamburger bun on top of that thing and call it a pizza And you can actually validate this verify this thing so Think about linkage So here's some standards that that deal with linkage and you have your eyes which we're all familiar with but There's actually really specific ways to use your eyes And XML namespaces and you've probably seen these things in a lot of HTML You don't know what they are But essentially these are defining With with these your eyes what these names namespaces are as they're used later on in this HTML or in this case in this RDF and You can see down here how they're utilized how these namespaces are utilized Like right there. You have a creative commons license and you can see right there terms license What is a turn what are terms? What is a license? Well, something automated can go up here and and look at and And go to that URL and go find out what terms are and if you go to that URL about terms You can learn and see data about what those terms are if that URL still works That's the problem with the web is that these URLs might not work anymore often These servers go down So descriptive meaning It's it's essentially symbols like what what is describing what what is the name of something and it seems silly to us because we just talk we understand the stuff but you know something automated really It's it has to know so an assertion that we might make is Los Angeles it is a city the assertion on a semantic web would be broken up like this Subject predicate object this object is a URI to really clear what? Los Angeles is it's a type of and all this stuff right here This is at the basis of a standard called RDF This is called a triple and RDF is all about declaring many many many triples To create something. It's meaningful and and then it even connects so Descriptive meaning standards how how it would be expressed in the pizza ontology So you have toppings right you want to talk about what a topping is it's a functional property and ingredient of pizza And this is how you would declare that for a machine a machine could possibly understand what a topping is Not that the machine understands what a topping is but the machine would be able to interact with topping data in a way that is reasonable, right It's as a developer it seems ridiculous however that you go through this effort to help something automated So to take it one step further and it gets further and further and deeper and deeper the more you dig in structural meaning To be able to reason about something you have to know how these things might relate how these entities that you're talking about pizza toppings Mushrooms how they might relate and what is appropriate? Like it might not be appropriate to put a pizza as a topping on top of a mushroom and Still call it a pizza. That's not valid So that's ridiculous, but to a machine that really might count if it's making pizza. So Here's how the standard might come come about there's There's something in in in the In the ontology standard w3c owl. It's called transitive property now here This is the almost philosophical notion about it, but it's philosophical ingredients of ingredients are ingredients of the whole and The idea is that you you have an ingredient on a pizza That ingredient may have a sub-ingredient But that sub-ingredient is still an ingredient of the pizza and it's amazing But you have to tell a machine about that otherwise it's gonna get very confused and possibly make a pizza that isn't isn't gonna work out, right? So here's here's how that looks Again as a developer, I might be terrified of this But I might use a tool that would generate this Not enough tools are out there that are easy to deal with not enough tools are out there generating this kind of thing So here's here's a here's one of my favorite topics these crazy pizzas they make in places like Taiwan and Japan Probably Hong Kong this pizza has little baby hot dogs little Ketchup's on top of each baby hot dog and then you can kind of see the logic Now if you want to make an automatic pizza make baker It's it could use that ontology and potentially make this pizza and still be a valid pizza according to the ontology But it's kind of ridiculous. That's why I chose this Um Really, it's It's pedantic like it's it's it's too much work and that's man who's spawning called it right there And he actually worked on many standards at the W3C And he started digital bizarre which is a really interesting company right now And I consider him sort of an anti-hero. He developed a new standard called Jason LD and The idea is that you're going to add context to data with a lot less work as a developer now Jason LD is becoming a very important standard like for example the in Google accepts it if you're an airline and you want you want the the Flight tickets to show up in your email that way Google will accept Jason LD. So Jason LD has become quite quite a large standard and here's what it looks like It's a lot less ponderous than the RDF that you saw earlier. It's not XML It's Jason very developer friendly, but it still has a lot of elements that are semantic or Provide context So when you think about semantic Ethereum Like what's the appropriate level? How far do we want to go? I I consider it. I'm thinking about it And I think it's important to foster creativity, but not to overdo it right just enough for for us to have Composability and you know, this is a good metaphor. You create a standard for Lego brick But you let people build whatever they want with it, but you need to have some structure And Ethereum obviously has a lot of metadata involved addresses signatures token balances You know, we're gonna have identity claims the URIs are associated there in the descriptive side, you know, you have ABI's documentation, of course and structure enforced in the EVM like you you can have As many objects as you want and you know that nobody is going to mess around with it. It's done right so One of the reasons why we we should put more metadata if possible into our work Is the permanency of it? We might not be around and this this application is still being used in the future and Obviously ecosystem Thinking about tokens or identity these these are Identity itself is potentially creating great ecosystems You create these footholds when you do metadata when you do it, right? and swarm itself is actually quite an opportunity because You can use JSON LD in there and you can connect Connect all these things together like right now. We're thinking you'll you'll refer to JSON LD that's hosted on swarm in your contract But you should do it the other way around too so that all your documentation all your data all your contracts everything Somebody could figure it all out even if you're not there to explain it even if your documentation is on the web that no longer exists So the lessons are pretty clear Be light be light about standards If if we have standards, it's more like documentation and we really encourage people to do it. It's fun And the key is steal the good stuff from the W3C because they really do have a lot of good ideas We don't have to do it all but just explore it and you'll find it. There's there's a lot of very interesting stuff in there Just don't explore it too much because it's quite overwhelming. It's for it's ridiculous sometimes But still the vision of it is quite amazing. It's it's very interesting history. So that's it Hope this helps you make your applications That's it