<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Geospatial Reasoning with Shape les for Supporting Policy Decisions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Henrique Santos</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>James P. McCusker</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Deborah L. McGuinness</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Rensselaer Polytechnic Institute</institution>
          ,
          <addr-line>Troy NY, USA 12180</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Policies are authoritative assets that are present in multiple domains to support decision-making. They describe what actions are allowed or recommended when domain entities and their attributes satisfy certain criteria. It is common to nd policies that contain geographical rules, including distance and containment relationships among named locations. These locations' polygons can often be found encoded in geospatial datasets. We present an approach to transform data from geospatial datasets into Linked Data using the OWL, PROV-O, and GeoSPARQL standards, and to leverage this representation to support automated ontology-based policy decisions. We applied our approach to locationsensitive radio spectrum policies to identify relationships between radio transmitters coordinates and policy-regulated regions in Census.gov datasets. Using a policy evaluation pipeline that mixes OWL reasoning and GeoSPARQL, our approach implements the relevant geospatial relationships, according to a set of requirements elicited by radio spectrum domain experts.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Policies are commonly de ned as decision-making assets that express one or more
actions allowed or recommended under certain conditions. In the radio
communications domain, policies are created to help manage the use of a limited
electromagnetic spectrum. Many policies are location-speci c, meaning that they are
only applicable when the usage of the radio spectrum is to occur in speci c
geographic locations, as dictated by the policy. In the United States, the National
Telecommunications and Information Administration Manual of Regulations and
Procedures for Federal Radio Frequency Management 1 (NTIA Redbook ) is a
compilation of regulatory policies that de ne the conditions organizations, systems,
and devices must satisfy to compatibly share radio spectrum while minimizing
interference. Because policies in the NTIA Redbook regulate both commercial
and federal spectrum usage, it is common to nd military facilities, as well as
regulations covering domestic and international locations.</p>
      <p>Copyright ©2021 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
1 http://bit.ly/NTIA_Redbook</p>
      <p>
        The US Census Bureau publishes geospatial datasets about the United States,
its territories, and points of interest, in its Census.gov data portal. The datasets
contain high-de nition polygons, usually in the shapefile [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] format, of many
locations referred by radio spectrum policies. Although this format is a popular
choice for encoding geographical entities, its main use-case is to support data
interchange among geographic information systems (GIS). The shapefile
format usually requires the use of a GIS to allow operations over the data, including
calculations and queries. Therefore, it is not very suitable for integrating with
ontology-based applications.
      </p>
      <p>
        We present an approach to allow ontology-based applications to leverage
geospatial data in formats not easily accessible or referred from within
ontology constructs, and to use this data to perform geospatial calculations. We
implemented the approach to support automated radio spectrum policy
decisions. This is accomplished by representing Census.gov relevant polygons in the
GeoSPARQL [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] vocabulary, and by de ning OWL [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] classes that encode the
policies' location rules. A policy evaluation pipeline that mixes OWL reasoning
and GeoSPARQL leverages this model to elicit spatial relationships, providing
high-de nition spatial calculations. This approach was evaluated to perform well
in terms of coverage of geospatial requirements, as elicited by domain experts. It
is implemented as part of the Dynamic Spectrum Access (DSA) Policy
Framework [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], which was developed to serve as a machine-readable policy repository
to support increased automation of policy evaluations.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Transforming Census.gov shapefiles</title>
      <p>The majority of location-sensitive policies in the NTIA Redbook refer to these
types of locations: military facilities, States, or Country. Because the policies
are originally authored in natural language, and targeted at spectrum
managers, they refer to locations by their names (e.g. \Fairbanks", \Camp Parks"),
without a comprehensive de nition of the boundaries of such regions. To
support automation of policy decisions, it becomes crucial to encode and leverage
the polygons for these relevant locations.</p>
      <p>The Census Bureau is the United States agency that serves as the nation's
leading provider of quality data about its people and economy. Yearly, the agency
publishes updated and authoritative geospatial datasets to provide meaning and
context to statistical data the bureau produces. Largely published in the
shapefile format, the published data2 does include State boundaries and military
installations, conveniently supporting our policy use-case. The State dataset is
composed of 56 polygons, representing the 50 U.S. States, District of Columbia,
plus 5 U.S. territories. The military installation dataset has 859 polygons,
describing information about airports, laboratories, training areas, etc. In addition
to the polygons, the datasets contain some minimal metadata about the
locations, including a unique ID, and a legal name.
2 https://www.census.gov/programs-surveys/geography/geographies/
mapping-files.html</p>
      <p>
        We have applied the Semantic Extract, Transform, and Load-r (SETLr [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ])
