W3C home > Mailing lists > Public > www-ws@w3.org > September 2003

Re: Grounding puzzle

From: Mithun Sheshagiri <mits1@csee.umbc.edu>
Date: Fri, 19 Sep 2003 17:16:51 -0400 (EDT)
To: David Martin <martin@AI.SRI.COM>
Cc: Drew McDermott <drew.mcdermott@yale.edu>, <www-ws@w3.org>
Message-ID: <Pine.LNX.4.30.0309191715010.5179-100000@linuxserver1.cs.umbc.edu>

Sorry when I said profile ontology I was talking about a profile ontology
that is used to capture a person's profile and not the daml-s profile.

mithun

mithun

On Fri, 19 Sep 2003, David Martin wrote:

> Thanks, Mithun.
>
> I think you have given an excellent answer, but I would just clarify 2
> things ...
>
> Mithun Sheshagiri wrote:
>
> >
> >
> > On Fri, 19 Sep 2003, Drew McDermott wrote:
> >
> >
> >>
> >>Suppose there is a web service that works like this:
> >>
> >>  For all person, residing in the U.S., if you send
> >>              social_sec_no(person) [a string of 9 digits]
> >>  to this service, it will return
> >>              telephone_num(person) [a string of 10 digits]
> >>
> >>Between WSDL, the DAML-S process, and the grounding, how does this
> >>fact get represented?
> >
> > The DAML-S atomic process would be the following (I assume here that the
> > output is unConditional):
> >
> > AtomicProcess: TelLookUp
> > input: sSN
> > unConditionalOutput: phoneNumber
> >
> > sSN is a property that points to a concept called Social_sec_no. This
> > concept is defined in a profile ontology which also defines the datatype
> > for this concept (string of 9 digits). The property that associates
> > Social_sec_no to the upper concept Person is hasSSN
>
> There's no reason why the Social Security number concept should be part
> of the service's profile.  It can be defined anywhere on the semantic
> Web, and can then of course be referenced by both the profile and the
> process model.  Similarly for the phone number concept, just below.
>
> >
> > Similarly, phoneNumber points to a concept defined in the profile
> > ontology, Telephone_num. The corresponding property is hasTelNum
> >
> > The grounding would point a WSDL description that uses the
> > Request-Response transport primitive. Part of the WSDL description would
> > look like this.
> > message definition:
> > <message name="SSN_Input">
> >       <part name="sSN" daml-property="profile:#hasSSN"/>
> > </message>
> >
> > <message name="phoneNum_Output">
> >       <part name="phoneNum" daml-property="profile:#hasTelNum"/>
> > </message>
>
> Since what's grounded is an atomic process, it would be more correct to
> reference properties that are defined in the process model for the
> service, e.g.:
>
>   <part name="sSN" daml-property="MyServiceProcessModel:#hasSSN"/>
>
> Regards,
>
> David Martin
>
> >
> > port desription:
> > <portType name="TelLookUp_port">
> > <operation name="TelLookUp_operation" daml-s-process="BT:#TelLookUp">
> >         <input message="SSN_Input"/>
> >         <output message="phoneNum_Output"/>
> > </operation>
> > </portType>
> >
> > Now the daml-property in the message description would be used by a
> > specialized DAML sensitive WSDL processor to pick datatype information
> > from the profile ontology.
> >
> > I hope this is what you were looking for.
> >
> > mithun
> >
> >>I realize there's an issue about representing the quantifier in the
> >>first place, but that's not my main concern.  My main concern is
> >>_where_ the various "pieces" of the fact reside.
> >>
> >>--
> >>                                             -- Drew McDermott
> >>                                                Yale University CS Dept.
> >>
> >>
> >
> >
>
>
Received on Friday, 19 September 2003 17:17:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:44 GMT