Re: expectedMediaType and Accept header syntax (was Re: Action it em: HTTP binding for accepts header and output Serialization.)

Asir Vedamuthu wrote:

>>Actually, we may want to regard this as a bug: 
>>it is desirable to have a syntax for expectedMediaType 
>>compatible with the HTTP Accept header syntax.
>>    
>>
>
>+1 to consider that as a bug (see [1]). According to prose  [2], "The type
>of the expectedMediaType element information item is xs:string. The value of
>the expectedMediaType element is similar to the value allowed for the
>'Accept' header defined by HTTP 1.1 specification, Section 14.1 [IETF RFC
>2616]."
>  
>
Yes, it is a bug as the intent is clear.

>[1] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0246.html
>[2] http://www.w3.org/TR/2004/WD-xml-media-types-20040608/#expectedMediaType
>
>Asir
>
Thanks.

--umit

>
>-----Original Message-----
>From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
>Behalf Of Hugo Haas
>Sent: Thursday, June 24, 2004 8:28 AM
>To: David Orchard
>Cc: Web Services Description
>Subject: expectedMediaType and Accept header syntax (was Re: Action item:
>HTTP binding for accepts header and output Serialization.)
>
>
>* David Orchard <dorchard@bea.com> [2004-06-24 03:59-0700]
>  
>
>>huh.  If the expected media type uses spaces as separators, then this is
>>a different string than the HTTP accept header.  And thus the media type
>>cannot be used to create the accept header.  Voila, problem about
>>relating the two of them is solved, as there is some application
>>specific relationship.
>>    
>>
>
>Actually, we may want to regard this as a bug: it is desirable to have
>a syntax for expectedMediaType compatible with the HTTP Accept header
>syntax.
>
>This can be done simply by making expectedMediaType a comma-separated
>list of expectedMediaTypeItem by using the appropriate regular
>expression, which I'm afraid will be complex.
>
>Also, I just realized that our syntax doesn't accomodate
>accept-params[1].
>
>Regards,
>
>Hugo
>
>  1. http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1
>  
>

-- 
Umit Yalcinalp                                  
Consulting Member of Technical Staff
ORACLE
Phone: +1 650 607 6154                          
Email: umit.yalcinalp@oracle.com