Minutes of SWSA Telecon March 16, 2004

Massimo P., Mike D., Mark B., Stuart W., Amit Seth, Mike Huhns, Andi E

F2F May 23-4 (Sun, Mon) with DAML PI meeting 25-6 


MP: recapping last week: how to get to a reqs doc. MP sent out first cut at
Discovery last night.

Stuart took responsibility for Negotiation

AS: 4 dimensions of semantic specification
input/output, function semantics, qos, execution time semantics. 
On QoS, student has paper and there is 
on line web journal paper. (will email ptr)

Their work on QoS is coordinated with IBM.

MB: do you have an ontology for QoS?

AS: we are building one, will be done soon. 

AS: We also have WSDL-S - semantic description of WSDL, we annotate wrt this
ontology.  have tool for annotating web services. Accepted into Web
conference, Eclipse toolkit available in May.  Use of Java Metadata for
annotating code. Looking at QoS for composite processes.

QoS Issues addressed: cost, time, reliability, domain specific measure of 
quality of work performed. 

MB: Sounds like you will be able to contribute to many sections of this
doc. QoS in Negotiation and contracting will be harder than in some other sections. 

AS: Yes, QoS negotiation is hard when there are tradeoffs across multiple
dimensions. That is where it becomes quite interesting. We have not gone
very far into this yet.

MP: One issue in my draft is QoS. It appears in capability and matching both. Amit,
feel free to add to this.

AS: By Friday, I will send to this list a tech report on QoS issues. Plus a
use case contribution focused on QoS. At that point Massimo, you can make
the connection ot your part. Journal of Web semantics paper - pointer to that. 
Semantic Annotation - WWW paper in Sem Web Track. Separately write a page or so on QoS for the reqs document. 

MB: Amit, will you be able to attend F2F? AS: Probably yes. 
AS: I'm doing a tutorial at WWW with Paco Curbera on WS and Semantic Web, and QoS. 
Tutorial is on the first day of the conference. 

MH: Will be able to make at least the first day of F2F

MB: My conclusion is that we should add a 'cross-cutting requirements'
section to the document (two sub sections) to discuss QoS, Security and Privacy. 

Writing Assignments: 

By end of the week if possible, each should draft a page or two of
bulletized requirements in the topic area agreed to during the discussion:

MarkB will add a section on 'general requirements' to cover 
Quality of service (Amit Sheth)
Privacy and Security (Norman Sadeh and Tim Finin)

Stuart will work on Process Enactment

Massimo has generated stuff for Discovery

Tim and Norman will do P&S. 

MB will work on Community Serivces Section.

(MB will be in Palo Alto next week. Will try to call in, but Chris B should lead.)