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: Version Control Commit by tara_athan


Author: tara_athan
Date: 2012-12-12 11:39:44 -0500 (Wed, 12 Dec 2012)
New Revision: 44
Web View: https://tools.oasis-open.org/version-control/browse/wsvn/legalruleml/?rev=44&sc=1

Added:
   trunk/examples/draft/ex2.1.2-deontic.lrml
Log:
A demo of the deontic syntax, including

Statements:
<lrml:Statements>
<lrml:ConstitutiveStatement>
<lrml:PrescriptiveStatement>
<lrml:FactualStatement>
<lrml:Penalty>
<lrml:Reparation>

Deontic Operators
<lrml:Obligation>
<lrml:Permission>
<lrml:Prohibition>
<lrml:Right>

as well as
<ruleml:Rule>  (to different content models, tailored to Constitutive and Prescriptive statements)
<lrml:SuborderList>

and renaming
<RuleContext> -> <Context> (so it can be used for interpretations of any kind of statement)

and edges

<lrml:hasStatements>
<lrml:hasStatement>
<lrml:hasTemplate>
<lrml:appliesModality>
<lrml:toStatement>
<ruleml:formula> (new versions for deontic operators and the suborder list)

Concerns include:
1. possible confusion between <LegalStatement> (used to define a local alias for an external legal statement) and <Statement> (used to construct the RuleML expression of such legal statements)

2. need to verify my choice of content model for deontic operators to coordinate with the RuleML expressivity (Horn, disjunctive or first-order logic)



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