---------------------------------------------
Notes for the WSMO Phone Conference
on February 2, 2005
---------------------------------------------

Present: john, dieter, jos, emilia, cristina, doug, martin, jacek, reto, adrian, axel, livia, brahmananda, james, laurentiu, michael st.

Notes taken by Reto


Next meeting 12am GMT


Deliverables
------------

Include D15 in activity sheet
Change names of activity sheets, they all have the same name
Make sure that the links are right!
Jos delete acknowledgement in template
Jos fix acknowledgement in "Persistent URIs for WSMO and WSML deliverables"


* D3.1
 - next version friday next week
 - copy mission statement in the introduction!
 
 john:
 - very ontology focused
 - more motivation to use WSMO: more about goals, mediators...
 - provides a section about motivation

 jos:
 - WSMO is not about implementation, but only about interfaces

 dieter:
 - next version contains example of choreography, not orchestration

 axel:
 - put the full example in the appendix to see the whole picture

 jos:
 - textual description about external ontologies and link
 - remove out-dated deliverables in Sec. 6 ==> Jos sents a list with deliverables to remove


* D14
 - next version, next friday
 - add cristina in author list 
 - include shared variables in D2: Titi, Holger / publish it!
 - latest version of this document is included in the WSMO document for w3c submission

 jos:
 - what language to use in listings ==> WSML
 - semantic link between choreography and capability
	==> some words about that in the introduction

 john:
 - why state signature? what role? same for state and guarded transitions...
 - reasons for these elements in section 1

 jos:
 - mode is a nfp, so no additional concept needed (nfp are extensible)
 - semantics of guarded transition
	==> same as ASM

 axel:
 - proposal for semantics of attribute value changes (?)
 
 jos:
 - how is capability realized in the choreography? Add info to section 5!

 cristina:
 - Listing 8 second transition if and then contain same memberOf statement; not necessary!

 dieter:
 - reservation vs. processed_reservation concepts, this would avoid infinit triggering. 
	Is however not a problem to be addressed in specification of service
 - shared variables YES 

 - result is a keyword only in postcondition expressions ==> offline discussion

 jos:
 - mode: what? relation to transition rules
 - invocation mechanism does not imply message exchange, also used in Triple Space

 jacek:
 - invocation mechanism -> read/write (grounding D24)

 jos:
 - prs is a prefix for a mediator, mediators do not contain concept
	==> jos provides a new listing 3

 
* D15
 - new version: friday in two weeks

 jos:
 - use stylesheet of choreography for listings
 - signatures same comments as for choreography

 - ALWAYS use mediators to invoke goals
 - invocation of a mediator is not defined yet; this is a mediator issue


* D24.1
 - new deadline in a month

 jos:
 - title? WSMO and/or WSMX?

 jacek:
 - Title changed to: "Aligning WSMO with existing Web services specifications"
 - Grounding more important to WSMO, thus seperate deliverable

 dieter:
 - add rational and link to D24.2
 - more arguments for statements
 - rational for end of 1.1
 
 jos:
 - conclusion should be self-contained ==> will certainly be extended, after the rest will finished
 	==> remove conclusion or make it understandable


* D24.2
 - next version should contain both approaches: titi/jacek and matt/adrian
 - next version will contain a default grounding (cf. below)
 - make human operator intervention clearer
 - new deadline in two weeks

 jos:
 - grounding WSMO or WSML ontologies? goal to ground WSML ontologies

 axel:
 - this grounding is not a mediator but an adapter (special type of mediator?)
 
 jacek:
 - mediators are WSML to WSML; here we deal with WSML to WSDL, an element that wSMO does not know!

 john:
 - represent grounding in WSML. default grounding from WSML to XML needed

 jos:
 - graphic to show interlation of elements between WSML and WSDL

 axel:
 - how to bind WSDL to choreography
	==> still an open issue, and subject to further research


Discussions
-----------

* W3C submission documents
 - State: WSMO aligned with D2, WSML with D16.1 refinements till end of the week (for WSMX as well)
 - Primer aligned with WSMO Primer
 - Avoid links to WSMO deliverables to have self-contained document. 
	Exception: Refer to WSMO deliverable for discovery D5.1 and comparison document D4.1


* The WSMO deliverables directory structure
 - Use "TR" instead of year, files stay as they are and are redirected
 - Titi contacts technicians to set up new delivery structure
 - Editors responsible for linking their own deliverables


* Capitalization of terms: web services, Web services, or Web Services
 - capitalize Web or everything?
 - Web, Semantic Web, service