RE: [uddi-spec] WSDL TN: Issue 5 - identification of port

[Anne Thomas Manes <anne@manes.net>]

Regarding targetNamespaces:

I'm not an XML Schema expert, but from my interpretation of the WSDL schema,
the only places where you can specify a targetNamespace is on the
<definitions> element and on a <schema> element within the <types> element.
Therefore I don't think that it's possible for two ports within the same
WSDL file to belong to different namespaces.

Anne


> -----Original Message-----
> From: John Colgrave [mailto:colgrave@hursley.ibm.com]
> Sent: Wednesday, November 20, 2002 9:42 AM
> To: uddi-spec
> Subject: [uddi-spec] WSDL TN: Issue 5 - identification of port
>
>
>
> I think I have already covered at least part of this in one of the earlier
> notes.  One reason for requiring the namespace name and local name in the
> UDDI metadata is so that equivalent deployment WSDL can be
> generated by two
> independent tools.
>
> The local name is also required in the wsdlDeployment case where a service
> has more than one port and only the base URL of the deployment
> WSDL file is
> in UDDI, that is, we are not using XPointer.
>
> I am not sure that you cannot define more than one targetNamespace in a
> single WSDL file so the namespace may also be required to
> uniquely identify
> the correct service/port in the wsdlDeployment case also.
>
> We could choose not to categorise the bindingTemplate with the port
> namespace in the V3 model, but at the cost of requiring the containing
> service to be retrieved to find it.
>
> John
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>