<?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">Extending Shape Expressions for different types of knowledge graphs</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Jose</forename><forename type="middle">Emilio</forename><surname>Labra-Gayo</surname></persName>
							<affiliation key="aff0">
								<orgName type="laboratory">WESO lab</orgName>
								<orgName type="institution">University of Oviedo</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Extending Shape Expressions for different types of knowledge graphs</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">881FEA8A36075F5FB04D0EA8524F9BDC</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T18:39+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>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Shape Expressions (ShEx) has been proposed as a concise and human-readable language to describe and validate RDF. Inspired by regular expressions, it offers an expressive formalism to describe graph structures based on regular bag expressions. Although plain RDF is one of the common data formats employed to represent knowledge graphs, there have been several proposals to either extend RDF with the so-called RDF-Star or RDF 1.2, or to employ other formalisms like property graphs. In this paper we present an overview and comparison of those approaches and propose three possible extensions of ShEx: ShEx-Star which can be used to validate RDF-Star, ShEx-N: that can be used when nodes also act as properties in RDF and PShEx, which can be used to describe property graphs. We present some examples and a semantics of each extension.</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>Although Knowledge graphs have been successfully adopted by the industry, an important aspect of their practical application is the quality of the data that they contain. In order to increase their quality, it is necessary to have some mechanisms that can check the conformance of the data to some kind of schema. Knowledge graphs are usually considered schema-less, because there is no mandatory schema, however, in most cases the data curators have an implicit schema in mind. Having the possibility to materialize that implicit schema into a machine processable form that can be automatically verified can mitigate the risk of non-conformant data.</p><p>In practice, there are several types of technologies that can be used for knowledge graphs <ref type="bibr" target="#b0">[1]</ref>: Directed edge-labeled graphs, whose main representative are RDF graphs, and Property graphs, which allow property-value pairs and labels to be associated with nodes and edges.</p><p>In the case of RDF, two main technologies have been proposed for validation: ShEx <ref type="bibr" target="#b1">[2]</ref> and SHACL <ref type="bibr" target="#b2">[3]</ref>, which are based on the notion of a shape as a description of the topology of some specific kind of nodes. In this way, it is possible to define a schema as a set of shapes which describe the expected properties of some nodes, their expected cardinalities and the kind of nodes. These schemas, can be used to validate RDF data and check if it conforms to those shapes. We employ ShEx in the paper because it can be seen as a description language for RDF acting as grammar where a ShEx schema represents the set of all the RDF graphs that conform to it.</p><p>Envelope labra@uniovi.es (J. E. Labra-Gayo) GLOBE http://labra.weso.es (J. E. Labra-Gayo) Orcid 0000-0001-8907-5348 (J. E. Labra- <ref type="bibr">Gayo)</ref> There has been a proposal for an extension of RDF called RDF-Star <ref type="bibr" target="#b3">[4]</ref> and a Working Group is currently working taking that proposal as input to define what is currently called RDF 1.2 <ref type="bibr" target="#b4">[5]</ref>. The proposal extends RDF with the possibility of having triples as subjects or objects in statements. The relationship between that extension and property graphs has already been studied <ref type="bibr" target="#b5">[6]</ref>.</p><p>Although ShEx was defined to describe and validate RDF, we consider that it can be extended to describe and validate RDF-Star (or RDF 1.2), so in this paper we explore a possible extension of the language in that direction. Apart from that, the shapes in ShEx are usually centered on describing nodes that act as either subjects or objects, but in RDF, it is also possible to add statements whose subjects or objects are also the predicates of other statements. We also explore a possible extension of ShEx where it is possible to define shapes about nodes that act as properties. Finally, although there have been several proposals to define schemas for property graphs, we consider that the grammar-based approach of ShEx can also be helpful, so we also explore what it would look like to extend ShEx for describing and validating property graphs.</p><p>The main contributions of this paper are to present three extensions of ShEx: ShEx-Star for RDF-Star (section 3), ShEx-N for describing nodes as properties (section 4) and PShEx for property graphs (section 5), with their abstract syntax and semantic definitions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">RDF and ShEx</head><p>Definition 1 (RDF triple and RDF Graph). Given a set of IRIs I , a set of blank nodes B and a set of literals Lit, an RDF triple is a tuple (𝑠, 𝑝, 𝑜) where 𝑠 ∈ I ∪ B is called the subject, 𝑝 ∈ I is called the predicate and 𝑜 ∈ I ∪ B ∪ Lit is called the object. An RDF graph G is a set of RDF triples.</p><p>There are several syntaxes for RDF graphs like Turtle, N3, RDF/XML, etc. In this document, we will use Turtle.</p><p>Example 1 (Example of an RDF graph in Turtle). The following snippet contains a simple RDF graph with two nodes :a and :b. prefix : &lt;http://example.org/&gt; :a :name "Alice" ;</p><p>:knows :b . :b :firstname "Robert", "Julius" ;</p><p>:lastname "Smith" .</p><p>The neighbors of a node 𝑛 ∈ V in an RDF graph G are defined as 𝑛𝑒𝑖𝑔ℎ𝑠(𝑛,</p><formula xml:id="formula_0">G) = {(𝑛, 𝑝, 𝑦) | (𝑛, 𝑝, 𝑦) ∈ G} ∪ {(𝑥, 𝑝, 𝑛) | (𝑥, 𝑝, 𝑛) ∈ G} ∪ {(𝑥, 𝑛, 𝑦) | (𝑥, 𝑛, 𝑦) ∈ G}.</formula><p>Shape Expressions (ShEx) were proposed as such a language in 2014 <ref type="bibr" target="#b1">[2]</ref>. It was designed as a high-level and concise domain-specific language to describe RDF. The syntax of ShEx is inspired by Turtle and SPARQL, while the semantics was inspired by RelaxNG and XML Schema. In this section we describe a simplified abstract syntax of ShEx following <ref type="bibr" target="#b6">[7]</ref>    Intuitively, shape expressions define conditions about nodes while triple expressions define conditions about the neighborhood of nodes, and shapes qualify those neighborhoods by allowing (open shapes) or disallowing (closed shapes) triples with other predicates. We omit negation and disjunction operator to simplify the interactions between negation and recursion, which led to a stratified negation requirement in ShEx.</p><p>The restrictions imposed on shape expressions schemas in <ref type="bibr" target="#b7">[8]</ref> also apply here. Namely, in a schema (L, 𝛿, S)</p><p>• The shape label references used by the definition function 𝛿 are themselves defined, i.e. if @l appears in some shape definition, then l belongs to L; • No definition 𝛿(l) uses a reference @l to itself, neither directly nor transitively, except while traversing a shape. For instance, 𝛿(l) = @l AND 𝑠𝑒 is forbidden, but 𝛿(l) = { 𝑝 − → @l} is allowed.</p><p>Example 2 (Example of ShEx schema). A ShEx schema that describes the RDF graph presented in example 1 can be defined as:</p><formula xml:id="formula_1">L = {𝑃𝑒𝑟𝑠𝑜𝑛 } 𝛿(𝑃𝑒𝑟𝑠𝑜𝑛) = { ( 𝑛𝑎𝑚𝑒 − −−− → 𝑆𝑡𝑟𝑖𝑛𝑔 | 𝑓 𝑖𝑠𝑡𝑛𝑎𝑚𝑒 − −−−−−− → 𝑆𝑡𝑟𝑖𝑛𝑔*; 𝑙𝑎𝑠𝑡𝑛𝑎𝑚𝑒 − −−−−− → 𝑆𝑡𝑟𝑖𝑛𝑔); 𝑘𝑛𝑜𝑤𝑠 − −−−− → @𝑃𝑒𝑟𝑠𝑜𝑛 * }</formula><p>ShEx has several concrete syntaxes like a compact syntax (ShExC) and an RDF syntax defined based on JSON-LD (ShExJ) <ref type="foot" target="#foot_1">2</ref> . Example 3. An example of a ShEx schema using ShExC compact syntax. The semantics of ShEx schemas is based on a conformance relation parameterized by a shape assignment: we say that node 𝑛 in graph G conforms to shape expression 𝑠𝑒 with shape assignment 𝜏, and we write G, 𝑛, 𝜏 ⊨ 𝑠𝑒.</p><p>The following rules are defined similar to <ref type="bibr" target="#b8">[9]</ref>, where it is shown that there exists a unique maximal shape assignment 𝜏 max that allows us to define conformance independently of the shape assignment. The conformance relation is defined recursively on the structure of 𝑠𝑒 by the set of inference rules presented in table <ref type="table">1</ref> where 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒) is the set of predicates that appear in a triple expression 𝑡𝑒 and can be defined as:</p><formula xml:id="formula_2">𝐶𝑜𝑛𝑑 𝑐𝑜𝑛𝑑(𝑛) = 𝑡𝑟𝑢𝑒 G, 𝑛, 𝜏 ⊨ 𝑐𝑜𝑛𝑑 𝐴𝑁 𝐷 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 1 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 2 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 1 AND 𝑠𝑒 2 𝑆ℎ𝑎𝑝𝑒𝑅𝑒𝑓 𝛿(l) = 𝑠𝑒 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 G, 𝑛, 𝜏 ⊨ @𝑙 𝐶𝑙𝑜𝑠𝑒𝑑𝑆ℎ𝑎𝑝𝑒 𝑛𝑒𝑖𝑔ℎ𝑠(𝑛, G) = 𝑡𝑠 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 G, 𝑛, 𝜏 ⊨ CLOSED {𝑡𝑒} 𝑂𝑝𝑒𝑛𝑆ℎ𝑎𝑝𝑒 𝑡𝑠 = {⟨𝑥, 𝑝, 𝑦⟩ ∈ 𝑛𝑒𝑖𝑔ℎ𝑠(𝑛, G) | 𝑝 ∈ 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒)} G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 G, 𝑛, 𝜏 ⊨ {𝑡𝑒}</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 1</head><p>Inference rules for ShEx shape expressions</p><formula xml:id="formula_3">𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 ; 𝑡𝑒 2 ) = 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 ) ∪ 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 2 ) 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 | 𝑡𝑒 2 ) = 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 ) ∪ 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 2 ) 𝑝𝑟𝑒𝑑𝑠( 𝑝 − → 𝑡𝑒) = {𝑝} 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 * ) = 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒) 𝑝𝑟𝑒𝑑𝑠(𝜖)</formula><p>= ∅ The rules for node constraints (𝐶𝑜𝑛𝑑) and conjunction are as expected. A node 𝑛 conforms to an open shape with triple expression 𝑡𝑒 if its neighborhood restricted to the triples with predicates from 𝑡𝑒 conform, meaning that triples whose predicates are not mentioned in 𝑡𝑒 are not constrained by the shape (rule 𝑂𝑝𝑒𝑛𝑆ℎ𝑎𝑝𝑒). Conformance to a closed shape requires to consider the whole neighborhood of the node (rule 𝐶𝑙𝑜𝑠𝑒𝑑𝑆ℎ𝑎𝑝𝑒).</p><p>Conformance to a triple expression uses a second relation defined on sets on neighborhood triples 𝑡𝑠 instead of nodes 𝑛. The set of neighborhood nodes 𝑡𝑠 of a graph G conforms to a triple expression 𝑡𝑒 with shape assignment 𝜏, written as G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒, as defined by the inference rules in table <ref type="table">2</ref>.</p><formula xml:id="formula_4">𝐸𝑎𝑐ℎ𝑂𝑓 (𝑡𝑠 1 , 𝑡𝑠 2 ) ∈ 𝑝𝑎𝑟𝑡(𝑡𝑠) G, 𝑡𝑠 1 , 𝜏 ⊩ 𝑡𝑒 1 G, 𝑡𝑠 2 , 𝜏 ⊩ 𝑡𝑒 2 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 ; 𝑡𝑒 2 𝑂𝑛𝑒𝑂𝑓 1 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 | 𝑡𝑒 2 𝑂𝑛𝑒𝑂𝑓 2 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 2 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 | 𝑡𝑒 2 𝑇 𝐶 1 𝑡𝑠 = {⟨𝑥, 𝑝, 𝑦⟩} G, 𝑦, 𝜏 ⊨ 𝑠𝑒 G, 𝑡𝑠, 𝜏 ⊩ 𝑝 − → 𝑠𝑒 𝑇 𝐶 2 𝑡𝑠 = {⟨𝑦, 𝑝, 𝑥⟩} G, 𝑦, 𝜏 ⊨ 𝑠𝑒 G, 𝑡𝑠, 𝜏 ⊩ 𝑠𝑒 𝑝 − → 𝑆𝑡𝑎𝑟 2 (𝑡𝑠 1 , 𝑡𝑠 2 ) ∈ 𝑝𝑎𝑟𝑡(𝑡𝑠) G, 𝑡𝑠 1 , 𝜏 ⊩ 𝑡𝑒 G, 𝑡𝑠 2 , 𝜏 ⊩ 𝑡𝑒 * G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 * 𝑆𝑡𝑎𝑟 1 G, ∅, 𝜏 ⊩ 𝑡𝑒 * Table 2</formula><p>Inference rules for ShEx triple expressions</p><p>A shape assignment 𝜏 for graph G and S is called valid if for every node 𝑛 in G and every shape expression label l defined in S, if 𝑛@l ∈ 𝜏, then G, 𝑛, 𝜏 ⊨ @l.</p><p>According to Boneva et al <ref type="bibr" target="#b6">[7]</ref>, for every graph G, there exists a unique maximal valid shape assignment 𝜏 max such that if 𝜏 is a valid shape assignment for G and S, then 𝜏 ⊆ 𝜏 max .  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">RDF-Star and ShEx-Star</head><formula xml:id="formula_5">𝛿(𝑃𝑒𝑟𝑠𝑜𝑛) = { ( 𝑛𝑎𝑚𝑒 − −−− → 𝑆𝑡𝑟𝑖𝑛𝑔 | 𝑓 𝑖𝑠𝑡𝑛𝑎𝑚𝑒 − −−−−−− → 𝑆𝑡𝑟𝑖𝑛𝑔*; 𝑙𝑎𝑠𝑡𝑛𝑎𝑚𝑒 − −−−−− → 𝑆𝑡𝑟𝑖𝑛𝑔); ≪ 𝑘𝑛𝑜𝑤𝑠 − −−−− → @𝑃𝑒𝑟𝑠𝑜𝑛 ≫{| 𝑐𝑒𝑟𝑡𝑎𝑖𝑛𝑡𝑦 − −−−−− → 𝐷𝑒𝑐𝑖𝑚𝑎𝑙|}* }</formula><p>The expression ≪ 𝑝 − → 𝑠𝑒 ≫{|𝑡𝑒|} describes a triple term whose predicate is 𝑝 and whose object conforms to the shape expression 𝑠𝑒 and that can be the subject of triples conforming to triple expression 𝑡𝑒. The formal semantics can be described as:</p><formula xml:id="formula_6">𝑇 𝑇 𝐶 1 𝑡𝑠 = {⟨≪ 𝑡 ≫, 𝑝, 𝑦⟩} G, 𝑦, 𝜏 ⊨ 𝑠𝑒 𝑛𝑒𝑖𝑔ℎ𝑠(≪ 𝑡 ≫, G) = 𝑡𝑠 ′ G, 𝑡𝑠 ′ , 𝜏 ⊩ 𝑡𝑒 G, 𝑡𝑠, 𝜏 ⊩≪ 𝑝 − → 𝑠𝑒 ≫ {|𝑡𝑒|} 𝑇 𝑇 𝐶 2 𝑡𝑠 = {⟨𝑥, 𝑝, ≪ 𝑡 ≫⟩} G, 𝑥, 𝜏 ⊨ 𝑠𝑒 𝑛𝑒𝑖𝑔ℎ𝑠(≪ 𝑡 ≫, G) = 𝑡𝑠 ′ G, 𝑡𝑠 ′ , 𝜏 ⊩ 𝑡𝑒 G, 𝑡𝑠, 𝜏 ⊩≪ 𝑠𝑒 𝑝 − → ≫ {|𝑡𝑒|}</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 3</head><p>Inference rules for ShEx-Star new triple term expressions</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">ShEx-N: Describing nodes that act as properties</head><p>In the RDF data model, predicates can also act as subjects or objects or triples. This aspect is not taken into account in traditional ShEx, where the shapes describe the topology of nodes without considering their potential role as predicates.  In order to capture these appearances in a single shape, it is possible to add a new kind of triple expression:</p><p>𝑡𝑒 ::= . . . Same definitions as in 2 | 𝑠𝑒 1 − → 𝑠𝑒 2 Triple constraint with focus node acting as predicate and subject conforming to 𝑠𝑒 1 and object conforming to 𝑠𝑒 2 The semantics of triple term constraints can be defined as:</p><formula xml:id="formula_7">𝑁 𝑃 1 𝑡𝑠 = {⟨𝑠, 𝑥, 𝑜⟩} G, 𝑠, 𝜏 ⊨ 𝑠𝑒 1 G, 𝑜, 𝜏 ⊨ 𝑠𝑒 2 G, 𝑡𝑠, 𝜏 ⊩ 𝑠𝑒 1 − → 𝑠𝑒 2</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 4</head><p>Inference rules for ShEx-N Example 7 (Example of a ShEx-N schema). The following ShEx-N schema defines the shape 𝐹 𝑟𝑖𝑒𝑛𝑠ℎ𝑖𝑝𝑃𝑟𝑜𝑝𝑒𝑟𝑡𝑦 which validates the node :knows in example 6:</p><formula xml:id="formula_8">𝛿(𝐹 𝑟𝑖𝑒𝑛𝑑𝑆ℎ𝑖𝑝𝑃𝑟𝑜𝑝𝑒𝑟𝑡𝑦) = { 𝑠𝑘𝑜𝑠∶𝑟𝑒𝑙𝑎𝑡𝑒𝑑 − −−−−−−−− → [∶ 𝐹 𝑟𝑖𝑒𝑛𝑑𝑠ℎ𝑖𝑝] ; @𝑃𝑒𝑟𝑠𝑜𝑛 − → @𝑃𝑒𝑟𝑠𝑜𝑛 } 𝛿(𝑃𝑒𝑟𝑠𝑜𝑛) = { ∶𝑛𝑎𝑚𝑒 − −−−− → 𝑆𝑡𝑟𝑖𝑛𝑔 | ∶𝑓 𝑖𝑟𝑠𝑡𝑛𝑎𝑚𝑒 − −−−−−−− → 𝑆𝑡𝑟𝑖𝑛𝑔* ; ∶𝑙𝑎𝑠𝑡𝑛𝑎𝑚𝑒 − −−−−−− → 𝑆𝑡𝑟𝑖𝑛𝑔 ; 𝑘𝑛𝑜𝑤𝑠 − −−−− → @𝑃𝑒𝑟𝑠𝑜𝑛 * }</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Property graphs and PShEx</head><p>Property graphs have become popular thanks to several commercial graph databases like Neo4j<ref type="foot" target="#foot_2">3</ref> , JanusGraph<ref type="foot" target="#foot_3">4</ref> or Sparksee <ref type="foot" target="#foot_4">5</ref> . A property graph has unique identifiers for each node/edge and allows to add property-value annotations to each node/edge in the arc as well as type annotations.</p><p>The following definition of a property graph follows <ref type="bibr" target="#b10">[11]</ref>.</p><p>Definition 4 (Property graph). Given a set of types T , a set of properties P, and a set of values V , a property graph G is a tuple ⟨N , E, 𝜌, 𝜆 𝑛 , 𝜆 𝑒 , 𝜎 ⟩ where</p><formula xml:id="formula_9">N ∩ E = ∅, 𝜌 ∶ E ↦ N × N is a total function, 𝜆 𝑛 ∶ N ↦ 𝐹 𝑖𝑛𝑆𝑒𝑡(T ), 𝜆 𝑒 ∶ E ↦ T , and 𝜎 ∶ N ∪ E × P ↦ 𝐹 𝑖𝑛𝑆𝑒𝑡(V ).</formula><p>A property graph is formed by a set of node identifiers N and a set of edges E where 𝜌 associates a pair of nodes (𝑛 1 , 𝑛 2 ) to every 𝑒 ∈ E where 𝑛 1 is the subject and 𝑛 2 is the object, 𝜆 𝑛 associates a set of types for node identifiers (notice that property graphs allow nodes to have more than one type), 𝜆 𝑒 associates a types for each edge identifier, and 𝜎 associates a set of values to pairs (𝑖, 𝑝) such that 𝑖 ∈ N ∪ E is a node or edge and 𝑝 ∈ P is a property. Example 8. As an example, we will represent information that Alice knows Robert with a certainty of 0.5 T = {Person, knows} P = {name, certainty} V = {"Alice", "Robert", "Julius", "Smith", 0.5}</p><formula xml:id="formula_10">N = {𝑛 1 , 𝑛 2 } E = {𝑟 1 } 𝜌 = 𝑟 1 ↦ (𝑛 1 , 𝑛 2 ) 𝜆 𝑛 = 𝑛 1 ↦ {Person}, 𝑛 2 ↦ {Person} 𝜆 𝑒 = 𝑟 1 ↦ knows 𝜎 = (𝑛 1 , 𝑛𝑎𝑚𝑒) ↦ {"Alice"} (𝑛 2 , 𝑓 𝑖𝑟𝑠𝑡𝑛𝑎𝑚𝑒) ↦ {"Robert", "Julius"} (𝑛 2 , 𝑙𝑎𝑠𝑡𝑛𝑎𝑚𝑒) ↦ {"Smith"} (𝑟 1 , 𝑐𝑒𝑟𝑡𝑎𝑖𝑛𝑡𝑦) ↦ {0.5}</formula><p>Figure <ref type="figure" target="#fig_5">4</ref> presents a possible visualization of a property graph. We define a ShEx extension called PShEx that can be used to describe and validate Property graphs. In property graphs, nodes and edges can have associated labels as well as a set of property/values. In this way, it is necessary to adapt the definition of ShEx to describe pairs or property/values. PShEx is composed of three main categories: shape expressions (𝑠𝑒) that  describe the shape of nodes, triple expressions (𝑡𝑒) that describe the shape of edge relationships and property-value expressions (𝑝𝑣𝑠) that describe sets of property/values associated with node/edge identifiers.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 5 (PShEx schema).</head><p>A PShEx Schema is a tuple ⟨L, 𝛿⟩ where L set of shape labels, and 𝛿 ∶ L → S is a total function from labels to shape expressions 𝑠𝑒 ∈ S defined using the abstract syntax:</p><p>𝑠𝑒 </p><formula xml:id="formula_11">L = { 𝑃𝑒𝑟𝑠𝑜𝑛} 𝛿(𝑃𝑒𝑟𝑠𝑜𝑛) = ℎ𝑎𝑠𝑇 𝑦𝑝𝑒 𝐻 𝑢𝑚𝑎𝑛 AND ⌊𝑛𝑎𝑚𝑒 ∶ 𝑆𝑡𝑟𝑖𝑛𝑔 | 𝑓 𝑖𝑟𝑠𝑡𝑛𝑎𝑚𝑒 ∶ 𝑆𝑡𝑟𝑖𝑛𝑔 * , 𝑙𝑎𝑠𝑡𝑛𝑎𝑚𝑒 ∶ 𝑆𝑡𝑟𝑖𝑛𝑔⌋ AND { 𝑘𝑛𝑜𝑤𝑠 − −−−− → @𝑃𝑒𝑟𝑠𝑜𝑛 ⌊𝑐𝑒𝑟𝑡𝑎𝑖𝑛𝑡𝑦 ∶ 𝐷𝑒𝑐𝑖𝑚𝑎𝑙⌋* }</formula><p>In order to define the semantic specification of PShEx we will need to define the neighborhood of a node in a property graph.</p><p>The neighbors of a node 𝑛 ∈ N in a property graph G = ⟨N , E, 𝜌, 𝜆 𝑛 , 𝜆 𝑒 , 𝜎 ⟩ are defined as 𝑛𝑒𝑖𝑔ℎ𝑠(𝑛) = {(𝑛, 𝑝, 𝑦, 𝑣𝑠) | ∃𝑣 ∈ E such that 𝜌(𝑣) = (𝑛, 𝑦) ∧ 𝜆 𝑒 (𝑣) = 𝑝 ∧ 𝑣𝑠 = {(𝑘, 𝑣) | 𝜎 (𝑘, 𝑣) = 𝑤𝑠 ∧ 𝑣 ∈ 𝑤𝑠}}. For a node 𝑛, we define the property value set as 𝑝𝑟𝑜𝑝𝑣𝑠(𝑛) = {(𝑘, 𝑣) | 𝜎 (𝑘, 𝑣) = 𝑤𝑠 ∧ 𝑣 ∈ 𝑤𝑠}</p><p>The semantic specification of PShEx can be defined in a similar way to the ShEx one. Given a property graph G, and a shape assignment 𝜏, a node identifier 𝑛 ∈ N conforms with a shape expression 𝑠𝑒, which is represented as G, 𝑛, 𝜏 ⊨ 𝑠𝑒 and follows the rules presented in 5 where 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒) is the set of edge labels (or predicates) that appear in a triple expression 𝑡𝑒 and can be defined as:</p><formula xml:id="formula_12">𝐶𝑜𝑛𝑑 𝑡𝑠 𝜆 𝑛 (𝑛) = 𝑣𝑠 𝑐𝑜𝑛𝑑 𝑡𝑠 (𝑣𝑠) = 𝑡𝑟𝑢𝑒 G, 𝑛, 𝜏 ⊨ 𝑐𝑜𝑛𝑑 𝑡𝑠 𝐴𝑁 𝐷 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 1 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 2 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 1 AND 𝑠𝑒 2 𝐶𝑙𝑜𝑠𝑒𝑑𝑆ℎ𝑎𝑝𝑒 𝑛𝑒𝑖𝑔ℎ𝑠(𝑛, G) = 𝑡𝑠 G, 𝑡𝑠, 𝜏 ⊩ 𝑠 ′ G, 𝑛, 𝜏 ⊨ CLOSED {𝑡𝑒} 𝑂𝑝𝑒𝑛𝑆ℎ𝑎𝑝𝑒 𝑡𝑠 = {⟨𝑥, 𝑝, 𝑦⟩ ∈ 𝑛𝑒𝑖𝑔ℎ𝑠(𝑛, G) | 𝑝 ∈ 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒)} G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 G, 𝑛, 𝜏 ⊨ {𝑡𝑒} 𝑆ℎ𝑎𝑝𝑒𝑅𝑒𝑓 𝛿(l) = 𝑠𝑒 G, 𝑛, 𝜏 ⊨ 𝑠𝑒 G, 𝑛, 𝜏 ⊨ @𝑙 𝑃𝑉 𝑆 𝑝𝑟𝑜𝑝𝑣𝑠(𝑛) = 𝑠 G, 𝑠, 𝜏 ⊢ 𝑝𝑣𝑠 G, 𝑛, 𝜏 ⊨ 𝑝𝑣𝑠</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 5</head><p>Rules for PShEx shape expressions</p><formula xml:id="formula_13">𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 ; 𝑡𝑒 2 ) = 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 ) ∪ 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 2 ) 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 | 𝑡𝑒 2 ) = 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 1 ) ∪ 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 2 ) 𝑝𝑟𝑒𝑑𝑠( 𝑝 − → 𝑡𝑒) = {𝑝} 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒 * ) = 𝑝𝑟𝑒𝑑𝑠(𝑡𝑒) 𝑝𝑟𝑒𝑑𝑠(𝜖)</formula><p>= ∅ As in the case of ShEx, the previous definition uses a second conformance relation defined on sets of triples 𝑡𝑠 instead of nodes 𝑛. The set of neighborhood nodes 𝑡𝑠 from a property graph G conforms to a triple expression 𝑡𝑒 with shape assignment 𝜏, written G, 𝑡𝑠, 𝜏 ⊩ 𝑠, as defined by the inference rules represented in table <ref type="bibr">6.</ref> In the case of PShEx we declare a new conformance relationship G, 𝑠, 𝜏 ⊢ 𝑞𝑠 between a graph G a set 𝑠 ∈ 𝑃 × 𝑉 of property-value elements, a shape assignment 𝜏 and a property-value specifier 𝑝𝑣𝑠 whose rules are defined in table <ref type="table">7</ref> where 𝑝𝑟𝑜𝑝𝑠(𝑝𝑣𝑠) is the set of properties that appear in a property-value specifier 𝑝𝑠 and can be defined as:</p><formula xml:id="formula_14">𝑝𝑟𝑜𝑝𝑠(𝑝𝑠 1 , 𝑝𝑠 2 ) = 𝑝𝑟𝑜𝑝𝑠(𝑝𝑠 1 ) ∪ 𝑝𝑟𝑜𝑝𝑠(𝑝𝑠 2 ) 𝑝𝑟𝑜𝑝𝑠(𝑝𝑠 1 | 𝑝𝑠 2 ) = 𝑝𝑟𝑜𝑝𝑠(𝑝𝑠 1 ) ∪ 𝑝𝑟𝑜𝑝𝑠(𝑝𝑠 2 ) 𝑝𝑟𝑜𝑝𝑠(𝑝𝑠 * ) = 𝑝𝑟𝑒𝑑𝑠(𝑝𝑠) 𝑝𝑟𝑜𝑝𝑠(𝑝 ∶ 𝑐𝑜𝑛𝑑 𝑣 ) = {𝑝}</formula><p>As in the case of ShEx, the semantics of ShEx schemas can be defined independently on shape assignments. A shape assignment 𝜏 for graph G and S is called valid if for every node 𝑛 in G and every shape expression label l defined in S, if 𝑛@l ∈ 𝜏, then G, 𝑛, 𝜏 ⊨ @l.</p><formula xml:id="formula_15">𝐸𝑎𝑐ℎ𝑂𝑓 (𝑡𝑠 1 , 𝑡𝑠 2 ) ∈ 𝑝𝑎𝑟𝑡(𝑡𝑠) G, 𝑡𝑠 1 , 𝜏 ⊩ 𝑡𝑒 1 G, 𝑡𝑠 2 , 𝜏 ⊩ 𝑡𝑒 2 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 ; 𝑡𝑒 2 𝑂𝑛𝑒𝑂𝑓 1 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 | 𝑡𝑒 2 𝑂𝑛𝑒𝑂𝑓 2 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 2 G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 1 | 𝑡𝑒 2 𝑇 𝑟𝑖𝑝𝑙𝑒𝐶𝑜𝑛𝑠𝑡𝑟𝑎𝑖𝑛𝑡 𝑡𝑠 = {⟨𝑥, 𝑝, 𝑦, 𝑠⟩} G, 𝑦, 𝜏 ⊨ @l G, 𝑠, 𝜏 ⊢ 𝑞𝑠 G, 𝑡𝑠, 𝜏 ⊩ 𝑝 − → @l 𝑞𝑠 𝑆𝑡𝑎𝑟 1 G, ∅, 𝜏 ⊩ 𝑡𝑒 * 𝑆𝑡𝑎𝑟 2 (𝑡𝑠 1 , 𝑡𝑠 2 ) ∈ 𝑝𝑎𝑟𝑡(𝑡𝑠) G, 𝑡𝑠 1 , 𝜏 ⊩ 𝑡𝑒 G, 𝑡𝑠 2 , 𝜏 ⊩ 𝑡𝑒 * G, 𝑡𝑠, 𝜏 ⊩ 𝑡𝑒 * Table 6</formula><p>Rules for PShEx triple expressions</p><formula xml:id="formula_16">𝑂𝑝𝑒𝑛𝑃𝑉 𝑠 𝑠 ′ = {(𝑝, 𝑣) ∈ 𝑠|𝑝 ∈ 𝑝𝑟𝑜𝑝𝑠(𝑝𝑠)} G, 𝑠 ′ , 𝜏 ⊢ 𝑝𝑠 G, 𝑠, 𝜏 ⊢ ⌊𝑝𝑠⌋ 𝐶𝑙𝑜𝑠𝑒𝑃𝑉 𝑠 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 G, 𝑠, 𝜏 ⊢ ⌈𝑝𝑠⌉ 𝐸𝑎𝑐ℎ𝑂𝑓 𝑃𝑠 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 1 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 2 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 1 , 𝑝𝑠 2 𝑂𝑛𝑒𝑂𝑓 𝑃𝑠 1 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 1 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 1 | 𝑝𝑠 2 𝑂𝑛𝑒𝑂𝑓 𝑃𝑠 2 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 2 G, 𝑠, 𝜏 ⊢ 𝑝𝑠 1 | 𝑝𝑠 2 𝑆𝑡𝑎𝑟𝑃𝑠 1 G, ∅, 𝜏 ⊢ 𝑝𝑠 * 𝑆𝑡𝑎𝑟𝑃𝑠 2 (𝑠 1 , 𝑠 2 ) ∈ 𝑝𝑎𝑟𝑡(𝑠) G, 𝑠 1 , 𝜏 ⊢ 𝑝𝑠 G, 𝑠 2 , 𝜏 ⊢ 𝑝𝑠 * G, 𝑠, 𝜏 ⊢ 𝑝𝑠 * 𝑃𝑟𝑜𝑝𝑒𝑟𝑡𝑦𝑉 𝑎𝑙𝑢𝑒 𝑠 = {(𝑝, 𝑤)} 𝑐𝑜𝑛𝑣 𝑣 (𝑤) = true G, 𝑠, 𝜏 ⊢ 𝑝 ∶ 𝑐𝑜𝑛𝑑 𝑣</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 7</head><p>Rules for PShEx property-value specifiers</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Related work</head><p>ShEx was initially proposed in 2014 <ref type="bibr" target="#b1">[2]</ref> as a concise and human readable language to describe and validate RDF. It was based on a variant of regular expressions called Regular Bag Expressions <ref type="bibr" target="#b11">[12]</ref> which also supports recursive shapes. Combining negation with recursive shapes was later studied in <ref type="bibr" target="#b8">[9]</ref> where a well founded formal semantics for ShEx for proposed based on stratification. Our definition of ShEx is based on that work, although we omitted negation, disjunction and EXTRA declarations of shape expressions in this paper. After ShEx was proposed, a W3C Data Shapes working group was chatered whose result was SHACL, proposed as a recommendation in 2017 <ref type="bibr" target="#b2">[3]</ref>. The specification of SHACL didn't have an abstract syntax and left the semantics of recursive shapes as an implementation dependent feature enabling the appearance of several proposals that define an abstract syntax and add semantics for SHACL with negation and recursion <ref type="bibr" target="#b12">[13,</ref><ref type="bibr" target="#b13">14,</ref><ref type="bibr" target="#b14">15,</ref><ref type="bibr" target="#b15">16]</ref>. A comparison between both ShEx and SHACL was provided in <ref type="bibr" target="#b16">[17]</ref> while in <ref type="bibr" target="#b17">[18]</ref>, a simple language was defined that can be used as a common subset of both. We consider that some of our extensions to ShEx could also be applied to SHACL. The approach followed in this paper to extend ShEx was started in this paper <ref type="bibr" target="#b18">[19]</ref> where we had already proposed an initial version of PShEx and WShEx <ref type="bibr" target="#b19">[20]</ref>, another extension of ShEx to support the Wikibase data model. WShEx is conceptually similar to PShEx although a distinct feature of the Wikidbase data model is that the values of properties can also be nodes in the graph, which can be considered as a generalized property graphs model. This model was called MARS (Multi-Attributed Relational Structures) in <ref type="bibr" target="#b20">[21]</ref>.</p><p>There are several proposals for property graphs schemas. GQL is an upcoming ISO standard (ISO39075) <ref type="foot" target="#foot_5">6</ref> which is currently being developed and addresses the property graph model. In order to provide support for GQL, PG-Schema <ref type="bibr" target="#b21">[22]</ref> was proposed as a simple schema language for property graphs. PG-Schema does not support cardinality constraints on edges, which could be simulated using PG-Keys <ref type="bibr" target="#b22">[23]</ref>. In <ref type="bibr" target="#b23">[24]</ref>, the authors propose a common framework for property graph schema languages based on first order logic rules which supports cardinality constraints. The closest proposal to PShEx would be the Property Graph Shapes Language (ProGS) <ref type="bibr" target="#b10">[11]</ref> although that language is based on SHACL and some of the differences SHACL vs ShEx could also be applied to ProGS vs PShEx. For example, PShEx doesn't have property path expressions and ProGS doesn't have regular bag expressions. Another difference is that ProGS includes negation and recursion while in the version of PShEx included in this paper we omitted negation. Comparison between RDF-Star and property graphs at the data model have already been studied. In <ref type="bibr" target="#b24">[25]</ref> proposes a common model for RDF, RDF-Star and property graphs that they call statement graph, which is inspired by the OneGraph <ref type="bibr" target="#b25">[26]</ref> vision. The conversion between property graphs and RDF/RDF-Star is also studied in <ref type="bibr" target="#b5">[6]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Conclusions and future work</head><p>We have presented three extensions to ShEx for different types of knowledge graphs: ShEx-* adds support for RDF-Star, ShEx-N adds a constraint to describe nodes that act as properties, and PShEx can be used to describe and validate property graphs. We presented an abstract syntax and formal semantics for each of the variants.</p><p>There are several lines of future work. On the theoretical level, it will be necessary to research the computational complexity implications of these features as well as the combination of these features with other features from ShEx like negation, disjunction, EXTRA declarations, and even the potential integration of all the features together in a single language. On the implementation level: it will be necessary to propose a concrete compact syntax for each variant that can be useful by data model engineers as well as devise algorithms that can be used to check the conformance of graphs to the corresponding schemas. Although we used ShEx in this paper, another line of future work would be to check which of the features proposed in this paper could also be applied to SHACL.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>prefix : &lt;http://example.org/&gt; prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; &lt;Person&gt; { (:name xsd:string | :firstname xsd:string * ; :lastname xsd:string ); :knows @&lt;Person&gt; * }</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>RDF-Star has been proposed as an extension of RDF where the subjects and objects can be triples. We present a formal definition of RDF-Star based on [10]: Definition 3 (RDF-Star). An RDF-Star triple is a tuple 𝑡 defined recursively as follows: Any RDF triple 𝑡 ∈ (I ∪ B) × I × (I ∪ B ∪ Lit) is an RDF-Star triple; and given RDF-Star triples 𝑡 and 𝑡 ′ and RDF terms 𝑠 ∈ (I ∪ B), 𝑝 ∈ I and 𝑜 ∈ (I ∪ B ∪ Lit), the tuples (≪ 𝑡 ≫, 𝑝, 𝑜), (𝑠, 𝑝, ≪ 𝑡 ′ ≫) and (≪ 𝑡 ≫, 𝑝, ≪ 𝑡 ′ ≫) are RDF-Star triples. An RDF-Star graph is a set of RDF-Star triples. Example 4 (Example of an RDF-Star graph in Turtle-Star notation). The following snippet contains a simple RDF-Star graph with two nodes :a and :b.prefix : &lt;http://example.org/&gt; :a :name "Alice" . &lt;&lt; :a :knows :b &gt;&gt; :certainty 0.5 . :b :firstname "Robert", "Julius" ; :lastname "Smith" .</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Basic RDF-Star example</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: RDF example with a property as a node</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Example graph visualization of a property graph</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>1 </figDesc><table /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head></head><label></label><figDesc>Example 6 (Example of an RDF graph a node acting as a property). The following snippet contains a simple RDF graph where :knows is both a node and a property.</figDesc><table><row><cell cols="2">prefix : &lt;http://example.org/&gt;</cell><cell></cell><cell></cell></row><row><cell cols="4">prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;</cell></row><row><cell>:a :name "Alice" ;</cell><cell></cell><cell></cell><cell></cell></row><row><cell>:knows :b .</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">:b :firstname "Robert", "Julius" ;</cell><cell></cell><cell></cell></row><row><cell>:lastname "Smith" .</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">:knows skos:related :Friendship .</cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell cols="2">:Friendship</cell></row><row><cell></cell><cell cols="2">skos:related</cell><cell></cell></row><row><cell></cell><cell>:knows</cell><cell></cell><cell></cell></row><row><cell>:a</cell><cell></cell><cell></cell><cell>:b</cell></row><row><cell>:name</cell><cell cols="2">:firstname</cell><cell>:firstname</cell><cell>:lastname</cell></row><row><cell>"Alice"</cell><cell>"Robert"</cell><cell cols="2">"Julius"</cell><cell>"Smith"</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_4"><head></head><label></label><figDesc>::= 𝑐𝑜𝑛𝑑 𝑡 𝑠 Basic boolean condition on set of types 𝑡 𝑠 ⊆ T | 𝑠𝑒 1 AND 𝑠𝑒 2 As an example, we can define a PShEx schema that describes the property graph from example 8 where ℎ𝑎𝑠𝑇 𝑦𝑝𝑒 𝑡 is a condition that is satisfied when the set of types of a node contains the type 𝑡, i.e. ℎ𝑎𝑠𝑇 𝑦𝑝𝑒 𝑡 (𝑣𝑠) = true if 𝑡 ∈ 𝑣𝑠 and 𝑆𝑡𝑟𝑖𝑛𝑔, 𝐷𝑒𝑐𝑖𝑚𝑎𝑙 are conditions on the values that are satisfied when the values have the corresponding type.</figDesc><table><row><cell></cell><cell></cell><cell>Conjunction</cell></row><row><cell>|</cell><cell>@l</cell><cell>Shape label reference for l ∈ L</cell></row><row><cell>|</cell><cell>𝑝𝑣𝑠</cell><cell>Property-value specifiers of a node</cell></row><row><cell>|</cell><cell>CLOSED {𝑡𝑒}</cell><cell>Closed shape</cell></row><row><cell>|</cell><cell>{𝑡𝑒}</cell><cell>Open shape</cell></row><row><cell cols="2">𝑡𝑒 ::= 𝑡𝑒 1 ; 𝑡𝑒 2</cell><cell>Each of 𝑡𝑒 1 and 𝑡𝑒 2</cell></row><row><cell>|</cell><cell>𝑡𝑒 1 | 𝑡𝑒 2</cell><cell>Some of 𝑡𝑒 1 or 𝑡𝑒 2</cell></row><row><cell>|</cell><cell>𝑡𝑒 *</cell><cell>Zero or more 𝑡𝑒</cell></row><row><cell>|</cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>Open property-value specifiers 𝑝𝑠</cell></row><row><cell>|</cell><cell>⌈𝑝𝑠⌉</cell><cell>Closed property-value specifiers 𝑝𝑠</cell></row><row><cell cols="2">𝑝𝑠 ::= 𝑝𝑠 1 , 𝑝𝑠 2</cell><cell>Each of 𝑝𝑠 1 and 𝑝𝑠 2</cell></row><row><cell>|</cell><cell>𝑝𝑠 1 | 𝑝𝑠 2</cell><cell>OneOf of 𝑝𝑠 1 or 𝑝𝑠 2</cell></row><row><cell>|</cell><cell>𝑝𝑠 *</cell><cell>zero of more 𝑝𝑠</cell></row><row><cell>|</cell><cell>𝑝 ∶ 𝑐𝑜𝑛𝑑</cell><cell></cell></row></table><note>𝑝 − → @l 𝑝𝑣𝑠 Triple constraint with property type 𝑝 whose nodes satisfy the shape l and property-values 𝑝𝑣𝑠 𝑝𝑣𝑠 ::= ⌊𝑝𝑠⌋ 𝑣 Property 𝑝 with value conforming to 𝑐𝑜𝑛𝑑 𝑣 𝑐𝑜𝑛𝑑 𝑣 𝑠 is a boolean condition on sets of values 𝑣 𝑠 ⊆ V Example 9.</note></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">The full specification of ShEx is available at https://shex.io/shex-semantics/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">See ShEx specification<ref type="bibr" target="#b7">[8]</ref> for details.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://neo4j.com/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">https://janusgraph.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">https://www.sparsity-technologies.com/#sparksee</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">https://www.iso.org/standard/76120.html</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>This work has been partially funded by the Project ANGLIRU: ANGLIRU: Applying kNowledge Graphs to research data interoperabiLIty and ReUsability, code: PID2020-117912RB. The discussions held during our participation in Dagstuhl seminar 24102 Shapes in graph data: theory and implementation helped us to write some of the ideas included in this paper.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Hogan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Blomqvist</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cochez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Amato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>De Melo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Gutiérrez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kirrane</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Navigli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Neumaier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A.-C</forename><surname>Ngonga Ngomo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Polleres</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">M</forename><surname>Rashid</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Rula</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Schmelzeisen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">F</forename><surname>Sequeda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staab</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Zimmermann</surname></persName>
		</author>
		<idno type="DOI">10.2200/S01125ED1V01Y202109DSK022</idno>
		<ptr target="https://kgbook.org/.doi:10.2200/S01125ED1V01Y202109DSK022" />
		<title level="m">Knowledge Graphs, number 22 in Synthesis Lectures on Data, Semantics, and Knowledge</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Shape Expressions: An RDF Validation and Transformation Language</title>
		<author>
			<persName><forename type="first">E</forename><surname>Prud'hommeaux</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Solbrig</surname></persName>
		</author>
		<idno type="DOI">10.1145/2660517.2660523</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 10th International Conference on Semantic Systems, SEMANTICS 2014</title>
				<editor>
			<persName><forename type="first">H</forename><surname>Sack</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">A</forename><surname>Filipowska</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Lehmann</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><surname>Hellmann</surname></persName>
		</editor>
		<meeting>the 10th International Conference on Semantic Systems, SEMANTICS 2014<address><addrLine>Leipzig, Germany</addrLine></address></meeting>
		<imprint>
			<publisher>ACM Press</publisher>
			<date type="published" when="2014">September 4-5, 2014. 2014</date>
			<biblScope unit="page" from="32" to="40" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">H</forename><surname>Knublauch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Kontokostas</surname></persName>
		</author>
		<ptr target="https://www.w3.org/TR/2017/REC-shacl-20170720/" />
		<title level="m">Shapes Constraint Language (SHACL), W3C Recommendation 20 July 2017, W3C Recommendation, World Wide Web Consortium</title>
				<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Wood</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Lanthaler</surname></persName>
		</author>
		<ptr target="https://w3c.github.io/rdf-star/cg-spec" />
		<title level="m">RDF-star and SPARQL-star, Draft Community Group Report, World Wide Web Consortium</title>
				<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">RDF 1.2 Concepts and Abstract Syntax, W3C Working Draft</title>
		<author>
			<persName><forename type="first">O</forename><surname>Hartig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P.-A</forename><surname>Champin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Kellogg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Seaborne</surname></persName>
		</author>
		<ptr target="https://www.w3.org/TR/rdf12-concepts/" />
	</analytic>
	<monogr>
		<title level="m">World Wide Web Consortium</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Converting property graphs to rdf: a preliminary study of the practical impact of different mappings</title>
		<author>
			<persName><forename type="first">S</forename><surname>Khayatbashi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Ferrada</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Hartig</surname></persName>
		</author>
		<idno type="DOI">10.1145/3534540.3534695</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 5th ACM SIGMOD Joint International Workshop on Graph Data Management Experiences and Systems (GRADES) and Network Data Analytics (NDA), SIGMOD/PODS &apos;22</title>
				<meeting>the 5th ACM SIGMOD Joint International Workshop on Graph Data Management Experiences and Systems (GRADES) and Network Data Analytics (NDA), SIGMOD/PODS &apos;22</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Semantics and Validation of Shapes Schemas for RDF</title>
		<author>
			<persName><forename type="first">I</forename><surname>Boneva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">G</forename><surname>Prud'hommeaux</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web -ISWC 2017 -16th International Semantic Web Conference</title>
		<title level="s">Lecture Notes in Computer Science</title>
		<editor>
			<persName><forename type="first">C</forename><surname>Amato</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><surname>Fernández</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">V</forename><forename type="middle">A M</forename><surname>Tamma</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">F</forename><surname>Lécué</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">P</forename><surname>Cudré-Mauroux</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><forename type="middle">F</forename><surname>Sequeda</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">C</forename><surname>Lange</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Heflin</surname></persName>
		</editor>
		<meeting><address><addrLine>Vienna, Austria</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2017">October 21-25, 2017. 2017</date>
			<biblScope unit="volume">10587</biblScope>
			<biblScope unit="page" from="104" to="120" />
		</imprint>
	</monogr>
	<note>Proceedings, Part I</note>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<author>
			<persName><forename type="first">E</forename><surname>Prud'hommeaux</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Boneva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Kellog</surname></persName>
		</author>
		<ptr target="https://shexspec.github.io/spec/" />
		<title level="m">Shape Expressions Language 2</title>
				<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="volume">0</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Semantics and validation of shapes schemas for rdf</title>
		<author>
			<persName><forename type="first">I</forename><surname>Boneva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Prud'hommeaux</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Foundations of RDF* and SPARQL* -An Alternative Approach to Statement-Level Metadata in RDF</title>
		<author>
			<persName><forename type="first">O</forename><surname>Hartig</surname></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-1912/paper12.pdf" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 11th Alberto Mendelzon International Workshop on Foundations of Data Management and the Web</title>
		<title level="s">CEUR Workshop Proceedings</title>
		<editor>
			<persName><forename type="first">J</forename><forename type="middle">L</forename><surname>Reutter</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">D</forename><surname>Srivastava</surname></persName>
		</editor>
		<meeting>the 11th Alberto Mendelzon International Workshop on Foundations of Data Management and the Web<address><addrLine>Montevideo, Uruguay; Sun SITE Central Europe</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1912">June 7-9, 2017. 1912. 2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">ProGS: Property Graph Shapes Language</title>
		<author>
			<persName><forename type="first">P</forename><surname>Seifer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Lämmel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staab</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-88361-4_23</idno>
		<idno type="arXiv">arXiv:2107.05566</idno>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2021">2021</date>
			<biblScope unit="volume">12922</biblScope>
			<biblScope unit="page" from="392" to="401" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Complexity and Expressiveness of ShEx for RDF</title>
		<author>
			<persName><forename type="first">S</forename><surname>Staworko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Boneva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Hym</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">G</forename><surname>Prud'hommeaux</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">R</forename><surname>Solbrig</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">18th International Conference on Database Theory, ICDT 2015</title>
				<imprint>
			<publisher>Schloss Dagstuhl -Leibniz-Zentrum fuer Informatik</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="volume">31</biblScope>
			<biblScope unit="page" from="195" to="211" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Semantics and Validation of Recursive SHACL</title>
		<author>
			<persName><forename type="first">J</forename><surname>Corman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">L</forename><surname>Reutter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Savković</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web -ISWC 2018 -17th International Semantic Web Conference</title>
		<title level="s">Lecture Notes in Computer Science</title>
		<editor>
			<persName><forename type="first">D</forename><surname>Vrandečić</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">K</forename><surname>Bontcheva</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suárez-Figueroa</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">V</forename><surname>Presutti</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">I</forename><surname>Celino</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><surname>Sabou</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">L</forename><surname>Kaffee</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">E</forename><surname>Simperl</surname></persName>
		</editor>
		<meeting><address><addrLine>Monterey, CA, USA</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2018">October 8-12, 2018. 2018</date>
			<biblScope unit="volume">11136</biblScope>
			<biblScope unit="page" from="318" to="336" />
		</imprint>
	</monogr>
	<note>Proceedings, Part I</note>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Stable model semantics for recursive shacl</title>
		<author>
			<persName><forename type="first">M</forename><surname>Andresel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Corman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ortiz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">L</forename><surname>Reutter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Savkovic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Simkus</surname></persName>
		</author>
		<idno type="DOI">10.1145/3366423.3380229</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of The Web Conference 2020</title>
				<meeting>The Web Conference 2020</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
	<note>WWW &apos;20</note>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Fixpoint semantics for recursive SHACL</title>
		<author>
			<persName><forename type="first">B</forename><surname>Bogaerts</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Jakubowski</surname></persName>
		</author>
		<idno type="DOI">10.4204/EPTCS.345.14</idno>
		<ptr target="https://doi.org/10.4204/EPTCS.345.14.doi:10.4204/EPTCS.345.14" />
	</analytic>
	<monogr>
		<title level="m">Proceedings 37th International Conference on Logic Programming (Technical Communications), ICLP Technical Communications 2021, Porto (virtual event)</title>
				<editor>
			<persName><forename type="first">A</forename><surname>Formisano</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Y</forename><forename type="middle">A</forename><surname>Liu</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">B</forename><surname>Bogaerts</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">A</forename><surname>Brik</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">V</forename><surname>Dahl</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">C</forename><surname>Dodaro</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">P</forename><surname>Fodor</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">G</forename><forename type="middle">L</forename><surname>Pozzato</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Vennekens</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">N</forename><surname>Zhou</surname></persName>
		</editor>
		<meeting>37th International Conference on Logic Programming (Technical Communications), ICLP Technical Communications 2021, Porto (virtual event)<address><addrLine>EPTCS</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2021-09">September 2021. 2021</date>
			<biblScope unit="volume">345</biblScope>
			<biblScope unit="page" from="41" to="47" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Well-founded semantics for recursive shacl</title>
		<author>
			<persName><forename type="first">A</forename><surname>Chmurovic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Šimkus</surname></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-3203/" />
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2022">3203. 2022</date>
			<biblScope unit="page" from="2" to="13" />
		</imprint>
	</monogr>
	<note>CEUR Workshop proceedings</note>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m" type="main">Validating RDF Data, volume 7 of Synthesis Lectures on the Semantic Web: Theory and Technology</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Prud'hommeaux</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Boneva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Kontokostas</surname></persName>
		</author>
		<idno type="DOI">10.2200/s00786ed1v01y201707wbe016</idno>
		<ptr target="https://doi.org/10.2200/s00786ed1v01y201707wbe016.doi:10.2200/s00786ed1v01y201707wbe016" />
		<imprint>
			<date type="published" when="2017">2017</date>
			<publisher>Morgan &amp; Claypool</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Challenges in RDF Validation</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Labra Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>García-González</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Fernández-Alvarez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Prud'hommeaux</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-06149-4_6</idno>
	</analytic>
	<monogr>
		<title level="m">Current Trends in Semantic Web Technologies: Theory and Practice, Studies in Computational Intelligence</title>
				<editor>
			<persName><forename type="first">G</forename><surname>Alor-Hernández</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><forename type="middle">L</forename><surname>Sánchez-Cervantes</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">A</forename><surname>Rodríguez-González</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">R</forename><surname>Valencia-García</surname></persName>
		</editor>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="121" to="151" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<title level="m" type="main">Creating knowledge graphs subsets using shape expressions</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E L</forename><surname>Gayo</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2110.11709</idno>
		<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">Wshex: A language to describe and validate wikibase entities</title>
		<author>
			<persName><forename type="first">J.-E</forename><surname>Labra-Gayo</surname></persName>
		</author>
		<ptr target="https://ceur-ws.org/Vol-3262/paper3.pdf" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 3rd Wikidata Workshop 2022 co-located with the 21st International Semantic Web Conference (ISWC2022), Virtual Event</title>
		<title level="s">CEUR Workshop Proceedings</title>
		<editor>
			<persName><forename type="first">L</forename><surname>Kaffee</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><surname>Razniewski</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">G</forename><surname>Amaral</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">K</forename><forename type="middle">S</forename><surname>Alghamdi</surname></persName>
		</editor>
		<meeting>the 3rd Wikidata Workshop 2022 co-located with the 21st International Semantic Web Conference (ISWC2022), Virtual Event<address><addrLine>Hanghzou, China</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2022-10">October 2022. 2022</date>
			<biblScope unit="volume">3262</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Logic on MARS: ontologies for generalised property graphs</title>
		<author>
			<persName><forename type="first">M</forename><surname>Marx</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Krötzsch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Thost</surname></persName>
		</author>
		<idno type="DOI">10.24963/ijcai.2017/165</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 26th International Joint Conference on Artificial Intelligence (IJCAI&apos;17), International Joint Conferences on Artificial Intelligence</title>
				<editor>
			<persName><forename type="first">C</forename><surname>Sierra</surname></persName>
		</editor>
		<meeting>the 26th International Joint Conference on Artificial Intelligence (IJCAI&apos;17), International Joint Conferences on Artificial Intelligence</meeting>
		<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="1188" to="1194" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Pg-schema: Schemas for property graphs</title>
		<author>
			<persName><forename type="first">R</forename><surname>Angles</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Bonifati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Dumbrava</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Fletcher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Green</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hidders</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Libkin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Marsault</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Martens</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Murlak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Plantikow</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Savkovic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Schmidt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Sequeda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staworko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Tomaszuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Voigt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Vrgoc</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Zivkovic</surname></persName>
		</author>
		<idno type="DOI">10.1145/3589778</idno>
	</analytic>
	<monogr>
		<title level="j">Proceedings of the ACM on Management of Data</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="1" to="25" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Pg-keys: Keys for property graphs</title>
		<author>
			<persName><forename type="first">R</forename><surname>Angles</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Bonifati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Dumbrava</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Fletcher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">W</forename><surname>Hare</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hidders</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">E</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Libkin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Martens</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Murlak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Perryman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Savković</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Schmidt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Sequeda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staworko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Tomaszuk</surname></persName>
		</author>
		<idno type="DOI">10.1145/3448016.3457561</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 2021 International Conference on Management of Data, SIGMOD/PODS &apos;21</title>
				<meeting>the 2021 International Conference on Management of Data, SIGMOD/PODS &apos;21</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">A formal design framework for practical property graph schema languages</title>
		<author>
			<persName><forename type="first">N</forename><surname>Beeren</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Fletcher</surname></persName>
		</author>
		<idno type="DOI">10.48786/EDBT.2023.40</idno>
		<ptr target="https://doi.org/10.48786/edbt.2023.40.doi:10.48786/EDBT.2023.40" />
	</analytic>
	<monogr>
		<title level="m">Proceedings 26th International Conference on Extending Database Technology, EDBT 2023</title>
				<editor>
			<persName><forename type="first">J</forename><surname>Stoyanovich</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Teubner</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">N</forename><surname>Mamoulis</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">E</forename><surname>Pitoura</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Mühlig</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">K</forename><surname>Hose</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><forename type="middle">S</forename><surname>Bhowmick</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><surname>Lissandrini</surname></persName>
		</editor>
		<meeting>26th International Conference on Extending Database Technology, EDBT 2023<address><addrLine>Ioannina, Greece</addrLine></address></meeting>
		<imprint>
			<publisher>OpenProceedings</publisher>
			<date type="published" when="2023">March 28-31, 2023. 2023</date>
			<biblScope unit="page" from="478" to="484" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<monogr>
		<author>
			<persName><forename type="first">E</forename><surname>Gelling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Fletcher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Schmidt</surname></persName>
		</author>
		<idno type="DOI">10.48550/ARXIV.2304.13097</idno>
		<idno type="arXiv">arXiv:2304.13097</idno>
		<ptr target="https://doi.org/10.48550/arXiv.2304.13097.doi:10.48550/ARXIV.2304.13097" />
		<title level="m">Bridging graph data models: Rdf, rdf-star, and property graphs as directed acyclic graphs</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">The onegraph vision: Challenges of breaking the graph model lock-in1</title>
		<author>
			<persName><forename type="first">O</forename><surname>Lassila</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Schmidt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Hartig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Bebee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Bechberger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Broekema</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Khandelwal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Lawrence</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">M</forename><surname>Lopez Enriquez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Sharda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Thompson</surname></persName>
		</author>
		<idno type="DOI">10.3233/sw-223273</idno>
	</analytic>
	<monogr>
		<title level="j">Semantic Web</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="page" from="125" to="134" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

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