- From: Steve Tuecke <tuecke@mcs.anl.gov>
- Date: Sat, 29 Jun 2002 08:47:21 -0500
- To: www-ws-desc@w3.org
Section 2.6 Service Description Component states: "A port has a REQUIRED "name" property, which is used to identify this port. The name property MUST be unique across the entire descriptions group in which the containing service description component resides. Note that while the name property is of type NCName, it SHALL NOT be used as the localPart of a qualified name with the targetNamespace of the containing descriptions group as the namespace name." Sorry if I missed this discussion previously, but why is there the restriction on using the name property as the local part of a qualified name? This seems to be a new restriction since WSDL 1.1. There is obviously no need for it to be a qname within the closed universe of WSDL, since nothing else in WSDL needs to refer to a service element. However, if I want to be able to unambiguously refer to a particular service from elsewhere (i.e. some application specific XML), it seems very useful to be able to use the service name as the local part of a qualified name. Also, given this restriction, then what is the point of naming the service at all? What else is that name used for? -Steve
Received on Saturday, 29 June 2002 09:48:20 UTC