W3C home > Mailing lists > Public > www-ws-desc@w3.org > February 2002

DR032 [was Requirements]

From: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
Date: Wed, 13 Feb 2002 15:31:57 -0800
Message-ID: <2E33960095B58E40A4D3345AB9F65EC1054D924E@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
To: <www-ws-desc@w3.org>
Waqar, interesting... Of course we could expose version through an
element / attribute in the spec's namespace, but that doesn't seem like
the right solution for the other examples you give. 

Are you thinking of the general problem of composing an
application-defined SOAP Body with SOAP Headers defined by the
underlying plumbing or service policy? Maybe the former could be defined
with a port type, and the latter composed in separately through another
mechanism.

--Jeff

-----Original Message-----
From: Sadiq, Waqar [mailto:waqar.sadiq@eds.com] 
Sent: Monday, February 11, 2002 6:32 AM
To: www-ws-desc@w3.org
Subject: Requirements


 
Here is another requirement:
 
[DR032] In a lot of cases, it is important for the server to expose some
service wide properties/attributes.  These properties/attributes have
the service-level scope and could be used to describe either some Qos
parameters or some application specific characteristics.  As an example,
a service may want to expose an attribute which describes the version
number of the service.  Hence, a web service description language should
be able to model service level attributes/properties.
 
Thanks,
 
_______________________________________________
Waqar Sadiq
 
EDS EIT EASI - Enterprise Consultant
MS: H3-4C-22
5400 Legacy Drive
Plano, Texas 75024
 
phone: +01-972-797-8408 (8-837)
e-mail: waqar.sadiq@eds.com
fax: +01-972-605-4071
_______________________________________________
 
 
 
Received on Wednesday, 13 February 2002 18:35:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:18 GMT