A common approach to the process of reaching agreements is the publication of templates that guide parties to create agreement oers that are then sent for approval to the template publisher. In such scenario, a common issue the template publisher must address is to check whether the agreement oer received is compliant or not with the template. Furthermore, in the latter case, an automated explanation of the reasons of such non-compliance is very appealing. Unfortunately, although there are proposals that deal with checking the compliance, the problem of providing an automated explanation to the non-compliance has not yet been studied in this context. In this paper, we take a subset of the WS-Agreement recommendation as a starting point and we provide a rigorous denition of the explanation for the non-compliance between templates and agreement oers. Furthermore, we propose the use of constraint satisfaction problem (CSP) solvers to implement it and provide a proof-of-concept implementation. The advantage of using CSPs is that it allows expressive service level objectives inside SLAs.
In REF this technique is revised to be applicable in WS-Agreement and a new technique to explain the non-compliance conflicts between templates and agreement offers is introduced.
Explaining the Non-Compliance between Templates and Agreement Offers in WS-Agreement
ICSOC/ServiceWave
Computer Science