- From: Youenn Fablet <youenn.fablet@crf.canon.fr>
- Date: Thu, 27 Apr 2006 17:49:57 +0200
- To: www-ws-desc@w3.org
- Message-id: <4450E825.3010604@crf.canon.fr>
Hi all,
I have just finished generating the component model dumps of the wsdl
good documents.
I just picked the test-suite.xml file and generated my test script
through XSLT. Fairly quick in fact :-)
Please find attached the results.
Two side notes:
- There is still a problem with 3 testsuite wsdl files
(SchemaLocationFragment-1G/Items.wsdl,
XSImport-2G/reservationItems.wsdl, XSImport-3G/reservationItems.wsdl).
All of these files make reference to XSD data types through QNames but
with a wrong namespace. I have fixed these files locally (type="string"
is now type="xs:string") and produced a dump with these fixed files. I
added the fixed wsdl files in the attached zip file.
- Our implementation still fails on the Import-2G example as it
raises an error when trying to create two components of the same type
with the same ns+name, the reason being that we have not implemented the
component equivalence rules. Anyway, the parser still produces a
component model dump.
I have a process question related to the last point: do we really need
two interoperable implementations for every aspect of the spec, e.g. the
equivalence rules ? Or is it sufficient to document the reasons behind
different behaviors ?
Hope this helps anyway,
Regards,
Youenn
Attachments
- application/x-zip-compressed attachment: documents.zip
Received on Thursday, 27 April 2006 15:50:39 UTC