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

Ticket #242 (closed design: fixed)

Opened 4 years ago

Last modified 4 years ago

handling of unknown disposition types

Reported by: julian.reschke@gmx.de Owned by: julian.reschke@gmx.de
Priority: normal Milestone: unassigned
Component: content-disp Severity: Active WG Document
Keywords: Cc:
Origin: http:///www.w3.org/mid/1283723895.4459.19.camel@henriknordstrom.net

Description

3.2. Disposition Type

Other disposition types SHOULD be handled the same way as "attachment" (see also [RFC2183], Section 2.8).

Shouldn't that read "Unknown disposition types"? or to be verbosely explicit "Unknown or unhandled disposition types"?

Seems odd to block future extensions like this. RFC2183 also speaks about unknown disposition types, not other.

Change History

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

From [989]:

Rephrase instructions on handling unknown disposition types (see #242)

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

  • Status changed from new to closed
  • Resolution set to incorporated

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

From [990]:

editorial: fix Henrik's last name in credits (see #242)

comment:4 Changed 4 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:5 Changed 4 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed

Closed in last call process.

Note: See TracTickets for help on using tickets.