<!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>A Methodology for Encoding Regulatory Rules</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Hanif Bhuiyan</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Francesco Olivieri</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Guido Governatori</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mohammad Badiul Islam</string-name>
          <email>badiul.islamg@data61.csiro.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andy Bond</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andry Rakotonirainy</string-name>
          <email>r.andryg@qut.edu.au</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Data61, CSIRO</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Queensland University of Technology (QUT), Centre for Accident Research and Road Safety (CARRS-Q)</institution>
          ,
          <addr-line>Queensland</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper introduces a methodology for the encoding of rules into a semantic logical format to facilitate the automated reasoning process. We demonstrate how to identify, capture, combine, and thus formulate all the components from rules into a computationally-oriented formalism. The need for the methodology is motivated by the desire for automated reasoning of automated vehicle information regarding tra c rules. We use Defeasible Deontic Logic as a formal foundation of our methodology. The overtaking tra c rule is our use-case to illustrate the usefulness of our methodology. Through this use-case, it is seen that the logical semantic representation of the tra c rules seems conceivable to support automated reasoning. This paper includes the source materials, the use cases, proposed methodology, and the example of encoding.</p>
      </abstract>
      <kwd-group>
        <kwd>Rules • Terms • Legal norms • Defeasible Deontic Logic</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Road crash is a major concern of global public health due to the epidemic growth
