users@jax-rs-spec.java.net

[jax-rs-spec users] [jsr339-experts] Some issues with section 3.7.2

From: Sergey Beryozkin <sberyozkin_at_talend.com>
Date: Mon, 8 Apr 2013 17:06:21 +0100

Hi Santiago, All,

I have some difficult time reading the section 3.7.2, specifically, the
3.7.2/3/b part, it starts from

(1)

"If after filtering the set M has more than one element, sort it in
descending order as follows. Let
a client media type be of the form n/m;q=v1 , a server media type be of
the form n/m;qs=v2 and
a combined media type of the form n/m;q=v1 ;qs=v2 ;d=v3 , where the
distance factor d is defined
below."

and then it mentions, after specifying the terms:

(2)

"Given these definitions, we can now sort M in descending order based on
≥ as follows7 :
• Let t be the request content type and CM a resource method’s @Consumes
set of server
media types, we use the media type max≥ {S(t, c) | (t, c) ∈ {t} × CM }
as primary key.
"

Now, given that a 'qs' factor comes into consideration only when a
client Accept values are checked against @Produces values, why have we
defined a combined media type in (1) as having 'qs' and then presumably
using that combined media types in (2), when referring to @Consumes ?

Thanks, Sergey