[ https://issues.oasis-open.org/browse/LEGALRULEML-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tara Athan updated LEGALRULEML-17:
----------------------------------
Component/s: Examples-approved
Examples-draft
XSLT compactifier
XSLT for post-processing of schemas
XSLT for postprocessing generated instances
XSLT normalizer
> <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: Examples-approved, Examples-draft, Relax NG-modules, XSD schema, XSLT compactifier, XSLT for post-processing of schemas, XSLT for postprocessing generated instances, XSLT normalizer
> 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)
