OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalruleml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [XML] source example


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.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]