[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: --------------------------------- Component/s: Examples-draft > 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: Examples-approved, Examples-draft, Relax NG-driver, Relax NG-modules, XSD schema, XSLT for post-processing of schemas > Reporter: Tara Athan > Assignee: 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]