of road fatalities. Every day, more than 3,7001 people die due to road crashes.
From world road crash statistics, it was found that the driver's behaviour is the
main contributing factor for 90% of these crashes [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. In Australia, around 30%
of road crashes occurred due to speeding2. From 2013-20173, in Queensland, the
average death due to high speed was 58 per year. To overcome these driver's
behaviour related errors, Automated Vehicles (AVs) can be introduced to follow
tra c rules properly, which can reduce road fatalities and injuries, and improve
road safety [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. As AVs are designed and programmed to follow tra c rules [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ],
therefore, it is suggested that AVs would be the solution to tra c violations [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ].
However, tra c rules are expressed in natural language, therefore it is required
to encode them into a machine-computable format to be processable by AVs.
Only then it might be e ective for monitoring or validating AV driving action
through automatic tra c rule reasoning [
        <xref ref-type="bibr" rid="ref2 ref26 ref29">2,29,26</xref>
        ].
      </p>
      <p>
        Rule encoding is one of the important requirements for compliance checking,
automated reasoning, and legal validation [
        <xref ref-type="bibr" rid="ref30 ref31">31,30</xref>
        ]. However, rule encoding is a
complex task due to its domain-speci c, sentence length, clause embedding, and
structure. Moreover, rules include thousands of provisions and complex norms,
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], which make the encoding task more challenging. Several research works
have been done to address these issues [
        <xref ref-type="bibr" rid="ref21 ref28">28,21</xref>
        ]. Standards for the representation
of norms and legal knowledge have been proposed [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. For example, XML
serialisations have been presented for business contracts [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], business process
compliance [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], GDPR regulations [
        <xref ref-type="bibr" rid="ref25 ref5">5,25</xref>
        ] and building regulations [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. There
are also some commercial products available (Oracle Policy Automation 4) that
provide services to translate regulations into executable language and also served
with an interactive natural language interface on the web.
      </p>
      <p>
        Tra c rules are often detailed and complex and, therefore, it is a big challenge
to encode them. There have been several e orts to encode tra c rules for di erent
purposes [
        <xref ref-type="bibr" rid="ref26 ref7">7,26</xref>
        ]. Costescu [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] proposed a tra c rules formalisation method using
Higher Order Language (HOL) to keep the AV accountable. Shardin et al [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]
presented an expert system to formalise the tra c rules for controlling the
autonomous vehicle in certain situations. However, none of the previous research
considers how to resolve the con icts and how to handle norms and exceptions
in the rules, which are the most important variant features of the tra c rules.
Therefore, here we propose a Defeasible Deontic Logic (DDL) based encoding
methodology to translate tra c rules (natural text) into a semantic logical
format (machine-computable). The integration of DDL makes our rule encoding
methodology more applicable and useful for handling the exceptions, situation
con icts, ambiguities, and various forms of norms. An example of translating a
tra c rule into semantic logical format is shown in Figure 1. The use case we
used in this work is derived from the Queensland Tra c Rules, Australia5. The
motivation for the use of DDL is provide below.
      </p>
      <p>
        Legal reasoning has some special features, which are norms and exceptions.
Usually, norms set baseline conditions but later, they are open to exceptions.
These exceptions are also expressed as norms. Norms prescribe behaviour using
permissions, obligations, and prohibitions. Therefore, we need a logical approach
to handle such exceptions in the tra c rules. In legal reasoning, DDL has been
successfully proposed [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] to handle the exceptions and it is also seen that it
does not undergo from problems a ecting other logics used for reasoning about
compliance and norms [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. For the representation of rules, DDL is a conceptually
profound approach, and at the same time, it exhibits a computationally feasible
4 https://www.oracle.com/technetwork/apps-tech/policy-automation/overvie
w/index.html
5 https://www.legislation.qld.gov.au/view/html/inforce/current/sl-2009-0
194#sec.20
environment to reason about them. Furthrmore, Defeasible Deontic Logic (DDL)
is computationally feasible since we can compute the extension of a theory in
linear time [
        <xref ref-type="bibr" rid="ref14 ref15">15,14</xref>
        ] and it is suitable to e cient implementations [
        <xref ref-type="bibr" rid="ref16 ref19">19,16</xref>
        ].
      </p>
      <p>There are several situations in con ict within the Queensland tra c rules,
which may create problems for automatic tra c rule reasoning regarding AV.
For example, in Tra c rules, Part 12, Division 3, Rule 170 says
(2) A driver must not stop on a road within 20m from the nearest point
of an intersecting road at an intersection with tra c lights, unless the
driver| (a) stops at a place on a length of road, or in an area, to which
a parking control sign applies; and (b) is permitted to stop at that place
under this regulation.</p>
      <sec id="sec-1-1">
        <title>Also, in Part 12, Division 1, Rule 165 recites</title>
        <p>the driver may stops at a particular place, or in a particular way because
the condition of the driver, a passenger, or the driver's vehicle makes it
necessary for the driver to stop in the interests of safety, and the driver
stops for no longer than is necessary in the circumstances.</p>
        <p>
          These two rules can contradict each other regarding stopping on a road. The
main purpose of these examples is not to show the di erence in tra c behaviour
but rather to nd the solution to follow the appropriate rule in such di erent
situations. These type of con icts often may be solved by the explicit priority
rules. However, Leens and Lucivero [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] noticed that subtle con ict arises in
the rules that may not be solved by rule priorities. To solve such issues, there
is one e ective approach by [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], which works based on logic using a suitable
variant. Regarding such issues, approaches by [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ], [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ] are also well known in
nonmonotonic logic areas.
2
        </p>
        <p>Tra</p>
        <p>c Rules Encoding
The proposed methodology consists of four modules as shown in Figure 2. Here,
we introduce our methodology to translate the tra c rules into the semantic
logical format. The input of the system is tra c rules (natural text) as shown in
Figure 1(a). In the rst module, we de ne atoms from the rules. In the second
module, we determine the norms. The if-then structure is identi ed and generated
from the rules in the third module. Finally, we use Defeasible Deontic Logic
(DDL) on the atoms, norms and if-then structure to make the semantic logical
format. The modules are explained below. An example of making a semantic
logical format of tra c rules is shown in Figure 1.</p>
        <p>De ne Atoms This section outlines in brief that how we de ne atoms from rules.
An atom is a predicate symbol including constants or variables that contains no
logical connectives. Here to de ne atoms, we use terms of the rule sentence. A
term is a variable or an individual constant in the sentence. This work deals with
those variables and constants that refer to subject (s), predicate (p), property
(pr), object (o), and quali er (q) (Figure 3) in the rule sentence.</p>
        <p>In natural language a subject is refers to that term about which something is
said in the sentence. The something which is said about something is the predicate
of the sentence. The predicate of a subject-predicate sentence indicates relation or
a property. The object is what that subject does something to. In another word,
object are the results of action. Quali ers are that terms which usually enhance
or limits the other word meaning. In one sense it can be said as an adverb of the
sentence. Before generating terms, some article preprocessing are done on the text.
Like, we are not considering the verbs (auxiliary, principal and modal) for this
task. In logic, Subjects are variable or constant in the rule sentence that refers to
the entity always. Predicate always refers to the properties or action of entities.
Properties indicate the relation between subject and predicate. Object refers to
the properties of the entities. Quali ers refer to the variable that enhances or
limits the entities.</p>
        <p>Atom is a combination of these terms and composed as a statement which
only can be evaluated as true or false. For example \The bus breaks the tra c
rule". According to the linguistic perspective, the term `bus' is the subject of
the sentence as this sentence is about this. The term `tra c rule' is the object of
the sentence as the subject is doing something to it. The term (verb) `breaks'
is the predicate of the sentence as it expresses the relation between the subject
(bus) and object (tra c rule). In logical approach, `bus' is that variable (subject)
which refers the entity of the sentence. `breaks' is the predicate constant which
refers the action of the entity. `tra c rule' is an individual of the sentence which
refers the properties of the entity. So in a logical way, we can represent the above
example as Predicate (subject, object): B(b,t): Breaks (bus, truck). Therefore the
atom can be represented as Subject-Predicate-Object: bus Breaks theTra cRule.</p>
        <p>In tra c rules, the rule structure are not equally structured. Due to this
heterogeneity of the rules information, the atom structure varies. An example of
identifying terms and de ning atom from the tra c rule is shown in Figure 1
(b) &amp; (c). Throughout the empirical study of the Queensland Tra c Rules, we
semantically de ne the atom in terms of ve aspects which are:
Subject-PredicateObject; Subject-Predicate-Quali er-Object; Subject-Property,
Subject-PredicateObject-Object; Subject-Quali er-Predicate-Object. Some examples are shown
below.</p>
        <p>Example 1 : Overtaking tra c rule section 151A: 3 (c) \the rider rides in a
school zone".</p>
      </sec>
      <sec id="sec-1-2">
        <title>Subject Predicate Object the rider rides in school zone</title>
      </sec>
      <sec id="sec-1-3">
        <title>Generated Atom: rider IsRidingIn schoolZone. Example 2 :Overtaking tra c rule section 140: b \the driver can safely overtake the vehicle".</title>
      </sec>
      <sec id="sec-1-4">
        <title>Subject Predicate Quali er Object the driver overtake safely the vehicle</title>
      </sec>
      <sec id="sec-1-5">
        <title>Generated Atom: driver CanSafelyOvertake vehicle.</title>
        <p>
          Determining Norms Norms stipulate the conditions in the rule to perform
speci c actions. Every norm is represented by one or more rules, which could
either constitutive or prescriptive rules [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. Constitutive rules de ne the terms
speci c to legal documents, whereas prescriptive rules are used to encode the
obligation, permission, and prohibition, . . . , and the conditions under which they
are entering into force to follow according to legal document. An obligation is a
type of legal requirement where the subject has to perform an action otherwise
a violation is triggered, whereas prohibition is about an action that cannot be
performed; if it is performed, then the result represents a violation.
        </p>
        <p>Prescriptive rules are determined based on conceptual semantic understanding
and some special keywords, which are \must", \must not", \should", \ought", etc.
For prescriptive rules, we consider only obligation, prohibition and permission
norms. We identify the constitutive rules through our knowledge of understanding
and descriptive notions in the sentences. Some examples of descriptive notions are
\it is", \means", \does", \does not", etc. An example of determining prescriptive
and constitutive norms from overtaking tra c rules, is shown Figure 4.</p>
        <p>
          Generate if-then Structure Typically rules contain conditions and norms,
which control the behaviour of the subject. From a legal perspective, rules use
conditions on some actions to achieve particular behaviours. Rules can be analysed
based on the subject's behaviour and the circumstances [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. In AI &amp; Law domain
it is widely accepted that norms have if-then conditional structure [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ]. Therefore,
for encoding tra c rules, we make the conditional structure using the atoms and
norms (prescriptive or constitutive).
        </p>
        <p>if (X1; : : : ; Xn)
then [norms]
f Y g
Here, (X1; : : : ; Xn) is the antecedent (premises), and Y is the conclusion
(consequent) of the rule. In a tra c rules context, norms represent the situation
of actions. Some actions are mandatory to follow; some are not. For example,
\Rule 144A: Keeping a safe lateral distance when passing bicycle rider". The
rule expresses an obligation for the driver while passing a bicycle rider. A simple
example of generating an if-then structure is shown in Figure 5.</p>
        <p>
          Rules Encoding Defeasible Deontic Logic (DDL) is the combined form of
defeasible logic and deontic logic. DDL can deal with both normative and
defeasible reasoning based on defeasible logic [
          <xref ref-type="bibr" rid="ref23 ref3">23,3</xref>
          ] and deontic logic. We identify
and combine atoms, norms, and if-then structure using DDL to create semantic
logical format (machine-computable) of the rules. A brief overview of how DDL
is used to represent tra c rules is given below.
        </p>
        <p>
          Defeasible theory consists of ve distinct knowledge foundations: strict rules,
facts, defeasible rules, superiority relations, and defeaters [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. The theoretical
notion of defeasible logic (DL) is D (F; R; ) where, F is a set of facts, R is a set
of rules, and is a superiority relation over R.
        </p>
        <p>DL consists of a nite set of literals, where a literal is either an atomic
proposition or its negation. Given a literal X, X denotes its complement. That
is, if X = Y then X = :Y , and if X = :Y then X = Y .</p>
        <p>Facts (F ) are conclusive and unambiguous statements. A fact is represented
either in the form of state a airs (literal or modal literal) or actions that have
been performed and are considered as always true. For example, \Honda is a
Motorbike", is represented by: Motorbike(Honda).</p>
        <p>
          A rule (r 2 R) describes the relationship between premises and conclusion and
we can specify the strength of this relationship. Based on the relationship strength
of the rules, we can di erentiate defeasible rules, strict rules and defeaters [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ].
These rules are represented by the following expressions X1; : : : ; Xn ! Y (Strict
Rules), X1; : : : ; Xn ) Y (Defeasible Rules) and X1; : : : ; Xn ; Y (Defeaters),
where X1; : : : ; Xn is the antecedent or premises (clauses) and Y is the consequent
or conclusion (e ect) of the rule. Besides these, rules also contain free variables
which are interpreted as the ground instances.
        </p>
        <p>Strict rules are rules in the classical sense: whenever the premises are
indisputable (e.g. a fact) so is the conclusion. For example, \a motorbike is vehicle,"
formally: Motorbike(Honda) ! Vehicle(Honda).</p>
        <p>Defeasible rules are rules that can be defeated by contrary evidence. An
example of a tra c rule is: \Part 11 Division 4 Section 151 B (3): the rider is
taken to have unlawfully edge ltered along the length of road|(a) the rider
does not hold an O type licence for the class of the motorbike". In summary, a
motorbike can edge lter if the rider holds an O type licence, so formally we can
write: Motorbike(Honda) ) EdgeFilteringVehicle(Honda). From this information,
it can be concluded that a motorbike can edge lter on the road unless there is
any evidence is provided that the motorbike cannot edge lter. A defeasible rule
with empty premises would be considered as a presumption.</p>
        <p>Defeaters are rules, that are used to prevent the conclusion. As an example,
:(rider HoldOTypeLicence Vehicle(Honda)) ; :EdgeFilteringVehicle(Honda).
From this rule we can state that Honda is an edge ltering vehicle but if the
rider of a Honda does not hold a O type licence, then it cannot edge lter on
the road. This statement can prevent the conclusion of edge ltering. This is not
also supporting the no edge ltering.</p>
        <p>Defeasible Logic is a non-monotonic, skeptical approach that does not support
a contradictory conclusion. It aims to resolve the con icts between knowledge.
For example, suppose there is information, and it has support to conclude A,
but also there is information which does not support A and prevents it from
concluding A. If the support for A has priority over :A , then it might be possible
to conclude A. In such scenarios no conclusion can be made unless the rules are
prioritized. The superiority relation ( ) used the priority set among the rules,
where one rule may override the conclusion of other rules. An example of edge
ltering concept using the Turnip Engine is shown in Table 1.</p>
        <p>In Table 1, we can see that, no conclusive decision can be made until we use
the superiority relation . Without using the superiority relation, we can only
conclude that Honda is an Edge Filtering vehicle. After using the superiority
relation like r1 r0 and r2 r1, then we can conclude that (as in the result
section of Table 1) a professional rider can Edge Filter if he/she has a O Type
Licence but learner or provisional rider cannot edge ltering.</p>
        <p>In addition to defeasibility, tra c rules also engage with deontic concepts,
which are obligation (O), permission (P), and prohibition (F). For example,
considering the concept \overtake", we can de ne these notions as:
[F]overtake
[O]overtake
[P]overtake
[O]:overtake
[F]:overtake
:[O]:overtake</p>
        <p>An example of representing tra c rules using DDL is given below. For this
example, we use the Queensland Overtaking tra c rules (Part 11 Division 3 rule
140 in Tra c Rules).</p>
        <p>; (Empty Set) ) [F] Overtake
driver (HasClearViewOf approachingTra c)
^ driver (CanSafelyOvertake vehicle) ) [P] Overtake</p>
        <p>A simple and complete example of encoding Overtaking Tra c Rules: 141 (1)
using Defeasible Deontic Logic (DDL) is shown in Figure 1.
3</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Limitation</title>
      <p>
        This work uses Defeasible Deontic Logic (DDL) to de ne a logical semantic
representation of tra c rules; however, there are some issues regarding the
accuracy and completeness of the representation. Given the sophisticated and
varied nature of tra c rules, identifying all the terms, norms, rule types and
conditions is a challenging task, as these components found in explicit or implicit
linguistic forms. As noted, the generic interpretation is not represented here. Only
ve di erent aspects of combination between subject, predicate, object, property,
and quali er are considered for de ning atoms. In terms of norms determination
from rules, only explicit types of norms (obligation, permission, and prohibition)
are considered, although there might be di erent types of permission and other
normative e ects [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. There are some questions which may arise regarding the use
of defeasible deontic logic in this work. As we did not evaluate the methodology
based on any gold standard or any other approaches. Despite the above issues,
there are signi cant advantages of our proposed encoding methodology, which are
domain independence and scope of applicability. This methodology can be used
in other domains such as anti-money laundering rules and regulations, university
rules and regulations, etc.
4
      </p>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>Encoding the complex and varying nature of tra c rules is a challenging task. Any
wrong encoding of the rule can adversely e ect on the reasoning process. Therefore,
we proposed a Defeasible Deontic Logic (DDL) based encoding methodology for
translating tra c rules into a semantic logical format (machine-computable),
which can be used for automatic tra c rule reasoning to validate automated
vehicle legal behaviour. The methodology incorporates the components and
behaviour of regulations such as atoms (de ned from terms), norms, and if-then
structure to analyse the rule content as well as identify the actions and activities
of the rules. DDL is applied to the characteristics of the rules to resolve con icts
and understand the norms and exceptions more explicitly. In the future, we plan
to enhance the scale and scope of this proposed methodology. We intend to cover
all possible combinations of terms and normative e ects for this task. Besides
work on the overall tra c rules, we also plan to work on other domains to make
this encoding methodology more e cient and standard in the eld of Law and
AI research.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Aberg</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Tra c rules and tra c safety</article-title>
          .
          <source>Safety science 29(3)</source>
          ,
          <volume>205</volume>
          {
          <fpage>215</fpage>
          (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Aladin</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varlamov</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chuvikov</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chernenkiy</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smelkova</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baldin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Logic-based arti cial intelligence in systems for monitoring the enforcing tra c regulations</article-title>
          .
          <source>In: Materials Science and Engineering</source>
          . vol.
          <volume>534</volume>
          , pp.
          <volume>12</volume>
          {
          <fpage>25</fpage>
          . IOP Publishing (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Antoniou</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Billington</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maher</surname>
            ,
            <given-names>M.J.:</given-names>
          </string-name>
          <article-title>Representation results for defeasible logic</article-title>
          .
          <source>ACM Transactions on Computational Logic (TOCL) 2</source>
          (
          <issue>2</issue>
          ),
          <volume>255</volume>
          {
          <fpage>287</fpage>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Banks</surname>
            ,
            <given-names>T.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Banks</surname>
            ,
            <given-names>F.Z.</given-names>
          </string-name>
          :
          <article-title>Corporate legal compliance handbook</article-title>
          . Aspen Publishers Online (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Bartolini</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenzini</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Robaldo</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>The DAta Protection REgulation COmpliance Model</article-title>
          .
          <source>IEEE Secur. Priv</source>
          .
          <volume>17</volume>
          (
          <issue>6</issue>
          ),
          <volume>37</volume>
          {
          <fpage>45</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Costescu</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <article-title>M.: Keeping the autonomous vehicles accountable: Legal and logic analysis on tra c code</article-title>
          .
          <source>In: Conference Vision Zero for Sustainable Road Safety in Baltic Sea Region</source>
          . pp.
          <volume>21</volume>
          {
          <fpage>33</fpage>
          . Springer (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Damm</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          , Peter,
          <string-name>
            <given-names>H.J.</given-names>
            ,
            <surname>Rakow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Westphal</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          :
          <article-title>Can we build it: formal synthesis of control strategies for cooperative driver assistance systems</article-title>
          .
          <source>Mathematical Structures in Computer Science</source>
          <volume>23</volume>
          (
          <issue>4</issue>
          ),
          <volume>676</volume>
          {
          <fpage>725</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Ghannad</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>Y.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dimyadi</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Solihin</surname>
          </string-name>
          , W.:
          <article-title>Automated bim data validation integrating open-standard schema with visual programming language</article-title>
          .
          <source>Advanced Engineering Informatics</source>
          <volume>40</volume>
          ,
          <issue>14</issue>
          {
          <fpage>28</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Gordon</surname>
            ,
            <given-names>T.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rotolo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Rules and norms: Requirements for rule interchange languages in the legal domain</article-title>
          .
          <source>In: RuleML 2009</source>
          . pp.
          <volume>282</volume>
          {
          <fpage>296</fpage>
          . LNCS 5858, Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Governatori</surname>
          </string-name>
          , G.:
          <article-title>Representing business contracts in RuleML</article-title>
          .
          <source>International Journal of Cooperative Information Systems</source>
          <volume>14</volume>
          (
          <issue>2-3</issue>
          ),
          <volume>181</volume>
          {
          <fpage>216</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>The Regorous approach to process compliance</article-title>
          .
          <source>In: 2015 IEEE 19th International Enterprise Distributed Object Computing Workshop</source>
          . pp.
          <volume>33</volume>
          {
          <fpage>40</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Governatori</surname>
          </string-name>
          , G.:
          <article-title>Practical normative reasoning with defeasible deontic logic</article-title>
          . In: d'Amato,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Theobald</surname>
          </string-name>
          , M. (eds.)
          <source>Reasoning Web</source>
          <year>2018</year>
          , pp.
          <volume>1</volume>
          {
          <fpage>25</fpage>
          . LNCS 11078, Springer International Publishing,
          <string-name>
            <surname>Cham</surname>
          </string-name>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hashmi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lam</surname>
            ,
            <given-names>H.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Villata</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palmirani</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Semantic business process compliance checking using LegalRuleML. In: Knowledge Engineering and Knowledge Management</article-title>
          . pp.
          <volume>746</volume>
          {
          <fpage>761</fpage>
          . LNAI 10024, Springer International (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Olivieri</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rotolo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scannapieco</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Computing strong and weak permissions in defeasible logic</article-title>
          .
          <source>Journal of Philosophical Logic</source>
          <volume>42</volume>
          (
          <issue>6</issue>
          ),
          <volume>799</volume>
          {
          <fpage>829</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rotolo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>BIO logical agents: Norms, beliefs, intentions in defeasible logic</article-title>
          .
          <source>Autonomous Agents and Multi-Agent Systems 17(1)</source>
          ,
          <volume>36</volume>
          {
          <fpage>69</fpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rotolo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rubino</surname>
          </string-name>
          , R.:
          <article-title>Implementing temporal defeasible logic for modeling legal reasoning</article-title>
          .
          <source>In: JSAI International Symposium on Arti cial Intelligence</source>
          . pp.
          <volume>45</volume>
          {
          <fpage>58</fpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Khorasani</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tatari</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yadollahi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rahimi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Evaluation of intelligent transport system in road safety</article-title>
          .
          <source>International Journal of Chemical, Environmental &amp; Biological Sciences (IJCEBS) 1</source>
          (
          <issue>1</issue>
          ),
          <volume>110</volume>
          {
          <fpage>118</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Kowalski</surname>
            ,
            <given-names>R.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Toni</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Abstract argumentation</article-title>
          .
          <source>In: Logical Models of Legal Argumentation</source>
          , pp.
          <volume>119</volume>
          {
          <fpage>140</fpage>
          . Springer (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Lam</surname>
            ,
            <given-names>H.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>The making of SPINdle</article-title>
          . In: RuleML
          <year>2009</year>
          . pp.
          <volume>315</volume>
          {
          <fpage>322</fpage>
          . LNCS 5858, Springer, Heidelberg (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Leenes</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lucivero</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Laws on robots, laws by robots, laws in robots: regulating robot behaviour by design</article-title>
          .
          <source>Law, Innovation and Technology</source>
          <volume>6</volume>
          (
          <issue>2</issue>
          ),
          <volume>193</volume>
          {
          <fpage>220</fpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>de Maat</surname>
          </string-name>
          , E.,
          <string-name>
            <surname>Winkels</surname>
          </string-name>
          , R.:
          <article-title>Automated classi cation of norms in sources of law</article-title>
          .
          <source>In: Semantic processing of legal texts</source>
          , pp.
          <volume>170</volume>
          {
          <fpage>191</fpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>McCarty</surname>
            ,
            <given-names>L.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cohen</surname>
            ,
            <given-names>W.W.:</given-names>
          </string-name>
          <article-title>The case for explicit exceptions</article-title>
          .
          <source>In: LPNMR</source>
          . pp.
          <volume>81</volume>
          {
          <issue>94</issue>
          (
          <year>1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Nute</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Defeasible deontic logic</article-title>
          , vol.
          <volume>263</volume>
          . Springer Science &amp; Business
          <string-name>
            <surname>Media</surname>
          </string-name>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24. OASIS:
          <article-title>LegalRuleML Core Speci cation Version 1.0</article-title>
          .
          <string-name>
            <given-names>OASIS</given-names>
            <surname>Committee</surname>
          </string-name>
          <article-title>Speci cation (</article-title>
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Palmirani</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
          </string-name>
          , G.:
          <article-title>Legal knowledge modelling for GDPR compliance checking</article-title>
          .
          <source>In: JURIX 2018</source>
          . pp.
          <volume>101</volume>
          {
          <fpage>110</fpage>
          . IOS Press (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Rizaldi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Altho</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Formalising tra c rules for accountability of autonomous vehicles</article-title>
          .
          <source>In: 2015 IEEE 18th International Conference on Intelligent Transportation Systems</source>
          . pp.
          <volume>1658</volume>
          {
          <fpage>1665</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Sartor</surname>
          </string-name>
          , G.:
          <article-title>Legal reasoning</article-title>
          . Springer (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Sergot</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sadri</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kowalski</surname>
            ,
            <given-names>R.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kriwaczek</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hammond</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cory</surname>
          </string-name>
          , H.T.:
          <article-title>The british nationality act as a logic program</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>29</volume>
          (
          <issue>5</issue>
          ),
          <volume>370</volume>
          {
          <fpage>386</fpage>
          (
          <year>1986</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Shadrin</surname>
            ,
            <given-names>S.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varlamov</surname>
            ,
            <given-names>O.O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ivanov</surname>
            ,
            <given-names>A.M.:</given-names>
          </string-name>
          <article-title>Experimental autonomous road vehicle with logical arti cial intelligence</article-title>
          .
          <source>Journal of advanced transportation</source>
          <year>2017</year>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Wyner</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
          </string-name>
          , G.:
          <article-title>A study on translating regulatory rules from natural language to defeasible logics</article-title>
          . In: Fodor,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Roman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Anicic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Wyner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Palmirani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Sottara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Levy</surname>
          </string-name>
          ,
          <string-name>
            <surname>F</surname>
          </string-name>
          . (eds.)
          <source>RuleML Challenge</source>
          <year>2013</year>
          . vol.
          <volume>1004</volume>
          .
          <string-name>
            <surname>CEUR-WS.org</surname>
          </string-name>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Wyner</surname>
            ,
            <given-names>A.Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peters</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>On rule extraction from regulations</article-title>
          .
          <source>In: JURIX 2011</source>
          . pp.
          <volume>113</volume>
          {
          <issue>122</issue>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>