Re: [legalruleml] [XML] source example

[monica.palmirani <monica.palmirani@unibo.it>]

some specific comments in the text.
mp
Il 05/05/2012 00:54, Tara Athan ha scritto:

As was discussed earlier, the next step is to develop a real example from a natural language statement into to XML. This example should contain defeasible rules, but should not require representation of deontic or temporal aspects. I have some suggestions as to how this may be brought about.
1. the deontic and temporal aspects can be "hidden" (for now) in the names of relations and references to sources.

2. confine (for now) our examples to a single authority and timestamp, so that we do not yet tackle cross-references between multiple authorities or across time. The entire knowledgebase could be considered as a contextual statement: As of time YYYY-MM-DDThh:mm:ss some agent of Authority A declares that ( ... ). At this stage we would not address the issue of how to merge knowledgebases from different authorities, or from the same authority but different timestamps.

Example: “Anyone who violates Art. 1 and Art. 5 and Art. 7 and Art. 15 of the ACT 20 shall be punished following the Art. 23 in the Act 30”

can be expressed as

<Rulebase>
<legalruleml:metadata xsi:type="&legalruleml;rulebasemetadata">
<Data>
<legalruleml:authority legalruleml:mode="&legalruleml;inherit" iri="&authorities;A"/>
<legalruleml:timestamp legalruleml:mode="&legalruleml;inherit">2012-04-25T12:00:00-05:00</legalruleml:timestamp>

*** the "timestamp" term recalls a particular legal concept: it is digital signature process put on a digital document that produces legal effects fixed in a certain date and time, I suggest to not use it.

