[DAML-S] About grounding of services

Hi,

[[Some may say it is too late for such comments but I think the following is 
a serious contribution.]]

Is it right that a concrete SW component may provide several services?  In 
my opinion, yes! (e.g. 
http://www.daml.org/services/daml-s/0.9/Service.daml#provides has no 
cardinality restrictions)

Is that right that service groundings are supported by concrete SW 
components and not by the service itself?  In my opinion, yes!

If we accept my answers to the above questions, it seems to me that we'd 
better to add a new class called SWComponent (or ServiceProvider if it isn't 
confusing) that provides as many services as it likes, merge ServiceProfile 
and Service into one class called Service, and eliminate the properties 
'presentedBy' and 'presents'.  Then, we must redefine 'supports' with 
SWComponent as its domain and ServiceGrounding as its range and add a new 
property called theService/binds/enacts/utilizes/employs with 
ServiceGrounding as its domain and Service as its range.  The attached class 
diagram summarizes this idea putting aside many details, such as classes 
modeling the information about the code base of SWComponent and access rights.

I appreciate your comments in advance.

Regards,

-- Saied Tazari

P.S. This idea and the attached diagram is part of a publication to be
submitted to SWDB (http://swdb.semanticweb.org).  I disclosed it to this
group only as a contribution to DAML-S discussions.