Opened 9 years ago

Closed 9 years ago

#281 closed editorial (incorporated)

confusing undefined parameter in media range example

Reported by: julian.reschke@… Owned by: julian.reschke@…
Priority: normal Milestone: 14
Component: p3-payload Severity: Active WG Document
Keywords: Cc:

Description

Karl Dubost reports:

The prose on "section 6.1" about "Accept" [1] is confusing. There is an example to explain that the "Media ranges can be overridden by more specific media ranges or specific media types." The example is:

    If more than one media range applies to a given 
    type, the most specific reference has precedence.  
    For example,

        Accept: text/*, text/html, text/html;level=1, */*

The parameter "level" is being introduced without saying that it is a private parameter (aka not defined anywhere). It is confusing. The reader is suddenly looking for the definition of this parameter. I would add in the prose something along.

    If more than one media range applies to a given 
    type, the most specific reference has precedence.  
    For example, with a private parameter "level", 

        Accept: text/*, text/html, text/html;level=1, */*

Change History (5)

comment:1 Changed 9 years ago by fielding@…

We should just change the parameter to charset and use a more realistic example with q values.

comment:2 Changed 9 years ago by julian.reschke@…

  • Owner set to julian.reschke@…

comment:3 Changed 9 years ago by julian.reschke@…

  • Milestone changed from unassigned to 14

comment:4 Changed 9 years ago by julian.reschke@…

From [1244]:

use a real parameter in Accept param example (see #281)

comment:5 Changed 9 years ago by julian.reschke@…

  • Resolution set to incorporated
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.