|Chiusano Joseph||Sep 20, 2004 5:04 pm|
|Thomas B. Passin||Sep 20, 2004 5:39 pm|
|Bullard, Claude L (Len)||Sep 21, 2004 2:49 pm|
|Thomas B. Passin||Sep 21, 2004 3:35 pm|
|Bullard, Claude L (Len)||Sep 22, 2004 8:44 am|
|Chiusano Joseph||Sep 22, 2004 1:48 pm|
|Bullard, Claude L (Len)||Sep 22, 2004 1:59 pm|
|Rick Marshall||Sep 22, 2004 2:23 pm|
|Rick Marshall||Sep 22, 2004 2:42 pm|
|Bullard, Claude L (Len)||Sep 24, 2004 6:45 am|
|Rick Marshall||Sep 24, 2004 2:38 pm|
|Bullard, Claude L (Len)||Sep 24, 2004 2:59 pm|
|David RR Webber (XML eBusiness)||Sep 27, 2004 10:11 am|
|Bullard, Claude L (Len)||Sep 27, 2004 10:26 am|
|Chiusano Joseph||Sep 27, 2004 11:52 am|
|Bullard, Claude L (Len)||Sep 27, 2004 12:30 pm|
|David RR Webber (XML eBusiness)||Sep 30, 2004 9:04 am|
|Bullard, Claude L (Len)||Sep 30, 2004 9:16 am|
|Subject:||RE: [xml-dev] [Fwd: Potential Gap (WAS Re: [owl-s] communication between web services)]|
|From:||Bullard, Claude L (Len) (len....@intergraph.com)|
|Date:||Sep 22, 2004 1:59:06 pm|
Ok. Yes. The portal is the front man for the middlemen and the main man. ;-)
The authenticated user (identity management) has already been assigned the role, privileges and scope so all they can do is query what they are pre-authorized to query. In effect, it is a report generator implemented much as we already implement such things for secure systems.
Umm... I thought the point of discovery and metadata services was to describe a service that is available and to ensure that the data exposed to the interface is and only is precisely what the offeror offers, not to enable discovery below that level. If the other web service has discovered what is enabled for it based on its role, then it is trying to complete something that it hasn't asked for before; iow, it is at the point of a negotiation and may need a new or new-to-it service.
I confess to having my brain wrapped around the Markle reports so I may be not making good sense of your example.
-----Original Message----- From: Chiusano Joseph [mailto:chiu...@bah.com] Sent: Wednesday, September 22, 2004 3:48 PM
I should be clearer: I was actually thinking of a different type of querying than ad hoc. I see ad hoc querying (as you know) as a type of query in which the queryer (is that a word?) is presented with a user interface (such as a portal) that may present drop-down lists of various category values (based on a set of taxonomies) from which they select, or use some type of textual query, etc. In such cases, there is full knowledge of the database schema by the entity that is requesting the information (e.g. the application code or ad hoc query tool behind the portal).
My example was one in which the request for information (the additional needed information) was made by an entity (the Hotel Reservation Web Service) that had no knowledge whatsoever of the "source" database schema - it just knows that it is missing information that it requires. So it seems to me that we may need some mechanism for an entity to communicate a request for information it needs to another entity in a standard mechanism, so that there is complete understanding between the 2 entities. Of course, the Travel Agent Web Service should be fully aware of the source database schema - so as long as it fully understands the request from the Hotel Reservation Web Service, it should be simple for the Travel Agent Web Service to query the source database for the needed information information. Now that I think about it more, a semantically aware database may not be necessary in this case - as long as there is sufficient semantic understanding between the requestor (Hotel Reservation Web Service) and requestee (Travel Agent Web Service).
However, there may be cases in which such a database may be valuable - let's suppose that there is a sufficient level of trust between a requestor and a semantically aware database, but an insufficient level of semantic understanding (as if the Hotel Reservation Web Service made a direct request to the source database in the example I've given). This is a case where such a database may be valuable, so that the requestor - which has no knowledge of the database schema - can request information from the database and receive exactly what it was looking for.
In closing, it looks like this could be a single mechanism to me - but applied to different types of entities (Web Services, databases, etc.).