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-29) First public review - LegalRuleML Core Specification v1.0


     [ https://issues.oasis-open.org/browse/LEGALRULEML-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Monica Palmirani updated LEGALRULEML-29:
----------------------------------------

    Component/s: Official documentation - LegalRuleML Core Specification v1.0 

> First public review - LegalRuleML Core Specification v1.0
> ---------------------------------------------------------
>
>                 Key: LEGALRULEML-29
>                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-29
>             Project: OASIS LegalRuleML TC
>          Issue Type: Task
>          Components: Official documentation - LegalRuleML Core Specification v1.0 
>            Reporter: Monica Palmirani
>            Assignee: Monica Palmirani
>              Labels: editorial, work_required
>
> From: Jim Cabral. ECF OASIS TC.
> The written specification, particularly Sections 4 and 5, are dense with jargon which make it difficult for most people to parse (it was quite challenging for me, at least).  While these sections are important to the specification, they are labeled as non-normative.  Are they truly non-normative?  If so, would they be better moved to an appendix so that the reader or OASIS member considering approval of the specification focuses their attention on the normative sections



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