Re: [wsn] WS-Eventing use of Xpath

[Tom Maguire <tmaguire@us.ibm.com>]

Yes, I think that was the point Igor was on yesterday.  This problem seems
much larger then WS-N.  I would think that W3C would need to define the on
the wire and serialization/deserialization semantics for XPath "in-scope"
namespaces.

Tom


Steve Graham/Raleigh/IBM@IBMUS wrote on 09/21/2004 08:40:20 AM:

>
> So, the use of "in-scope" namespaces seems to suffer the same
> problem that WSN is facing with its use of XPath, correct?
>
> ++++++++
> Steve Graham
> (919)254-0615 (T/L 444)
> STSM, On Demand Architecture
> Member, IBM Academy of Technology
> <Soli Deo Gloria/>
> ++++++++
>
>
> "Sedukhin, Igor S" <Igor.Sedukhin@ca.com> wrote on 09/21/2004 08:16:01
AM:
>
> > Here is the statement in WS-Eventing regarding use of XPath, which
> I referred to on
> > the yesterday's call
> > [
> > s:Envelope/s:Body/*/wse:Filter/@Dialect=' http://www.w3.
> org/TR/1999/REC-xpath-19991116'
> > Value of /s:Envelope/s:Body/*/wse:Filter is an XPath [XPath 1.0]
predicate
> > expression (PredicateExpr); the context of the expression is:
> > Context Node: the SOAP Envelope containing the notification.
> > Context Position: 1.
> > Context Size: 1.
> > Variable Bindings: None.
> > Function Libraries: Core Function Library [XPath 1.0].
> > Namespace Declarations: The [in-scope namespaces] property [XML
> Infoset] of /s:
> > Envelope/s:Body/*/wse:Filter.
> > ]
> > -- Igor Sedukhin .. (igor.sedukhin@ca.com)
> > -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788