W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2006

Re: Endpoint component {name} property vs xml representation as a QName

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Wed, 14 Jun 2006 10:46:53 -0400
To: "Jeremy Hughes" <hughesj@apache.org>
Cc: www-ws-desc@w3.org, www-ws-desc-request@w3.org
Message-ID: <OFCD7CEE73.2078B636-ON8525718D.0050146F-8525718D.00513A8B@ca.ibm.com>

That looks like a copy and paste error. As you correctly state, an enpoint 
is uniquley identified by the Service QName and the Endpont NCName [1]


Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca

"Jeremy Hughes" <hughesj@apache.org> 
Sent by: www-ws-desc-request@w3.org
06/14/2006 10:17 AM


Endpoint component {name} property vs xml representation as a QName


Section 2.15.1 makes this statement:

"Endpoint components are local to a given Service component; they
cannot be referred to by QName"

but then the XML representation section ( says:

"The name attribute information item together with the targetNamespace
attribute information item of the description element information item
forms the QName of the endpoint."

surely this is inconsistent. What use is the targetNamespace of the
name attribute if it isn't exposed in the component model? In any case
you can't refer to an endpoint component uniquely by way of a QName -
you need a service component {name} (a QName) and the endpoint
component {name} (an NCName).

Received on Wednesday, 14 June 2006 16:30:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:59 UTC