[OASIS Issue Tracker] (LEGALRULEML-8) Ambiguity of syntax when an edge is allowed to be either leaf or not skipped

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/LEGALRULEML-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tara Athan updated LEGALRULEML-8:
---------------------------------

    Resolution: 
a) all edges that can be unambiguously reconstructed should be skippable.
b) allow Nodes within Context to have the same content model as that Node element directly under LegalRuleML.
c) compact serialization has either leaf or skipped edge
d) normalized serialization has only stripe and explicit node (no leaf edge)

In order to implement this, I have had to add a few new Node elements:
Actor (has a superclass for Agent and Figure)
Scope (as a superclass for Statements and the various flavors of Statement, within inScope)

> Ambiguity of syntax when an edge is allowed to be either leaf or not skipped
> ----------------------------------------------------------------------------
>
>                 Key: LEGALRULEML-8
>                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-8
>             Project: OASIS LegalRuleML TC
>          Issue Type: Improvement
>          Components: Relax NG-modules
>            Reporter: Tara Athan
>
> Currently there are certain edges that may have content but also may occur as leaf edges. E.g. "inScope" could occur as a leaf edge
> <inScope keyref="#stmts1"/>
> or as an edge with content
> <inScope>
>   <Statements keyref="#stmts2"/>
> </inScope>
> Due to the limitations of XSD, a schema that allows both of these patterns must also allow their combination
> <inScope keyref="#stmts1>
>   <Statements keyref="#stmts2"/>
> </inScope>
> and then it is ambiguous what the scope actually is.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)