W3C home > Mailing lists > Public > www-ws-desc@w3.org > May 2002

Re: issue: optional parts in <message>?

From: Prasad Yendluri <pyendluri@webmethods.com>
Date: Tue, 07 May 2002 08:28:54 -0700
Message-ID: <3CD7F2B6.2494B8AC@webmethods.com>
To: Jean-Jacques Moreau <moreau@crf.canon.fr>
CC: www-ws-desc@w3.org
Jean-Jacques,

No. I was not referring to what actually goes on the wire (I am aware of MIME, DIME
SOAP messages with Attachments specifications).

The follow-up was on the subject of XML-Schema based representation of binary types
from Mike Deem (in the context of using XML schema for as a potential replacement for
messages at the abstract level). Please see the original message below.

Regards, Prasad

Jean-Jacques Moreau wrote:

> If you are referring to what actually goes on the wire, MIME+HTTP, DIME[1] or
> SOAP+Attachments[2] allow sending the GIF unencoded.
>
> Jean-Jacques.
>
> [1] http://www.ietf.org/internet-drafts/draft-nielsen-dime-01.txt
> [2] http://www.w3.org/TR/SOAP-attachments
>
> Prasad Yendluri wrote:
>
> > I know this is just an example but, here there is a fundamental typing of gif to
> > base64 encoding. I may not want to do any encoding? Is possible to capture binary
> > types without having do either Hex or Base64 encoding?

-------- Original Message --------
Subject: RE: issue: optional parts in <message>?
Resent-Date: Sat, 4 May 2002 00:54:35 -0400 (EDT)
Resent-From: www-ws-desc@w3.org
Date: Fri, 3 May 2002 21:53:40 -0700
From: "Mike Deem" <mikedeem@microsoft.com>
To: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>,"Jeffrey Schlimmer"
<jeffsch@windows.microsoft.com>,<www-ws-desc@w3.org>

It could look like this:

   <xs:complexType name="medical-record">
    <xs:sequence>
     <xs:element name="person-name" type="xs:string"/>
     <xs:element name="head-xray" type="tns:gif"/>
    </xs:sequence>
   </xs:complexType>

   <xs:simpleType name="gif">
    <xs:restriction base="xs:base64Binary">
     <xs:annotation>
      <xs:appinfo>
       <content:mediaType value="image/gif"/>
      </xs:appinfo>
     </xs:annotation>
    </xs:restriction>
   </xs:simpleType>

  == Mike ==

-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
Sent: Fri 5/3/2002 6:49 PM
To: Mike Deem; Jeffrey Schlimmer; www-ws-desc@w3.org
Cc:
Subject: Re: issue: optional parts in <message>?

 "Mike Deem" <mikedeem@microsoft.com> writes:
 > Sorry. I'll get those links fixed. [1] should work. See section 6.
 >
 > In any case, the idea is to use a mediaType annotation element in a
 > restriction on a base64Binary or hexBinary base type. This annotation is
 > used in the style of a facet to constrain the media type of the binary
 > data.

 I know .. I've heard that from others before too. But not being an
 XSD expert I'm not sure I see exactly how that would look. Can you
 please write it down?

 FYI, here's what the 2-item message consisting of a string name and
 an image (say a head xray) would like in WSDL 1.1:

     <message name="medical-record">
         <part name="person-name" type="xsd:string"/>
         <part name="head-xray" mimeType="image/gif"/>
     </message>

 Sanjiva.
Received on Tuesday, 7 May 2002 11:41:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:20 GMT