wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsdm] Weather station WSDL and RequestProcessingDigest comments
- From: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- To: "David Melgar" <dmelgar@us.ibm.com>,"Campana Jr., Salvatore J" <sal.campana@hp.com>
- Date: Thu, 31 Mar 2005 11:19:19 -0500
BTW it is <xsd:element ref="wsnt:TopicExpression" minOccurs="1" maxOccurs="1" /> not
wsnt:Topic!!
Also in the interop doc I will remove
<
element ref="bbry:CurrentTime"/>
-- Igor Sedukhin
.. (igor.sedukhin@ca.com)
-- (631)
342-4325 .. 1 CA Plaza, Islandia, NY
11749
On the call today I questioned if we
needed to define weather station WSDL. But it seems like we do need to define an
operation on a web service.
In the MOWS
Request Processing Digest act, there needs to be some operation which is invoked
which causes the event to be sent. This operation could be a
GetResourceProperty(FCCID) or GetManageabilityReferences.
It is unclear to me what resource is intended to be
represented by the Weather Station Service. Is it a webservice (MOWS), or is the
resource a weather station? Correlateable properties are meant to indicate if
two different EPRs represent management of the same resource. Using FCCID
property to determine if two web services represent the same resource seems to
indicate that the resource is the weather station, not the web service.
If the weather station web service is
intended to be the web service managed using MOWS then the GetResourceProperty
or GetManageabilityReferences operation can be invoked on this web service to
drive the Request Processing Digest act. This step should be added to the
act.
The provided WSDL for weather
station mixes the business web service, and the management provider endpoint.
These should be separate port types. They could be implemented at the same port,
but this is not typical. The resource properties document reference by each port
type is different since the properties available through each port type
differ.
Weather station port type
(business) should have the following operations as a minimum:
- GetResourceProperty: FCCID is the only required
property.
-
GetManageabilityReferences
ManagementProvider port type which manages the weather station needs to
have these operations:
-
GetResourceProperty: WSDM defined properties, MOWS metrics, etc.
- GetMultipleResourceProperties
- Subscribe
- GetCurrentMessage: This isn't used by the interop scenarios, but is
part of the NotificationProducer port type defined by WSN.
David Melgar
Web Services Toolkit
Development
Emerging
Technologies
dmelgar@us.ibm.com
"Campana Jr., Salvatore J"
<sal.campana@hp.com>
03/24/2005 01:43 PM
|
To
| <wsdm@lists.oasis-open.org>
|
cc
|
|
Subject
| [wsdm] Interop Wsdl
Files |
|
I've attached our WSDL files for the various interop services and
the
xsd (corrected xsd:String-> xsd:string) from the interop
document..
You'll notice that the spec WSDLs and XSDs are referenced using
relative
paths..that will probably need to
change....
Note: I have the
GetManageabilityReferences operation in the
WeatherStation service, however I
think it was noted that the operation
could exist in another
service.
Thx!
-S
--------------------
Sal
Campana
HP Software
Engineer
phone: 856.638.6284
email:
sal.campana@hp.com
---------------------------------------------------------------------
To
unsubscribe, e-mail: wsdm-unsubscribe@lists.oasis-open.org
For additional
commands, e-mail: wsdm-help@lists.oasis-open.org
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]