Re: profilehierarchy

Hi -

carlo beffa wrote:

> Thanks for your interest.
> 
> I undestood that every service profile can be associated with different 
> profile hierarchies, but let me consider the following distributed scenario:
> 
> Service A associated with profileheirarchyX, and found on server I;
> Service B associated with profilehierarchyY and found on server II;
> 
> Through composition a new Service C is created by combining Services A 
> and B and the developer associates its profile with a profileHierarchy Z...
> Does this mean that any reference to profilehierarchies X and Y is lost 
> due to the combination process?

No.

> If I wanted to know which profile hierarchies are associated to services 
> A and B, what would be the best thing to do?

It's a bit roundabout, but the information is there.

As you probably know, in OWL-S composition focuses on processes, not 
services.  So your composition will be centered about a process PC 
(let's say), which is composed of processes PX and PY.  For each process 
there can be a property called "describes" that refers to the 
corresponding service instance.  Then, by visiting each service instance 
you can follow the "presents" property to find the associated profile 
instance (or instances).

Regards,
David Martin

> 
> thanks again
> 
> regards
> 
> Carlo
> 
> */Danilo Ercoli <ercoli@gmail.com>/* wrote:
> 
>     trying to understand the issues behind profilehierarchy ontology. In
>      > CongoBuy profile this is associated with the BookSelling concept.
>     Though
>      > this is a composite service made up of other services, there is no
>      > association of these other services, atomic or composite with the
>      > profilehierarchy ontology. Is this done to
>      > 1. keep the profilehierarchy to the bare minimum required, or
>      > 2. its not envisioned that every OWL-S service atomic or not be
>     associated
>      > with such categorisation, but only the top level service is or
>      > 3. maybe something is missing?
> 
>     Il Profilo di un servizio puo' appartenere ad una o piu' categorie
>     definite in una qualche ontologia (Ho usato il termine categorie, ma
>     alla fine dei conti sono concetti definiti in OWL) . In particolare,
>     nell'ontologia da te citata, sono state definite diverse tipologie di
>     servizio per la vendita on/line. (Ma questo credo ti sia chiaro).
>     Non c'e' collegamento col Service Process, e' quindi solamente il
>     profilo a definire la categoria. Anche se il profilo referenzia un
>     processo composito. Resta il fatto che un servizio puo' pubblicare
>     piu' profili e quindi puo' appartenere a piu'di una categoria in
>     precedenza definite.
> 
>     Spero di esserti stato d'aiuto.
> 
>     Danilo.
> 
>     ----------------------
>     "Every step that you take
>     Could be your biggest mistake
>     It could bend or it could break
>     But that's the risk that you take."
> 
> 
> ------------------------------------------------------------------------
> Does your mail provider give you FREE antivirus protection?
> *Get Yahoo! Mail* 
> <http://us.rd.yahoo.com/mail/uk/taglines/gmail_com/virus/*http://uk.mail.yahoo.com/> 
>

Received on Tuesday, 13 December 2005 23:59:36 UTC