 So, let's start the presentation. So, connection. You know, when everyone says about connection, we all are connected to each other by different relationships, right? If I am a speaker and you are an attendee, then how we are connected? We are connected by relationship. What is that relationship? You hear me, right? I can deliver you in my content. So, that's the relationship, right? So, this connection has been throughout this universe in different terms. Be that in a human-driven form that we understand, or be that in the form of digital technology. So, my connection term here is not on the other aspects, but rather on the digital platform. So, whenever we think about connection, then it gives us connection between the relationship between two nodes. So, we can see two nodes in A and B, right? So, what are they doing? Yeah, what are they doing? They are interacting, right? So, there is a bilateral relationship between them. Now, when we think about two different nodes and their relationship, so A interacts B in a different manner, and B interacts A in a different manner. Similarly, father interacts with son in a different manner, and son interacts with his father in a different manner, right? So, the relationship is something like that. When you see this in a bigger domain, then the connection gets a little bit of messier, and then we need to find where the connection exists between each of these terms, right? So, you can see here A is connected to B, B is connected to C, and C is connected to A. So, if I have to find the relationship between the B and the A, then I can easily find through the A to B, but if I have to find from D to M to A, then I have to go through the node D, right? So, there are some hidden places where we need to explore to find the connection. Now, so what kind of connection are you talking about in this series? So, this is what I am trying to deliver it to you, right? You have an application or a blog site or a website, right? So, you publish your content in the internet, and then the internet gets fired, right? You have content, video content, articles, many visuals, and then many how to do something like that, blah, blah, blah, right? Many systems you have recorded in the online systems, you have posted it all over there, and then made it available in the internet. And the internet is a big mess of things already. So, in that big mess, how can we categorize all the data? So, my presentation is on that. And then you can see if I have to find the meaning of symphony, then I can easily understand, right? How the different nodes contribute to the meaning of symphony. So, symphony is a music. I am an orchestra of symphony. So, you get a message, right? When I see this graph, then I know the meaning of symphony. So, if I have to find a meaning of one word, then in a whole system there we can search to other beings in the world also. So, you have to know about it, then you can know about my peers, know about my, know about, know about the students, know about my family, right? So, it can be anyway. You don't have to approach me already to know me. So, that's the major principle. So, the web of information. Information is itself a web. And I am talking here, the web of information, right? So, this is what? So, in this macro content, they are creating a web, right? And then we are putting that content in the Internet. So, that's itself a web. So, in this web of information, how do I recognize my content? That is the biggest challenge in today's world. It is related by, when you are talking about the web of information, you are trying to find information through Google search, through TikToks, through many social media sites, and all of these things are getting accumulated in the Internet. So, in this context, right? This is the diagram that I took from Cambridge Internet. So, that shows how the different genres of the music are connected to each other across different worlds. And you can see it is very large. And there are many nodes, there are many relationships, even though all of them are related to knowledge. So, all the Internet content that we are making available should fit, will be recognized as one of those nodes in this world. If I write in something about music, then the music tournaments goes in this way. Then you have introduced many concepts. So, how do you link these other? One way is, let Google do the task for you. You will connect all the terms for you. And another way is, you can manually provide the information so that anyone that is working in data intensive applications can actually get benefits from your website and the web content that you publish in the Internet. Okay. So, knowledge representatives. I have talked a lot about information and web and stuff. And then this is a new job, knowledge representatives. So, what is knowledge? It's a very important term, I think, I should say. So, whenever I start to describe a car, then I can say that car has something, this must win and car can drive by steering wheels. So, I can make influences also. So, if I say car is a vehicle, then I don't need to say that car will move on that road. So, knowledge representatives is something like that. You just give a very little information and then you get the most benefit out of the information that you provide. That is the knowledge over the knowledge. So, how do we do this in the Internet? Actually, I have talked a lot. So, how do you do this in the Internet? So, we have developed, we understand three concepts here already. Knowledge, relationships. So, when you are talking about knowledge, then that will be two different jobs that are represented in a graph. And then the relationship will be in RDP changes as arrows. And you can see here easily, Ram is a person, Ram works in IH company, Ram has a job. Those from three parts, they are known as chiplets. So, Ram is a person, he is one chiplet, Ram works in IH company, he is another chiplet. And the chiplets make up sense. Without them, they only exist, but they are not connected. So, when I am thinking about IH company and person, then I can work out throughout to the Ram. So, this is the concept actually. So, let's go how we can develop this one. So, we will know more about the knowledge representation rules and work out through some of the examples. And actually, this document looks boring, right? And we are going to develop this document. And it looks wonderful for the developers though, because even though it is difficult at first try, they can extract information from this document very easily. So, this is something that we are trying to achieve. This content will be available in the Internet through the RDF, right? And this is how we devise our RDF document. So, it is, you can see, it is an external document itself. And then we describe where the terms are collected. We collect it from the RDFS URL, RDF URI, FOF URI, SI URI, and OWL URI. So, all the content that I am publishing in the Internet are borrowed, actually borrowed from this website. So, what I am trying to do is I am trying to introduce my concept but with the help of established concepts, you know, those which are probably in the Internet, with the help of those I am trying to publish my content away. And here we are trying to define new object property, right? So, this is a new object property. Object property is the relationship that we are trying to define. And then it talks about our home base. And it has a title, it has a website, and the object property ends here. So, it looks something similar to schema.org, right? If you are involved in SEO, then it looks something like that. So, we are trying to do something like that. But what we are doing, we are not using the concepts introduced in the Google through schema.org. But instead, we are developing our own concepts, own rights, right? We are the developers. We are making our own content. And then we think that this community needs these terms. Then why should we always borrow from the Google? Everything should not be Google, right? Something should come from us. So, this is an approach that we need to think whenever we are thinking to contribute to the internet community by developing our own terms. So, you can see here, there are links. Actually, these links are not any links. But these links define a specific path to the certain term that you have introduced. And we name it as URI, right? So, anything that is available through the RDF document can be accessible through the URI, right? Not only the website is available in the internet through the links, but also every path that you introduce are available through links. So, what does it create? We can now use the links again and again so that we can make more and more relationships. So, I want to now revise this, you know. So, if you have understood knowledge-based documents, then I think you get a little bit of idea. So, let's ask ourselves, are we using knowledge-based documents, right? So, you have to answer anything, answer now, okay? So, my first thing to you, are you using WordPress? Yes. Yes? Okay, if you are using WordPress, then you definitely know about SU. Are you using SU? Yes. Yes? Okay. So, if you know SU, then you think, you know, schema.org, yes? So, schema.org publishes all the concepts that you use for source engine optimization, right? And then, when you use the concepts, trans concepts from schema.org into your website, then they are available in the Google search. And how they appear is SU meta text. Now, if everything I said are very clear to you as your daily lifestyle as a developer or as a content writer, then I think, you know, you are using knowledge representation already, right? So, it is not a new term or rather a term that you should be familiar with. I'm only trying to focus on that. So, let's look at these steps to build our knowledge-based document. And here, I have listed out some of the, some of these points that we will be going through the demonstration. So, this is a, Protezy is an open source software. We will learn to use Protezy because looking at the RDF documents, all documents in itself is like working in the black and white script. And it gives more UI experience to the developer or non-developer who want to use their own all-base documents, RDF documents. And then, we will use existing all documents that are available today. And then, we will add own relationships, create instances, build our own all documents and publish using URI. So, next we go for the demonstration. And in this demonstration, you will be looking at a simple example of how you use all documents in the internet. And then, whenever you are publishing your content using that rules that you have just developed, then, so, this is the video. So, first thing you will do, obviously, is the Protezy. This is open source software. You can find it in this site. And why I am using Protezy? Because it is open source and also it is very popular and using academic resources. And here, you will find your own URL where you will publish your all documents, your document or RDF document. And then, using this URL, you are going to publish your content. And in your document, you start everything with theme. There is theme in everything. In classes, in objects, in object relations and in individuals, everything has a theme. So, you can see here, I have listed class, I have a theme. Object property has a theme. Individuals, non-individuals don't have theme because they are inherited from the class. So, let's connect the dots. So, we have two nodes here. And we are trying to connect it to our all document using object property. So, first, let's overlay the individuals. So, this goes some of your trails that you can do later in the evening. So, you just add on. Where the nodes can, you can, with your dictionary, you just load on here. This is the startup. And then, after that, let's understand how the nodes will be connected to each other. Because it gets easier. So, here, you define everything. He has a sibling. He has a parent. He lives in this city. Kind of like that relationship. So, with the help of those object relationships, we are making RDF documents. And then, after that, we go to the class declarations. So, class is declared. And then, so, this goes on. And then, after you introduce all the class concepts in the all document, or the RDF document that you have just introduced, you see that is a all file. And then, you can forest that content using a load. So, load what? Increase a human-edible site from that XML document. You just create it. And then, to implement logic, you just, you borrow those concepts from the URI document. You just publish. So, it's very easy. You just introduce the concept. And then, you use that concept in your document.