XSD Schemas - Which Direction

[Modica82]

Hi All,

I am in the process of designing a web service for my company. It is my
first commercial web service, so i think my "Hello World" coding model wont
quite cut it here :). Anyway, i am writing a design document for it, and
want to provide XSD Schema information for XML used.

My question is, do i provide XSD schemas for the XML being passed into the
system, and the XML returned, or do i just do it for the XML being passed in.
Also, how does this work? becuase if the types are serialized and
deserialized at both ends how do i provide a schema for this interaction, i
mean if my method takes in an int, does the WDSL take care of that and the
XSD is only for pure XML being passed in? Sorry if this makes no sence, i am
trying to get the story 100% so i know what i am doing.

Any advice would be great.

Thanks,

Rob

[Dino Chiesa [Microsoft]]

> do i provide XSD schemas for the XML being passed into the

system, and the XML returned, or do i just do it for the XML being passed
in.
Yes, both.

You should think of your service interface as message-based. The service
accepts a message and then (optionally) responds with a message. The schema
should describe what the message looks like. If you want to send only an
int, fine, but your design should wrap that in a message.

You can use the XML Schema designer in VS2003 to help you build the schema.
Other tools also work, of course. Or, if you're schema-savvy, you can use a
text editor and write it by hand.

check this out:
http://weblogs.asp.net/klaus.aschenb...25/247249.aspx

-D
"Modica82" <Mo******@discussions.microsoft.com> wrote in message
news:55**********************************@microsof t.com... Hi All,

I am in the process of designing a web service for my company. It is my
first commercial web service, so i think my "Hello World" coding model
wont
quite cut it here :). Anyway, i am writing a design document for it, and
want to provide XSD Schema information for XML used.

My question is, do i provide XSD schemas for the XML being passed into the
system, and the XML returned, or do i just do it for the XML being passed
in.
Also, how does this work? becuase if the types are serialized and
deserialized at both ends how do i provide a schema for this interaction,
i
mean if my method takes in an int, does the WDSL take care of that and the
XSD is only for pure XML being passed in? Sorry if this makes no sence, i
am
trying to get the story 100% so i know what i am doing.

Any advice would be great.

Thanks,

Rob

[Modica82]

Hi Dino,

Thanks for the response and the link, it spured me to look at an existing
document i passed over, the link is below if anyone is interested.

http://msdn.microsoft.com/msdnmag/is...ervicesDesign/

I have a question though, if i have several messages that say return a
boolean, can i generate a generic response and specify that all method
responses that return a boolean are controlled by my genericBooleanResponse
or genericIntegerResponse etc etc or would it be better to define a different
response for all methods??

Any input would be good,

Regards,

Rob

"Dino Chiesa [Microsoft]" wrote:

do i provide XSD schemas for the XML being passed into the
system, and the XML returned, or do i just do it for the XML being passed
in.

Yes, both.

You should think of your service interface as message-based. The service
accepts a message and then (optionally) responds with a message. The schema
should describe what the message looks like. If you want to send only an
int, fine, but your design should wrap that in a message.

You can use the XML Schema designer in VS2003 to help you build the schema.
Other tools also work, of course. Or, if you're schema-savvy, you can use a
text editor and write it by hand.

check this out:
http://weblogs.asp.net/klaus.aschenb...25/247249.aspx

-D
"Modica82" <Mo******@discussions.microsoft.com> wrote in message
news:55**********************************@microsof t.com...

Hi All,

I am in the process of designing a web service for my company. It is my
first commercial web service, so i think my "Hello World" coding model
wont
quite cut it here :). Anyway, i am writing a design document for it, and
want to provide XSD Schema information for XML used.

My question is, do i provide XSD schemas for the XML being passed into the
system, and the XML returned, or do i just do it for the XML being passed
in.
Also, how does this work? becuase if the types are serialized and
deserialized at both ends how do i provide a schema for this interaction,
i
mean if my method takes in an int, does the WDSL take care of that and the
XSD is only for pure XML being passed in? Sorry if this makes no sence, i
am
trying to get the story 100% so i know what i am doing.

Any advice would be great.

Thanks,

Rob

[Dino Chiesa [Microsoft]]

What you describe makes sense. No problem with that.
-D

"Modica82" <Mo******@discussions.microsoft.com> wrote in message
news:A0**********************************@microsof t.com...

Hi Dino,

Thanks for the response and the link, it spured me to look at an existing
document i passed over, the link is below if anyone is interested.

http://msdn.microsoft.com/msdnmag/is...ervicesDesign/

I have a question though, if i have several messages that say return a
boolean, can i generate a generic response and specify that all method
responses that return a boolean are controlled by my
genericBooleanResponse
or genericIntegerResponse etc etc or would it be better to define a
different
response for all methods??

Any input would be good,

Regards,

Rob

"Dino Chiesa [Microsoft]" wrote:

> do i provide XSD schemas for the XML being passed into the
> system, and the XML returned, or do i just do it for the XML being
> passed
> in.

Yes, both.

You should think of your service interface as message-based. The
service
accepts a message and then (optionally) responds with a message. The
schema
should describe what the message looks like. If you want to send only an
int, fine, but your design should wrap that in a message.

You can use the XML Schema designer in VS2003 to help you build the
schema.
Other tools also work, of course. Or, if you're schema-savvy, you can
use a
text editor and write it by hand.

check this out:
http://weblogs.asp.net/klaus.aschenb...25/247249.aspx

-D
"Modica82" <Mo******@discussions.microsoft.com> wrote in message
news:55**********************************@microsof t.com...

> Hi All,
>
> I am in the process of designing a web service for my company. It is
> my
> first commercial web service, so i think my "Hello World" coding model
> wont
> quite cut it here :). Anyway, i am writing a design document for it,
> and
> want to provide XSD Schema information for XML used.
>
> My question is, do i provide XSD schemas for the XML being passed into
> the
> system, and the XML returned, or do i just do it for the XML being
> passed
> in.
> Also, how does this work? becuase if the types are serialized and
> deserialized at both ends how do i provide a schema for this
> interaction,
> i
> mean if my method takes in an int, does the WDSL take care of that and
> the
> XSD is only for pure XML being passed in? Sorry if this makes no
> sence, i
> am
> trying to get the story 100% so i know what i am doing.
>
> Any advice would be great.
>
> Thanks,
>
> Rob