OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [wsdm] What are we managing in MOWS: magic bullet solution

In the absense of the addressing standard the following could be a fix to #2 solution that makes it work like #3. However our preference would still be #4. We could go with the following as an interim solution until acceptable addressing standard is available to us. Then we would like to revisit this and insist on a simpler and more appropriate solution #4.

        binding[1] : xsd:Qname ... 
        address[1] : xsd:anyURI ... 
        description[1] : xsd:anyType - actual description document (WSDL) which contains the binding element and other associated information. The document MUST conform to WSDL 1.1. or 2.0 specification. It could contain WSDL imports and other elements allowed by WSDL. The document MUST contain the declaration of the binding component identified by the QName. This is not a location, this is the actual document that MUST be returned. The document is what the provider of manageability uses to describe the binding and all necessary related elements. The precise contents of this document is at the discretion of the implementer of this property/capability.

        version[0..1] : xsd:string ... 

        descriptionDocumentLocations[0..n] : anyURI      

We want to let the TC know that we observe a very dangerous tendency among the member companies to overengineer the WSDM standard. We believe that this could lead to the standard being irrelevant to the wider community of users and not helping the intended interoperability goal.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788

-----Original Message-----
From: Guru Bhat [mailto:Guru.Bhat@oracle.com] 
Sent: Tuesday, December 09, 2003 5:05 PM
To: Sedukhin, Igor S
Subject: Re: [wsdm] What are we managing in MOWS: magic bullet solution


	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.


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* .. (igor.sedukhin@ca.com)
> --* (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* .. (igor.sedukhin@ca.com)
> --* (631) 342-4325* .. 1 CA Plaza, Islandia, NY 11788

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]