Igor,
Oracle is opposed to a solution that uses WS-Addressing given that it
is not a standard and the IP status for the same is not well
established. The wsdl:service approach you outline as an alternative is
one that we would prefer.
~Guru
Sedukhin, Igor S wrote:
> What comes along with my proposal below is a simple definition of the
> "identification" manageability capability.
>
> "The identification capability allows the provider of manageability to
> tell what it thinks it is managing. In other words refer/address/point
> to the resource it thinks it made manageable. The exact way of
> "referring" conforms to the subject domain of the resource."
>
>
> --* **Igor Sedukhin* .. ()
> --* (631) 342-4325* .. 1 CA Plaza, Islandia, NY 11788
>
>
>
> ------------------------------------------------------------------------
> *From:* Sedukhin, Igor S
> *Sent:* Monday, December 08, 2003 7:34 PM
> *To:* WSDM TC
> *Subject:* [wsdm] What are we managing in MOWS: magic bullet solution
>
> I just realized why are we struggling so hard with the MOWS
> indetification part. We need to point to the MOWS thing that is being
> managed. Why don't we just do that: point using WS-Addressing address
> (_http://www-106.ibm.com/developerworks/webservices/library/ws-add/#endpointreferences_).
> And so I popose
>
> #4:
> Identify the MOWS thing that we are managing using wsa:EndpointReference
>
> If one would argue that then it should be the wsdl:service with all of
> its contents instead of EndpointReference, I must say to be arguable it
> has to be wsdl:endpoint with all of its contents. That is also acceptable.
>
> --* **Igor Sedukhin* .. ()
> --* (631) 342-4325* .. 1 CA Plaza, Islandia, NY 11788
>
