W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > November 2005

FW: describing a service that returns an image/jpg (for example)

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 14 Nov 2005 14:47:37 -0800
Message-ID: <37D0366A39A9044286B2783EB4C3C4E8BB0ADB@RED-MSG-10.redmond.corp.microsoft.com>
To: <sanjiva@wso2.com>
Cc: <public-ws-desc-comments@w3.org>

Thanks for your comment.  The WS Description Working Group tracked this
as a Last Call comment LC360 [1].  The WG was unable to reach consensus
to add this functionality at this late date, and closed the issue with
no action.

As we plan to go to CR shortly, if we don't hear from you within 10
days, we will assume this satisfies your concern.

[1] http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC360

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Sanjiva Weerawarana
> Sent: Thursday, October 13, 2005 9:47 AM
> To: WS-Description WG
> Subject: describing a service that returns an image/jpg (for example)
> 
> 
> Consider a service that takes a URI and returns a picture.
> 
> Input message:
> 
> <element name="input">
>   <complexType>
>     <sequence>
>       <element name="id" type="xsd:string"/>
>     </sequence>
>   </complexType>
> </element>
> 
> Output message:
> 
> <element name="output">
>   <complexType>
>     <sequence>
>       <element name="image" type="xsd:base64"
>                xmime:expectedContentType="image/*"/>
>     </sequence>
>   </complexType>
> </element>
> 
> Operation:
> 
> <operation name="gimme-image"
>            style="style/iri style/one-binary-thing">
>   <input message="tns:input"/>
>   <output message="tns:output"/>
> </operation>
> 
> Note that the use of the style "style/iri" on /operation effectively
> constrains the input element. The addition of the style
> "style/one-binary-thing" constrains the output schema to be of the
> pattern above: exactly one child in the sequence and it must be
declared
> as xsd:base64 along with the xmime:expectedContentType attribute.
> 
> And now the all important binding:
> 
> <binding name="foo" interface="..">
>   <operation name="gimme-image" whttp:operation="GET"
>         whttp:outputSerialization="image/jpg"/>
> </binding>
> 
> When we document the "one-binary-thing" style we say that that if that
> style is used then the output serialization must be set to something
> that conforms to the expected content type given in the schema.
> 
> This obviously needs to be spec'ized to become real, but is it really
> that simple?
> 
> Sanjiva.
> 
Received on Monday, 14 November 2005 23:00:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:32 GMT