wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsdm] multiple versions of wsa
- From: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- To: "David Melgar" <dmelgar@us.ibm.com>
- Date: Fri, 1 Apr 2005 12:53:01 -0500
Picking 2004/08 meeans you'd have to
deal with WSRF/WSN which WSDM has a dependency on. Their
schemas.
Now,
merely switching the dependency on the newer versions of WSRF/WSN would help and
WSDM does not need to change, but it means different MEPs and different schemas
for property retrieval and notifications and will certainly derail the
whole interop at this point.
The
thing is that in the current interop, going by the words of specs, ALL of the
endpoints MUST support at least 2003/03 WSA. I guess in order not to derail the
whole thing, I'd pick this for the interop. I;'d' rather have troubles with 2
interop acts instead of the whole interop altogether.
-- Igor Sedukhin
.. (igor.sedukhin@ca.com)
-- (631)
342-4325 .. 1 CA Plaza, Islandia, NY
11749
I agree that WSDM should settle on a
single version of WSA.
In earlier
mailing list discussions it sounded like WSDM should deal with this issue as an
errata soon after the interop, but the concensus seemed to be that it would not
get settled before the interop.
Any
route that we take for the interop has potential for confusion. The WSA specs do
not normatively describe how to convert between WSA versions. The 2004/06
version of WSRF/WSN implies that it only works with the 2003/03 version of
WSA.
We have gone through
considerable effort to attempt to accept either version WSA headers and respond
with the same version. We are attempting to generate 2004/08 version EPRs from
WSDM operations, and 2003/03 from WSN subscription. We intend to send WSA header
versions that correspond to the EPR being acted upon. Versioning scenarios can
get complex and I wouldnt be surprised if we don't conform to our guidelines.
Its a shame that we've spent so much time dealing with WSA versioning.
If you had to pick one version, I could
argue for either version. 2003/03 is the version defined by the WSN/WSRF specs
so WSDM could easily pick that version to use. 2004/08 is the version our
tooling natively supports so it would be easiest for us to settle on.
David Melgar
Web Services Toolkit
Development
Emerging
Technologies
dmelgar@us.ibm.com
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
04/01/2005 11:14 AM
|
To
| "Hideharu Kato"
<hideharu@sdl.hitachi.co.jp>,
<wsdm@lists.oasis-open.org>
|
cc
|
|
Subject
| RE: [wsdm] multiple
versions of wsa |
|
It would be a bit too late to make this adjustmeent to the interop
right
now. But, if you were to choose which ONE to implement, pick
2003/03.
That way it will likely to work except for a few acts like
MUWS
Relationships and MOWS Manageability
References.
-- Igor Sedukhin ..
(igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY
11749
-----Original Message-----
From:
Hideharu Kato [mailto:hideharu@sdl.hitachi.co.jp]
Sent: Friday, April 01,
2005 9:00 AM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] multiple
versions of wsa
I don't believe that testing
of wsa is the main focus of the interop.
So, I'd like to propose that we
should use only one version(2004/08) of
wsa during the Interop.
I think
that WSDM will need to support 2004/08/addressing in the near
future because
the latest version of WSRF/WSN support that version.
I'm not going to implement WS-Addressing but WSDM.
If I use the
current apache addressing,
I would have some troubles with it
because it
does not deal with multiple versions of wsa
simultaneously.
I don't mean that the
current WSDM spec. should be modified.
I would say that WSDM should use
2004/08/addressing only for the
Interop.
---------------------------------------
Hideharu Kato
2nd
Research Dept.
Hitachi,Ltd.,Systems Development Laboratory E-mail
:
hideharu@sdl.hitachi.co.jp Tel : +81-44-959-0248 Fax :
+81-44-959-0853
--------------------------------------
----- Original Message -----
From: "Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
To: "David Melgar"
<dmelgar@us.ibm.com>
Cc: <wsdm@lists.oasis-open.org>
Sent:
Friday, April 01, 2005 1:29 AM
Subject: RE: [wsdm] Groups - WSDM 1.0 interop
scenarios.doc uploaded
ok I can take
care of that. I was going to finalize the interop doc
after todays call
anyways. Current has a lot of changes which will all
be accepted after todays
call.
-- Igor Sedukhin ..
(igor.sedukhin@ca.com <mailto:igor.sedukhin@ca.com>
)
-- (631)
342-4325 .. 1 CA Plaza, Islandia, NY 11749
_____
From: David Melgar
[mailto:dmelgar@us.ibm.com]
Sent: Thursday, March 31, 2005 11:28 AM
To:
Sedukhin, Igor S
Cc: wsdm@lists.oasis-open.org
Subject: Re: [wsdm] Groups
- WSDM 1.0 interop scenarios.doc uploaded
Comments on latest interop doc
-
Bootstrap. I thought we had said on email that we'd
do HTTP Get
of the EPR(s). Latest one doesn't show that.
-
Weather station WSDL doesn't include
GetManageabilityReferences
operation.
- MOWS
Request processing notification act does not include the
step to invoke the
GetCurrentTemperature operation or some action to
kick off the
notification.
David Melgar
Web Services
Toolkit Development
Emerging
Technologies
dmelgar@us.ibm.com
Igor.Sedukhin@ca.com
03/31/2005
01:53 AM
To
wsdm@lists.oasis-open.org
cc
Subject
[wsdm] Groups -
WSDM 1.0 interop scenarios.doc
uploaded
The document
revision named WSDM 1.0 interop scenarios.doc has been
submitted by Igor
Sedukhin to the OASIS Web Services Distributed
Management (WSDM) TC document
repository. This document is revision #3
of WSDM 1.0 interop
scenarios.doc. Document Description: doc in a more
or less acceptable
shape
anything yellow needs work View Document
Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document_
id=12070
Download
Document:
http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/12070/WSD
M%201.0%20interop%20scenarios.doc
Revision: This document is revision #3
of WSDM 1.0 interop scenarios.doc.
The document details page referenced
above will show the complete
revision history. PLEASE NOTE: If the
above links do not work for you,
your email application may be breaking
the link into two pieces. You
may be able to copy and paste the entire
link address into the address field
of your web browser. -OASIS
Open
Administration
---------------------------------------------------------------------
To
unsubscribe from this mail list, you must leave the OASIS TC that
generates
this mail. You may a link to this group and all your TCs
in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To
unsubscribe from this mail list, you must leave the OASIS TC that
generates
this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]