<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">ProductKG: A Product Knowledge Graph for User Assistance in Daily Activities</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Michaela</forename><surname>Kümpel</surname></persName>
							<email>michaela.kuempel@uni-bremen.de</email>
							<affiliation key="aff0">
								<orgName type="department">Institute for Artificial Intelligence</orgName>
								<orgName type="institution">University of Bremen</orgName>
								<address>
									<addrLine>Am Fallturm 1</addrLine>
									<postCode>28359</postCode>
									<settlement>Bremen</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Michael</forename><surname>Beetz</surname></persName>
							<email>beetz@cs.uni-bremen.de</email>
							<affiliation key="aff0">
								<orgName type="department">Institute for Artificial Intelligence</orgName>
								<orgName type="institution">University of Bremen</orgName>
								<address>
									<addrLine>Am Fallturm 1</addrLine>
									<postCode>28359</postCode>
									<settlement>Bremen</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff1">
								<address>
									<postCode>2023</postCode>
									<settlement>Sherbrooke</settlement>
									<region>Québec</region>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">ProductKG: A Product Knowledge Graph for User Assistance in Daily Activities</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">77FD687C7C55A038322BB598DC69F3FA</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T19:26+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Knowledge Graph</term>
					<term>Web Knowledge Acquisition</term>
					<term>product ontology</term>
					<term>semantic Digital Twin</term>
					<term>Knowledge Graph Application (M. Beetz) 0000-0002-0408-3953 (M. Kümpel); 0000-0002-7888-7444 (M. Beetz)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The Web offers plenty of product information that is valuable for supporting decision processes. Research on Web knowledge acquisition and the Semantic Web has led to the creation of many domain ontologies and Web applications. What still is lacking is a connection of such knowledge to the real world. If object information is linked to environment information, users can get better, more personalised support in their daily activities like shopping or cooking since this enables them to link information about leftover products in the fridge to recipe information or a health profile to products the user is looking at in the store. It has been shown that semantic Digital Twins can successfully link object to environment information that can be used by agents like smartphone or service robot. Such semantic Digital Twins can offer even more services to users if they are connected to product information from the Web.</p><p>This work introduces ProductKG, an open-source product knowledge graph integrating modular product information from the Web as well as accurate environment information from a semantic Digital Twin that can be customised for different applications and used devices as an example knowledge graph for assisting users in daily activities. We describe the design process and modularity of the knowledge graph as well as example applications of it, including an Augmented Reality shopping assistant, a dietary recommender and a hands-free recipe application. The modular ontologies enable personalisation of applications as well as accessing object information in relation to the current environment. We evaluate the acceptance of one example application through a user study. ProductKG is publicly available and will be maintained and extended over time in order to facilitate various applications such as in the retail and household domain.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>In the Semantic Web, ontologies and knowledge graphs have been a research focus for a while, resulting in partially interlinked domain ontologies with different consumer applications. It has been shown that knowledge graphs are a powerful tool that can be used to efficiently answer questions. However, there is a need for research on linking knowledge graphs to real world systems. If knowledge graphs can be grounded in the real world, the contained knowledge becomes perceivable and actionable to users. While we believe that this connection of object to environment information is beneficial for many different domains, in this work we concentrate on product information, which is due to • Environment structure. Products often hold a barcode as identifier and can usually be found in very structured environments: they are stored in shelves or cabinets, which helps in identifying perceived objects. • Availability of environment information. Digital agents can already create environment models of retail stores and household environments autonomously <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref>. • Availability of Web Information. Product information as well as product images are available in many web stores and consumer websites.</p><p>It has been shown that semantic Digital Twins (semDTs) can successfully be used for linking object to environment information in the retail domain for customer support <ref type="bibr" target="#b2">[3]</ref>. The concept of a Digital Twin, "the digital equivalent to a physical product" was introduced by Grieves in 2003 <ref type="bibr" target="#b3">[4]</ref>. Using Digital Twins to create exact virtual representations of the real world has been a technology trend in digitisation of manufacturing and industry <ref type="bibr" target="#b4">[5]</ref>. A semantic Digital Twin can be described as the semantic connection of environment information into a digital representation of an environment. While a semDT offers detailed environment information, it only offers limited object or product information from connected enterprise management systems. We therefore extend the idea and link semDTs to a knowledge graph of product information acquired from Web sources. In this work, we refer to a knowledge graph as an aggregation of ontologies comprising Web information that allow reasoning about the contained facts. With this connection we get access to both detailed environment and vast product information.</p><p>This work introduces ProductKG, a knowledge graph that consists of semantic product information from the Semantic Web and the World Wide Web in modular ontologies that are linked to environment information which can be combined and customised for various applications. It enables a customer browsing the aisles with their smartphone to highlight all deodorants that were dermatologically tested but also visualise nutritional information for a product in the fridge, for example. In this work we describe the creation of the ProductKG knowledge graph and its ontologies. We showcase the benefits of using ProductKG in example applications in retail and household environments as depicted exemplary in Figure <ref type="figure" target="#fig_0">1</ref>. The applications use the same basic user profile with different implementations like highlighting product preferences, recommending recipes for available products or showing preferred information such as product labels. The novelty of ProductKG lies in the connection of exact location information from a semantic Digital Twin to modular product information acquired from the Web into a knwoldge graph, leading to various applications with consumer focus as an embodiment of the contained knowledge.</p><p>The main contributions of this paper are: first, we create ProductKG with its modular ontologies based on Web information, link it to other Semantic Web sources and make it publicly available. Second, we integrate semDT environment information in such a way that it can be used by AR devices as well as robots. Third, we showcase the applicability of ProductKG in daily environments on smartphone and smart glasses, thus making ProductKG perceivable and actionable. These contributions are validated by a system usability study for one of the applications.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related Work</head><p>On the one hand, recent research has focused on standardised mapping, in particular of retail environments. The benefits of using standardised maps has been identified in <ref type="bibr" target="#b5">[6]</ref>. The idea of creating semantic Digital Twins of retail environments as standardised maps has been proposed in <ref type="bibr" target="#b2">[3]</ref> for shopping assistance or shop-floor assistance for product refilling. It has additionally been shown how semDTs can be used in retail applications to route a customer to a searched product on different devices such as smartphone and robot <ref type="bibr" target="#b1">[2]</ref>. While the shown applications reveal the power of semantic Digital Twins and the included environment information, they lack detailed product information and cannot easily be extended to other applications like finding substitute products in a store or recipes one can prepare with a given product.</p><p>On the other hand, there has been research on creation of product knowledge graphs (e.g. <ref type="bibr" target="#b6">[7,</ref><ref type="bibr" target="#b7">8]</ref>) and food product knowledge graphs, resulting in partially interlinked domain ontologies with consumer applications ranging from agricultural over health specific to recipe centered (e.g. <ref type="bibr" target="#b8">[9,</ref><ref type="bibr" target="#b9">10,</ref><ref type="bibr" target="#b10">11]</ref>). Although the created ontologies, knowledge graphs and their exemplary applications are impressive, they do not connect the contained object or product information to environment information.</p><p>This work aims at bringing together both research topics by interlinking semantic Digital Twins with a product knowledge graph.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Acquired Knowledge</head><p>Knowledge graphs can be created a) manually (which will not be further discussed in the following), b) by accessing structured external (Web) sources and c) by accessing unstructured external (Web) sources <ref type="bibr" target="#b11">[12]</ref>. ProductKG consists of a location ontology created by accessing a robot map (as described in <ref type="bibr" target="#b0">[1]</ref>) as well as modular product information ontologies that contain structured or unstructured Web information as described in the following.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Structured External Sources</head><p>In order to generalise applications for the use on different devices and in differing applications, we need to have precise, interchangeable environment information. A standardized map is also beneficial for localization of products in a store. We create a location ontology that is linked to precise environment information in a semantic Digital Twin environment model. A location ontology can be generated for any indoor environment following the approach described in <ref type="bibr" target="#b0">[1]</ref> and <ref type="bibr" target="#b2">[3]</ref>. We additionally derive product dimension information from the perception system. The robot uses its RGB and RGB-D sensors to identify the amount of consecutive products and calculate product width, height and depth.</p><p>The positions in the semantic Digital Twin use a fixed reference frame with a given origin, usually set to a randomly chosen corner of the room. In contrast to this, Augmented Reality (AR) devices use the varying device position when starting an application as origin and display its digital content relative to the device position. To solve this discrepancy for a use of the location ontology in both robot and AR applications, we encode all product locations in the location ontology relative to shelf, table or other object positions as described in more detail in <ref type="bibr" target="#b1">[2]</ref>. In the AR shopping applications we then use spatial perception and match the world origin of the game to the reference frame origin of the semantic Digital Twin. We also use world anchors for locking positions in the physical space, a technique that has proven effective in other work <ref type="bibr" target="#b12">[13]</ref>. World anchors need to be created once and will be loaded in every subsequent run of the application. Thus, product positions can be inferred relative to world anchors and digital content can be displayed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Structured Web Information</head><p>ProductKG integrates and links to structured Web information. On the one hand, we integrate parts of structured Web information like the FoodKG ontologies <ref type="bibr" target="#b10">[11]</ref> for a product-specific recipe recommendation. This is done by reusing the food product classification of the FoodOn ontology <ref type="bibr" target="#b8">[9]</ref>, which we intertwine with the product classification in the product taxonomy. ProductKG also integrates nutrition information from the Compositional Dietary Nutrition (cdno) ontology <ref type="bibr" target="#b13">[14]</ref> as well as nutritional product information like Nutri-Score, product labels or packaging size for food products from Open Food Facts<ref type="foot" target="#foot_0">1</ref> . For food classes, we access product class nutrition information from the FoodData central<ref type="foot" target="#foot_1">2</ref> from the U.S. Department of agriculture. The information is stored in a food-nutrition ontology, which then links to the FoodOn classification and therefore can be used for food products in the product taxonomy.</p><p>On the other hand, we interlink ProductKG to existing data sources by re-using many existing URIs and standard vocabulary as proposed in the Linked Data standards by Bizer, Heath et al. <ref type="bibr" target="#b14">[15]</ref>. We do not, however, use the owl:sameAs property but the oboInOwl:hasDbXref annotation property to interlink two data sources, as proposed by the gene ontology (GO) consortium <ref type="bibr" target="#b15">[16]</ref>. This is due to the fact that owl:sameAs increases file sizes since it creates duplicate entries while the oboInOwl:hasDbXref not only avoids duplicate entries but also looks more descriptive to a user browsing the ontologies using Protégé. Both the GO and the FoodOn workgroup are part of the OBO foundry <ref type="bibr" target="#b16">[17]</ref>, a community focussing on the development of interoperable ontologies for the biological sciences. We chose to reuse many of the OBO foundry ontologies (besides FoodOn and cdno we link to the human disease ontology (doid) <ref type="bibr" target="#b17">[18,</ref><ref type="bibr" target="#b18">19]</ref> and the human phenotype ontology <ref type="bibr" target="#b19">[20]</ref>) since they are openly accessible, are already following the same upper ontologies and have a strong community.</p><p>The product classification is further linked to Wikidata and the Product Types Ontology<ref type="foot" target="#foot_2">3</ref> wherever possible. We also use the Good Relations web vocabulary for E-Commerce<ref type="foot" target="#foot_3">4</ref> . Furthermore, ProductKG links to chemical information about allergens in the Chemical entities of biological interest (ChEBI) <ref type="foot" target="#foot_4">5</ref> ontology. The allergen ontology additionally links to other Semantic Web sources like the National Drug File (NDRF) of BioPortal<ref type="foot" target="#foot_5">6</ref> or Drugbank <ref type="foot" target="#foot_6">7</ref> . The advantage of using many Linked Data sources lies in its adaptability to changes. If a concept is changed in a linked source, the new information is immediately available in applications.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3.">Unstructured Web Information</head><p>For creation of the ProductKG ontologies we additionally acquire unstructured Web information to create structured knowledge sources that machines can query. In order for ProductKG to be usable in various environments, it needs a general product taxonomy that can be used for different domains of daily activities like at home, in drugstores and grocery stores. Most techniques for taxonomy creation aim at properly modeling a domain by using a pattern-based approach for taxonomy induction <ref type="bibr" target="#b20">[21]</ref> to learn simple but precise contextual patterns in a Web document. For a more generalised approach we use Information Extraction <ref type="bibr" target="#b21">[22]</ref> techniques on online store sitemaps of different retail domains to automatically create a more general product taxonomy.</p><p>Since online stores usually offer a sitemap in their robots file <ref type="foot" target="#foot_7">8</ref> , we use this sitemap for Information Extraction to avoid spamming of websites and be more time-efficient. Sitemaps of online stores are usually hidden .xml files that consist of a list of Uniform Resource Locators (URLs) of children websites so that crawlers can easily access them. For a general product classification we create a product class structure from sitemaps of two online stores representing different retail sectors, namely Aldi-Nord (grocery store) and dm (drugstore). We then use Owlready to generate ontologies out of the extracted information. The resulting product taxonomies are merged into one global product taxonomy that additionally integrates parts of the FoodOn food product taxonomy. For this, extracted product categories are standardised to lower case words while special characters and numbers are deleted. This allows for an accurate matching of categories of different stores as will further be explained in Section 4.3.</p><p>We further use Information Extraction to acquire product ingredient information from online stores for use in the ingredient ontology and information like brand, awarded labels, weight, filling capacity and country of origin from Codecheck 9 , a consumer-oriented product information website. Again, we standardise the extracted information as before and manually add additional semantic information such as linking a specific label to a label category. What is more, product ingredients are classified as allergens according to information from the U.S. Food &amp; Drug administration (FDA) website 10 .</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Composition of ProductKG</head><p>We continue to explain the contained ontologies in ProductKG as well their accordance to the FAIR (Findable, Accessible, Interoperable, Reusable) principles <ref type="bibr" target="#b22">[23]</ref> and how ProductKG can be extended in the following.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Ontology Alignment</head><p>As depicted in Figure <ref type="figure" target="#fig_1">2</ref>, the product builds the core of ProductKG. The modular ontologies in ProductKG have different foci that can be used to retrieve additional product information for different applications. All ontologies contained in ProductKG with their most relevant properties and their current use in applications as well as the number of axioms are detailed in Table <ref type="table">1</ref>. 9 Codecheck website: https://www.codecheck.info/ 10 FDA website: https://www.fda.gov/ </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 1</head><p>Ontologies contained in ProductKG with their most relevant properties and their use in applications. Italic information sources belong to ProductKG while all other mentioned sources are external. One major challenge in ontology alignment of ontologies with such different foci is the use of diverse upper ontologies. While ProductKG is based on the DOLCE+DnS Ultralite (DUL) ontology with its descriptions of relations of actions, objects and agents, the OBO foundry ontologies are based on the Basic Formal Ontology (bfo) defining occurrents and continuants. Thus, external concepts like processes that are defined as occurents in bfo need to be aligned with the definitions of tasks, actions and processes as events from DUL. To simplify ontology reuse in ProductKG, we focus on the domain and solely integrate product information. In particular, the main DUL class ProductKG is based upon is PhysicalObject -the class of all objects perceivable in an environment. In DUL, a 𝑃 ℎ𝑦𝑠𝑖𝑐𝑎𝑙𝑂𝑏𝑗𝑒𝑐𝑡 ∈ 𝑂𝑏𝑗𝑒𝑐𝑡 ∈ 𝐸𝑛𝑡𝑖𝑡𝑦. In bfo, a 𝐹 𝑜𝑜𝑑𝑃 𝑟𝑜𝑑𝑢𝑐𝑡 ∈ 𝐹 𝑜𝑜𝑑𝑀 𝑎𝑡𝑒𝑟𝑖𝑎𝑙 ∈ 𝑀 𝑎𝑡𝑒𝑟𝑖𝑎𝑙𝐸𝑛𝑡𝑖𝑡𝑦 ∈ 𝐶𝑜𝑛𝑡𝑖𝑛𝑢𝑎𝑛𝑡 ∈ 𝐸𝑛𝑖𝑡𝑦. In ProductKG we align these by stating that 𝐹 𝑜𝑜𝑑𝑃 𝑟𝑜𝑑𝑢𝑐𝑡(bfo) ∈ 𝑔𝑟𝑜𝑐𝑒𝑟𝑖𝑒𝑠 ∈ 𝑃 𝑟𝑜𝑑𝑢𝑐𝑡𝑂𝑟𝑆𝑒𝑟𝑣𝑖𝑐𝑒(gr) ∈ 𝑃 ℎ𝑦𝑠𝑖𝑐𝑎𝑙𝑂𝑏𝑗𝑒𝑐𝑡(DUL) a food product of the Food Ontology is a subclass of groceries in ProductKG, which we define as a Product or Service of the Good Relations vocabulary, which then belongs to the physical object class of DUL.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ontology Information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2.">Accordance to FAIR principles</head><p>The FAIR guiding principles for scientific data management and stewardship <ref type="bibr" target="#b22">[23]</ref> were proposed in 2016 in order to improve the reusability of data holdings. They introduce four principles: Findability, Accessibility, Interoperability, and Reusability that we apply to ProductKG as explained in the following:</p><p>• Findability: ProductKG and its application page are openly accessible and can be found at https://michaelakuempel.github.io/ProductKG/. We use persistent URLs (http://purl. org/ProductKG/) for the contained ontologies that redirect the user to the current storage location of the ontologies. • Accessibility: ProductKG is publicly available with all ontologies, a link to its triple store SPARQL endpoint <ref type="foot" target="#foot_8">11</ref> as well as an grlc <ref type="bibr" target="#b24">[25]</ref> RESTful API for the example queries <ref type="foot" target="#foot_9">12</ref>demonstrated in the shopping assistant applications. • Interoperability: Section 3.2 describes the different vocabularies that are used or linked to in ProductKG. Hence, applications built on those ontologies can easily integrate Produc-tKG information. • Reusability: Entities in the ProductKG ontologies use annotation properties like language labels (which currently are implemented in english and german), comments and links to term defining webpages such as wikidata or the product ontology as descriptors. All ProductKG ontologies come with a clearly stated licence, can be downloaded and reused.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3.">Extending ProductKG</head><p>ProductKG can easily be extended if new sources are linked to product names. Using product names for classification has been shown to be quite efficient for linking. For ontologies, Word2Vec can be used to expand the contained knowledge by learning sibling classes <ref type="bibr" target="#b25">[26]</ref> and for linking taxonomies one could use either Word2Vec or Node2Vec with good results. If we want to link quite different ontologies such as taxonomies to a brand ontology, the domain of interest changes from linking two "shampoo" classes to linking one "shampoo" class to "Elvital Dream Length Super Strengthening Shampoo", for example. Here, the distinct product name consists of multiple words. Doc2Vec has been shown to efficiently handle multiple words with context <ref type="bibr" target="#b26">[27]</ref>. Therefore, we use Doc2Vec for linking of the different ontologies to the product taxonomy.</p><p>Even product master data can easily be linked to ProductKG, which is important if different users want to access ProductKG information. For this, we propose to do a preprocessing to have all product names in lower case format. We tested linking product master data containing about 300,000 product names and received a top-1 accuracy of 80% and a top 5 accuracy of 97%. What is more, if the algorithm suggested to have an accuracy of more than 90%, it was actually true in 95% of tested cases.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Consumer Applications of ProductKG</head><p>Using ProductKG, we can answer many complex questions about products, their ingredients, contained allergens, nutrition values, labels, brands or recipes that can be prepared with them, for example. The connection to the semantic Digital Twin additionally enables to locate products in the current environment. It has already been shown in previous work how semantic Digital Twins can successfully be used for shopping assistants to help customers find searched products <ref type="bibr" target="#b1">[2]</ref>. The triple store used for storage of the knowledge graph offers a SPARQL endpoint for information access that can be accessed by different agents like robot or smartphone.</p><p>The following applications demonstrate the applicability of the ProductKG knowledge graph as one source of data for a range of consumer applications. In omnichannel applications with one source of data, it does not matter if the consumer accesses the information through a Web interface, a smartphone, smart glasses or via interaction with a robot. The following applications show how the same data can be accessed through various channels for different applications. The used devices in the applications are exchangeable.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1.">Application 1: Preference Visualisation in AR Using HoloLens</head><p>This openly accessible application <ref type="foot" target="#foot_10">13</ref> highlights all objects that do not comply with a set preference on a HoloLens as depicted in Figure <ref type="figure" target="#fig_0">1</ref> on the left. A user can specify a preference such as an unwanted ingredient and all products that contain the ingredient get a digital overlay, a red X.</p><p>To localize the HoloLens in the retail laboratory we use spatial perception and match the world origin of the Unity game to the reference frame origin of the robot environment map as discussed in 3.1. To load an environment map, a user has to scan a QR code that loads the semantic Digital Twin map including the parent anchor. Product positions are inferred relative to this parent anchor. Each product in the game is created as a X game object named according to the ProductKG product names. Thereby, objects can be set visible or invisible automatically according to the query result.</p><p>A consumer in the store will see a menu on the wall, displaying options of preferences like "vegan", "eco-friendly" or "no alcohol". Once a preference is chosen, all opposing products will be highlighted as depicted in Figure <ref type="figure" target="#fig_0">1</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2.">Application 2: Information Visualisation in AR Using a Smartphone.</head><p>This application highlights interesting product information using a smartphone. It uses image targets for image recognition. Therefore, we rely on images or barcodes of products available in daily environments. Hence this application works more reliable in the more static retail environment than in dynamic household environments.</p><p>A consumer using the app can scan a product they are interested in to instantly see interesting product information like which label the recognised product has as well as an information slider displaying the name of the recognized product. By clicking on or sliding of the product name, additional product information like contained ingredients and allergens or recipes that can be prepared with the product can be listed. Aside from that, the product can be added to the shopping cart. The smartphone application to visualize interesting product information is depicted in Figure <ref type="figure" target="#fig_0">1</ref> on the right for a recipe recommender and a shopping assistant. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.3.">Application 3: Personalised Nutrition Recommender</head><p>ProductKG offers a basic user profile ontology that can be integrated and instantiated in ontologies like the food-nutrition or ingredient ontology for personalised applications. Figure <ref type="figure" target="#fig_2">3</ref> shows an example nutrition recommender application based on personal dietary preferences 14 . A user can (but does not need to) enter personal information like weight, age, gender and daily activity level. The data is not saved, but the user is instantiated based on the given input values. In Figure <ref type="figure" target="#fig_2">3</ref>, a user is searching for products that are rich in vitamin D, nutritional values of coffee and nutrients and products that might treat a headache. The results pages show products in accordance to the preferences and query. Based on this, the user can proceed to see detailed product information or what recipes could be prepared with it. Through connected semDTs, users can also see where a searched product is available or compare prices.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">System Usability Evaluation</head><p>For an assessment of system usability we performed a user study based on the system usability scale, which we extended for a question about the helpfulness of the application, i.e. if the users think that the dietary recommendation will help them in achieving their goals. We performed the user study with n=24 participants by promoting the website and randomly asking website visitors for their feedback based on the following hypotheses:</p><p>• We expect that the application is easy to use. • We expect that the idea of the website is understood quickly.</p><p>• We expect that the functionality of the website is understood easily.</p><p>• We expect the overall application and its subpages to be perceived equally complex.</p><p>The performed user study yielded some interesting results, some of which are visualised in Figure <ref type="figure" target="#fig_3">4</ref>. Overall, the user study results suggest that users would reuse the application. 14 The Web Applications are available at: http://productkg.informatik.uni-bremen.de/ • As expected, the users did find the application in general easy to use. Surprisingly, this is only true for the general application. Some subpages were assessed as being too complex. • The users were able to quickly grasp the application and its subpages. Again, the overall application received better results than its subpages. • The functionality of the app was evaluated as easily understandable both for the general application and its subpages. • It is interesting to see that the results of the application in general and the subpages offering different information differ. Users were very interested in the symptom page and used it more than other pages. • The nutrition recommender subpage was evaluated as being very helpful.</p><p>• Most of the users would reuse the app. The symptom subpage received most interest.</p><p>Users said that they were most likely to reuse this part of the application. Those users that would not reuse the app mainly were disappointed in the design of the application.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Results and Future Work</head><p>This work describes the ProductKG knowledge graph with all its ontologies and points out the benefits of linking a knowledge graph to a semantic Digital Twin, making it perceivable and actionable. All sources used for information acquisition and creation of the contained ontologies are described. We show the applicability of the knowledge graph in various applications.</p><p>Having a publicly available knowledge graph makes it accessible to different machines, which we demonstrate by querying ProductKG by smart glass (HoloLens) and smartphone. The example applications emphasise the value of the connection of semantic product information to location information, while the power of the applications stem from the use of modular ontologies that can be personalized and queried through a single access point. ProductKG offers:</p><p>• A product taxonomy that can be reused for applications in different daily environments.</p><p>• A framework of modular ontologies that can be accessed for different consumer needs and applications. • A connection to existing ontologies like wikidata, FoodOn or ChEBI, allowing for further applications based on the contained knowledge. • A connection to exchangeable, standardised Digital Twin environment models, thereby enabling environment-dependent applications, bringing the knowledge to the user.</p><p>We believe that ProductKG is a powerful example of connecting knowledge graphs to semantic Digital Twins and will continue to use this approach for different domains such as bookstores as well as more user applications in daily environments. Future work will additionally focus on an integration of the different applications into a single daily activity application. Additionally, we hope to add more semDTs that are openly accessible and we plan on using knowledge graphs for enabling higher robot autonomy in daily environments.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Example applications enabled by ProductKG: left: smart glass shopping support, middle: smart glass recipe assistant, right: smartphone recipe and shopping support.</figDesc><graphic coords="2,447.02,531.22,56.25,96.67" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Overview of ProductKG ontologies and their links to external sources.</figDesc><graphic coords="6,89.29,405.95,416.71,220.41" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Personalised nutrition recommender.</figDesc><graphic coords="10,89.29,357.06,416.70,226.67" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Evaluation results for examining App usability.</figDesc><graphic coords="11,108.88,489.13,375.02,161.17" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">Open Food Facts: https://world.openfoodfacts.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">Food Data central: https://fdc.nal.usda.gov/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">Product Types Ontology: http://www.productontology.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">Good Realtions vocabulary: http://www.heppnetz.de/ontologies/goodrelations/v1</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">Chemical entities of biological interest: https://www.ebi.ac.uk/chebi/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">NDRF at BioPortal: https://bioportal.bioontology.org/ontologies/NDFRT/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_6">Drugbank: https://go.drugbank.com/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_7">A robots file is the /robots.txt file located at the root of a website with instructions for web robots on how to crawl the website and which information can be axtracted.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_8">The ProductKG API can be accessed at this SPARQL endpoint: https://api.krr.triply.cc/datasets/mkumpel/ ProductKG/services/ProductKG/sparql</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="12" xml:id="foot_9">Example queries can be accessed online: http://grlc.io/api/michaelakuempel/ProductKG/SPARQLfiles/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="13" xml:id="foot_10">HoloLens application: https://github.com/michaelakuempel/HoloPreferenceDemo</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>We thank Naser Azizi and Sorin Arion for their support towards this work.</p><p>The research reported in this paper has been partially supported by the German Federal Ministy of Education and Research; Project-ID 16DHBKI047 "IntEL4CoRo -Integrated Learning Environment for Cognitive Robotics", University of Bremen, the Federal Ministry for Economic Affairs and Energy BMWi within the Knowledge4Retail project, subproject semantic Digital Twin 01MK20001M (https://knowledge4retail.org) as well as the German Research Foundation DFG, as part of Collaborative Research Center (SFB) 1320 "EASE -Everyday Activity Science and Engineering", University of Bremen (http://www.ease-crc.org/). The research was conducted in subproject R04 "Cognition-enabled execution of everyday actions".</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Robots Collecting Data: Modelling Stores</title>
		<author>
			<persName><forename type="first">M</forename><surname>Beetz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Stelter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Beßler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Dhanabalachandran</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Neumann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Mania</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Haidu</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-031-06078-6_2</idno>
		<imprint>
			<date type="published" when="2022">2022</date>
			<publisher>Springer International Publishing</publisher>
			<biblScope unit="page" from="41" to="64" />
			<pubPlace>Cham</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Robotic shopping assistance for everyone: Dynamic query generation on a semantic digital twin as a basis for autonomous shopping assistance</title>
		<author>
			<persName><forename type="first">M</forename><surname>Kümpel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Dech</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Hawkin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Beetz</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 22nd International Conference on Autonomous Agents and Multiagent Systems (AAMAS 2023)</title>
				<meeting>the 22nd International Conference on Autonomous Agents and Multiagent Systems (AAMAS 2023)<address><addrLine>London, United Kingdom</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2023">2023</date>
			<biblScope unit="page" from="2523" to="2525" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Semantic digital twins for retail logistics</title>
		<author>
			<persName><forename type="first">M</forename><surname>Kümpel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">A</forename><surname>Mueller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Beetz</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-88662-2_7</idno>
	</analytic>
	<monogr>
		<title level="m">Dynamics in Logistics: Twenty-Five Years of Interdisciplinary Logistics Research in</title>
				<editor>
			<persName><forename type="first">M</forename><surname>Freitag</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">H</forename><surname>Kotzab</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">N</forename><surname>Megow</surname></persName>
		</editor>
		<meeting><address><addrLine>Bremen; Germany; Cham</addrLine></address></meeting>
		<imprint>
			<publisher>Springer International Publishing</publisher>
			<date type="published" when="2021">2021</date>
			<biblScope unit="page" from="129" to="153" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Grieves</surname></persName>
		</author>
		<title level="m">Virtually perfect: driving innovative and lean products through product lifecycle management</title>
				<imprint>
			<publisher>Space Coast Press</publisher>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The industry use cases for the digital twin idea</title>
		<author>
			<persName><forename type="first">P</forename><surname>Augustine</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Advances in Computers</title>
		<imprint>
			<biblScope unit="volume">117</biblScope>
			<biblScope unit="page" from="79" to="105" />
			<date type="published" when="2020">2020</date>
			<publisher>Elsevier</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">A personal handheld multi-modal shopping assistant</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Davis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Prasad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Schuricht</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Melliar-Smith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">E</forename><surname>Moser</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International conference on Networking and Services (ICNS&apos;06)</title>
				<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page" from="117" to="117" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Building an operational product ontology system</title>
		<author>
			<persName><forename type="first">T</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>-H. Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>-G. Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Chun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Shim</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Electronic Commerce Research and Applications</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="page" from="16" to="28" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">All you need to know to build a product knowledge graph</title>
		<author>
			<persName><forename type="first">N</forename><surname>Zalmout</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Liang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><forename type="middle">L</forename><surname>Dong</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 27th ACM SIGKDD Conference on Knowledge Discovery &amp; Data Mining</title>
				<meeting>the 27th ACM SIGKDD Conference on Knowledge Discovery &amp; Data Mining</meeting>
		<imprint>
			<date type="published" when="2021">2021</date>
			<biblScope unit="page" from="4090" to="4091" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Foodon: a harmonized food ontology to increase global food traceability, quality control and data integration</title>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">M</forename><surname>Dooley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">J</forename><surname>Griffiths</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">S</forename><surname>Gosal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">L</forename><surname>Buttigieg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Hoehndorf</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Lange</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">M</forename><surname>Schriml</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">S</forename><surname>Brinkman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">W</forename><surname>Hsiao</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">npj Science of Food</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page" from="1" to="10" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">An example of food ontology for diabetes control</title>
		<author>
			<persName><forename type="first">J</forename><surname>Cantais</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Dominguez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Gigante</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Laera</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Tamma</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the International Semantic Web Conference 2005 workshop on Ontology Patterns for the Semantic Web</title>
				<meeting>the International Semantic Web Conference 2005 workshop on Ontology Patterns for the Semantic Web</meeting>
		<imprint>
			<date type="published" when="2005">2005</date>
			<biblScope unit="page" from="1" to="9" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Foodkg: a semantics-driven knowledge graph for food recommendation</title>
		<author>
			<persName><forename type="first">S</forename><surname>Haussmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Seneviratne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Ne'eman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Codella</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C.-H</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">L</forename><surname>Mcguinness</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">J</forename><surname>Zaki</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="146" to="162" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Knowledge graphs on the web-an overview</title>
		<author>
			<persName><forename type="first">N</forename><surname>Heist</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Hertling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Ringler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Paulheim</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Knowledge Graphs for eXplainable Artificial Intelligence: Foundations, Applications and Challenges</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="page" from="3" to="22" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Augmented reality for industry 4.0: Architecture and user experience</title>
		<author>
			<persName><forename type="first">A</forename><surname>Jakl</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Schöffer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Husinsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Wagner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">FMT</title>
		<imprint>
			<biblScope unit="page" from="38" to="42" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Knowledge representation and data sharing to unlock crop variation for nutritional food security</title>
		<author>
			<persName><forename type="first">L</forename><surname>Andrés-Hernández</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Baten</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Halimi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Walls</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">J</forename><surname>King</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Crop Science</title>
		<imprint>
			<biblScope unit="volume">60</biblScope>
			<biblScope unit="page" from="516" to="529" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<author>
			<persName><forename type="first">C</forename><surname>Bizer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Heath</surname></persName>
		</author>
		<title level="m">How to publish linked data on the web</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">The gene ontology resource: 20 years and still going strong</title>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">O</forename><surname>Consortium</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Nucleic acids research</title>
		<imprint>
			<biblScope unit="volume">47</biblScope>
			<biblScope unit="page" from="D330" to="D338" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">The obo foundry: coordinated evolution of ontologies to support biomedical data integration</title>
		<author>
			<persName><forename type="first">B</forename><surname>Smith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ashburner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Rosse</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Bard</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Bug</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Ceusters</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">J</forename><surname>Goldberg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Eilbeck</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ireland</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">J</forename><surname>Mungall</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Nature biotechnology</title>
		<imprint>
			<biblScope unit="volume">25</biblScope>
			<biblScope unit="page" from="1251" to="1255" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Disease ontology: a backbone for disease semantic integration</title>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">M</forename><surname>Schriml</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Arze</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Nadendla</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y.-W</forename><forename type="middle">W</forename><surname>Chang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Mazaitis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Felix</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Feng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">A</forename><surname>Kibbe</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Nucleic acids research</title>
		<imprint>
			<biblScope unit="volume">40</biblScope>
			<biblScope unit="page" from="D940" to="D946" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">The human disease ontology 2022 update</title>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">M</forename><surname>Schriml</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">B</forename><surname>Munro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Schor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Olley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Mccracken</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Felix</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">A</forename><surname>Baron</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Jackson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">M</forename><surname>Bello</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Bearer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Nucleic acids research</title>
		<imprint>
			<biblScope unit="volume">50</biblScope>
			<biblScope unit="page" from="D1255" to="D1261" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">The human phenotype ontology</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">N</forename><surname>Robinson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Mundlos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Clinical genetics</title>
		<imprint>
			<biblScope unit="volume">77</biblScope>
			<biblScope unit="page" from="525" to="534" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Datarover: a taxonomy based crawler for automated data extraction from data-intensive websites</title>
		<author>
			<persName><forename type="first">H</forename><surname>Davulcu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Koduri</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Nagarajan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 5th ACM international workshop on Web information and data management</title>
				<meeting>the 5th ACM international workshop on Web information and data management</meeting>
		<imprint>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="9" to="14" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Open information extraction from the web</title>
		<author>
			<persName><forename type="first">O</forename><surname>Etzioni</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Banko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Soderland</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">S</forename><surname>Weld</surname></persName>
		</author>
		<idno type="DOI">10.1145/1409360.1409378</idno>
	</analytic>
	<monogr>
		<title level="j">Commun. ACM</title>
		<imprint>
			<biblScope unit="volume">51</biblScope>
			<biblScope unit="page" from="68" to="74" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">The fair guiding principles for scientific data management and stewardship</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">D</forename><surname>Wilkinson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dumontier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">J</forename><surname>Aalbersberg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Appleton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Axton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Baak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Blomberg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J.-W</forename><surname>Boiten</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">B</forename><surname>Da Silva Santos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">E</forename><surname>Bourne</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Scientific data</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page" from="1" to="9" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<monogr>
		<title level="m" type="main">Robotic Clerks: Autonomous Shelf Refilling</title>
		<author>
			<persName><forename type="first">A</forename><surname>Cavallo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Costanzo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>De Maria</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Natale</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Pirozzi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Stelter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Kazhoyan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Koralewski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Beetz</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-031-06078-6_6</idno>
		<imprint>
			<date type="published" when="2022">2022</date>
			<publisher>Springer International Publishing</publisher>
			<biblScope unit="page" from="137" to="170" />
			<pubPlace>Cham</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<analytic>
		<title level="a" type="main">grlc Makes GitHub Taste Like Linked Data APIs</title>
		<author>
			<persName><forename type="first">A</forename><surname>Meroño-Peñuela</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Hoekstra</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-319-47602-5_48</idno>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web: ESWC 2016 Satellite Events</title>
				<meeting><address><addrLine>Heraklion, Crete, Greece</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2016-06-02">May 29 -June 2, 2016. 2016</date>
			<biblScope unit="page" from="342" to="353" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">Using word2vec to build a simple ontology learning system</title>
		<author>
			<persName><forename type="first">G</forename><surname>Wohlgenannt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Minic</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ISWC (Posters &amp; Demos)</title>
				<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<monogr>
		<title level="m" type="main">An empirical evaluation of doc2vec with practical insights into document embedding generation</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">H</forename><surname>Lau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Baldwin</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
