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: [OASIS Issue Tracker] (LEGALRULEML-23) SuborderList should not be recursive

    [ https://issues.oasis-open.org/browse/LEGALRULEML-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61202#comment-61202 ] 

Tara Athan commented on LEGALRULEML-23:

The definition of SuborderList specifically says that it is be recursive. If we now are going to disallow that, then the definition should be changed.

Is Now:
SuborderList : a Deontic Specification for a sequence of Deontic Specifications, i.e., Obligations, Prohibitions, Permissions, Rights and/or Suborder Lists. When a SuborderList holds, a Deontic Specification in the SuborderList holds if all Deontic Specifications that precede it in the SuborderList have been violated.
[11/4/15, 7:44:16 AM] Tara Athan: Also SuborderList is not limited to contents which are Deontic Specifications if Deontic Specifications are restricted to be only the simple Obligation, ..., modal formulas, as opposed to compound formulas e.g. And.

> SuborderList should not be recursive
> ------------------------------------
>                 Key: LEGALRULEML-23
>                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-23
>             Project: OASIS LegalRuleML TC
>          Issue Type: Bug
>          Components: RDFS metamodel, Relax NG-modules
>            Reporter: Tara Athan
> The kind of formulas allowed in SuborderList should be made the same as those allowed in Obligation etc.
> Incidentally, there is a typo for the definition of the formula choice pattern for Obligation that inadvertently excludes Or.

This message was sent by Atlassian JIRA

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