<!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>Checking Compliance in European Tender Documents through Ontologies and Rules</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Isabella Distinto</string-name>
          <email>isabella.distinto@unibo.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>CIRSFID, University of Bologna</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this paper we present an overview of the PhD thesis, which aims to show the feasibility of a legal knowledge modeling based on the definitions included into legal texts using Semantic Web techniques in order to check compliance of tender documents to EU Directives. We show a hybrid approach, i.e. a theory and a system that combine the use of Akoma-Ntoso standard to describe legal texts, OWL 2.0 for modeling legal concepts and the emerging LegalRuleML standard for providing a rule-based extension of legal knowledge representation on the top of ontologies.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>The world of public procurements is a field of great significance for many reasons. It
is one of the main economic activities of Governments, since through procurements
are acquired services and goods for functioning of the res publica and for meeting
needs of citizens' communities. This activity represents also a significant business
opportunity for economic operators because public procurement in the EU accounts
for 17% of EU GDP. In this scenario, the regular conduct of tendering processes plays
a key role, in terms of transparency and fairness in bidding competitions, reduction of
litigation-related costs, but also corruption fighting strategies.</p>
      <p>
        A tender situation can be considered as a complex case, in which agents, documents
and processes play an interactive role. Norms on public procurements contracts
regulate either the content of documents and the conduct of processes. Through the
representation of knowledge contained in normative texts it is possible to define the
abstract, lawfully type of those documents or processes. Each single document or
applied procedure is an instance of the abstract type defined by normative provisions.
With respect to documents involved in processes related to European public
procurements, both the abstract type and the actual token can be represented with
languages of Semantic Web, in order to describe all the layers perspective of this kind
of texts: structure (as organization of the texts), metadata (as any information that was
not approved by the authority in the document), ontology (as any legal concept called
from text that need a modeling), and finally legal knowledge representation (as
modeling of rules). Through this articulate definition of legal knowledge, as showed
in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], it is possible to bridge the gap between legal text description of procurement
documents and legal knowledge representation that on these same texts start.
This structured knowledge base can be exploited by a system that, making use of an
inference engine, may enable automated reasoning useful to check compliance of
tender documents and processes involved (ABox) with legal concepts and rules, as
norm expressions (TBox).
      </p>
      <p>We define compliance the conformity of a legal document and/or of a relevant
behavior with the normative prescriptions regulating them. The difference between
the prescription stated in legal texts and its actual application is a compliance failure.
Through compliance check is possible to detect this failure.</p>
      <p>The ultimate goal of the research is to produce a set of pilot cases in order to show the
feasibility of such kind of system that would facilitate the monitoring by the
administrations on the regular conduct of procedures for the award of public
contracts.</p>
    </sec>
    <sec id="sec-2">
      <title>2 Background and approaches</title>
      <p>
        XML-based standards are widely adopted by Governments of several countries for
