<?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">Implementing Usage Control Policies Using Reification with RDF-Star and SPARQL-Star</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Ines</forename><surname>Akaichi</surname></persName>
							<email>ines.akaichi@wu.ac.at</email>
							<affiliation key="aff0">
								<orgName type="department">Institute for Complex Networks</orgName>
								<orgName type="institution">WU</orgName>
								<address>
									<settlement>Vienna</settlement>
									<country>Austrian</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Giorgos</forename><surname>Flouris</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Institute of Computer Science</orgName>
								<orgName type="institution">FORTH</orgName>
								<address>
									<settlement>Heraklion</settlement>
									<country key="GR">Greece</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Irini</forename><surname>Fundulaki</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Institute of Computer Science</orgName>
								<orgName type="institution">FORTH</orgName>
								<address>
									<settlement>Heraklion</settlement>
									<country key="GR">Greece</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sabrina</forename><surname>Kirrane</surname></persName>
							<email>sabrina.kirrane@wu.ac.at</email>
							<affiliation key="aff0">
								<orgName type="department">Institute for Complex Networks</orgName>
								<orgName type="institution">WU</orgName>
								<address>
									<settlement>Vienna</settlement>
									<country>Austrian</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Implementing Usage Control Policies Using Reification with RDF-Star and SPARQL-Star</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">F9E2214148F55FE66D489C0E49F9EE79</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T16:47+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>RDF-star, SPARQL-star, Usage Control, Policies Orcid 0000-0002-6020-5572 (I. Akaichi)</term>
					<term>0000-0002-8937-4118 (G. Flouris)</term>
					<term>0000-0002-4812-9896 (I. Fundulaki)</term>
					<term>0000-0002-6955-7718 (S. Kirrane)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In decentralized environments usage control (UC) is crucial for governing asset and resource usage. In an earlier work, we proposed GUCON, a generic graph pattern based policy framework for UC enforcement, which offers a formal semantics for specifying and reasoning over UC policies. Although GUCON caters for the expression of various rules using graph patterns, the incorporation of temporal constraints is cumbersome. In this paper, we propose an instantiation of the GUCON framework that demonstrates how RDF-star can be used for rule representation and SPARQL-star for compliance checking. Additionally, we extend the original policy language to cater for temporal constraints.</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 modern decentralized systems, such as the Internet of Things (IoT) and data spaces, usage control becomes crucial for managing assets and resources <ref type="bibr" target="#b0">[1]</ref>. In previous work <ref type="bibr" target="#b1">[2]</ref>, we proposed the generic graph pattern-based policy framework for usage control enforcement (GUCON), which provides an abstract structure with formal semantics for UC policy specification and includes algorithms for policy-specific reasoning tasks such as compliance, requirements, and consistency checking. GUCON uses conditional deontic rules based on graph patterns and deontic concepts (permission A, prohibition P, obligation O, and dispensation D), with formal semantics rooted in graph patterns <ref type="bibr" target="#b2">[3]</ref>. It introduces a Knowledge Base (KB) to capture domain knowledge and events, serving as the foundation for reasoning about and enforcing UC policies. An essential aspect of UC is expressing and reasoning over environmental and system constraints (e.g., temporal, spatial, purpose, events) <ref type="bibr" target="#b3">[4,</ref><ref type="bibr" target="#b4">5]</ref>. Although GUCON can express various conditions on data usage through graph patterns, adding constraints such as temporal constraints can make the expressions cumbersome. To address this, we propose using reification to express constraints as part of UC rule conditions. Specifically, we use RDF-star for rule expression and 1 { 2 ? s h a r e r d f : t y p e s p l o g : S h a r i n g E v e n t ;   SPARQL-star for our compliance checker. We illustrate the application of our solution with a football embargo use case. In this scenario, media outlets are permitted to share specific extracts from a football match, such as highlights, photographs, and interviews, only after a specified time or event (e.g., the end of the match). To model this information, we developed an ontology based on the Sport Schema ontology 1 , which describes a sports event as part of a competition structure (e.g., league, championship), and the ontology for media resources 2 , which details media coverage (e.g., photos, interviews) as part of an event. In this paper, we use the 2020 English Premier League competition as a recurring example.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related Work</head><p>RDF reification is the standard way to express metadata about RDF triples. Reification involves converting a basic triple to an rdf:Statement, that describes the original triple as a resource. While RDF reification is a standard approach, it can be verbose and cumbersome <ref type="bibr" target="#b5">[6]</ref>. Alternative approaches include the use of named graphs, or RDF-Star 3 . When it comes to UC specifically, Robaldo <ref type="bibr" target="#b6">[7]</ref> proposed to use reified I/O logic to express norms and make use of representation languages, such as SHACL, to implement compliance checking <ref type="bibr" target="#b7">[8]</ref>. While their work highlights the significance of reification in compliance checking, it primarily focuses on normative reasoning. Additionally, expressing environmental or system constraints is outside of their focus. In this paper, due to their enhanced expressivity and efficiency, we propose to use RDF-star to express constraints on top of UC rules and SPARQL-star to build a compliance checking algorithm on top of GUCON. 1 IPTC Sport Schema, https://sportschema.org/schema-overview/ 2 Media Resources 1.0, https://www.w3.org/TR/mediaont-10/ 3 RDF-star and SPARQL-star, https://w3c.github.io/rdf-star/cg-spec/editors_draft.html 1 { 2 &lt;&lt;?x eg : s h a r e egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e &gt;&gt; 3 s p l o g : o c c u r s ? t .  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Using Reification to Model Usage Control Policies</head><p>A KB is an RDF graph describing the set of actual knowledge. A GUCON rule is of the form: 𝑐𝑜𝑛𝑑 ⇝ 𝑑𝑎, where 𝑐𝑜𝑛𝑑 is a SPARQL graph pattern, and 𝑑𝑎 is a deontic pattern, where 𝑑 ∈ {A, P, O, D}, and 𝑎 is a called an action pattern. An action pattern is a SPARQL triple pattern where the subject, property, and object refer to an entity name, an action name, and a resource name, respectively, with variables present in all three positions. A UCR can be read as follows: if the condition (𝑐𝑜𝑛𝑑) is satisfied by the KB, then the deontic pattern (𝑑𝑎) may (A), must not (P), must (O), or need not (D) be satisfied. In Listing 1, we express the permission rule from our use case using GUCON (we assume that 2021-02-25T21:00:00 implies the end of the match).</p><p>In this paper, we propose to extend GUCON with reification in order to express constraints on top of the rules, also called GUCON-Star. In particular, the action pattern representing the action of sharing data is reified by using a quoted triple. This quoted triple can then be used in the body of the rule as a way to describe constraints, in our case, a temporal constraint. The same rule from Listing 1 is expressed using GUCON-Star in Listing 2.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Compliance Checking in RDF-star/ SPARQL-star</head><p>The original GUCON compliance algorithm from <ref type="bibr" target="#b1">[2]</ref> checks for only obligation and prohibition compliance, assuming permissions and dispensations are always valid. With the addition of constraints, rule semantics change, such as temporal permissions becoming valid only after a specific time. We extend our compliance checker to evaluate permissions, prohibitions, obligations, and dispensations with constraints. Below, we present a KB extract containing logs from a system tracking media coverage sharing for football matches. The KB is described using the SPECIAL Policy Log Vocabulary 4 . The log shows eg:JohnSmith sharing a media resource from the English Premier League 2020 Season, including details like occurrence time and description. More details describing the logs can be found in our GitHub 5 . The compliance 4 The SPECIAL Policy Log Vocabulary, https://ai.wu.ac.at/policies/policylog/ 5 https://github.com/Ines-Akaichi/GUCON-star/tree/main 1 eg : J o h n S m i t h 2 r d f : t y p e eg : P e r s o n ; 3 eg : p o s i t i o n eg : J o u r n a l i s t . 9 d c t : t i t l e " Log o f t r a c k i n g a p p l i c a t i o n o f media s h a r i n g o f t h e p r e m i e r l e a g u e match "@en ; 10 d c t : d e s c r i p t i o n " T h i s c o n t a i n s a l l t r a c e s o f media c o v e r a g e s h a r i n g "@en ; checker uses a UC rule and a KB as input. It determines rule condition matches via ASK SPARQL-star queries over the KB, deciding compliance accordingly. For temporal permissions and dispensations, the engine checks whether the KB contains a match for the UC rule's body that satisfies the temporal constraint; if so, the KB is compliant. For obligations and prohibitions, a match means the KB is compliant for obligations and non-compliant for prohibitions. The sharing that occured at "2021-02-25T20:30:50Z", makes eg:JohnSmith non compliant with the rule defined in Listing 2. The compliance checker and inputs are available on our GitHub page.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Discussion and Future Work</head><p>In this poster, our focus was on demonstrating how RDF-star and SPARQL-star syntax can be utilized to serialize GUCON policies with various constraints. As an important next step, we aim to define the semantics of this new serialization so that future implementations of compliance engines are able of consistently and accurately enforcing GUCON UCPs. Furthermore, our compliance checker primarily handles temporal constraints and filter operators. We aim to expand its functionality to accommodate other types of constraints. Given that UC involves managing dynamic policies, temporal constraints can evolve, such as when a match ends, thus we are interested in exploring the mutability of constraints within the context of GUCON. Additionally, due to the absence of benchmarking in UC <ref type="bibr" target="#b8">[9]</ref>, we plan to represent GUCON using various representation languages such as Datalog, ASP, etc. This will allow us to compare the performance of different engines.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>3 r</head><label>3</label><figDesc>d f : s u b j e c t ? x ; 4 r d f : p r e d i c a t e eg : s h a r e ; 5 r d f : o b j e c t egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e ; 6 s p l o g : o c c u r s ? t .</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>7 8 ?</head><label>8</label><figDesc>x r d f : t y p e eg : P e r s o n ; 9 eg : p o s i t i o n eg : J o u r n a l i s t .</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Listing 1 :</head><label>1</label><figDesc>10 11 FILTER ( ? t &gt; "20 21 −02 −2 5 T21 : 0 0 : 0 0 Z"^^x s d : d a t e T i m e ) 12 } 13 −&gt; 14 { 15 A { ? x : s h a r e egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e } 16 } Policy Representation using GUCON.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>4 5?</head><label>4</label><figDesc>x r d f : t y p e eg : P e r s o n ; 6 eg : p o s i t i o n eg : J o u r n a l i s t .</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>7 8FILTER</head><label>7</label><figDesc>( ? t &gt; "20 21 −0 2 − 25 T21 : 0 0 : 0 0 Z"^^x s d : d a t e T i m e ) ? x eg : s h a r e egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e } 13 } Listing 2: Policy Representation using GUCON-star.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>4 5</head><label>4</label><figDesc>eg : J o h n S m i t h eg : s h a r e egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e . : t y p e s p l o g : Log ;</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head></head><label></label><figDesc>11 d c t : i s s u e d " 20 21 −02 −2 5 T20 : 3 0 : 5 0 Z"^^x s d : d ateTime Stamp ; 12 p r o v : w a s A t t r i b u t e d T o eg : T r a c k i n g S y s t e m R 2 D 2 ; 13 s p l o g : e v e n t &lt;&lt; eg : J o h n S m i t h eg : s h a r e egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e &gt;&gt; . 14 15 &lt;&lt; eg : J o h n S m i t h eg : s h a r e egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e &gt;&gt; 16 r d f : t y p e s p l o g : S h a r i n g E v e n t ; 17 d c t : d e s c r i p t i o n "We t r a c k e d a new s h a r i n g o f match m a t e r i a l s "@en ; 18 s p l o g : i n s t a n c e D a t a egmc : l . p r e m i e r l e a g u e . com −2020 − c o v e r a g e ; 19 s p l o g : o c c u r s "2 021 −0 2 − 25 T20 : 3 0 : 5 0 Z"^^x s d : d a t e T i m e .Listing 3: Extract of a Log.</figDesc></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><forename type="first">C</forename><surname>Jung</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Dörr</surname></persName>
		</author>
		<title level="m">Data Usage Control</title>
				<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Gucon: A generic graph pattern based policy framework for usage control enforcement</title>
		<author>
			<persName><forename type="first">I</forename><surname>Akaichi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Flouris</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Fundulaki</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kirrane</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-031-45072-3_3</idno>
		<ptr target="https://doi.org/10.1007/978-3-031-45072-3_3" />
	</analytic>
	<monogr>
		<title level="m">Rules and Reasoning: 7th International Joint Conference, RuleML+RR 2023</title>
				<meeting><address><addrLine>Oslo, Norway</addrLine></address></meeting>
		<imprint>
			<publisher>Proceedings</publisher>
			<date type="published" when="2023">September 18-20, 2023. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Semantics and complexity of sparql</title>
		<author>
			<persName><forename type="first">J</forename><surname>Pérez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Arenas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Gutierrez</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web -ISWC</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Hilty</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Basin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Pretschner</surname></persName>
		</author>
		<title level="m">LNCS 3679 -On Obligations</title>
				<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
	<note type="report_type">Technical Report</note>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">A policy language for distributed usage control</title>
		<author>
			<persName><forename type="first">M</forename><surname>Hilty</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Pretschner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Basin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Schaefer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Walter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Computer Security -ESORICS</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<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="https://api.semanticscholar.org/CorpusID:2010537" />
	</analytic>
	<monogr>
		<title level="m">Alberto Mendelzon Workshop on Foundations of Data Management</title>
				<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Towards compliance checking in reified I/O logic via SHACL</title>
		<author>
			<persName><forename type="first">L</forename><surname>Robaldo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 18th International Conference on Artificial Intelligence and Law, ICAIL</title>
				<meeting>the 18th International Conference on Artificial Intelligence and Law, ICAIL</meeting>
		<imprint>
			<date type="published" when="2021">2021. 2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Compliance checking on firstorder knowledge with conflicting and compensatory norms: a comparison among currently available technologies</title>
		<author>
			<persName><forename type="first">L</forename><surname>Robaldo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Batsakis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Calegari</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Calimeri</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Fujita</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Governatori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Morelli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Pacenza</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Pisano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Satoh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Tachmazidis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Zangari</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence and Law</title>
		<imprint>
			<biblScope unit="volume">32</biblScope>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">I</forename><surname>Akaichi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kirrane</surname></persName>
		</author>
		<ptr target="https://arxiv.org/abs/2203.04800" />
		<title level="m">Usage control specification, enforcement, and robustness: A survey</title>
				<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

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