Participants:Dieter, Emilia, Doug, Jaceck, Reto, Holger, Adrian, Martin, Titi, Michael, Ioan

Juan, Ruben not active member anymore

D14
Axel and James shall report on deliverable progress

D24.2
Adrian sends email with final deadline for next version

D29
please indicate which sections are written by which author?
please also correct author in activity sheet

section 1.1
delete reference to fensel and bussler paper
introduce different mediation levels: (1) ontological (data), (2) logical (functionality), (3) choreography , (4)

orchestration and then introduce the mediator structure, michael please do so.
michael: delta relation is different for different types (e.g. gg an wg mediator)
dieter: the delta is the same (difference in functionality)
dieter: delta defines the logical theroy expression the difference

section 2
delete second paragraph in 2.1

section 3
focus on logical mediation (functionality) and only refer to oo-mediation
definition of the logical gap between goal and service, subsumption etc. should only be mentioned as special case.

section 4
restructure: makes oo-mediation (oo-mediator) and logical mediation(gg-mediator) using previous described mediators.
emilia: there have to be mentioned the matching notions (e.g. plug-in)
dieter: this special purpose matches should go
--- some discussion around specific matches and generic delate relation
conclusion: funtional mediation should only be described in section 3

4.2.2 should be called communication level mediation

section 5: michael should make a short section adopting it to the new structure.

new version 2nd of September (probably without Emilias comments)

D30
review from wsdl-s group ongoing.
extensions are:
allow pre/post also on interface level
choreography could be added to wsdl-s
attribute model reference should also be allowed for the wsdl service
effects and assumptions are not explicitly differentiated from pre/postcondtions in wsdl-s, but can be done using

non-functional properties.

D31
REST: don't want stateful conversation between 2 resources, however one resource can have a state but
this should not be private to a conversation

WSRF add good practice how to encode state using wsdl (i.e. encoding statfull resources such as shopping carts into seperate web services)

WSRF does not specify control flow over operations.

what are we doing now with wsrf?
...nothing specific to wsrf
Dieter: freeze activity D31.