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-17) <lrml:inScope> should not have content, only attributes


Tara Athan created LEGALRULEML-17:
-------------------------------------

             Summary: <lrml:inScope>  should not have content, only attributes
                 Key: LEGALRULEML-17
                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-17
             Project: OASIS LegalRuleML TC
          Issue Type: Bug
          Components: Relax NG-modules, XSD schema
            Reporter: Tara Athan
            Assignee: Tara Athan


Currently the <inScope> element is allowed to have content which is either <lrml:Statements> or one of the LegalRuleML Statement elements. The original intent was that the Node element would carry a @keyref attribute to refer to the Statement(s) definition that occurs in the proper place. However, it would be necessary to define a different element type to enforce that only empty Statement(s) appear within <inScope>. But there is no usecase for this empty element that could not be handled just as well by an empty <inScope> tag with @keyref attribute.



--
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]