RE: WS-Eventing issue 6424 proposal

Your point is well taken.  However, 6424 is really about if we should use Infoset in the specs and then an example of how to do such a thing, that we can use as a "template" for making the changes in all the specs.  I think we need to agree (or not) on using Infoset and the template first .
What you seem to be having issue with is the "content" of the changes proposed by the Eventing Editor in order to  fulfill the obligation to update the Eventing spec to use Infoset.  I think that is a different issue, and you are right, you can't really create that issue till an Editor's draft of the changes are available (assuming we decide to use Infoset).
Does that make sense?

From: Gilbert Pilz []
Sent: Friday, March 06, 2009 3:43 PM
To: Geoff Bullen
Cc: Chou, Wu (Wu); Doug Davis; Li Li;;
Subject: Re: WS-Eventing issue 6424 proposal


I'm confused. Currently the description of wse:Subscribe contains no mention of wsa:To. Wu has just posted a proposal for 6424 ( that adds the following to WS-Eventing:

The REQUIRED [event source] property provides the value of the WS-Addressing wsa:To element.
So how can it be that this has no connection to issue 6424? How can I raise an issue against a proposal that hasn't been accepted?

- gp

Geoff Bullen wrote:
if you think this is a real issue, then you should probably file a separate bug for it, as it does not seem to have any real connection with issue 6424.

From:<> [] On Behalf Of Gilbert Pilz
Sent: Friday, March 06, 2009 3:18 PM
To: Chou, Wu (Wu)
Cc: Doug Davis; Li Li;<>;<>; Geoff Bullen
Subject: Re: WS-Eventing issue 6424 proposal

I know I should have said this earlier, but I'm a bit concerned that WS-Eventing is requiring the presence of a header which is optional in the WS-Addressing specification that defines that header:
This OPTIONAL element (whose content is of type xs:anyURI) provides the value for the [destination] property. If this element is NOT present then the value of the [destination] property is ""<>.
I foresee implementation problems due to the fact that the presence or absence of the wsa:To header may be solely under the control of the WS-Addressing message handler and may not be controllable by the code that creates the wse:Subscribe message.

- gp

Chou, Wu (Wu) wrote:

Many thanks for your comments and suggestions, especially the one regarding the cardinality. Here is an updated Infoset draft (v7) of the Subscribe Section of Eventing (clean+marked copies). We really moved a long way with all comments and contributions received.


- Wu Chou.

Received on Saturday, 7 March 2009 00:59:32 UTC