Uploaded image for project: 'OASIS LegalRuleML TC'
  1. OASIS LegalRuleML TC
  2. LEGALRULEML-8

Ambiguity of syntax when an edge is allowed to be either leaf or not skipped

    XMLWordPrintable

    Details

    • Proposal:
      Hide

      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 the two forms in the compact syntax, which would be the same as the normalized serialization.

      Show
      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 the two forms in the compact syntax, which would be the same as the normalized serialization.
    • Resolution:
      Hide

      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)

      Show
      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)

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              taraathan Tara Athan (Inactive)
              Reporter:
              taraathan Tara Athan (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: