W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2004

Issue 195 [was RE: Features and Properties versus Extensions]

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Thu, 1 Jul 2004 16:50:51 -0700
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA2041DE8DA@RED-MSG-30.redmond.corp.microsoft.com>
To: "David Orchard" <dorchard@bea.com>
Cc: <www-ws-desc@w3.org>

David, in preparation for dispatching this issue next Thursday - is the
issue properly summarized as "define an expression language (or augment
an existing expression language) to navigate the WSDL component model?"

If so, I think there will be significant resistance to that at this
point, as Sanjiva's post below suggests.  If not, what is the issue
you'd like addressed here?

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Sanjiva Weerawarana
> Sent: Monday, May 17, 2004 2:33 AM
> To: Glen Daniels; David Orchard
> Cc: www-ws-desc@w3.org
> Subject: Re: Features and Properties versus Extensions
> 
> 
> "David Orchard" <dorchard@bea.com> writes:
> > > It seems to me that this is a new data model layered on top
> > > of the XML data model, and I'd probably actually want a new
> > > query language for it or at least an xpath function.  What
> > > I'd really like is to ask "get the property with
> > > name=httpauthentication in the binding element and follow the
> > > f&p rules to generate it".  Something like
> > > "property[@name="httpauthentication"]/binding/operation[@name=
> > > "op2"" where the property function evaluates the name in the
> > > context that it is given.
> > >
> > > Is this roughly right?
> >
> > I think this is perhaps an interesting direction to think about, but
> > certainly not necessary to make the model useful.  WSDL itself, as
many
> > application dialects are, seems to be "a new data model layered on
top
> > of the XML data model", no?
> 
> IMO the simplest way to provide an XPath query language for F&P
> is to add an XPath extension as DaveO suggests, but not at the
> top level:
> 
>
/definitions/binding/operation[@name="op2"]/x:property("httpauthenticati
on
> ")
> 
> The semantics of x:property(string) can be defined to navigate the
> "parent" hierarchy of properties.
> 
> Another option is to introduce an extension axis for properties, but
> that's
> a bit more complicated .. esp. for users.
> 
> No, I'm not suggesting that WSDL define any such query mechanisms.
> 
> Sanjiva.
Received on Thursday, 1 July 2004 19:51:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:31 GMT