[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [legalruleml] [XML] source example
Tara, many thanks for your example. Neverhteless I appreciate very much if you start from 2.8isomorphism.001 document. It includes the example mentioned and a more complete scenario (N:M association) that is the add value for LegalRuleML respect pure RuleML. Legal Rules has properties and they are all inter-connected for permitting a "legal validation" and a "legal use". So we need to manage in the same time: temporal aspect (versioning), multiple textual provisions, type of defeasible rules. Take also in serious consideration that we (Guido and I) want strongly separate METADATA on the RULES from the RULES and only occasionally or incidentally we want to permit "on-place" metadata. This is very important in the legal domain for permitting digital signature of some fragment of the XML (metadata and rules separated) for archiving purpuses or for making the rules legal valid. So the following annotation is strongly discouraged, even if possible: <Var>X</Var> <Ind iri="&ACT20;art5"/> We prefer to have association between <Atom> and <Source> in metadata block as specified in my document. Also @capability="&dfs;defeasible" is a property that is better to specify in <metadata> block and not in the place because it could be change over the time. Finally we decied to use <Metadata> name not <Data> in the last TC meeting for not confusing the Data tag with the Metadata tag. 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>
</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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]