- From: Martin Chapman <martin.chapman@oracle.com>
- Date: Thu, 4 Aug 2005 14:09:06 +0100
- To: "'Bjoern Hoehrmann'" <derhoermi@gmx.net>
- Cc: <public-ws-chor-comments@w3.org>
As far as we are concered this is enough text to tell an xpath processor what the "cdl:" prefix relates to. Are we missing something? Martin. >-----Original Message----- >From: public-ws-chor-comments-request@w3.org >[mailto:public-ws-chor-comments-request@w3.org] On Behalf Of >Bjoern Hoehrmann >Sent: Wednesday, August 03, 2005 8:31 PM >To: Martin Chapman >Cc: public-ws-chor-comments@w3.org >Subject: Re: W3C WS-Choreo WG - Issue 964 > > > >* Martin Chapman wrote: >>We discussed this at our con call yesterday: >>http://www.w3.org/2005/08/02-ws-chor-irc >> >>The problem you are citing should be resolved by the text in the 4th >>paragraph of section 5.3: >>http://www.w3.org/2002/ws/chor/edcopies/cdl/cdl.html > >There is just > > WS-CDL defines XPath function extensions as described in the >following > section. The function extensions are defined in the standard WS-CDL > namespace "http://www.w3.org/2005/08/ws-chor/cdl". The prefix "cdl:" > is associated with this namespace. > >This does not define processing of > > <?xml version='1.0'?> > <element xmlns:cdl='... not cdl ...' xpath='cdl:example(...)' /> > >or > > <?xml version='1.0'?> > <element xmlns:foo='http://www.w3.org/2004/12/ws-chor/cdl' > xpath='foo:example(...)' /> > >so no, this does not address my concern. >-- >Björn Höhrmann · mailto:bjoern@hoehrmann.de · >http://bjoern.hoehrmann.de Weinh. Str. 22 · >Telefon: >+49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim >· PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ > >
Received on Thursday, 4 August 2005 13:08:37 UTC