See also: IRC log
last minutes approved
<scribe> ACTION: EricP to add text gravy to his annotated Amazon WSDL and put it in Examples document [PENDING] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20061003#action01]
<scribe> ACTION: EricP to get feedback from XMLCore about attrExtensions element [PENDING] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20061003#action02]
Jacek: Next F2F in Athens
... will provide web page for logistics and registration
... 2 telecons cancelled: next week from now and first week in November
... documents published, reviews within your organisations welcome
Eric: apparently no real conflicts
... probably same situation as with WS-Policy
Jacek: possible addition of new media type for SAWSDL, but we don't need it
... who should send Eric's comments to the group?
<ericP> WS-MEX document
Jacek: Francisco Curbera and Jeffrey Schlimmer to be contacted
<JacekK> ACTION: Jacek and Joel to send Paco Curbera and Jeffrey Schlimmer a pointer to the WS-MEX comments from Eric [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20061003#action03]
Jacek: in candidate recommendation we need to verify the spec is implementable
... we need criteria for this
... typically 2 interoperable implementations
... what kinds of implementations are there?
... existing ones: Radian and WSMO Studio
... what do organisations plan to do on this?
Rama: IBM has an editor as well based on WSDL-S
... may be updated to become candidate implementation
<JacekK> ACTION: IBM reps to report on their implementation (plans) [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20061003#action04]
Eric: what is an implementation?
Rama: we need to define specific scenarios
<laurenth> too much echo, i cannot hear, sorry
<Amit-John> Amit and John join-- sorry for the delay
Jacek: Marin Dimitrov was asking for an API
... we could envisage methods for retrieving where a model applies
Rama: tools might differ in many aspects but probably we should define an extension of WSDL4J
John: we can provide our extension
Jacek: API for parsing and creating (WSLD4J extension)
... second level -> GUI tools for annotating (like WSMO Studio and Radian)
... third level: use these annotations for more advanced uses (discovery, etc)
Joel: interoperability should not be a constraint in implementations of higher level functionality
Laurent: some should target higher risks
... such as multiple model references
Jacek: this process should allow us to identify performance and implementation problems
eric: can SPDL be taken as a valid implementation?
<Zakim> ericP, you wanted to say that the ambiguity of finding *best* solutions can be solved by having only one valid solution and to ask if SPDL would count
eric: SPDL can dump all the annotations
Jacek: could be considered as an API implementation
... we should define a format for comparing the outputs of the different APIs
... criteria: parsing API, serializing API (WSLD4J like)
... second level: GUI tools
... not tested on the interoperability level
... third level to be considered as a "bonus" for now
John: we have Radiant and another tool Lumina for discovery
Rama: must implementations be Open Source?
Jacek: no
... we just need reports that demonstrate they work
dicovery tool Lumina: http://lsdis.cs.uga.edu/projects/meteor-s/downloads/Lumina/
Rama: Usage Guide is in 1st public draft, what's the process next?
Jacek: depends on the spec evolution
... there would probably be another draft before the final WG Note
... no need for it to go to LC before it is a WG note, but we can do it
Amit: will the meeting be 1.5 days or 2 days
Jacek: keep it 2 days for now
Amit: APIs, tools, demos for last day