WSMO Telcon 07-27-2005
Notes taken by Reto

Present: Dieter, Emilia, Cristina, Uwe, Jacek, Brigitta, Reto, Adrian, Titi, James, Ioan, Matt


Juan, Ruben, Carlso should be moved to non activ member list


Deliverables:

D6.1 Activity Sheet
===================


D24.2 WSMO Grounding
====================
Fix headings of section 2
Make state-of-the-art subsection for 2.1 - 2.3
Example in 2.7 should be after Definition 2.7
Mention D16.1 for WSML to XML
  ==> new version 19 Aug 2005


D29 WSMO Mediators
==================
Introduction assigned to Adrian
 - better name for ontological relations in table 1?!
	==> call delta relation
	==> given example: strengthening, weakening
 - WW mediator needs another box: protocol mediation to clearly distinguish WG from WW

Section XXX
 - Introduce subsections at the beginning

Section 2
 - delete mediationServiceCapability as it is already in hasMediationService
 - remove usedMappings, could be a parameter of the goal capability

Section 3 and elsewhere
 - ontological relation is renamed to delta relation

Section 4
 - move 4.3.1 to GG Mediator (Section 3). This is weakening of different goals!
 - add protocol relation

Section 5
 - leave Guarded Transisiton and weaken the content: WW mediation for choreography


==> new version 5 Aug 2005


Working Draft: Aligning WSMO and WSDL-S by Jacek
================================================

 - Missing part depends on data grounding
 - WSMO does not have operations
	==> Without these challenges pretty straight forward to combine WSMO with WSDL-S

 - Needs to be checked with WSDL-S people
 - Assumption: WSMO service == collection of WSDL operations

Dieter: 
	2nd paragraph in Introduction - upper case for Section and mention Section 3 explicitely
	Update and make it a deliverable D30 - deadline: 5 Aug 2005 
	Make the same for WSRF to get WSRF-S - deadline: 5 Aug 2005


James, Jacek write mail explaining missmatch WMSO Choreography updates and WSDL operations
	Make this clear in new version of D14 (5 Aug 2005)


Talk: Semantic Web Services Roadmap by Dieter
=============================================

We should not be to specific about Semantic Web and Web service but broader to target SOA in general.

Call Triple Space TripleS in future?

SESA := Semantic Enables Service Architecture (Technical Kernel as basis of SemGrid or UbiServ)

Compare WSMX pricture with OGSA (job for wSMX WG).

ASM (James): Execution Engine is ongoing work... depends also on D14 and wsmo4j extensions.

Discuss the presence of Semantic Repository and Triple Space. Shouldnt SemRep not be part of TripleS? (job for WSMX WG)

Clarification about location and organisation of WSMX components (job for WSMX WG)