For this reason I propose to use <legalruleml:creationTime> (as the FRBR) for marking up the creation date of an _expression_ of a norm (a legal rule is a particular _expression_ of the norm see standard http://www.ifla.org/files/cataloguing/frbr/frbr_2008.pdf).

Other temporal categories are necessary following the theory of law: inforce, efficacy, applicability
in force: interval of time when the act/article/provision enters into the legal system and it becames legal binding
example: Section 52. The Act shall come into force on 1st May, 2012.

efficacy: interval of time when the judge can apply the norm
example: Section 80. The Act takes effect on 1st January, 2013.

applicability: when the judge apply the norm
example: Section 11. Sections 5 and 9 only of this Act shall apply to emergency events which happened after 1st June, 2013 and they shall apply since 1st June 2015.
(exemption of the taxation for the emergency events, floods, etc.)

For more information see:
www.nicta.com.au/pub?doc=4983
http://www.springerlink.com/content/1323268x7h3qj201/

For these reasons the proposal on the temporal aspetcs (AS FOR THE SOURCES) are the following.
STEP1.
To have a unique block with the NEUTRAL events for avoiding duplication:
<events>
    <event id="e1" value="2012-05-01T01:01:00.0Z"/>
    <event id="e2" value="2013-01-01T01:01:00.0Z"/>
    <event id="e3" value="2013-06-01T01:01:00.0Z"/>
    <event id="e4" value="2015-06-01T01:01:00.0Z"/>
</events>

STEP2.
a block for specifying the intervals and the legal semantic of the intervals.
<times id="t1">
    <time start="#e1"  timeType="inforce"/>
    <time start="#e2" end="#e4" timeType="efficacy"/>
    <time start="#e3" end="#e4" timeType="applicability"/>
</times>

STEP3.
to connect these information to the rules (with the same mechanism of the sources):
   <ruleInfo node=”ruleInfo1” refersTo=”#rule1”>
      <sources>
         <source element="#atom1" refersTo="#ID1"/>
         <source element="#atom2" refersTo="#ID5"/>
         <source element="#atom3" refersTo="#ID7"/>
         <source element="#atom4" refersTo="#ID15"/>
         <source element="#head1" refersTo="#ID23"/>
      </sources>
        <ruleType value="defeasible"
                  refersTo="/ontology/defeasible.owl"/>
        <jurisdiction value=”europe”
                      refersTo="/ontology/europe.owl"/>
        <author value=”governatori” refersTo="#aut2"/>
        <times value=”#t1”/>
        <authority value=”justice”
                   referstTo=”/ontology/ministyOfJustice.owl”/>
   </ruleInfo>

STEP4.
<Implies material="no"  closure="universal" node="rule1">
    <if>
        <And>
            <Atom node="atom1">
            <Rel iri="legalruleml;violates"/>
            <Var>X</Var>
        </Atom>
        <Atom node="atom2">
            <Rel iri="legalruleml;violates"/>
            <Var>X</Var>
        </Atom>
        <Atom node="atom3">
            <Rel iri="legalruleml;violates"/>
            <Var>X</Var>
        </Atom>
        <Atom node="atom4">
            <Rel iri="legalruleml;violates"/>
                <Var>X</Var>
          </Atom>
       </And>
    </if>
    <then node="head1">
        <Atom node="atom5">
            <Rel iri="legalruleml;shall_be_punished_following"/>
            <Var>X</Var>
        </Atom>
    </then>
</Implies>

</Data>
</legalruleml:metadata>
<Implies material="no"
capability="&dfs;defeasible"
closure="universal">
<if>
<And>
<Atom>
<Rel iri="legalruleml;violates"/>
<Var>X</Var>
<Ind iri="&ACT20;art1">
</Atom>
<Atom>
<Rel iri="legalruleml;violates"/>
<Var>X</Var>
<Ind iri="&ACT20;art5">
</Atom>
<Atom>
<Rel iri="legalruleml;violates"/>
<Var>X</Var>
<Ind iri="&ACT20;art7">
</Atom>
<Atom>
<Rel iri="legalruleml;violates"/>
<Var>X</Var>
<Ind iri="&ACT20;art15">
</Atom>
</And>
</if>
</then>
<Atom>
<Rel iri="legalruleml;shall_be_punished_following"/>
<Var>X</Var>
<Ind iri="&ACT30;art23">
</Atom>
</then>
</Implies>
</Rulebase>

This could be compacted with a more specific relation

<Rulebase>
<legalruleml:metadata xsi:type="&legalruleml;rulebasemetadata">
<Data>
<legalruleml:authority legalruleml:mode="&legalruleml;inherit" iri="&authorities;A"/>
<legalruleml:timestamp legalruleml:mode="&legalruleml;inherit">2012-04-25T12:00:00-05:00</legalruleml:timestamp>
</Data>
</legalruleml:metadata>
<Implies material="no"
capability="&dfs;defeasible"
closure="universal">
<if>
<Atom>
<Rel iri="legalruleml;violates_all"/>
<Var>X</Var>
<Ind iri="&ACT20;art1">
<Ind iri="&ACT20;art5">
<Ind iri="&ACT20;art7">
<Ind iri="&ACT20;art15">
</Atom>
</if>
</then>
<Atom>
<Rel iri="legalruleml;shall_be_punished_following"/>
<Var>X</Var>
<Ind iri="&ACT30;art23">
</Atom>
</then>
</Implies>
</Rulebase>

The deontic aspects of the premises are hidden by the references to the articles, which will later be expanded as, perhaps, deontic modal operators applied to descriptions of the actions that are prohibited.

Temporal aspects of the conclusion are hidden in the relation ("shall be..."), to be expanded later as, perhaps, temporal modal operators applied to the conclusion.

More realistic examples are needed to flesh out this approach.

---------------------------------------------------------------------
To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: legalruleml-help@lists.oasis-open.org

.

-- 
===================================
Associate professor of Legal Informatics 
School of Law
Alma Mater Studiorum Università di Bologna 
C.I.R.S.F.I.D. http://www.cirsfid.unibo.it/ 
Palazzo Dal Monte Gaudenzi - Via Galliera, 3 
I - 40121 BOLOGNA (ITALY) 
Tel +39 051 277217 
Fax +39 051 260782 
E-mail  monica.palmirani@unibo.it 
====================================

LA RICERCA C’È E SI VEDE:
5 per mille all'Università di Bologna - C.F.: 80007010376
http://www.unibo.it/Vademecum5permille.htm

Questa informativa è inserita in automatico dal sistema al fine esclusivo della realizzazione dei fini istituzionali dell’ente.