A framework for conflict analysis of normative texts written in controlled natural language

Angelov, Krasimir; Camilleri, John J.; Schneider, Gerardo

doi:10.1016/j.jlap.2013.03.002

Cited by 18 publications

(18 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The use of controlled natural languages (CNL) [219] has been proposed in different works in order to facilitate bridging the gap between the natural language description of the original document and a more formal representation in the form of a formal language [14,89,91,238]. In a legal specification setting, there is initial work in this direction, but we are still far from reaching this goal [86,90,91].…”

Section: Contracts: Normative Documentsmentioning

confidence: 99%

A survey of challenges for runtime verification from advanced application domains (beyond software)

Sánchez

Schneider

Ahrendt

et al. 2019

Form Methods Syst Des

Self Cite

View full text Add to dashboard Cite

Runtime verification is an area of formal methods that studies the dynamic analysis of execution traces against formal specifications. Typically, the two main activities in runtime verification efforts are the process of creating monitors from specifications, and the algorithms for the evaluation of traces against the generated monitors. Other activities involve the instrumentation of the system to generate the trace and the communication between the system under analysis and the monitor.Most of the applications in runtime verification have been focused on the dynamic analysis of software, even though there are many more potential applications to other computational devices and target systems. In this paper we present a collection of challenges for runtime verification extracted from concrete application domains, focusing on the difficulties that must be overcome to tackle these specific challenges. The computational models that characterize these domains require to devise new techniques beyond the current state of the art in runtime verification.

show abstract

Section: Contracts: Normative Documentsmentioning

confidence: 99%

A survey of challenges for runtime verification from advanced application domains (beyond software)

Sánchez

Schneider

Ahrendt

et al. 2019

Form Methods Syst Des

Self Cite

View full text Add to dashboard Cite

show abstract

“…This might be done by means of using controlled natural languages as an intermediate language and by encoding C-O diagrams into GF as has been recently done for the language CL [33].…”

Section: Discussionmentioning

confidence: 99%

Specification and Verification of Normative Texts Using C-O Diagrams

D́ıaz

Cambronero

Martínez

et al. 2014

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

C-O diagrams have been introduced as a means to have a more visual representation of normative texts and electronic contracts, where it is possible to represent the obligations, permissions and prohibitions of the different signatories, as well as the penalties resulting from non-fulfillment of their obligations and prohibitions. In such diagrams we are also able to represent absolute and relative timing constraints. In this paper we present a formal semantics for C-O diagrams based on timed automata extended with information regarding the satisfaction and violation of clauses in order to represent different deontic modalities. As a proof of concept, we apply our approach to two different case studies, where the method presented here has successfully identified problems in the specification.Index Terms-Normative documents, electronic contracts, deontic logic, formal verification, visual models, timed automata, C-O diagrams Ç 1 INTRODUCTION I N software context, the term contract has been traditionally used as a metaphor to represent limited kinds of "agreements" between software elements at different levels of abstraction. The first use of the term in connection with software programming and design was by Meyer [1], in the context of the language Eiffel (programming-by-contracts, or design-by-contract), and relied on Hoare's notion of pre and post-conditions and invariants. Though this paradigm has proven to be useful for developing object oriented systems, it seems to have shortcomings for novel development paradigms such as service-oriented computing and componentbased development. These new applications have a more involved interaction and therefore require a more sophisticated notion of contracts.As a response, behavioral interfaces have been proposed to capture richer properties more than simple pre and postconditions [2]. With this specifications, it is possible to express contracts concerning the history of events, including causality properties. However, this approach is limited when it comes to contracts containing exceptional behavior, since the focus is mainly on the interaction concerning expected (and prohibited) behavior.In the context of service oriented architectures (SOA), there are several service contract specification languages, such as ebXML [3], WSLA [4], and WS-Agreement [5]. These standardized specification languages suffer from one or more of the following problems: they are restricted to bilateral contracts, lack formal semantics (so it is difficult to reason about them), their treatment of functional behavior is rather limited and the sub-languages used to specify security constraints are usually limited to small application-specific domains. The lack of suitable languages for contracts in the context of SOA is a clear conclusion of the survey [6] where a taxonomy is presented.Some researchers have investigated variants of deontic logic [7] to specify different aspects of software systems. Deontic logic is concerned (among other things) with the formalization of moral and legal obligati...

show abstract

“…The language features dynamic vocabulary based on input UML diagrams where vocabulary updates are achieved by re-compiling the grammar using the GF compiler when needed. Angelov et al [1] present a conflict detection framework where Grammatical Framework is used to map the contract language CL into a CNL. Statement modalities, such as obligation, permission and prohibition, are applied to complex actions.…”

Section: Cnl Properties With References To Labelsmentioning

confidence: 99%

Participatory Verification of Railway Infrastructure by Representing Regulations in RailCNL

Luteberget

Camilleri

Johansen

et al. 2017

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. Designs of railway infrastructure (tracks, signalling and control systems, etc.) need to comply with comprehensive sets of regulations describing safety requirements, engineering conventions, and design heuristics. We have previously worked on automating the verification of railway designs against such regulations, and integrated a verification tool based on Datalog reasoning into the CAD tools of railway engineers. This was used in a pilot project at Norconsult AS (formerly Anacon AS). In order to allow railway engineers with limited logic programming experience to participate in the verification process, in this work we introduce a controlled natural language, RailCNL, which is designed as a middle ground between informal regulations and Datalog code. Phrases in RailCNL correspond closely to those in the regulation texts, and can be translated automatically into the input language of the verifier. We demonstrate a prototype system which, upon detecting regulation violations, traces back from errors in the design through the CNL to the marked-up original text, allowing domain experts to examine the correctness of each translation step and better identify sources of errors. We also describe our design methodology, based on CNL best practices and previous experience with creating verification front-end languages.

show abstract

A framework for conflict analysis of normative texts written in controlled natural language

Cited by 18 publications

References 6 publications

A survey of challenges for runtime verification from advanced application domains (beyond software)

A survey of challenges for runtime verification from advanced application domains (beyond software)

Specification and Verification of Normative Texts Using C-O Diagrams

Participatory Verification of Railway Infrastructure by Representing Regulations in RailCNL

Contact Info

Product

Resources

About