W3C home > Mailing lists > Public > public-ws-resource-access-comments@w3.org > December 2009

Re: AW: Issue 8323 - resolution

From: Doug Davis <dug@us.ibm.com>
Date: Wed, 9 Dec 2009 19:04:51 -0500
To: <johannes.echterhoff@igsi.eu>
Cc: public-ws-resource-access@w3.org, public-ws-resource-access-comments@w3.org
Message-ID: <OF292AF7A1.F41A1461-ON85257688.00003F64-85257688.000074C3@us.ibm.com>
Thanks for noticing the bad xpath!
its now fixed in: http://www.w3.org/2002/ws/ra/edcopies/wseventing.html

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.



"Johannes Echterhoff" <johannes.echterhoff@igsi.eu> 
12/09/2009 05:25 PM
Please respond to
<johannes.echterhoff@igsi.eu>


To
Doug Davis/Raleigh/IBM@IBMUS
cc
<public-ws-resource-access@w3.org>, 
<public-ws-resource-access-comments@w3.org>
Subject
AW: Issue 8323 - resolution






Doug et al.,

This solution is fine for me.

One question: is the subscribe request in example 4-1 consistent with
example 5-1? In example 4-1, the filter expression is "/*/ow:Speed/[node() 
>
50]" - when I try to evaluate the expression against the event XML
(ow:WindReport) shown in example 5-1 using XMLSpy, it does not work. The
expression "/*/ow:Speed > 50" works, though. Maybe you want to change
example 4-1 accordingly so that it contains the other Xpath 1.0 
expression?

Regards,
Johannes Echterhoff


> -----Ursprüngliche Nachricht-----
> Von: public-ws-resource-access-request@w3.org 
[mailto:public-ws-resource-
> access-request@w3.org] Im Auftrag von Doug Davis
> Gesendet: Dienstag, 8. Dezember 2009 21:49
> An: johannes.echterhoff@igsi.eu
> Cc: public-ws-resource-access@w3.org; public-ws-resource-access-
> comments@w3.org
> Betreff: Issue 8323 - resolution
> 
> 
> Johannes,
>   thank you for your comments [1] on WS-Eventing.  This resulted in 
issue
> 8323 [2] being opened to track the discussions and on 12/08/09 the 
Working
> Group discussed this issue.  In WS-Eventing, in section 2.3, it 
indicates
> that:
>         Filtering occurs prior to any formatting of notification 
messages.
> Then in section 5, under the definition of the XPath filter dialect, it
> defines the root of the XPath processing as:
>         Context Node: the root of the event XML.
> Between these two point it was determined that the spec is clear that 
the
> XPath operates over the raw (unwrapped) event XML - as such the WG 
decided
> that no further specification updates are needed.   Please respond back 
to
> this list with your agreement, or disagreement, on this resolution.
> 
> [1] http://lists.w3.org/Archives/Public/public-ws-resource-
> access/2009Nov/0055.html
> [2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=8323
> 
> thanks
> -Doug Davis
> ______________________________________________________
> 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.
Received on Thursday, 10 December 2009 00:05:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 December 2009 00:05:47 GMT