structuring legal documents. Some Legal XML standard (such as Akoma-Ntoso
standard [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]) envisages the connection of structured legal texts with ontologies.
Upon this connection, ontologies can be intended as a common vocabulary for shared
understanding of terms and a powerful tool to express the legal concepts in a formal
and unambiguous way. In that way it is possible to have a link between legal language
or terms and legal concept-based representation, as defined by the same text.
We distinguish between two types of legal knowledge, which can be represented
through languages of Semantic Web [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The first is static knowledge, namely any
concept that is used in legal domain as mean of classification of facts (or ontological
instances), by applying certain rules. We think that the role of ontologies is to model
all static and definitional aspects of these rules-contained knowledge components.
Indeed, legal systems are built upon concepts, whose semantics is defined by the same
text in which they are invoked and through which are enabled inferences, broadly
coincident with teleological purposes of norms. These kinds of knowledge
components are also called “intermediate legal concepts” [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ], since through them are
represented preconditions and legal consequences, in the same way of rules, or as
“inferential links” [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
      </p>
      <p>The second type of legal knowledge is the dynamic one. The ontological level is used
to classify instances (facts) into ontological classes (abstract types). Such classified
facts are then subject to certain provisions. This is the point where ontologies and
rules meet. Indeed, even if in many cases rules applied to classified instances may be
represented through first order logic (necessary condition), in many others cases
monotonic reasoning based on Open World Assumptions (OWA) is not suitable for
reasoning with knowledge-base inconsistencies or conflicts among rules. In legal
domain, accordingly to a set of information an argument can be considered true, but if
the set under consideration is enriched, maybe the truth of the argument has to be
revised. This type of situation is well known as defeasibility and typically is required
non-monotonic logic with Closed World Assumptions (CWA) to represent it. So, our
hypothesis is based on the assumption that it is possible to recognize rules that define
ontologically legal concepts (in terms of proof-of-concepts) and rules that are applied
to legal concepts.</p>
      <p>
        Over the last decades, many rules interchange languages has been produced. The
most relevant are undoubtedly RuleML [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], SVBR [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], SWRL [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], RIF [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] and
LKIF [
        <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
        ]. As noted in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], these languages are not suited to represent rules of legal
domain. Both SWRL and RIF are not able to meet the requirements of legal
knowledge representation, such as the isomorphism and the defeasibility, which can
not be represented with a series of chained implications in first-order logic. It's also
necessary to emphasize that the same type of rules can be implemented in ontologies
through the additional features (Property Chain Inclusion) of OWL 2.0. Also SVBR
suffer the same kind of limitation. Instead, LKIF, although designed specifically for
modeling legal knowledge, is based on the ISO Common Logic standard that does not
look as a candidate standard to be widely adopted within the World Wide Web
community. RuleML has been designed to become the markup language for the
Semantic Web Rules: it is based on XML, is suitable to integrate inferences from
Web ontologies, is extensible since it is built with a modularity approach. However, it
lacks of extensions required by the legal knowledge. Thus, the extension of RuleML
with key features of rules extracted from legal knowledge is now the goal of
LegalRuleML [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] emerging standard. This last language, indeed, allows to meet the
requirements of isomorphism (i.e. the one-to-one correspondence between the atomic
rule and the fragment of natural language text in which the rule is expressed), the
specification of normative effects (such as deontic, qualificatory or potestative, just to
name a few), the dynamic feature of norm and normative effects and the reification
(namely the fact that rules are like objects with relevant properties, such as
jurisdiction, authority and temporal constraints). For these reasons, we chose to
represent rules in LegalRuleML.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3 Related works</title>
      <p>
        Compliance checking is a field that is typically related to business domain. There is
a vast literature on various techniques developed for supporting compliance checking
of business processes to regulations. Just to name a few, Governatori et al. have been
proposed approaches based on multi-modal logic [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] and on a specialized logic,
namely Formal Contract Language (FCL) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] to formalize contracts' rules in order to
manage the compliance of contractual relationships in business processes. Many other
works are based on the formal representation of business contracts and their
performance [
        <xref ref-type="bibr" rid="ref5 ref8">5, 8</xref>
        ]. An approach based on the use of an ontology of compliance
requirements for service processes is described in [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ]: however this work represent
an exception in field of business process compliance checking.
      </p>
      <p>
        About the legal domain, under the NEURONA project, has been developed a legal
