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: Deliverables was: [legalruleml] TC goal



I think the track has already  been detailed ...
Deliverables

The LegalRuleML TC will provide XML representations that address the aforementioned requirements and support interchange with the business rule domain.

  1. LegalRuleML semantic level (e.g. temporal dimension) drafts – within six months of the first TC meeting
  2. LegalRuleML logic level (e.g. defeasibility, deontic, and argumentation) drafts – within eight months of the first TC meeting
  3. LegalRuleML integration with business and process rule drafts – within ten months of the first TC meeting
  4. Pilot use cases – within twelve months of the first TC meeting
  5. Tutorials and general documentation – continuously produced and updated during the entire process

cheers
carl

On Wed, Jul 11, 2012 at 2:36 PM, Boley, Harold <Harold.Boley@nrc-cnrc.gc.ca> wrote:
Dear Monica,

You wrote on July 07, 2012
(https://lists.oasis-open.org/archives/legalruleml/201207/msg00003.html):

"In these months we focalized too
much our attention on RuleML compliance rather than to follow the needs
of the legal community."

The TC Charter says (https://www.oasis-open.org/committees/legalruleml/charter.php):

"The goal of the LegalRuleML TC is to extend RuleML [RuleML 2011] with
features specific to the formalisation of norms, guidelines, and legal reasoning."

When one extends a language, there is no problem with compliance,
as new features are added to the language.

In the case of LegalRuleML, the new features must be specific to
the formalization of norms, guidelines, and legal reasoning.

So, in order to be truthful to the goal of the TC, to stay on track,
and to reach (reasonably many of) the planned deliverables in the
remaining months of the TC, we need to check that proposed features are
specific to the formalisation of norms, guidelines, and legal reasoning.

The language is seriously at risk of getting unmanageably big and
very hard to implement (with reasoning engines etc.) in its entirety!

Instead of trying to incorporate ever more features into LegalRuleML, often not
specific to the Legal Domain (or even duplicating features from supporting layers:
https://lists.oasis-open.org/archives/legalruleml/201207/msg00012.html), we need
to focus quickly, leaving features not specific to the formalisation of norms,
guidelines, and legal reasoning to the long-standing partnership with RuleML
(cf. https://lists.oasis-open.org/archives/legalruleml/201207/msg00001.html).

Best,
Harold




--
CEO CheckMi
President BTUSAR Dive Team
Producer Shore Adventure
Cell (usa) (732) 497-CARL {2275}
CarlMattocks@CheckMi.com
Information Risk Checks > Secure Continuous Service


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]