to these datasets. SETLr orchestrates ETL pipelines by the use of a script in
Turtle format that de nes data sources, extract and transform processes, and
destination formats. SETLr was executed in both geospatial datasets to
extract shapes' information and transform them into geographical features
using the PROV-O [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] (prov:Location) and GeoSPARQL (geo:Feature,
sf:Geometry) ontologies. Because each phase of the ETL pipeline in SETLr
is de ned as an RDF resource, the complete provenance of how these
geographical features came to be is maintained, thereby supporting the explanation of
policy decisions in more complex scenarios where multiple locations sources are
involved.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Geospatial Reasoning on Radio Spectrum Policies</title>
      <p>Geospatial reasoning is a crucial capability when evaluating policies. Many
policies, including those that regulate radio spectrum usage, are only applicable
when their speci ed location rules are satis ed. These locations include named
locations that can be mapped to features from geospatial datasets, and
polygons de ned directly in the policy's rules. Either way, location rules need to be
correctly evaluated, taking into consideration which polygons the policy
regulates, as well as coordinates that are subject to evaluation (e.g. where a radio
transmission is to occur).</p>
      <p>
        We designed the DSA Policy Framework [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] to serve as a machine-readable,
radio spectrum policy repository that can be used to automatically process
radio transmission requests. The framework utilizes the World Wide Web
Consortium's (W3C) OWL 2 and PROV-O, and the Open Geospatial Consortium's
(OGC) GeoSPARQL 1.0 standards as a modeling foundation of radio spectrum
policies and involved entities. Figure 1 shows the RDF model of a transmission
request within the DSA Policy Framework. Transmission requests are de ned as
prov:Activity, with the associated requester as a prov:Agent. Attributes
that further characterize the transmission are represented using either PROV-O
(including the location attribute) or a domain ontology. Coordinates in which
requesters are located are represented as Well-Known Text (WKT) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] string,
and expressed using the geo:asWKT predicate.
      </p>
      <p>Transmission
xsd:dateTime</p>
      <p>POINT
(-114.23 33.20)
Agent (Requester)</p>
      <p>Activity (Action)
wasAssociatedWith</p>
      <p>GenericJTRS_Radio
hasAttribute
atLocation
startedAtTime
endedAtTime
Frequency</p>
      <p>Range</p>
      <p>Location</p>
      <p>asWKT</p>
      <p>Fig. 1. The DSA request model</p>
      <p>To allow the evaluation of the relationships between coordinates from
transmissions and policy-regulated locations, we have pursued the representation of
these locations as an OWL ontology where classes represent policy locations. To
exemplify this approach, we will use the second provision of the US91 policy
from the NTIA Redbook, which reads (with adaptations):
\In the sub-band 1761-1780 MHz, Federal earth stations in the space
operation service may transmit at the following 25 sites and non-Federal
base stations must accept harmful interference caused by the operation
of these earth stations: Fairbanks, Camp Parks, ... ."</p>
      <p>Besides the policy text itself, which explicitly lists 25 sites where the policy
is applicable, US91 is listed in the NTIA Redbook under the United States table,
because it is only applicable in the US and not internationally. Listing 1 shows
the representation of the involved locations for supporting this policy. Lines 1-7
de ne the USLocation class for expressing the entire United States land. This
class is de ned as a prov:Location and is a union of all States, District of
Columbia, and territories from the appropriate Census.gov dataset, using the
geo:sfWithin predicate from GeoSPARQL. Similarly, lines 9-16 extend this
class to express the speci c locations the above policy regulates, this time using
features from the military facilities Census.gov dataset.
To evaluate coordinates in transmission requests with policy-regulated locations,
we used the GeoSPARQL function predicates embedded in SPARQL queries, as
seen in Listing 2. The implemented queries focus on the within and
distance relationships. The queries infer triples in the format :req location
geo:sfWithin :NAMED LOCATION, or as a distance attribute with the
numerical distance as a value and in relation to some named location.</p>
      <p>Listing 2. GeoSPARQL statements to elicit select geospatial relationships.</p>
      <p>The inferred triples are asserted back into the transmission request RDF
