WSMO telephone conference notes 20041124 

- notes: Michael Stollberg 

- participants: 
John Domingue (Chair)
Christina Feier (DERI Innsbruck)
Douglas Foxvog (DERI Galway) 
Armin Haller (DERI Galway) 
Uwe Keller (DERI Innsbruck) 
Edward Kilgarriff (DERI Galway) 
Jacek Kopecky (DERI Innsbruck) 
Rubén Lara (DERI Innsbruck) 
Holger Lausen (DERI Innsbruck) 
Francisco Jose Martin-Recuerda Moyano (DERI Innsbruck) 
Eyal Oren (DERI Galway) 
Axel Polleres (DERI Innsbruck) 
Dumitru Roman (DERI Innsbruck) 
Michael Stollberg (DERI Innsbruck) 

- progress report / deliverables: 


D2: 
- goals and old mediators are re-introduced 
- John: 2 points which makes WSMO strong: 
	* decouple requests & services 
	* mediate between requester & provider for service usage 
- john: what should be changed in WSMO D2 

JOHN / TITI, PLEASE ADD:  

	* goal-based invocation 
	* inputs and outputs for Goals AND Services (although different notions) 

- do we need inputs and outputs in service descriptions? 
	* what is the relation to pre- / postconditions 
	* when / where is it actually used, i.e. relation between capability and choregraphy 

	.. decision on this delayed. 
- understanding capability <-> interface: 
	* capability is an abstraction of interaction interface 
	* basically, a capability specifies "if you give me that input, I will provide you this functionality" 
	* a interaction interface / choreography specifies how to interact with a service to achieve / consume the functionality 
	* preconditions define all required input along with constraints; the real input are located in the interaction interface / choreography 

- mediators will need a complete revision when the conceptual model / components of WSMO 1.1 are finished 

- Michael St.: adopt model from Conceptual Model of Chris Priest in identifying (a) description notions and (b) a generic SWS Usage process that specifies when which description notions are used or achieved as a result of a Mechanism; this might help to identify and specify what kind of description notions are needed, and what they have to look like 

- Jacek: rename "hasImportedOntologies" & "hasUsedMediators" to "importedOntologies" & "usedMediators" -- will be done by Titi  

- "service" vs. "web services": there should be a paragraph that clearly defines that WSMO talks about Web Services; .. titi takes care 

- what are the real top level notions of WSMO? Answer: Ontologies, Goals, Services, Mediators 

- proposal Michael Stollberg: according to previous comment, introduce 2 different aspects in WSMO; (1) WSMO Components which specify descriptions of  WSMO top level notions (Ontologies, Goals, Services, Mediators) as existing, and (2) WSMO Elements that are specified on basis of a generic Service Usage Process, e.g. Service Request, Service Contract, Service usage Result, etc. This would provide a 2-dimensional description of SWS, which follows the conceptual approach of Chris Priest's conceptual architecture    

- status / next steps: John will contact Dieter on proposed updates 
 

D3.2: is final now 


D3.3: 

- remarks John: 
	* move ontology listings to appendix to get to the interesting stuff as early as possible 
	* differentiate between Goals and Goal Instances / concrete Golas -- problem: this use case is on WSMO 1.0 

- new status: pending 

D3.4: 
- no progress, delayed due to other responsibilities of authors 
- status: pending 


D14: not discussed here, as version is not completed / ready for discussion 

next telephone conference: next week, same time