>I have a XSD that describes a standard (IEEE) implementation of a contract
> and related objects. I need to create a web service that implements the
[quoted text clipped - 18 lines]
>
> I'd appreciate any thoughts from anyone who knows more than me about this.
The XSD file isn't enough to specify a web service contract. It may tell you
the shape of the messages, but it can't, for instance, tell you that
operation X accepts messages A and B as parameters, returns C and D as
results, or may produce faults F and G. It can't tell you about the service,
either.
The XSD can be referenced from a WSDL, and the WSDL can be used as input to
WSDL.EXE /SERVER to generate a server stub. You can inherit from this and
create your server.
John
P.S. Some compliance checkers I've used complain about using wsdl:import to
import a schema. Apparently, you're supposed to do something like put an
empty schema in the wsdl:types section, and have that schema include the
real one. Something like that.
I ignored the compliance checker and continued developing my web service
using wsdl:import! I'll "fix" it in a future release.