I expressed the idea of ββthe inevitability of the transition of the global network from a site-centric structure to a user-centric one back in 2012 ( or in abbreviated form ). This year I tried to develop the theme of the new Internet in the text . Now posting the second part of the article. (I advise you to review before reading this page).
So what happens? Internet in the web 3.0 version is there, but there are no sites? What then is there?
There is data organized in a global semantic graph: everything is connected to everything, everything follows from something, everything was noticed, changed, created by someone specific. The last two points about βshouldβ and βsomeoneβ remind us that the graph should not be object, but subject-event. But this will be a separate story (previously see below). ). For now, it is enough for us to understand that the web 3.0 semantic graph is not a static set of knowledge, but is temporal, fixing the relationship of objects and actors of any activity in their temporal sequence.
Also, speaking about the data layer, it should be added that the global graph is necessarily divided into two unequal parts: a model tree that describes the connectivity of actions, concepts and their properties (corresponds to the set of terminological axioms TBox in OWL), and an object graph containing the fixation events of specific property values ββof things and actions (a set of statements about ABox individuals in OWL). And between these two parts of the graph, an unambiguous relationship is established: data about individuals - that is, specific things, actions, actors - can be formed and written into the graph only and exclusively according to the corresponding models. Well, as already mentioned, the global graph - first of all, its model part and, accordingly, the subject one - is naturally divided into segments according to thematic areas.
And now, from semantics, from data, we can move on to discussing the second epithet of web 3.0 - βdecentralizedβ, that is, to a description of the network. And it is obvious that the structure of the network and its protocols should be dictated by the same semantics. First of all, since the user is the generator and consumer of content, it is natural that he, or rather, his device, should be a network node. So, web 3.0 is a peer-to-peer network, the nodes of which are user devices.
To save in a data graph, for example, a description of a certain individual, the user must form a network transaction according to the existing concept model. The data is stored on the user's device and on the sites of other users subscribed to this model. Thus, exchanging transactions on a fixed set of models on which their joint activity is implemented, the participants in this activity form a more or less autonomous cluster. It turns out that the entire global semantic graph is distributed distributed across subject clusters and decentralized within clusters. Each node, working with certain models, can be included in several clusters.
Describing the network level, it is necessary to say a few words about consensus, that is, about the principles of data validation and synchronization on different nodes, without which a decentralized network cannot work. Obviously, these principles should not be the same for all clusters and all data, because transactions in the network can be both legally significant and official, junk. Therefore, several levels of consensus algorithms are implemented in the network, the choice of the necessary one is set by the transaction model.
It remains to say a few words about the user interface, about the semantic browser. Its functions are trivial: (1) graph navigation (by topic clusters), (2) searching and displaying data by domain models, (3) creating, editing data and sending network transactions by relevant models, (4) writing and executing dynamic action models, and, of course, (5) storage of graph fragments. This is a short description of the functions of the semantic browser and is the answer to the question: where are the sites? The only place that the user "visits" in the web 3.0 network is his semantic browser, which is a tool for both displaying and creating any content, any data, including models. The user himself determines the boundaries and form of displaying his network world, the depth of penetration into the semantic graph.
That's understandable, but where are the websites? Where do you need to go, what address to type in this very βsemantic browserβ to get to Facebook? How to find the company's website? Where to buy a T-shirt or watch a video channel? Let's try to figure it out with specific examples.
Why do we need Facebook or another social network? Obviously, for communication: to tell something about yourself and read, see what others are posting, exchange comments. At the same time, it is essential that we do not write to everyone and do not read everything - communication is always limited to dozens, hundreds, well, several thousand virtual friends. What is needed to organize such communication within the described configuration of a decentralized network? That's right: create a community cluster with a set of standard action models (make an entry, send a message, comment, like, etc.), configure access rights to the models and invite other users to subscribe to this set. Here we have βfacebookβ. Only not the global Facebook, which dictates terms to everyone and everything, but a customizable local social network, which is at the complete disposal of the cluster members. The user sends a transaction to the network according to one of the community models, say, his comment, the cluster members subscribed to this model receive the text of the comment and write it to their storages (attach it to a fragment of the subject graph) and display it in their semantic browsers. That is, we have a decentralized social network (cluster) for communication of a group of users, all the data of which is stored on the devices of the users themselves. Can this data be visible to users outside the cluster? This is a question about access settings. If there is permission, then the content of community members can be read by the software agent and presented in the browser of anyone who will search the graph. It should also be noted that the number and complexity of cluster models is not limited by anything - anyone can customize the community to suit the needs of any activity. Well, obviously, users can be members of an arbitrary number of clusters, both as active members and simply by subscribing to individual read-only models.
Now let's answer the question: how do we find the company's website? The answer is trivial: the place where comprehensive data about all companies is located is the corresponding sector of the semantic graph. Browser navigation or a company name search will help you get to this location. Then it all depends on the user - what models he needs to display data: a brief presentation, full information, a list of services, a list of vacancies or a message form. That is, a company for its representation in a semantic graph must use a set of standard models for sending transactions to the network, and immediately data about it will be available for search and display. If you need to customize and expand the presentation of the company on the network, it is possible to create your own models, including designer ones. There are no restrictions here, except for one: new models must be embedded in a single tree in order to ensure data connectivity in the subject graph.
A trivial solution for e-commerce as well. Each product (mobile phone, T-shirt) has a unique identifier, and the manufacturer enters the product data into the network. Naturally, he does this only once, signing the data with his private key. A company that is ready to sell this product places several standard-model price and delivery statements in the semantic graph. Further, each user independently solves the search problem for himself: whether he is looking for the right one among the goods that a seller known to him can provide, or he compares the same type of goods from different manufacturers and only then chooses a convenient supplier. That is, again, the place where the selection and purchase of goods takes place is the user's semantic browser, and not some website of the manufacturer or seller. Although, of course, both the manufacturer and the seller have the opportunity to create their own product display models that the buyer can use. If he wants, if he finds it convenient. And so, he can do everything using standard models for searching and displaying data.
It is worth saying a few words about advertising, about its place in the semantic web. And its placements remain traditional: either directly in the content (say, in videos), or in content display models. Only between advertisers and owners of content or models is the intermediary in the form of a site owner eliminated.
So, the functioning scheme of the semantic decentralized network, presented from the userβs point of view, is extremely unified: (1) all content is placed in a single global semantic graph, (2) content is recorded, searched and displayed according to concept models that provide semantic data connectivity, ( 3) user activity is implemented according to dynamic models, (4) the only place where activity occurs is the user's semantic browser.
Source: habr.com