Re: [regrep] V2 Spec Issues w/ WSDL Files

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Joel,

Comments inline below:

"Munter, Joel D" wrote:

> Farrukh,
>
> You are in fact using xsd1 for something entirely different.

Yes on closer inspection you are right xsd1 is for a different namespace than
XML Schema.

>
>
> Within registry.wsdl, you have the following already defined:
>         xmlns:xsd1="urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.0"
>
> Please separate the CVS comment from the XSD one.  Albeit, one was trivial,
> there were two issues here.

Logged as:

issue_num: 158
creation_date: 3/11/2002
category: WSDL
Priority: 3
is_resolved: No
description: Need to remove CVS comment.
resolution:
general_notes:
originator: Joel Munter
reported_version: CVS v 1.14
is_closed: No
resolution_version:

BTW I think we need the CVS comment. As you can see it is quite useful in
pinning down the exact version of the
file that the issue was logged on. I think we can minimize the information
recorded to the CVS version number.
I do not agree in retrospect that we should remove the version comment all
together. I agree that it should be limited
to version info only.

>
>
> Joel
>
> -----Original Message-----
> From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM]
> Sent: Monday, March 11, 2002 5:26 PM
> To: Munter, Joel D
> Cc: 'Oasis Registry TC'; 'Oasis Cooperating Registries'
> Subject: Re: [regrep] V2 Spec Issues w/ WSDL Files
>
> Joel,
>
> You are correct. The declaration declares xsd1 as the namespace prefix but a
> couple of places use xsd instead of xsd1.
> I have logged a new issue as follows:
>
> issue_num: 157
> creation_date: 3/11/2002
> category: WSDL
> Priority: 1
> is_resolved: No
> description: Registry.xsd does not declare namespace xsd but has refeernces
> to
> it. Need to remove CVS comment.
> resolution:
> general_notes
> reported_version: CVS v 1.14
> is_closed: No
> resolution_version:
>
> Thanks for finding this. We need to start an errata document to document and
> communicate issues like this. Lets make that a topic
> for next team meeting.
>
> --
> Regards,
> Farrukh
>
> "Munter, Joel D" wrote:
>
> > V2 Spec ISSUE 1) I am doing some validation of the V2 spec material and
> > tested the SOAPBinding WSDL file with a good validator.  Here is the error
> > that I received.
> >
> > <WsdlResults xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns="http://microsoft.com/net/wsdlverify">
> > 1234567890123456789012345678901234567890123456789012345678901234
> >          1         2         3         4         5         6
> >         <StandardOutput>Microsoft (R) Web Services Description
> >                 Language Utility [Microsoft (R) .NET Framework,
> >                 Version 1.0.3612.0] Copyright (C) Microsoft
> >                 Corporation 1998-2001. All rights reserved.
> >                 If you would like more help, please type "wsdl /?".
> >         </StandardOutput>
> >         <ErrorOutput>Error: There was an error processing
> >
> 'http://www.oasis-open.org/committees/regrep/documents/2.0/services/Registry
> > SOAPBinding.wsdl'.
> >                 - The document was understood, but it could
> >                   not be processed.
> >                 - The WSDL document contains links that could
> >                   not be resolved.
> >                 - There is an error in XML document (21, 26).
> >                 - Namespace prefix 'xsd' is not defined.
> >         </ErrorOutput>
> >         <ErrorHints>I was unable to diagnose why this WSDL
> >                 didn't work. You may want to verify that you
> >                 are using the 2001 XSD Schema (although this
> >                 isn't required by the WSDL spec, it is the
> >                 only schema version supported by many SOAP
> >                 SDKs.
> >         </ErrorHints>
> > </WsdlResults>
> >
> > The problem is that "xsd:" is referenced within the registry.wsdl but the
> > xsd namespace is never properly declared within the header of either file.
> >
> > e.g., the following which occurs several times with Registry.wsdl fails:
> >         <part name="content" type="xsd:any"/>
> > The fix is to declare the xsd namespace within the header.
> >
> > ----------------------------------------------------------------
> >
> > V2 Spec Issue 2) Even though some of this is a comment, we should remove
> the
> > following also.
> >
> > <!--xmlns:xsi = "http://www.w3.org/2000/10/XMLSchema-instance"
> > xsi:schemaLocation = "http://schemas.xmlsoap.org/wsdl/
> > file:///C:/jsews/ebxmlrr-spec/misc/schema/wsdl.xsd"-->
> >
> > <documentation>$Header:
> > /cvsroot/ebxmlrr/ebxmlrr-spec/misc/services/RegistrySOAPBinding.wsdl,v
> 1.14
> > 2001/12/02 15:59:11 farrukh_najmi Exp $
> > This is the the normative concrete SOAP/HTTP binding for the OASIS ebXML
> > Registry services.</documentation>
> >
> > Thanks,
> > Joel Munter
> > Distributed Systems, Intel Labs
> > joel.d.munter@intel.com
> > (480) 552-3076
> > (602) 790-0924 (cell)
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.oasis-open.org/ob/adm.pl>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

--
Regards,
Farrukh