[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [legalruleml] Behavior vs SuborderList
Hi Tara, I agreed it would be redundant to have both Behavior (or Behaviour:-) and SuborderList. Similarly, isn't it redundant to wrap the "content" of PrescriptiveStatement and Penalty with hasTemplate? All the best Guido On 08/12/2012, at 5:34 AM, Tara Athan <taraathan@gmail.com> wrote: > I started experimenting with the syntax we discussed on Wednesday. I am thinking it is redundant to have both <Behavior> and <SuborderList> > > Examples > > <lrml:PrescriptiveStatement> > <lrml:hasTemplate> > <ruleml:Rule> > <ruleml:if>...</ruleml:if> > <ruleml:then> > <lrml:SuborderList> > <ruleml:formula index="1"> ...</ruleml:formula> > <ruleml:formula index="2"> ...</ruleml:formula> > </lrml:SuborderList> > </ruleml:then> > </ruleml:Rule> > </lrml:hasTemplate> > <lrml:PrescriptiveStatement> > > <lrml:Penalty> > <lrml:hasTemplate> > <lrml:SuborderList> > <ruleml:formula index="1"> ...</ruleml:formula> > <ruleml:formula index="2"> ...</ruleml:formula> > </lrml:SuborderList> > </lrml:hasTemplate> > <lrml:PrescriptiveStatement> > > > Let me know what you think. > > Tara > > --------------------------------------------------------------------- > To unsubscribe, e-mail: legalruleml-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: legalruleml-help@lists.oasis-open.org > ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]