model, which then gets reasoned over by an OWL reasoner. Using those inferred
assertions, the location speci ed in the request can now be correctly reasoned
to belong to one or more location classes, such as those in Listing 1. To
exemplify this process, the coordinates for the request in Figure 1 are located in
Arizona. Because US91's second provision does not include any Arizona
locations, no triple linking the request location to one of the policy's locations would
be inferred. But, a triple linking the request location to the State of Arizona
would exist (:req location geo:sfWithin :STATE 04). In this setting,
the request location would be reasoned to belong to the USLocation class, but
not to the US91-2-c Location class, indicating that the transmission is to
occur in the United States, but the second provision of US91 is not applicable.</p>
      <p>Conversely, if the request in Figure 1 is modi ed to a coordinate within
the \Fairbanks" named location, a triple :req location geo:sfWithin
:Fairbanks will exist. Therefore, the request location will be reasoned to
belong to the US91-2-c Location class, making the second provision of US91
applicable.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Evaluation</title>
      <p>We worked with radio spectrum domain experts to elicit a set of geographical
requirements that a machine-readable policy model needs to support. They appear
in bold in the rst column of Table 1. The table contains columns for Policy
Representation and Request Evaluation. \Yes" indicates that the policy construct
is either Relevant or it has been fully addressed and Implemented. \Partial"
indicates that the current implementation meets a simpli ed requirement.</p>
      <p>Locations</p>
      <p>Named locations
Relative locations</p>
      <p>Polygons/Circles
Geographical rules</p>
      <p>Speci c location
List of locations</p>
      <p>Policy Representation Request Evaluation
Relevant Implemented Relevant Implemented
yes yes yes yes
yes partial yes partial
yes yes yes yes
yes
yes
yes
yes
yes
yes
yes
yes</p>
      <p>Most policies refer to locations by names or by coordinates (points, polygons,
and circles), but sometimes a location is expressed in relation to another
location. Currently, relative locations have been constrained to the ones expressed
using the distance relationship. Geographical rules are de ned in terms of the
requester being in a location or a list of locations. Our approach implements
these constructs using the geo:sfWithin predicate and OWL unions.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Related Work</title>
      <p>
        The works in [
        <xref ref-type="bibr" rid="ref11 ref13">11,13</xref>
        ] proposed approaches for converting geospatial content to
RDF, using mapping languages and ETL pipelines. The work in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] allows the
access of geospatial datasets, including shapefiles, using an ontology-based
data access approach. Our conversion relied on SETLr, which enables the data
conversion of geospatial data to RDF similar to the rst two approaches, but also
allows the maintenance of data transformation provenance. This maintenance is
important in this use-case for supporting the explanation of policy decisions.
      </p>
      <p>
        XACML 3.0, the eXtensible Access Control Markup Language [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], is a
