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-18) Eliminate unnecessary leaf edge forms


    [ https://issues.oasis-open.org/browse/LEGALRULEML-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61113#comment-61113 ] 

Tara Athan commented on LEGALRULEML-18:
---------------------------------------

Revision: It has been determined, through Issue #20, that certain edges should occur only in leaf from. This includes the "applies" edges, and similar edges, where the object of the relationship can be declared in a collection, and thus referenced through keyref, rather than being defined "in place" e.g. in a context. Therefore, the only edges that now fall within the scope of Issue #18 are the "has" edges, e.g. "hasLegalSources", ..., as these are the only remaining skippable edges in the lrml namespace.

> Eliminate unnecessary leaf edge forms
> -------------------------------------
>
>                 Key: LEGALRULEML-18
>                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-18
>             Project: OASIS LegalRuleML TC
>          Issue Type: Improvement
>          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
>              Labels: Usability
>
> In the compact serialization there are multiple ways to represent certain cases of empty Nodes - as the Node, with no edge stripe, and as the edge in leaf form (no children). For those cases where there is a unique type of child Node for this edge, the leaf edge is redundant. That is, in all cases it could be converted to the stripe-skipped Node form without loss of information. For parsimony, it would be better to have only one respresentation.



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