RE: [wsdm] RE: [wsrf] Issue: Finding WSDL from an EPR

thanks for the clarification. if that is the relationship 
between ws-policy and ws-metadataexchange, then am ok with it. 

From: Anthony Nadalin 
[mailto:] 
Sent: Tuesday, June 08, 2004 3:49 
PM
To: Srinivas, Davanum M
Cc: David Orchard; David 
Snelling; Sedukhin, Igor S; Savas Parastatidis; ; 

Subject: RE: [wsdm] RE: [wsrf] Issue: 
Finding WSDL from an EPR

If I have a JCE crypto library that only supports DES as that is all my 
application requires/mandates, is it a half baked solution since JCE 
architecture and implementation allows many more algorithms that I don't require 
for a given specification ?

Anthony Nadalin | work 512.838.0085 | cell 
512.289.4122
' 
src="gif00027.gif" width=16>"Srinivas, Davanum M" 
<>

  
  

    
      
        
          
            "Srinivas, Davanum M" 
              <> 
              
06/08/2004 01:59 PM

    
      
        
        

          

            
To

          
Anthony Nadalin/Austin/IBM@IBMUS

        

          

            
cc

          
"David Orchard" <>, "David Snelling" 
            <>, "Sedukhin, Igor S" 
            <>, "Savas Parastatidis" 
            <>, 
            <>, 
            <>

        

          

            
Subject

          
RE: [wsdm] RE: [wsrf] Issue: Finding WSDL from an 
          EPR

      
        
        

          
          

So, if the suggestion is for a platform developer who 
needs to support WSDM standard, they should have at least a half-baked impl of 
WS-MetadataExchange to support WSDM standard. That somehow does not sound 
right....

-- 
dims

From: Anthony Nadalin [mailto:] 

Sent: Tuesday, June 
08, 2004 2:44 PM
To: 
Srinivas, Davanum M
Cc: David Orchard; David Snelling; Sedukhin, Igor S; Savas 
Parastatidis; ; 

Subject: RE: [wsdm] RE: [wsrf] 
Issue: Finding WSDL from an EPR

Are you retrieving Policy or WSDL ? If so then the recipient and 
requestor of the message would have to support WS-Policy otherwise I don't see a 
prerequisite. In the case of Policy, this could be a 3rd party services and it 
may know nothing about WSDL only Policy and the service EPR may no nothing about 
Policy. So it depends on what you are doing and what I read in the notes below 
were on WSDL not policy.

Anthony Nadalin | work 512.838.0085 | cell 
512.289.4122
' 
src="gif00036.gif" width=16>"Srinivas, Davanum M" 
<>

  
  

    
      
        
          
            
              
                
                  
                    "Srinivas, Davanum M" 
                      <> 
                      
06/08/2004 12:35 PM

    
      
        
        

          
            
To

          
Anthony 
            Nadalin/Austin/IBM@IBMUS

        

          
            
cc

          
"David Orchard" 
            <>, "David Snelling" 
            <>, "Sedukhin, Igor S" 
            <>, "Savas Parastatidis" 
            <>, 
            <>, 
          <>

        

          
            
Subject

          
RE: [wsdm] RE: [wsrf] 
            Issue: Finding WSDL from an EPR

      
        
        

          
          

http://xml.coverpages.org/ni2004-03-05-a.html

WS-MetadataExchange specification defines three request-response message pairs to retrieve 
these three types of metadata. One retrieves the 
WS-Policy 
associated with the receiving endpoint or with a given target 
namespace; another retrieves either the WSDL associated 
with the receiving endpoint or with a given target namespace; a third retrieves 
the XML Schema with a given target namespace. Together these messages allow 
efficient, incremental retrieval of a Web service's metadata. 

From: Anthony 
Nadalin [mailto:] 
Sent: Tuesday, June 08, 2004 12:40 PM
To: Srinivas, Davanum 
M
Cc: 
David Orchard; David Snelling; Sedukhin, Igor S; Savas Parastatidis; 
; 
Subject: Re: [wsdm] RE: [wsrf] 
Issue: Finding WSDL from an EPR 

WS-MetadataExchange does not require WS-Policy, where did you 
read this ?

Anthony Nadalin | work 512.838.0085 | cell 
512.289.4122
' 
src="gif00045.gif" width=16>"Srinivas, Davanum M" 
<>

  
  

    
      
        
          
            
              
                
                  
                    
                      
                        
                          
                            
                              
                                
                                
                                "Srinivas, Davanum M" 
                                <> 
                                
06/08/2004 10:28 
                                AM

    
      
        
        

          
            
To

          
"David 
            Orchard" <>, "Savas Parastatidis" 
            <>, "Sedukhin, Igor S" 
            <>, "David Snelling" 
            <>, 
            <>

        

          
            
cc

          
<>

        

          
            
Subject

          
[wsdm] 
            RE: [wsrf] Issue: Finding WSDL from an 
EPR

      
        
        

          
          

Any follow up thoughts dave?

-- dims 

-----Original 
Message-----
From: Srinivas, Davanum M 
Sent: Monday, June 07, 2004 1:36 
PM
To: David Orchard; Savas Parastatidis; Sedukhin, Igor S; David 
Snelling;

Cc: 

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:]
Sent: 
Monday, June 07, 2004 1:22 PM
To: Srinivas, Davanum M; Savas Parastatidis; 
Sedukhin, Igor S; David
Snelling; 
Cc: 

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:]
> Sent: Tuesday, June 01, 2004 10:51 AM
> To: Savas 
Parastatidis; Sedukhin, Igor S; David Snelling; 
> 

> Cc: 
> 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:]
> Sent: Tuesday, June 01, 2004 1:43 PM
> To: Sedukhin, Igor 
S; David Snelling; 
> Cc: 

> 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:]
> 
> Sent: Tuesday, June 01, 2004 4:40 PM
> > To: David Snelling; 

> > Cc: 
> 
> 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 .. ()
> > -- (631) 
342-4325 .. 1 CA Plaza, Islandia, NY 11788
> > 
> > 
-----Original Message-----
> > From: David Snelling [mailto:]
> > Sent: Friday, May 28, 2004 3:32 AM
> > To: 

> > Cc: 
> 
> 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 <>
> >   
  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)
> > 

> > 
> 
> 
> 
> 
> 

To unsubscribe from this mailing list (and be removed 
from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.