Re: MetadataSection in WS-Eventing

Stephan Poehlsen <poehlsen@itm.uni-luebeck.de> wrote on 08/17/2010 
02:29:57 AM:
> Doug,
> 
> In an earlier version of WS-Eventing Appendix A there was a long part 
> http://www.w3.org/TR/2010/WD-ws-eventing-20100330/#id35822170
> After removing this part I thought that the EventDescriptions should not 

> appear anymore in MetadataSections.

Any metadata might appear within a MetadataSection - it all depends on 
whether
MEX is used to retrieve it or not.  That same metadata could also be 
available
through some other mechanisms - e.g. via an HTTP GET or inlined within a 
Policy
assertion.

In this particular case, while section A.1.1. of the latest spec pushes 
people 
towards embedding the EVD data within the EventSource policy assertion, 
some
people may still prefer to retrieve just the EVD by itself, without all of 
the
other noise (e.g. policy, wsdl...).  In these cases the EVD data might 
appear
within MEX sections because MEX.getMetadata() was used.

> Maybe it is possible in WS-Event-Descriptions Section 4.1.1 to express 
> more clearly, that the EventSource Policy and the MetadataSection are 
> two different things, otherwise the solution with the MetadataSection 
> might get lost when skimming over the spec.

What if we added an Example 4-5(section 4.1.1) that showed the EVD data 
being 
returned within a GetMetadataResponse(), would that help?

> So what about the NotificationWSDLs? From the current editor's 
> WS-Eventing spec, it is not clear for me that the NotificationWSDL is 
> retrievable via a MetadataSection. Especially since in section A.2.1 
> http://www.w3.org/TR/2010/WD-ws-eventing-20100330/#id35822333 the gray 
> box and Section A.3 was removed.

Like the previous one, what if we added an example in WS-Eventing's
A.2.1 that showed the Notification WSDL being pulled back from a 
MEX.getMetadata()?

-Doug

> Regards,
> Stephan
> 
> Doug Davis wrote:
> >
> > Stephan,
> > see: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10376
> > would the proposal address your concern?
> >
> > To your 2nd point... if you are starting with the Event Source WSDL 
then
> > yes you need to use ws-policy to embed the EVD data in it.
> > Of course, you could also just query the event source directly asking
> > for the EVD data - using MEX.getMetadata( "wsevd:EventDescriptions" );
> > and by-pass ws-policy all together.
> >
> > thanks
> > -Doug