Opened 11 years ago

Last modified 9 years ago

#326 closed editorial

Ideas for stuff that could go into a Part 0 — at Version 6

Reported by: julian.reschke@… Owned by:
Priority: normal Milestone: unassigned
Component: non-specific Severity: Active WG Document
Keywords: Cc:

Description (last modified by julian.reschke@…)

  • terminology
  • ABNF extensions (list rule)
  • combined ABNF (note that we have less dependencies between the parts than we used to have; maybe it's not useful to do this)
  • all IANA registrations
  • common index
  • HTTP version history (p1 appendix A)
  • Architecture (p1 section 2)
  • possibly parts of p1 section 7
  • acknowledgements?
  • general approach to conformance and error handling

Related to this, if we create a P0, we should also discuss which documents in the set need the "Obsoletes: 2616" disclaimer. All? P1..7? P0?

Change History (6)

comment:1 Changed 11 years ago by julian.reschke@…

  • Description modified (diff)

comment:2 Changed 11 years ago by mnot@…

  • Description modified (diff)

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

  • Description modified (diff)

comment:4 Changed 11 years ago by mnot@…

Another strong argument for a p0 came up in review of James' Prefer draft with the ADs; I-Ds (and other docs) referencing HTTP may now have to use up to seven separate references, which is quite unwieldy. A properly structured p0 would make a single reference possible.

comment:5 Changed 11 years ago by mnot@…

  • Severity changed from Candidate WG Document to Active WG Document

comment:6 Changed 11 years ago by julian.reschke@…

  • Description modified (diff)
Note: See TracTickets for help on using tickets.