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-8) Ambiguity of syntax when an edge is allowed to be either leaf or not skipped


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

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

    Proposal: 
Option 1. If we keep the syntax as-is, then we need to clarify the semantics of the "mixed case", e.g. ignore the keyref on any edge with children

Option 2. We could make the "compact" syntax more compact by allowing more of these edges to be skippable. Then the compact syntax would only accept
<Context> ...
  <inScope keyref="#stmts1"/>
or
<Context> ...
  <Statements keyref="#stmts1"/>

and these would both be expanded in the normalized serialization to
<Context> ...
  <inScope>
    <Statements keyref="#stmts1"/>

However, if an edge is not skippable, then it should be allowed to have only one of two forms in the compact syntax, which would be the same as the normalized serialization.

> 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 are considered to be required (not skippable) but also may occur as leaf edges. E.g. "inScope" could occur as
> <inScope keyref="#stmts1"/>
> or
> <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)


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