[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsdm] MUWS: New issue to consider?
Sedukhin, Igor S wrote: >Didn't we say in WSRF that you may use any of the embodiments you like > Well, insofar as I know, we did say that in WSRF. However, WSDM has not yet updated to the not-yet-released WSRF spec, so I think we (meaning WSDM) are (is) still restricted to WS-Addressing (if that's what you're asking). That said, I guess my question was do we/should we (for, say, interoperability) define how our EPR is constructed. Or do we just rely on the appropriate magic for obtaining one. I know that's probably what we say -- I'm just not terribly comfortable with it. > > >-- Igor Sedukhin .. (igor.sedukhin@ca.com) >-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 > > >-----Original Message----- >From: fred carter [mailto:fred.carter@amberpoint.com] >Sent: Tuesday, November 16, 2004 4:23 PM >To: wsdm@lists.oasis-open.org >Subject: [wsdm] MUWS: New issue to consider? > >In reading the WS-Management spec the other day, one thing that sticks >out as contextually different is that they describe a normative [I >think] mapping to WS-Addressing. That is, they make specific reference >to where the analogous concept to identity fits into the WS-Address. > >Do we need to map this? That is, to describe how to identify the >resource in question in our WS-Address? I think that this is currently >missing, and I don't recall seeing it specifically addressed in WSRF >(and it couldn't be, since they don't have an identity capability...). > >Seems like we could say that there must exist a ref prop that's the same >as the property in the property sheet in the WS-A. This leaves open >discovery, but that's a separate problem... > >Opinions? > >/fred > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]