wellknown policy language and de facto standard for representing attribute-based
access control (ABAC) [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] policies and requests. Importantly, XACML
provides a reference architecture for centralizing access control and a process model
for evaluating requests against existing policies that inform the design of access
control systems across domains and technologies. Thi [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] proposes an
OWLbased extension to XACML to support a generalized, context-aware, role-based
access control (RBAC) model, providing Spatio-temporal restrictions and
conforming with the NIST RBAC standard [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Their work augments the XACML
architecture with new functions and data types.
      </p>
      <p>Our approach combines OWL, PROV-O, and GeoSPARQL to encode
geospatial features, and an OWL reasoner to realize location class memberships. Our
representation builds on previous work by matching the cross-domain policy
expression semantics of XACML, extending it with the capacity to express rich
Spatio-temporal restrictions, enabling the implementation of a wide variety of
attribute-based policies across domains.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>This paper presents an approach for leveraging geographical features, originally
in shapefiles, to support policy decisions. In the radio spectrum domain, it
is commonplace for policies to regulate the usage of the spectrum in speci c
locations, therefore requiring spatial reasoning to identify relationships between
radio transmitters' coordinates and policy-regulated regions. This approach is an
integral part of the DSA Policy Framework, which is functioning as a prototype
policy management system in support of spectrum sharing operations.</p>
      <p>
        Future work involves the research and development of the application of
more spatial relationships, including relative locations. Besides, in other policy
publications, we have encountered locations that are expressed in unusual shapes.
These include paths, cones, and altitudes. More research is necessary to assess
the impact in both modeling and reasoning, should we pursue this line of work.
Finally, we are generalizing the approach to beyond radio spectrum policies
by initially supporting practitioners from multiple domains in the creation of
policies utilizing terminology and entities in domain knowledge graphs [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
Acknowledgements. This work is partially funded through the National
Spectrum Consortium (NSC) project number NSC-17-7030.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <source>eXtensible Access Control Markup Language (XACML) Version</source>
          <volume>3</volume>
          .0. http:// docs.oasis-open.
          <source>org/xacml/3</source>
          .0/xacml-3.0
          <article-title>-core-spec-os-en</article-title>
          .html
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. ISO/IEC 13249-
          <article-title>3:2016 Information technology | Database languages | SQL multimedia and application packages | Part 3: Spatial</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>PROV-O: The PROV Ontology</surname>
          </string-name>
          , https://www.w3.org/TR/prov-o/
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>ESRI</given-names>
            <surname>Shape le Technical Description</surname>
          </string-name>
          (
          <year>1998</year>
          ), https://www.esri.com/ Library/Whitepapers/Pdfs/Shapefile.pdf
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Battle</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kolas</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Enabling the geospatial Semantic Web with Parliament and GeoSPARQL</article-title>
          .
          <source>Semantic Web</source>
          <volume>3</volume>
          (
          <issue>4</issue>
          ),
          <volume>355</volume>
          {
          <fpage>370</fpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bereta</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xiao</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koubarakis</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Ontop-spatial: Ontop of geospatial databases</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>58</volume>
          ,
          <issue>100514</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Falkow</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          :
          <article-title>Towards a Domain-Agnostic Computable Policy Tool</article-title>
          . In:
          <article-title>ESWC 2021 Posters and</article-title>
          Demos
          <string-name>
            <surname>Track</surname>
          </string-name>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Ferraiolo</surname>
            ,
            <given-names>D.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>D.R.</given-names>
          </string-name>
          :
          <article-title>Role-Based Access Controls</article-title>
          .
          <source>In: 15th National Computer Security Conference</source>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Motik</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sattler</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>OWL 2: The next step for OWL</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>6</volume>
          (
          <issue>4</issue>
          ),
          <volume>309</volume>
          {
          <fpage>322</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>V.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>D.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferraiolo</surname>
            ,
            <given-names>D.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Voas</surname>
          </string-name>
          , J.:
          <article-title>Attribute-based access control</article-title>
          .
          <source>Computer</source>
          <volume>48</volume>
          (
          <issue>2</issue>
          ),
          <volume>85</volume>
          {
          <fpage>88</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Kyzirakos</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savva</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vlachopoulos</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vasileiou</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karalis</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koubarakis</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manegold</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>GeoTriples: Transforming geospatial data into RDF graphs using R2RML and RML mappings</article-title>
          .
          <source>Journal of Web Semantics 52-53</source>
          ,
          <issue>16</issue>
          {
          <fpage>32</fpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>McCusker</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chastain</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rashid</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Norris</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          :
          <article-title>SETLr: the semantic extract, transform, and load-r</article-title>
          .
          <source>Tech. Rep. e26476v1, PeerJ Inc</source>
          . (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Patroumpas</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alexakis</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giannopoulos</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Athanasiou</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>TripleGeo: an ETL Tool for Transforming Geospatial Data into RDF Triples</article-title>
          . In: EDBT/ICDT Workshops.
          <source>CEUR Workshop Proceedings</source>
          , vol.
          <volume>1133</volume>
          , pp.
          <volume>275</volume>
          {
          <issue>278</issue>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mulvehill</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Erickson</surname>
            ,
            <given-names>J.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McCusker</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gordon</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xie</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stou er</surname>
          </string-name>
          , S.,
          <string-name>
            <surname>Capraro</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pidwerbetsky</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burgess</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berlinsky</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turck</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ashdown</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          :
          <article-title>A Semantic Framework for Enabling Radio Spectrum Policy Management and Evaluation</article-title>
          . In: The Semantic Web {
          <article-title>ISWC 2020</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>Tran</given-names>
            <surname>Thi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.N.</given-names>
            ,
            <surname>Dang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.K.</given-names>
            :
            <surname>X-STROWL</surname>
          </string-name>
          :
          <article-title>A generalized extension of XACML for context-aware spatio-temporal RBAC model with OWL</article-title>
          .
          <source>In: Seventh International Conference on Digital Information Management (ICDIM)</source>
          . pp.
          <volume>253</volume>
          {
          <issue>258</issue>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>