LegalRuleML Core Specification Version 1.0
Committee Specification Draft 01 /
Public Review Draft 01
28 October 2016
Specification URIs
This version:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/legalruleml-core-spec-v1.0-csprd01.html (Authoritative)
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/legalruleml-core-spec-v1.0-csprd01.docx
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/legalruleml-core-spec-v1.0-csprd01.pdf
Previous version:
N/A
Latest version:
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html (Authoritative)
http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.docx
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 (monica.palmirani@unibo.it), CIRSFID, University of Bologna
Guido Governatori (Guido.Governatori@data61.csiro.au), Commonwealth Scientific and Industrial Research Organisation, Data61
Editors:
Monica Palmirani (monica.palmirani@unibo.it), CIRSFID, University of Bologna
Guido Governatori (Guido.Governatori@data61.csiro.au), Commonwealth Scientific and Industrial Research Organisation, Data61
Tara Athan (taraathan@gmail.com), Individual
Harold Boley (harold.boley@unb.ca), RuleML, Inc.
Adrian Paschke (paschke@inf.fu-berlin.de), RuleML, Inc.
Adam Wyner (azwyner@abdn.ac.uk), University of Aberdeen
Additional artifacts:
This prose specification is one component of a Work Product that also includes:
XSD schemas: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/xsd-schema/
RelaxNG schemas: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/relaxng/
XSLT transformations: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/xslt/
XSD-conversion drivers: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/generation/
RDFS metamodel: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/rdfs/
Metamodel diagrams: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/diagrams/
Examples: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/examples/
Declared XML namespaces:
http://docs.oasis-open.org/legalruleml/ns/v1.0/
http://docs.oasis-open.org/legalruleml/ns/mm/v1.0/
Abstract:
The objective of this document is to extend RuleML with formal features specific to legal norms, guidelines, policies and reasoning. It defines a specification (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.
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. Any other numbered Versions and other technical work produced by the Technical Committee (TC) are listed at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=legalruleml#technical.
TC members should send comments on this specification to the TC’s email list. Others should send comments to the TC’s public comment list, after subscribing to it by following the instructions at the “Send A Comment” button on the TC’s web page at https://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 TC’s web page (https://www.oasis-open.org/committees/legalruleml/ipr.php).
Note that any machine-readable content (aka Computer Language Definitions) declared Normative for this Work Product is provided in separate plain text files. In the event of a discrepancy between any such plain text file and display content in the Work Product's prose narrative document(s), the content in the separate plain text file prevails.
Citation format:
When referencing this specification the following citation format should be used:
[LegalRuleML-Core-v1.0]
LegalRuleML Core Specification Version 1.0. Edited by Monica Palmirani, Guido Governatori, Tara Athan, Harold Boley, Adrian Paschke, and Adam Wyner . 28 October 2016. OASIS Committee Specification Draft 01 / Public Review Draft 01. http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/csprd01/legalruleml-core-spec-v1.0-csprd01.html. Latest version: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html.
Notices
Copyright © OASIS Open 2016. 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 https://www.oasis-open.org/policies-guidelines/trademark for above guidance.
Table of Contents
Appendix A.Introduction 5
A.1Terminology 6
A.2Normative References 7
A.3Non-Normative References 8
A.4Typographical Conventions 9
Appendix B.Background, Motivation, Principles 10
B.1Motivation 11
B.2Objective 12
B.3Main Principles 13
B.4Criteria of Good Language Design 14
Appendix C.Vocabulary 15
C.1Scope of the vocabulary (non-normative) 16
C.2General Concepts (non-normative) 17
C.3Namespaces (normative) 18
C.4Node Elements (normative) 19
C.5RuleML Node Elements (normative) 21
C.6Edge elements (normative) 22
C.7Attributes on LegalRuleML elements, unqualified (normative) 24
C.8Non-skippable Edges (normative) 25
C.9LegalRuleML Metamodel (normative) 26
Appendix D.LegalRuleML Functional Requirements (non-normative) 27
D.1Functionalities 28
D.2Modeling Legal Norms 29
D.2.1Defeasibility 30
D.2.2Constitutive and Prescriptive Norms 33
D.2.3Deontic 35
D.2.3.1Modal and Deontic Operators 36
D.2.3.2Violation, Suborder, Penalty and Reparation 38
D.2.4Alternatives 40
D.3Metadata of the LegalRuleML Specifications 43
D.3.1Sources and Isomorphism 44
D.3.2Agent, Figure, Role 47
D.3.3Jurisdiction 49
D.3.4Authority 50
D.3.4.1Time and Events 51
D.4Associations and Context 54
D.4.1Associations 55
D.4.2Context 57
Appendix E.LegalRuleML XML Design Principles (non-normative) 59
E.1Design Principles 60
E.2XML Elements vs. Attributes 61
E.3LegalRuleML Syntactic Requirements 62
E.4Syntactic Objectives 63
E.5Node and Edge Element Dichotomy 64
E.5.1Node Elements 65
E.5.1.1Classification of Node Elements 66
E.5.2Edge Elements 68
E.5.2.1Classifications of Edge Elements 69
E.6Generic Node elements 71
E.7Serializations 72
E.7.1Normalized Serialization 73
E.7.2Compact Serialization 74
E.8Basic Dialect 75
E.9General Design Patterns 76
E.9.1Collection Design Pattern 77
E.9.2Recursive Element Pattern 78
E.9.3Marker Interface Pattern 79
E.10Specialized Design Patterns 80
E.10.1Ordered-Children Design Pattern 81
E.10.2Leaf Edges 82
E.10.3Branch Edges 83
E.10.4Leaf/Branch Edges 84
E.10.5Slot Design Pattern 85
E.11CURIES, Relative IRIs and the xsd:ID Datatype 86
E.12Distributed Syntax 87
E.13Metamodel Refinement 88
E.14Annotations - Comment and Paraphrase 89
E.15Identifiers - @xml:id and @iri 90
E.16Order of Elements within a LegalRuleML Document 91
E.17Relax NG Schema Design 92
E.17.1Modules 93
E.17.2Suites and Drivers 94
E.17.2.1Core Suites 95
E.17.2.2Basic, Compact, and Normal Suites 96
E.17.2.3LegalRuleML Drivers 97
E.18XSD Schema Derivation 98
E.18.1XSD-Conversion Drivers 99
E.18.2Conversion using Trang 100
E.18.3Post-processing with XSLT 101
E.19Differences between Relax NG and XSD Schemas 102
E.19.1@xsi:type 103
E.19.2@xsi:schemaLocation 104
E.19.3@xsi:nil and @xsi:noNamespaceSchemaLocation 105
E.19.4@xml:base 106
E.19.5@xml:id 107
E.19.6@key/@keyref 108
E.19.7Document Root Element 109
E.19.8Leaf/Branch Type Edges 110
E.20Prefix Mapping XSLT Transformation 111
E.21Validating XSLT Transformations 112
Appendix F.Comprehensive Examples 113
F.1 Section 29 of the Australian “National Consumer Credit Protection Act 2009” (Act No. 134 of 2009). 114
F.2Case 18/96, Bologna Tribunal, Imola Section 117
F.3US Code section 504 122
Appendix G.Conformance 125
Appendix H.Bibliography 126
Appendix I.Acknowledgments 128
Appendix J.RelaxNG schema - (normative) 129
Appendix K.XML-schema - (normative) 130
Appendix L.RDFS and XSLT – (normative) 131
Appendix M.Metamodel Graph – (non-normative) 132
Appendix N.Examples – (non-normative) 133
Appendix O.Example Fragments in Normal Form– (non-normative) 134
Appendix P.Acronyms (non normative) 145
Appendix Q.Generation – (non-normative) 146
Appendix R.Revision History 147
Share with your friends: |