Ok. Still, you'd specify operations input/output and binding to the HTTP
transport in the WSDL (components) itself, so it is only natural to
specify which interfaces these operations belong to in the WSDL too. I'm not
sure you want policy to contain such information, do you?
Besides WSDL 2.0 already has everything needed anyways. It is WSDL 1.1 that
we're having troubles with.
-----Original Message----- From: Anthony Nadalin
[mailto:drsecure@us.ibm.com] Sent: Mon 6/7/2004 5:49 PM
To: Sedukhin, Igor S Cc: Heather Kreger;
wsdm@lists.oasis-open.org Subject: RE: [wsdm] capabilities
proposal
That's fine policy can be metadata (some real fine lines are drawn here), I
would not like to see WSDM go off and reinvent in the policy/metadata space.
IBM's view is that policy can be used to express operational and metadata
about operations, WSDL may be just one place to express these there are many
other places.
Anthony Nadalin | work 512.838.0085 | cell
512.289.4122 "Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
06/07/2004 04:10 PM |
| This is operational metadata (just like WSDL is). It
may not resemble a policy, which is really metadata about WSDL and what it
defines.
The
underlying reason may be same as to why not use policy to express what
operations and message exchanges are supported. We use WSDL for
that.
--
Igor Sedukhin .. (igor.sedukhin@ca.com) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
From: Anthony Nadalin [mailto:drsecure@us.ibm.com]
Sent: Monday,
June 07, 2004 4:49 PM To: Heather Kreger Cc: wsdm@lists.oasis-open.org Subject: Re: [wsdm] capabilities
proposal
Why is this a proposed section in WSDM, seem like this is just
policy and intersection of policy
Anthony Nadalin | work 512.838.0085 |
cell 512.289.4122 Heather
Kreger/Raleigh/IBM@IBMUS
Heather Kreger/Raleigh/IBM@IBMUS
06/07/2004 02:57 PM |
| Hi folks, Here is an initial proposal for discovering capabilities.
I think we may be able to use something like this for discovering
manageability services as well. (See attached file:
Capabilities.wsdm.060404.doc)
This is just a
proposal and we can discuss on Thursday.
Heather Kreger STSM, Web
Services Lead Architect for SWG Emerging Technologies Author of "Java and
JMX: Building Manageable Systems" kreger@us.ibm.com 919-543-3211 (t/l
441) cell:919-496-9572To unsubscribe from this mailing
list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.
|