W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2004

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

From: Asir Vedamuthu <asirv@webmethods.com>
Date: Thu, 24 Jun 2004 05:34:22 -0700
Message-ID: <5B10E50E14A4594EB1B5566B69AD94072EF5D7@maileast>
To: 'Hugo Haas' <hugo@w3.org>, David Orchard <dorchard@bea.com>
Cc: Web Services Description <www-ws-desc@w3.org>

> 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]."

[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

-----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
-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Thursday, 24 June 2004 08:36:56 GMT

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