[uddi-spec] RE: V2 WSDL file updates for Basic Profile conformance

["Von Riegen, Claus" <claus.von.riegen@sap.com>]

John,

The correct interpretation of the wsdl:import feature led to extensive discussions in the WS-I Basic Profile WG. The observation was that even WSDL 1.1 itself is inconsistent on its usage - while the text says that it is to be used to import other WSDL documents, some examples use it in order to import XML schemas. R2003 was specified in order to disambiguate this interpretation and to promote interoperability.

There was no discussion on the correct interpretation of the xsd:import feature within the wsdl:types section - it is used in order to import XML schemas and nothing else.

So, in order to be on the safe side, my recommendation is to change the UDDI WSDL files. The use of the xsd:import feature in order to import the UDDI XML schema is at least not incorrect.

As for your issue with the schema targetNamespace, I'd be more than happy to omit the targetNamespace at all. I thought that several tools would need it but after several checks, I made the same observation as you - we don't need a targetNamespace for the schema. The schema import already ties the UDDI XML schema to the uddi namespace within the WSDL files.

Please find attached the corrected files.

Any other concerns?

Claus

-----Original Message-----
From: John Colgrave [mailto:colgrave@hursley.ibm.com]
Sent: Mittwoch, 4. Dezember 2002 12:11
To: Von Riegen, Claus; Andrew Hately; Patrick Felsted
Cc: UDDI Spec TC (E-mail)
Subject: Re: V2 WSDL file updates for Basic Profile conformance


Claus,

I am not convinced that WS-I have made the right decision on this whole
issue and am in the middle of discussing this with one of the IBM folks more
closely involved in WS-I than I.

I am a little concerned that we are trying to rush through changes as part
of the V2 submission that correspond to what is only a Working Group Draft
of the WS-I Basic Profile.

I am not sure that the right thing to do is to declare the same
targetNamespace on the schema as the WSDL definitions has.  I did try a
similar change with one of the V3 WSDL files without any targetNamespace on
the schema and that seemed to go through the tools we use OK.

John
----- Original Message -----
From: "Von Riegen, Claus" <claus.von.riegen@sap.com>
To: "Andrew Hately" <hately@us.ibm.com>; "Claus von Riegen"
<claus.von.riegen@sap.com>; "John Colgrave" <colgrave@hursley.ibm.com>;
"Patrick Felsted" <pfelsted@novell.com>
Cc: "UDDI Spec TC (E-mail)" <uddi-spec@lists.oasis-open.org>
Sent: Wednesday, December 04, 2002 10:37 AM
Subject: V2 WSDL file updates for Basic Profile conformance


> Andrew, John and Patrick, cc: UDDI Spec TC
>
> I took an action item (AR 005) at the last F2F in order to report back on
our findings w.r.t. potential updates of the UDDI WSDL files so that they
conform to the WS-I Basic Profile.
> As Luc correctly pointed out during the F2F, the current UDDI V2 and V3
WSDL files do not conform to the Basic Profile requirement R2003, which
states "A DESCRIPTION MUST only use the XML Schema "import" statement within
the xsd:schema element of the types section." The WSDL files currently use
the
> wsdl:import feature to import the UDDI XML schema.
>
> In order to conform to R2003, the files can easily be changed as follows
(taking the V2 Inquiry WSDL as an example):.
>
> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns="urn:uddi-org:inquiry_v2"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:uddi="urn:uddi-org:api_v2" targetNamespace="urn:uddi-org:inquiry_v2"
name="UDDI_Inquiry_API_V2">
> <import namespace="urn:uddi-org:api_v2"
location="http://www.uddi.org/schema/uddi_v2.xsd"/>
> ...
> </definitions>
>
> <definitions xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns="urn:uddi-org:inquiry_v2"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:uddi="urn:uddi-org:api_v2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
targetNamespace="urn:uddi-org:inquiry_v2" name="UDDI_Inquiry_API_V2">
> <types>
> <xsd:schema targetNamespace="urn:uddi-org:inquiry_v2">
> <xsd:import namespace="urn:uddi-org:api_v2"
schemaLocation="http://www.uddi.org/schema/uddi_v2.xsd"/>
> </xsd:schema>
> </types>
> ...
> </definitions>
>
> That is, the wsdl:import element is removed, an additional namespace for
XML Schema is added and the UDDI V2 schema is imported in the wsdl:types
section.
>
> Please find attached the proposed updates for both V2 WSDL files and tell
me if you observe any errors or inconsistencies
> I'd like to get your feedback on this proposed change as soon as possible
so that we can include the changed files in the UDDI V2 standards
submission.
>
> I suggest that we cover potential changes to the V3 WSDL files separately,
but analogous to our conclusion for V2.
>
> Thanks,
>  Claus
>
>  <<publish_v2_bp.wsdl>>  <<inquire_v2_bp.wsdl>>
>
>
>
>
>
>

Attachment: publish_v2_bp.wsdl
Description: Binary data

Attachment: inquire_v2_bp.wsdl
Description: Binary data