{"id":68,"date":"2021-10-29T11:53:11","date_gmt":"2021-10-29T09:53:11","guid":{"rendered":"https:\/\/project.inria.fr\/mikrolog\/?page_id=68"},"modified":"2023-09-27T10:55:06","modified_gmt":"2023-09-27T08:55:06","slug":"presentation","status":"publish","type":"page","link":"https:\/\/project.inria.fr\/mikrolog\/","title":{"rendered":"MiKroloG: The Microdata Knowledge Graph"},"content":{"rendered":"\n

Context<\/h2>\n\n\n\n

Searching the web has changed our daily lives; documents on the web containing a list of keywords can be found in a snap. Then, users wanted to find Things, not strings<\/a>. Thanks to knowledge graphs (KG), Searching the web has changed our daily lives; documents on the web containing a list of keywords can be found in a snap. However, keyword searches often return many irrelevant documents, pushing users to refine their keyword list following a trial-and-error process. Then, users wanted to find Things, not strings. \u201cParis\u201d as a string refers to the capital of France, but also a city in Canada, in Arkansas, a movie, a band, a ship, a person, or a  manuscript. Considering languages, \u201cParis\u201d means a \u201cbet\u201d in French. Searching for Things means a keyword query returns a Thing or a collection of Things instead of documents. Searching for Things requires a knowledge graph storing entities representing Things, i.e., an instance of a concept such as a person, a place, an event, etc. For example, there is one entity for Paris<\/a> as a city and another for Paris as a manuscript of 1844. Thanks to these knowledge graphs, users who request movies of James Cameron<\/a> receive a list of movies where James Cameron and his movies are Things, i.e., entities defined in the KG. <\/p>\n\n\n\n

However, searching the web and searching for Things are entirely different. Searching the web offers diversity at the price of noise. Searching for Things delivers exact answers, but we lose diversity. Is there a way to have diversity without noise?<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

Objectives<\/h2>\n\n\n\n

Slides of cominlabs days 25-27 September 2023<\/strong><\/a><\/h2>\n\n\n\n

In MiKroloG, we aim to search the web with Things. As KG returns a collection of entities, such entities may be used to retrieve web pages that refer to them. In this way, it is possible to have both diversity and accuracy. For instance, we may search the websites selling \u201cJames Cameron movies\u201d ordered by price and rating or for experimental data related to the COVID pandemic published by UK public universities ordered by date. These queries first explore existing knowledge graphs to retrieve collections of things like “UK public universities” and “James Cameron movies”. Then, we explore which “commercial websites” or “university web pages” refer to these things, i.e., we searched the web with Things. <\/p>\n\n\n\n

Searching the web with Things<\/strong> requires a close connection between the web of documents and Knowledge Graphs. Currently, this connection is partially powered by the embedding of microdata in web pages. Half of the web pages integrate microdata describing people, places, organizations, events, products, and drugs following the  Schema.org<\/a> ontology. This represents billions of facts spread over millions of constantly evolving websites. Google Dataset Search<\/a> relies on microdata to search for datasets on the web, Google Shopping<\/a> relies on microdata to feed its marketplace and search for products.<\/p>\n\n\n\n

To search  the web with Things<\/strong>, we face three main scientific challenges:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

<\/p>\n\n\n\n