- From: Christopher B Ferris <chrisfer@us.ibm.com>
- Date: Thu, 10 Jan 2008 15:14:30 -0500
- To: Paul Cotton <Paul.Cotton@microsoft.com>
- Cc: "public-ws-policy@w3.org" <public-ws-policy@w3.org>, public-ws-policy-request@w3.org, "tvanlessen@taval.de" <tvanlessen@taval.de>
- Message-ID: <OF60721293.533F74EF-ON852573CC.006EE5F0-852573CC.006F02C8@us.ibm.com>
+1 Christopher Ferris STSM, Software Group Standards Strategy email: chrisfer@us.ibm.com blog: http://www.ibm.com/developerworks/blogs/page/chrisferris phone: +1 508 234 2986 public-ws-policy-request@w3.org wrote on 01/09/2008 01:34:19 PM: > > We have received the following public comment on the WSDL 1.1 > Element Identifiers WG Note [2]. > > Note that the comment actually refers to [1] which is an Editor's > CVS version of the spec. But I believe the comment applies to the > published WG Note at [2]. > > > I'm wondering whether the second parameter ('operation') in > operation binding references should be really a QName. Shouldn't it > be a NCName? > > The examples are also referring to NCName, like http://...#wsdl11. > bindingOperation(TicketAgentSoap/listFlights) > > Here is my initial reaction: > > Table 2-1. "Rules for determining pointer parts for WSDL 1.1 > elements" [3] in the WSDL 1.1 Element Identifiers WG Note [2] and > the type of the second parameter is based on Table A-1. "Rules for > determining pointer parts for WSDL 2.0 components" from WSDL 2.0 [4]. > > In particular the WSDL 2.0 table [4] defines the operation parameter > for the binding references (e.g Binding Fault, Binding Operation, > Binding Message Reference, and Binding Fault Reference) as QName. > Since our table is based on the WSDL 2.0 table, I believe that we > defined the second parameter's type as QNAME to match what was done > in the WSDL 2.0 table [4]. > > If the commenter is correct then I believe this matter needs to be > first taken up as a comment on the WSDL 2.0 specification. > > Comments. > > /paulc > > [1] http://dev.w3.org/cvsweb/%7Echeckout% > 7E/2006/ws/policy/wsdl11elementidentifiers.html?content- > type=text/html;%20charset=utf-8#frag-ids > [2] http://www.w3.org/TR/2007/NOTE-wsdl11elementidentifiers-20070720/ > [3] http://www.w3.org/TR/2007/NOTE-wsdl11elementidentifiers-20070720/#frag-ids > [4] http://www.w3.org/TR/2007/REC-wsdl20-20070626/#frag-ids > > Paul Cotton, Microsoft Canada > 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 > Tel: (425) 705-9596 Fax: (425) 936-7329 > > > -----Original Message----- > From: public-ws-policy-qa-request@w3.org [mailto:public-ws-policy- > qa-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org > Sent: Friday, January 04, 2008 10:55 AM > To: public-ws-policy-qa@w3.org > Subject: [Bug 5346] Operation parameter in bindingOperation is of type QName > > > http://www.w3.org/Bugs/Public/show_bug.cgi?id=5346 > > Summary: Operation parameter in bindingOperation is of type QName > Product: WS-Policy > Version: PR > Platform: PC > URL: http://dev.w3.org/cvsweb/%7Echeckout%7E/2006/ws/policy/w > sdl11elementidentifiers.html?content- > type=text/html;%20charset=utf-8#frag-ids > OS/Version: Windows XP > Status: NEW > Severity: normal > Priority: P2 > Component: WSDL1.1-Element-Identifiers > AssignedTo: fsasaki@w3.org > ReportedBy: tvanlessen@taval.de > QAContact: public-ws-policy-qa@w3.org > > > I'm wondering whether the second parameter ('operation') in operation binding > references should be really a QName. Shouldn't it be a NCName? > > The examples are also referring to NCName, like > http://...#wsdl11.bindingOperation(TicketAgentSoap/listFlights) > >
Received on Thursday, 10 January 2008 20:14:52 UTC