forked from sleec/sleec.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
78 lines (64 loc) · 3.98 KB
/
Copy pathindex.html
File metadata and controls
78 lines (64 loc) · 3.98 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<link rel="stylesheet" type="text/css" href="style.css">
<title>SLEEC</title>
<meta name="description" content="Welcome to SLEECVAL">
</head>
<body>
<div id="header" class="center">
<a href="index.html"><img src="images/logo-sleec.png" width="100" height="90"></a>
<h2 style="color:purple; font-size:33px;">SLEECVAL: Specification and Validation of Normative Rules</h2>
</div>
<div id="menue" class="center">
<ul>
<li><a class="menu-link menu-active" href="index.html">Home</a></li>
<li><a class="menu-link" href="download.html">Download</a></li>
<li><a class="menu-link" href="documentation.html">Documentation</a></li>
</ul>
</div>
<div id="content" class="center" style="padding-top:10px;">
<div class="block" id="top-content">
<h2>About</h2>
<p>
SLEECVAL enables specification and validation of non-functional rules with the focus on SLEEC (social, legal, ethical, empathetic, and cultural) principles for autonomous agents. To best of our knowledge, our language and tool are novel in their support to formalise and validate normative rules that address SLEEC concerns. Our vision is to provide an automated framework to specify, validate, and verify that agents follow rules, reporting redundancy and conflicts.
</p>
<div id="image-content">
<div align="center" class="image-text">
<img class="image" src="images/sleec-workflow.png" />
<label class="img-text">SLEECVAL Workflow</label>
</div>
</div>
<div class="syntax" id="syntax-content">
<h2>SLEEC Language Syntax</h2>
<p>
SLEEC syntax is composed of defBlock and ruleBock. Definitions are recursively defined in the SLEEC language through events, measures or constants.
Every event and measure have an eventID and measureID respectively. The ruleBlock consist of triggers, responses, and defeaters. A trigger can combine events
as well as measures and expressions of them with any logical operation. Responses can be timed, and one can define deadlines and timeouts with
responses through within construct. SLEECVAL currently handles
seconds, hours and days as time units in the language . In order to handle the situations where the response event
cannot happen within a required time unit, we include the otherwise construct
to order the events. The concept of defeaters are conducted with unless together with a condition.
</p>
<div align="center" class="image-text">
<img class="image2" src="images/syntax.png" />
<label class="img-text">SLEEC Language Syntax</label>
</div>
</div>
<div class="semantics" id="semantics-content">
<h2>SLEEC Language Semantics into CSP</h2>
<p>
The tock-CSP processes that define the semantics of the rules are computed through a visitor pattern applied to each element of the SLEEC grammar syntax tree, with each SLEEC rule converted to a tock-CSP process. The computation is based on translation rules. Each event and measure is modelled in tock-CSP as a channel with measure types directly converted into existing CSP datatypes, or introduced as a new scalar datatype in CSP.
</p>
<div align="center" class="image-text">
<object data="images/semantics.pdf"
width="800"
height="800">
</object>
<label class="img-text">SLEEC Language Semantics</label>
</div>
</div>
</div>
</div>
</body>
</html>