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

Re: Grounding puzzle

From: Drew McDermott <drew.mcdermott@yale.edu>
Date: Fri, 19 Sep 2003 17:41:48 -0400 (EDT)
Message-Id: <200309192141.h8JLfmL22475@pantheon-po02.its.yale.edu>
To: www-ws@w3.org

   > 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?

   [Mithun Sheshagiri]
   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

   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 name="phoneNum_Output">
	 <part name="phoneNum" daml-property="profile:#hasTelNum"/>

   port desription:
   <portType name="TelLookUp_port">
   <operation name="TelLookUp_operation" daml-s-process="BT:#TelLookUp">
	   <input message="SSN_Input"/>
	   <output message="phoneNum_Output"/>

   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.


I've repeated your entire message in my answer, which I normally try
to avoid, so that people following this discussion can see that
nowhere in your solution do you actually say that if I send a Social
Security number for person P to the service, it will send me the
telephone number of P, *that very same person* (which is a slight
idealization, since people can have more than one phone number, or
less than one).  Or those same people can see that I've missed
something obvious, which wouldn't be unheard of.

Now that I ponder it, the obvious thing I may have overlooked is that
the statement is mostly captured in the IOPEs of the DAML-S process
description.  There's really not much left for the WSDL and grounding
to do except specify port bindings and maybe character sets.  The fact
that American Social Security numbers and telephone numbers have 9 and
10 digits respectively is part of the ontology, as you suggested.

                                             -- Drew McDermott
                                                Yale University CS Dept.
Received on Friday, 19 September 2003 17:41:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:12 UTC