Minutes of SWSA Telecon of June 22, 2004

Mark, Tim, Mike Dean, Massimo, Stuart



Options for publishing service descriptions

- internally, - so ask provider
- on web
- with registry



TF -- whoever provides the description should be explicit about who they are by signing
the description in some fashion. (authentication)

- what does it mean for an author to sign some RDF?
SW - XML Dsig 
TF-- How can we lift up from the syntax on this issue?

SW people tend to sign serializations of things. 

T - Provenance on SW in turmoil.

--------------------
M. We need a way to make statements about the support role of the SW, and our requirements for it. 

Tim - distinction between tell to registry and publish in terms of wrappers that can indicate
provenance.

M. use registry model to specify protocol elements, then generalize. 
- each message associated with publishing should be signed
-  service provider or authorized rep should be responsible to post
T.        - do we want to require this?

M. We need to distinguish ads from process models - process models more critically need provenance
info as they are the APIs of the services. 

M. Service should be able to answer how do you get used?
Services should publish or be able to answer queries for their service models.

-----------------------
Massimo

Typical Registry Protocols

- Register
- Login

- Query
- Publish
- update 
- retract

- Subscribe to changes

- Monitoring Queries - tell me all the web services that have a capability, let me know

UDDI now uses WSDL/SOAP