LegalRuleML Core Specification Version 1.0
Working Draft 23
5 October 2015
Specification URIs
This version:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csd01/legalruleml-core-spec-v1.0-csd01.html (Authoritative)
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csd01/legalruleml-core-spec-v1.0-csd01.pdf
Previous version:
N/A
Latest version:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.pdf
Technical Committee:
OASIS LegalRuleML TC
Chairs:
Monica Palmirani (), CIRSFID, University of Bologna
Guido Governatori (), NICTA
Editors:
Monica Palmirani (), CIRSFID, University of Bologna
Guido Governatori (), NICTA
Tara Athan, (), Individual
Harold Boley (harold.boley[AT]unb.ca), {Gordon:2009go}RuleML, Inc.
Adrian Paschke (paschke[AT]inf.fu-berlin.de), RuleML, Inc.
Adam Wyner (), University of Aberdeen
Abstract:
Summary of the technical purpose of the document
Status:
This document was last revised or approved by the OASIS LegalRuleML TC on the above date. The level of approval is also listed above. Check the “Latest version” location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/legalruleml/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/legalruleml/ipr.php).
Citation format:
When referencing this specification the following citation format should be used:
[LegalRuleML-Core]
LegalRuleML Core Specification Version 1.0. 07 August 2013. OASIS Committee Specification Draft 01. http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csd01/legalruleml-core-spec-v1.0-csd01.html.
Notices
Copyright © OASIS Open 2013. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/policies-guidelines/trademark for above guidance.
Table of Contents
1 Introduction 6
1.1 Terminology 6
1.2 Normative References 6
1.3 Non-Normative References 6
2 Background, Motivation, Principles 7
2.1 Objective 7
2.2 Main Principles 8
2.3 Criteria of Good Language Design 8
3. Vocabulary 10
3.1 General Concepts (non-normative) 10
3.2 Namespaces (normative) 10
3.3 Node Elements (normative) 10
3.4 RuleML Node Elements (normative) 12
3.5 Edge elements (normative) 12
3.6 Attributes on LegalRuleML elements, unqualified (normative) 14
3.7 LegalRuleML Metamodel 14
4 LegalRuleML Functional Requirements (non-normative) 15
4.1 Modelling Legal Norms 15
4.1.1 Defeasibility 16
4.1.2 Constitutive and Prescriptive Norms 1918
4.1.3 Deontic 20
4.1.4 Alternatives 2423
4.2 Metadata of the LegalRuleML Specifications 2726
4.2.1 Sources and Isomorphism 2726
4.2.2 Agent, Figure, Role 2827
4.2.3 Jurisdiction 3029
4.2.4 Authority 3029
4.2.5 Time and Events 3130
4.3 Associations and Context 32
4.3.1 Associations 32
4.3.2 Context 33
5 LegalRuleML XML Design Principles (non-normative) 3635
5.1 XML Elements vs. Attributes 3635
5.2 Node and Edge Element Dichotomy 3635
5.2.1 Node Elements 3635
5.2.2 Edge Elements 3736
5.3 Generic elements 3736
5.4 Serializations 3736
5.4.1 Normalized Serialization 3736
5.4.2 Compact Serialization 3736
5.5 General Design Patterns 3837
5.5.1 Collection Design Pattern 3837
5.6 Specialized Design Patterns 3837
5.6.1 Ordered-Children Design Pattern 3837
5.6.2 Leaf edges 3938
5.6.3 Slot Design Pattern 3938
5.7 CURIES, Relative IRIs and the xsd:ID Datatype 3938
5.8 Relax NG Schema Design 3938
5.8.1 Modules 3938
5.8.2 Relax NG Definition Templates 4039
5.8.3 Drivers 4039
5.9 XSD Schema Derivation 4039
5.9.1 Alternate Drivers 4039
5.9.2 Alternate Relax NG Modules 4039
5.9.3 Conversion using Trang 4140
5.9.4 Post-processing with XSLT 4140
6 LegalRuleML Specifications (normative) 4241
6.1 LegalRuleML RDFS Specifications 4241
6.2 LegalRuleML Main Components 4241
6.3 Subsidiary LegalRuleML Components 4241
7 Comprehensive Examples 4342
Section 29 of the Australian “National Consumer Credit Protection Act 2009” (Act No. 134 of 2009). 4342
7.2 Case 18/96, Bologna Tribunal, Imola Section 4544
7.3 US Code section 504 5049
8 Conformance 5352
9 Bibliogrphy 5453
Acknowledgments 5654
Annex–A - RelaxNG schema - (normative) 5755
Annex–B - XML-schema - (normative) 5957
Annex–C - RDFS and XSLT – (normative) 6058
Annex D – Metamodel Graph – (non-normative) 6159
Annex E – Examples – (non-normative) 6260
Revision History 6361
legalruleml-core-spec-v1.0-csd01 5 October 2015
Standards Track Work Product Copyright © OASIS Open 2015. All Rights Reserved. Page 5 of 65
1 Introduction
Introductory text.
1.1 Terminology
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].
1.2 Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.
[RDF] RDF 1.1 Primer, W3C Working Group Note 25 February 2014 http://www.w3.org/TR/2014/NOTE-rdf11-primer-20140225/
[RDFS] RDF Schema 1.1, W3C Recommendation 25 February 2014 http://www.w3.org/TR/rdf-schema/
[RelaxNG] http://relaxng.org/
[XSD] XML Schema Part 0: Primer Second Edition, W3C Recommendation 28 October 2004 http://www.w3.org/TR/xmlschema-0/
[XML] Extensible Markup Language (XML) 1.0 (Fifth Edition), W3C Recommendation 26 November 2008 http://www.w3.org/TR/2008/REC-xml-20081126/
[RFC3987] http://www.rfc-base.org/rfc-3987.html
[CURI] http://www.w3.org/TR/rdfa-syntax/#s_curies
1.3 Non-Normative References
[ConsumerRuleML] Consumer RuleML Specification 1.02. http://wiki.ruleml.org/index.php/Specification_of_Consumer_RuleML_1.02
[ReactonRuleML] http://reaction.ruleml.org
NOTE: The proper format for citation of technical work produced by an OASIS TC (whether Standards Track or Non-Standards Track) is:
[Citation Label]
Work Product title (italicized). Approval date (DD Month YYYY). OASIS Stage Identifier and Revision Number (e.g., OASIS Committee Specification Draft 01). Principal URI (version-specific URI, e.g., with filename component: somespec-v1.0-csd01.html).
2 Background, Motivation, Principles
Legal texts, e.g. legislation, regulations, contracts, and case law, are the source of norms, guidelines, and rules. As text, it is difficult to exchange specific information content contained in the texts between parties, to search for and extract structured the content from the texts, or to automatically process it further. Legislators, legal practitioners, and business managers are, therefore, impeded from comparing, contrasting, integrating, and reusing the contents of the texts, since any such activities are manual. In the current web-enabled context, where innovative eGovernment and eCommerce applications are increasingly deployed, it has become essential to provide machine-readable forms (generally in XML) of the contents of the text. In providing such forms, the general norms and specific procedural rules in legislative documents, the conditions of services and business rules in contracts, and the information about arguments and interpretation of norms in the judgments for case-law would be amenable to such applications.
The ability to have proper and expressive conceptual, machine-readable models of the various and multifaceted aspects of norms, guidelines, and general legal knowledge is a key factor for the development and deployment of successful applications. The LegalRuleML TC, set up inside of OASIS (www.oasis-open.org), aims to produce a rule interchange language for the legal domain. Using the representation tools, the contents of the legal texts can be structured in a machine-readable format, which then feeds further processes of interchange, comparison, evaluation, and reasoning. The Artificial Intelligence (AI) and Law communities have converged in the last twenty years on modeling legal norms and guidelines using logic and other formal techniques [5]{BenchCapon:2012hu}[Ashley and van Engers, 2011]. Existing methods begin with the analysis of a legal text by a Legal Knowledge Engineer, who scopes the analysis, extracts the norms and guidelines, applies models and a theory within a logical framework, and finally represents the norms using a particular formalism. In the last decade, several Legal XML standards have been proposed to represent legal texts [29]{Lupo:2007ws}[Lupo et al., 2007] with XML-based rules (RuleML, SWRL, RIF, LKIF, etc.) [15, 17]{Gordon:2008vi, Gordon:2009go}[Gordon et al., 2009, Gordon, 2008]. At the same time, the Semantic Web, in particular Legal Ontology research combined with semantic norm extraction based on Natural Language Processing (NLP) [14]{Francesconi:2010vd}[Francesconi et al., 2010], has given a strong impetus to the modelling of legal concepts [7, 9, 10]{Benjamins:2005wp, Boer:2008kh, Breuker:2006ts}[Boer et al., 2008, Benjamins et al., 2005, Breuker et al., 2006]. Based on this, the work of the LegalRuleML Technical Committee will focus on three specific needs:
1 To close the gap between legal texts that are expressed in natural language and semantic norm modeling. This is necessary in order to provide integrated and self-contained representations of legal resources that can be made available on the Web as XML representations [Palmirani et al., 2009] and so foster Semantic Web technologies such as: NLP, Information Retrieval and Extraction (IR/IE), graphical representation, as well as Web ontologies and rules.
2 To provide an expressive XML standard for modeling normative rules that satisfies legal domain requirements. This will enable use of a legal reasoning layer on top of the ontological layer, aligning with the W3C envisioned Semantic Web stack.
3 To apply the Linked Open Data [8]{BernersLee:2010wy}[Berners-Lee, 2010] approach to model raw data in the law (acts, contracts, court files, judgments, etc.) and to extend it to legal concepts and rules along with their functionality and usage. Without rules that apply to legal concepts, legal concepts constitute just a taxonomy [35]{Sartor:2009ev}[Sartor, 2009].
2.1 Objective
The objective of the LegalRuleML TC is to extend RuleML with formal features specific to legal norms, guidelines, policies and reasoning; that is, the TC defines a standard (expressed with XML-schema and Relax NG) that is able to represent the particularities of the legal normative rules with a rich, articulated, and meaningful markup language.
LegalRuleML models:
- defeasibility of rules and defeasible logic;
- deontic operators (e.g., obligations, permissions, prohibitions, rights);
- semantic management of negation;
- temporal management of rules and temporality in rules;
- classification of norms (i.e., constitutive, prescriptive);
- jurisdiction of norms;
- isomorphism between rules and natural language normative provisions;
- identification of parts of the norms (e.g. bearer, conditions);
- authorial tracking of rules.
Some matters are out of the scope of the TC and LegalRuleML such as specifications of core or domain legal ontologies.
2.2 Main Principles
The main principles of LegalRuleML are as follows.
Multiple Semantic Annotations: A legal rule may have multiple semantic annotations, where these annotations represent different legal interpretations. Each such annotation appears in a separate annotation block as internal or external metadata. A range of parameters provide the interpretation with respect to provenance, applicable jurisdiction, logical interpretation of the rule, and others.
Tracking the LegalRuleML Creators: As part of the provenance information, a LegalRuleML document or any of its fragments can be associated with its creators. This is important to establish the authority and trust of the knowledge base and annotations. Among the creators of the document can be the authors of the text, knowledge base, and annotations, as well as the publisher of the document.