OASIS LegalRuleML TC

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

Hi All, In order to finish the LegalRuleML tutorial in the remaining days before the RuleML-2012 Symposium, we propose to use only core material that has already found sufficient consensus in the TC. Below please find a feasible proposed structure of the LegalRuleML tutorial ("@@@" indicates open parts). We suggest today's Telecon AGENDA be devoted entirely to the tutorial. Best, Harold and Adrian ----------------------------------- * Intro - OASIS context of TC . LegalXML . Akoma Ntoso - Example bridging from RuleML to LegalRuleML * Selected consensual parts of the LegalRuleML Metamodel - upper-subclass.pdf/.rdfs - upper-properties.pdf/.rdfs (- optionally metadata.pdf/.rdfs with TimeInstant connection to Reaction RuleML) * Use Cases - Use Case 1: "Complaint @@@" . English Sources (. Controlled English in ACE?) . Discuss corresponding notions of selected Metamodel parts . Association between Rules and Sources - Use Case 2: "@@@" (- optionally Use Case 3: "SLA @@@") * Conclusions, Future Plans, and Call for Contributions

Dear Harold, my comments on the Agenda of the LegalRuleML Tutorial for favoring the meeting of today. Best, Monica Il 22/08/2012 19:16, Boley, Harold ha scritto: Hi All, In order to finish the LegalRuleML tutorial in the remaining days before the RuleML-2012 Symposium, we propose to use only core material that has already found sufficient consensus in the TC. Below please find a feasible proposed structure of the LegalRuleML tutorial ("@@@" indicates open parts). We suggest today's Telecon AGENDA be devoted entirely to the tutorial. Best, Harold and Adrian ----------------------------------- * Intro - OASIS context of TC . LegalXML . Akoma Ntoso *** Akoma Ntoso is not at all part of the LegalRuleML - Example bridging from RuleML to LegalRuleML * Selected consensual parts of the LegalRuleML Metamodel - upper-subclass.pdf/.rdfs - upper-properties.pdf/.rdfs (- optionally metadata.pdf/.rdfs with TimeInstant connection to Reaction RuleML) *** sources&references (isomorphism) *** defesibility * Use Cases - Use Case 1: "Complaint @@@" . English Sources (. Controlled English in ACE?) *** Controlled English is not in LegalRuleML task. The legal domain has strong difficulties to reduce the normative statement in ACE (e.g. theory of interpretation, critic to the reductionism theory, critic to the textualism theory, etc.) Latin language in particular. . Discuss corresponding notions of selected Metamodel parts . Association between Rules and Sources - Use Case 2: "@@@" *** sec. 504 US, 17 title is a good example of temporal needs/requirements (- optionally Use Case 3: "SLA @@@") * Conclusions, Future Plans, and Call for Contributions -- =================================== Associate professor of Legal Informatics School of Law Alma Mater Studiorum Università di Bologna C.I.R.S.F.I.D. http://www.cirsfid.unibo.it/ Palazzo Dal Monte Gaudenzi - Via Galliera, 3 I - 40121 BOLOGNA (ITALY) Tel +39 051 277217 Fax +39 051 260782 E-mail monica.palmirani@unibo.it ====================================

Hi All, > - Example bridging from RuleML to LegalRuleML (to be suggested by Harold, Adrian) Please find it below in the form of English sources for one slide of the Intro. Best, Harold and Adrian ------------------------------------------ Deliberation RuleML http://ruleml.org/papers/Primer/RuleMLPrimer2012-08-09/RuleMLPrimer-p10-2012-08-09.html "A customer gets a discount of 7.5 percent on the purchase of a product if the customer is premium and the product is luxury." Reaction RuleML "A customer gets a discount of 7.5 percent to be deducted from each purchase of a product, starting on July 1st, 2012 and ending on December 31st, 2012, if the customer is premium and the product is luxury." LegalRuleML "RuleML Inc discount contract: According to this contract, which is applicable in all member states of the European Union, a RuleML Inc customer gets a discount of 7.5 percent to be deducted from each purchase of a RuleML Inc product starting on July 1st, 2012 and ending on December 31st, 2012 if the customer is premium and the product is luxury."