[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrf] Issue: Finding WSDL from an EPR
Dave, I was merely advocating caution and not advocating a "re-invent"ed solution. AFAIK, WS-MetadataExchange drags in WS-Policy as well. Is this what you are advocating? Adding dependency on two more specs? If you need to implement WSDM? -- dims -----Original Message----- From: David Orchard [mailto:dorchard@bea.com] Sent: Monday, June 07, 2004 1:22 PM To: Srinivas, Davanum M; Savas Parastatidis; Sedukhin, Igor S; David Snelling; wsrf@lists.oasis-open.org Cc: wsdm@lists.oasis-open.org Subject: RE: [wsrf] Issue: Finding WSDL from an EPR Reducing dependencies as the critera for problem solving means re-inventing the wheel when potentially adequate technologies are not used to solve such problems. One of my pet peeves is the continual re-invention of the wheel that people want to do. Is there something technically inferior in ws-metadatexchange for this problem space? Cheers, Dave > -----Original Message----- > From: Srinivas, Davanum M [mailto:Davanum.Srinivas@ca.com] > Sent: Tuesday, June 01, 2004 10:51 AM > To: Savas Parastatidis; Sedukhin, Igor S; David Snelling; > wsrf@lists.oasis-open.org > Cc: wsdm@lists.oasis-open.org > Subject: RE: [wsrf] Issue: Finding WSDL from an EPR > > > This is one of my pet peeves...Let's please try to narrow down the > dependencies (to reduce the dependencies) for WSDM and not expand it. > Makes things harder to implement. > > Thanks, > dims > > -----Original Message----- > From: Savas Parastatidis [mailto:Savas.Parastatidis@newcastle.ac.uk] > Sent: Tuesday, June 01, 2004 1:43 PM > To: Sedukhin, Igor S; David Snelling; wsrf@lists.oasis-open.org > Cc: wsdm@lists.oasis-open.org > Subject: RE: [wsrf] Issue: Finding WSDL from an EPR > > All, > > Why don't you use the WS-MetadataExchange specification? > > I know that it has not been submitted to a standards body yet, but > that hasn't stopped this TC before, right? :-) > > Regards, > -- > Savas Parastatidis > http://savas.parastatidis.name > > > > -----Original Message----- > > From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com] > > Sent: Tuesday, June 01, 2004 4:40 PM > > To: David Snelling; wsrf@lists.oasis-open.org > > Cc: wsdm@lists.oasis-open.org > > Subject: RE: [wsrf] Issue: Finding WSDL from an EPR > > > > David, > > > > In addition to requiring service name and port in an EPR, I believe > the > > WSDM requirement is to have a normative (but optional :) > place in the > EPR > > for a URL to a WSDL document. That is 1) part of the requirement. > > > > Issue WSRF13 is only covering part 2) of the WSDM requirmenent. > > > > Now, apparently, 1) could be solved by other means as well e.g. > sending a > > GetWSDL request message (TBD) to an address provided by the EPR. > Still, a > > place in an EPR for a WSDM URL would not hurt. > > > > Before WSDM TC starts to look for other solutions, it would be > reasonable > > for WSRF TC to look at this part of an issue. > > > > > > -- Igor Sedukhin .. (igor.sedukhin@ca.com) > > -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 > > > > -----Original Message----- > > From: David Snelling [mailto:d.snelling@fle.fujitsu.com] > > Sent: Friday, May 28, 2004 3:32 AM > > To: wsrf@lists.oasis-open.org > > Cc: wsdm@lists.oasis-open.org > > Subject: [wsrf] Issue: Finding WSDL from an EPR > > > > Folks, > > > > This issue has been passed to us from the WSDM-TC. > > > > > [Disc01] > > > This is the issue of finding a WSDL from an EPR. I didn't > hear any > > > disagreement on the wording that we came up with for the > corresponding > > > requirement during the conf call last week. This > requirement (to be > > > passed to WSRF) reads in three parts: > > > > > > 1) Any EPR used to reference a WS-Resource must provide > sufficient > > > information for the consumer to retrieve the WSDL description of > the > > > WS-Resource. > > > > > > 2) The EPR must contain enough information to disambiguate which > port > > > and/or service to use. > > > > > > 3) The WSDL component model of the WS-Resource must be complete > (must > > > include, inline or import the schema of all referenced elements) > > > > > > > It is my understanding that if the answer to Issue WSRF13 > (Should we > > require service and port in the EPR?) is yes, then we have covered > this > > request. > > > > I suggest we link this request to WSRF13, and flag it so that if we > decide > > NO, we notify WSDM that we punted it back to them. > > > > Bryan: Please queue this for the New Issues discussion on > Monday week. > > Thanks. > > > > -- > > > > Take care: > > > > Dr. David Snelling <d.snelling@fle.fujitsu.com> > > Fujitsu Laboratories of Europe > > Hayes Park Central > > Hayes End Road > > Hayes, Middlesex UB4 8FE > > > > +44-208-606-4649 (Office) > > +44-208-606-4539 (Fax) > > +44-7768-807526 (Mobile) > > > > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]