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

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

From: Jeremy Hughes <hughesj@apache.org>
Date: Wed, 14 Jun 2006 15:17:34 +0100
Message-ID: <adbf02b10606140717x4453571bje1237c66eb11e9d3@mail.gmail.com>
To: www-ws-desc@w3.org


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 14:17:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:58 UTC