- From: Gilbert Pilz <gilbert.pilz@oracle.com>
- Date: Wed, 02 Dec 2009 06:56:51 +1000
- To: Doug Davis <dug@us.ibm.com>
- CC: David Snelling <David.Snelling@uk.fujitsu.com>, "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>, Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>
- Message-ID: <4B158313.8070801@oracle.com>
One way a service instance could support MEX w/out supporting GetMetadata is if it defines metadata resource endpoints for which a wst:Get returns a mex:Metadata element. - gp On 12/2/2009 2:20 AM, Doug Davis wrote: > > Hmmm, that's an interesting point. If an endpoint doesn't support > GetMetadata then in what way would they be MEX compliant? I guess > someone could claim that the endpoint might not support GetMetadata > but still uses the mex:Metadata wrappers in places - like in EPRs it > generates. > > thanks > -Doug > ______________________________________________________ > STSM | Standards Architect | IBM Software Group > (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com > The more I'm around some people, the more I like my dog. > > > *David Snelling <David.Snelling@uk.fujitsu.com>* > > 12/01/2009 11:13 AM > > > To > Doug Davis/Raleigh/IBM@IBMUS > cc > Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>, > "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org> > Subject > Re: 8201 - Clarify required and optional operations > > > > > > > > > > Doug, > > Look fine except: > > On 30 Nov 2009, at 14:45, Doug Davis wrote: > > WS-MEX: > GetMetadata Optional > > Seems strange to support a spec, but not implement it. > > Take care: > > Dr. David Snelling < David . Snelling . UK . Fujitsu . com > > Fujitsu Laboratories of Europe Limited > Hayes Park Central > Hayes End Road > Hayes, Middlesex UB4 8FE > Reg. No. 4153469 > > +44-7590-293439 (Mobile) > > > > ______________________________________________________________________ > > Fujitsu Laboratories of Europe Limited > Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE > Registered No. 4153469 > > This e-mail and any attachments are for the sole use of addressee(s) and > may contain information which is privileged and confidential. Unauthorised > use or copying for disclosure is strictly prohibited. The fact that this > e-mail has been scanned by Trendmicro Interscan and McAfee Groupshield > does > not guarantee that it has not been intercepted or amended nor that it is > virus-free. > > >
Received on Tuesday, 1 December 2009 20:58:27 UTC