W3C home > Mailing lists > Public > public-sws-ig@w3.org > March 2006

RE: Semantics of WSDL vs. semantics of service

From: Shi, Xuan <xshi@GEO.WVU.edu>
Date: Wed, 15 Mar 2006 11:57:07 -0500
Message-ID: <D81F456794C18B4DA3E2ABC47DBBEEF2094FBD@www.geo.wvu.edu>
To: "'Carine Bournez '" <carine@w3.org>, "'public-sws-ig@w3.org '" <public-sws-ig@w3.org>


Thanks very much for your kind information. I am glad to see we eventually
have something based on the same ground: we can separate service semantic
description from service development framework. Thus service semantics can
be neutral and independent from service providers.

Furthermore, my question is, if we can describe the service semantics in the
external resource, then why do we need WSDL again to transfer the message
between service provider and requester, since once we can describe the
service, then we can invoke the service directly over HTTP without the
serialization/deserialization process?

Best regards,


-----Original Message-----
From: Carine Bournez
To: public-sws-ig@w3.org
Sent: 3/15/06 11:44 AM
Subject: Re: Semantics of WSDL vs. semantics of service

On Wed, Mar 15, 2006 at 11:36:05AM -0500, Shi, Xuan wrote:
> Jacek,
> Thanks for your explanation. If you agree that semantic annotations
have no
> direct relation with WSDL elements, then why don't you create a
> and independent document to describe the *meaning* of your services?

Clarification about semantic annotation for wsdl:
The *meaning* is actually in a separate document (or several ones). The 
annotation in the WSDL is supposed to *point* to *external information*.

Carine Bournez -+ W3C Europe
Received on Wednesday, 15 March 2006 16:57:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:32:52 UTC