* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #281 (closed editorial: incorporated)

Opened 4 years ago

Last modified 4 years ago

confusing undefined parameter in media range example

Reported by: julian.reschke@gmx.de Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 14
Component: p3-payload Severity: Active WG Document
Keywords: Cc:
Origin: http:///www.w3.org/mid/F17EFCAF-1A19-4E41-9B5A-54CB5E70C019@opera.com

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

comment:1 Changed 4 years ago by fielding@gbiv.com

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

comment:2 Changed 4 years ago by julian.reschke@gmx.de

  • Owner set to julian.reschke@gmx.de

comment:3 Changed 4 years ago by julian.reschke@gmx.de

  • Milestone changed from unassigned to 14

comment:4 Changed 4 years ago by julian.reschke@gmx.de

From [1244]:

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

comment:5 Changed 4 years ago by julian.reschke@gmx.de

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