W3C home > Mailing lists > Public > public-ws-semann@w3.org > April 2006

RE: Scenarios for embedded annotations in WS description

From: Shi, Xuan <xshi@GEO.WVU.edu>
Date: Wed, 26 Apr 2006 10:53:41 -0400
Message-ID: <D81F456794C18B4DA3E2ABC47DBBEEF2095042@www.geo.wvu.edu>
To: "'Carine Bournez '" <carine@w3.org>, "'Daniela CLARO '" <Daniela.CLARO@eseo.fr>, "Shi, Xuan" <xshi@GEO.WVU.edu>
Cc: "''public-ws-semann@w3.org' '" <public-ws-semann@w3.org>, "'public-sws-ig@w3.org '" <public-sws-ig@w3.org>


Thanks for your kind attention and advice. I just want to show such examples
or challenges to people in 'public-ws-semann@w3.org', so that when they try
to demonstrate something to us, their ues cases will not just include some
simple and naive issues like "buy book", "buy ticket", "reserve hotel",
"credit card transaction", etc. They can use such living Web services and
demonstrate such approach is feasible, i.e. tell people those four Web
services implement the same address geocoding functions by adding/embedding
semantic annotations into those four WSDL documents.

As I discussed with Daniela regarding dynamic composition vs. dynamic
invocation, I still hope to see some people can use the real and existing
Web services for demonstration. A good scenario or use case is just what I
told Daniela in the past by composing Microsoft's TerraService with ESRI's
address geocoding service to retrieve a 1 ~ 20 meter resolution aerial photo
images for the input location/address. Then we can see, whether dynamic
composition will really lead to dynamic invocation. In my opinion, we should
focus on dynamic invocation first. Once we understand how dynamic invocation
works in different use cases and in different platforms (Java, .NET, etc.),
then we can figure out how to do dynamic composition. For this reason, we
will see that dynamic composition and dynamic invocation of Web services
need certain pre-conditions, which many not be applicable to all kinds of

Best wishes,


-----Original Message-----
From: Carine Bournez
To: Shi, Xuan
Cc: 'public-ws-semann@w3.org'; public-sws-ig@w3.org
Sent: 4/25/06 5:29 AM
Subject: Re: Scenarios for embedded annotations in WS description

On Mon, Apr 24, 2006 at 09:54:12AM -0400, Shi, Xuan wrote:
> Below are four WSDL urls for your kind attention. All of them have the
> function for address geocoding service. I'd be happy to see how you
guys add
> semantic annotations to such different WSDLs to tell people-they are
all the
> same service and function:

There are no semantic annotations embedded in your examples.
We are looking for scenarios where semantic annotations would be
embedded in the service description with an explanation on the need 
for *embedded* rather than *external* information.

> The remaining questions is how people can dynamically invoke such
> functions by reading the WSDL with *semantic annotations*?

This question is not in the scope of the SAWSDL WG, but the IG is the
right place for a debate (although it's maybe premature to ask for a 
full-fledged solution).
Received on Wednesday, 26 April 2006 14:54:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:12 UTC