ontology for the representation of data protection knowledge for reasoning about the
correctness of the information regarding personal data files and the correctness of the
measures of protection applied to these data files [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Some studies has been
conducted on the complexity and limitations of reasoning on EU Directives with
OWL [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>A pilot case scenario is used for explaining the described methodology. It is based
on the modeling of a complex norm extracted from the European Directive 2004/18
on the coordination of procedures for the award of public works contracts, public
supply contracts and public service contracts, namely the Art. 17. With this example,
we intend to show what are both the limits and the role of ontologies versus rules and
also that LegalRuleML allows to model articulated types of rules, which may be
encountered in modeling of legal knowledge.</p>
      <p>The article 17 of Directive 2004/18 states: “Without prejudice to the application of
Article 3, this Directive shall not apply to service concessions as defined in Article
1(4)”. In this norm are contained: a reference to a the legal concept of service
concession as defined by the same directive (in Art. 1 (4)); an exception to the
application of the Directive (“shall not applied”) and an exception of exception about
this rule in all the cases covered by the Art. 3 recalled by the Art. 17 (“Without
prejudice to the application of Article 3”). In legal domain this mechanism (to recall
another rule) is called meta-rule, since it is a rule about (the activation of) another
rule, namely the Art. 3. This article states that if a contracting authority grants special
or exclusive rights to carry out a public service activity to an entity other than such a
contracting authority, the act by which that right is granted shall provide that, in
respect of the supply contracts which it awards to third parties as part of its activities,
the entity concerned must comply with the principle of non-discrimination on the
basis of nationality1. Section 4.1 describes our proposal about modeling of legal
concepts (static knowledge); Section 4.2 describes how it is possible to model
complex metadata on the top of legal concepts with a syntax look-like LegalRuleML2.</p>
      <sec id="sec-3-1">
        <title>4.1 Proof of legal concepts as basis of proof of legal compliance</title>
        <p>As outlined in Section 1, legal concepts are basically identified by terms
incorporating inferential links between preconditions and legal consequences, in the
same way of rules. So, the role to express this kind of rules can be delegated to
ontologies and in that way the proof of legal concepts can serve as basis of proof of
legal compliance, since every individual belonging to a class of a specific legal
concept have to comply with the restrictions on this class. For the purpose of the
presented pilot case, we've developed an ontology3 for describing particularly the
class of Service Concession as defined in the Art. 1 (4) of the Directive
1 Article 3. Granting of special or exclusive rights: non-discrimination clause - Where a
contracting authority grants special or exclusive rights to carry out a public service activity
to an entity other than such a contracting authority, the act by which that right is granted
shall provide that, in respect of the supply contracts which it awards to third parties as part
of its activities, the entity concerned must comply with the principle of non-discrimination on
the basis of nationality.
2 Documents of the OASIS LegalRuleML TC are available at
https://www.oasisopen.org/committees/documents.php?wg_abbrev=legalruleml. The mailing list describing
the work in progress can be browsed at https://lists.oasis-open.org/archives/legalruleml/.
3 Available at http://codexml.cirsfid.unibo.it
2004/18/ec and the class of Act of grant to entities others than
authority as defined in the Art. 3 of the Directive 2004/18/ec. The main
commitments of this ontology are to check if an individual of type Public
Procurement</p>
        <p>Contract is also of type Service Concession, and which
individual belongs to the class of Service Concession, but is also of type Act of
grant to entities others than authority. In that way the rules are
applied upon the materializations made by the ontology on legal concepts.
According to the definition of Art. 1 (4) of the Directive 2004/18/ec the Class of
Service Concession is modeled as SubClassOf a Public procurement contract,
which has its object the right to exploitation the service or both the right to
exploitation the service and the payment:
&lt;EquivalentClasses&gt;
&lt;Class IRI="#ServiceConcession"/&gt;
&lt;ObjectIntersectionOf&gt;
&lt;Class IRI="#PublicProcurementContract"/&gt;
&lt;ObjectSomeValuesFrom&gt;
&lt;ObjectProperty IRI="#hasObjectOfContract"/&gt;
&lt;ObjectUnionOf&gt;
&lt;Class IRI="#RightOfExploitationTheService"/&gt;
&lt;ObjectIntersectionOf&gt;
&lt;Class IRI="#Payment"/&gt;
&lt;Class IRI="#RightOfExploitationTheService"/&gt;
&lt;/ObjectIntersectionOf&gt;
&lt;/ObjectUnionOf&gt;
&lt;/ObjectSomeValuesFrom&gt;
&lt;/ObjectIntersectionOf&gt;
&lt;/EquivalentClasses&gt;
According to the definition of Art. 3 of the Directive 2004/18/ec the Class of Act of
grant to entities others than authority is modeled as SubClassOf a
LegalDocument, by which is granted a right (special or exclusive) to a legal person
that is not a Contracting authority:
&lt;EquivalentClasses&gt;
&lt;Class IRI="#ActOfGrantToEntityOtherThanAuthority"/&gt;
&lt;ObjectIntersectionOf&gt;
&lt;Class IRI="#LegalDocument"/&gt;
&lt;ObjectSomeValuesFrom&gt;
&lt;ObjectProperty IRI="#byWhichIsGrantedRightTo"/&gt;
&lt;ObjectIntersectionOf&gt;
&lt;Class IRI="#LegalPerson"/&gt;
&lt;ObjectComplementOf&gt;</p>
        <p>&lt;Class IRI="#ContractingAuthority"/&gt;
&lt;/ObjectComplementOf&gt;
&lt;/ObjectIntersectionOf&gt;
&lt;/ObjectSomeValuesFrom&gt;
&lt;/ObjectIntersectionOf&gt;
&lt;/EquivalentClasses&gt;
if
then</p>
      </sec>
      <sec id="sec-3-2">
        <title>4.2 Rules in LegalRuleML</title>
        <p>We have modelled three rules4 using a very preliminary syntax of LegalRuleML5 for
testing the emerging standard and providing useful feedback to the OASIS TC:
• the rule1 is a defeasible rule and involves this fragment of the Art. 17:
“this Directive shall not apply to service concessions as defined in Article 1(4).”
The formalization of this text is the following:</p>
        <p>X is a member of the OWL class public-procurement-contract
X is a member of the OWL class called service-concession
X enters in the definition of the Article 1(4)
the Directive2004/18/EC shall not apply
rule3:
“Without prejudice to the application of Article 3”
if
• the rule2 has strength defeater and is also a meta-rule, since it activates the
X is a member of the OWL class public-procurement-contract
X is a member of the OWL class called service-concession
then
the Directive2004/18/EC shall apply
the rule3 is activated
• the rule3 is related to the content of Article 3;
if</p>
        <p>X is a member of the OWL class called service-concession</p>
        <p>X is a member of the OWL class
act-of-grant-to-entity-otherthan-authority
then</p>
        <p>X shall respect the principle of
Non-discriminationClauseOnTheBasisOfNationality</p>
        <p>X shall respect of supply contracts which it awards to third
parties as part of its activities
We concentrate our attention on the connection between rule2 and rule3 using
lrml:typeRule=&amp;legalRuleML;metaRule as attribute in the rule2 and the &lt;Ind
iri="#rule3"&gt;rule3&lt;/Ind&gt;:
&lt;Rule material="no" id="rule2" lrml:typeRule="&amp;legalRuleML;metaRule"&gt;
&lt;!-- Art.17 Without prejudice to the application of Article 3 --&gt;
&lt;if id="rule2-body"&gt;
&lt;And&gt;
&lt;Atom id="rule2-atom1"&gt;</p>
        <p>&lt;Rel iri="&amp;lkif;#member_of"&gt;is a member of the
publicprocurement-contract&lt;/Rel&gt;</p>
        <p>&lt;Var type="&amp;lkif;#public-procurement-contract"&gt;X&lt;/Var&gt;
&lt;/Atom&gt;
&lt;Atom id="rule2-atom2"&gt;</p>
        <p>&lt;Rel iri="&amp;lkif;#member_of"&gt;is a member of class
serviceconcession&lt;/Rel&gt;</p>
        <p>&lt;Var type="&amp;lkif;#service-concession"&gt;X&lt;/Var&gt;
4 “Article 17 Service concessions - Without prejudice to the application of Article 3, this</p>
        <p>Directive shall not apply to service concessions as defined in Article 1(4).”
5 We take in consideration the version available at the date of the paper submission:
http://www.oasisopen.org/apps/org/workgroup/legalruleml/download.php/45888/2.1defeasibility.002.002.doc
&lt;/Atom&gt;
&lt;/And&gt;
&lt;/if&gt;
&lt;then id="rule2-head"&gt;
&lt;And&gt;
&lt;Atom id="rule2-atom2"&gt;
&lt;Rel iri="&amp;lkif;#shallApply"&gt;shall apply&lt;/Rel&gt;
&lt;Ind iri="&amp;DIRECTIVE2004_18_ec"&gt;Directive2004_18_&lt;/Ind&gt;
&lt;/Atom&gt;
&lt;Atom id="rule2-atom2"&gt;
&lt;Rel iri="&amp;lkif;#shallApply"&gt;shall apply&lt;/Rel&gt;
&lt;Ind iri="#rule3"&gt;rule3&lt;/Ind&gt;
&lt;/Atom&gt;
&lt;/And&gt;
&lt;/then&gt;
&lt;/Rule&gt;</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>5 Ongoing and future perspectives</title>
      <p>
        In this paper we have shown how with an hybrid approach that integrates
ontologies in OWL 2.0 (for contents related to legal concepts) and rules in a
preliminary syntax of LegalRuleML (for the dynamic legal knowledge), it is possible
to express in a computable formalism also complex norms, maintaining the
isomorphic [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] relation with the text and with a clear distinction between roles of
ontologies and rules.
      </p>
      <p>Up to now, an ontology of European public procurement notices has been
developed from scratch in OWL 2.0, in order to represent concepts related to these
types of tender documents and processes involved. The ontology is based on both a
top-down and a bottom-up approach. Indeed it represents concepts extracted form
authoritative sources (Directive 2004/17/EC; Directive 2004/18/EC; etc.) compared
with natural language patterns derived from standard forms in use for these tender
documents6. The ontology is based on a modular approach and allows, for example,
inferences for classifying a contract notice as contract notice with European relevance
(i.e. upon EU threshold) or not. Another module of the ontology has the main
commitment to classify contract notices covered by the Government Procurement
Agreement: through this information it is possible to find out whether a call is open to
the participation of economic operators from countries that are not EU members.</p>
      <p>RDFa assertions in the XML enable the connection between the structural part of
legal texts and the classes of the ontology so developed. Finally upon the ontological
level, are represented rules applied to defined ontological classes as well as to
materializations inferred through reasoners such as Hermit or Pellet.</p>
      <p>We think that future perspectives on this work are strictly related to the investigation
of the topic of legal ontology evolution, in order to met the need to automatically
detect changes in legal concepts and allow for a sustainable evolutionary system
approach.
6 These forms are available at http://simap.europa.eu/buyer/forms-standard/index_en.htm</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgements</title>
      <p>A particular acknowledgement is due to Enrico Motta, provider of meaningful
research inputs during my stage at KMI - The Open University (UK), in the last
spring. Thanks go also to the TC of the RuleML Initiative and to the LegalRuleML
TC for their helpful hints. I am grateful to my tutor and mentor Monica Palmirani, for
her guidance in this challenging research.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Antoniou</surname>
            <given-names>G.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Bikakis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <article-title>DR-Prolog: A System for Defeasible Reasoning with Rules and Ontologies on the Semantic Web</article-title>
          ,
          <source>IEEE Transactions on Knowledge and Data Engineering</source>
          , vol.
          <volume>19</volume>
          , no.
          <issue>2</issue>
          , p.
          <fpage>233</fpage>
          -
          <lpage>245</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bench-Capon</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Coenen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <article-title>Isomorphism and legal knowledge based systems</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          ,
          <volume>1</volume>
          (
          <issue>1</issue>
          ):
          <fpage>65</fpage>
          -
          <lpage>86</lpage>
          ,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tabet</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Wagner</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <article-title>Design rationale for RuleML: A markup language for Semantic Web rules</article-title>
          . In I. F. Cruz,
          <string-name>
            <given-names>S.</given-names>
            <surname>Decker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          , and
          <string-name>
            <surname>D. L</surname>
          </string-name>
          . McGuinness, editors,
          <source>Proc. SWWS'01, The first Semantic Web Working Symposium</source>
          , pages
          <fpage>381</fpage>
          -
          <lpage>401</lpage>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Casellas</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nieto</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Meroño</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roig</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Torralba</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reyes</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <article-title>Ontological Semantics for Data Privacy Compliance: The NEURONA Project.</article-title>
          ,
          <source>In AAAI Spring Symposium: Intelligent Information Privacy Management</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Desai</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Narendra</surname>
            ,
            <given-names>N. C.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Singh</surname>
            ,
            <given-names>M. P.</given-names>
          </string-name>
          ,
          <article-title>Checking correctness of business contracts via commitments</article-title>
          ,
          <source>in Proc. AAMAS</source>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>ESTRELLA</given-names>
            <surname>Project</surname>
          </string-name>
          .
          <article-title>The legal knowledge interchange format (LKIF)</article-title>
          .
          <source>Deliverable 4</source>
          .3,
          <string-name>
            <surname>European</surname>
            <given-names>Commission</given-names>
          </string-name>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>ESTRELLA</given-names>
            <surname>Project</surname>
          </string-name>
          .
          <article-title>The reference LKIF inference engine</article-title>
          .
          <source>Deliverable 4</source>
          .3,
          <string-name>
            <surname>European</surname>
            <given-names>Commission</given-names>
          </string-name>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Farrell</surname>
            ,
            <given-names>A. D. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sergot</surname>
            ,
            <given-names>M. J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sallè</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bartolini</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <article-title>Using the event calculus for tracking the normative state of contracts</article-title>
          ,
          <source>International Journal of Cooperative Information Systems</source>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Gangemi</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sagri</surname>
            <given-names>M. T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tiscornia</surname>
            <given-names>D.</given-names>
          </string-name>
          ,
          <article-title>A Constructive Framework for Legal Ontologies</article-title>
          , in Benjamins, R.,
          <string-name>
            <surname>Breuker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A</given-names>
          </string-name>
          . (eds.):
          <article-title>Law and the Semantic Web</article-title>
          ,
          <string-name>
            <surname>LNCS</surname>
          </string-name>
          , Springer,
          <year>2005</year>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <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>
          , in: Rule Interchange and Applications, International Symposium,
          <source>RuleML 2009</source>
          , Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Milosevic</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          <article-title>Dealing with contract violations: formalism and domain specific language</article-title>
          .
          <source>In Proceedings of the Conference on Enterprise Computing EDOC</source>
          <year>2005</year>
          , IEEE Press,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Milosevic</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sadiq</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Compliance checking between business processes and business contracts</article-title>
          .
          <source>In: Proc. EDOC</source>
          <year>2006</year>
          , pp.
          <fpage>221</fpage>
          -
          <lpage>232</lpage>
          . IEEE, Los Alamitos (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tabet</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grosof</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Dean</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (May
          <year>2004</year>
          ).
          <article-title>SWRL: A semantic web rule language combining OWL and RuleML</article-title>
          . Available from http://www.w3.org/Submission/2004/SUBM-SWRL-
          <volume>20040521</volume>
          /.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Kifer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Rule Interchange Format:
          <article-title>The Framework</article-title>
          ,
          <source>Proceedings of the 2nd International Conference on Web Reasoning and Rule Systems, October 31- November 01</source>
          ,
          <year>2008</year>
          , Karlsruhe, Germany.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. OMG:
          <article-title>Semantics of business vocabulary and business rules (SBVR)</article-title>
          . http://www.businessrulesgroup.org/sbvr.shtml,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Palmirani</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Contissa</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rubino</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <source>Fill the Gap in the Legal Knowledge Modelling, Proceedings of the 2009 International Symposium on Rule Interchange and Applications, November 05-07</source>
          ,
          <year>2009</year>
          ,
          <string-name>
            <given-names>Las</given-names>
            <surname>Vegas</surname>
          </string-name>
          , Nevada.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Palmirani</surname>
            ,
            <given-names>M.</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>
          ,
          <string-name>
            <surname>Tabet</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paschke</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <article-title>LegalRuleML: XML-Based Rules</article-title>
          and Norms.; in RuleML America (
          <year>2011</year>
          ),
          <fpage>298</fpage>
          -
          <lpage>312</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Ross</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tû-Tû</surname>
          </string-name>
          ,
          <source>Harvard Law Review</source>
          , vol.
          <volume>70</volume>
          , pp.
          <fpage>812</fpage>
          -
          <lpage>825</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Sartor</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <article-title>Legal Reasoning and Normative Conflicts</article-title>
          ,
          <source>in Reasoning with Inconsistency</source>
          ,
          <year>1991</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Sartor</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <article-title>Understanding and Applying Legal Concepts: An Inquiry on Inferential Meaning</article-title>
          . In: Concepts in Law. Ed. by Jaap C.
          <article-title>Hage and Dietmar von der Pfordten</article-title>
          . Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Schmidt</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bartsch</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Oberhauser</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <article-title>Ontology-Based Representation of Compliance Requirements for Service Processes</article-title>
          .
          <source>In Proceedings of the Workshop on Semantic Business Process and Product Lifecycle Management</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Vitali</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          : Akoma Ntoso Release Notes, http://www.akomantoso.
          <source>org (accessed August 20</source>
          ,
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>