httpbis: Ticket #35: Normative and Informative references

Link:  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/35

Component: non-specific

References are now required to be split into "Normative" and "Informative".

Associated Checkins

julian.reschke@gmx.de (Tue, 01 Jan 2008 15:19:52 GMT)
[132]: Resolve #35: References: categorize RFC1766 and RFC2396 as normative (both ...
julian.reschke@gmx.de (Sat, 05 Jan 2008 11:54:39 GMT)
[151]: Categorize reference to RFC1737 as informative (addresses #35)
julian.reschke@gmx.de (Sat, 05 Jan 2008 12:30:13 GMT)
[152]: Resolve #35: categorize RFC1737 (URN) as informative, RFC4288 (media type ...

History

: comment added; owner, component set (Tue, 01 Jan 2008 15:02:49 GMT)

: comment added (Tue, 01 Jan 2008 15:16:27 GMT)

Note that there are several other issues related to this: #44, #45, #46, #55, #65, #66, #68, #86

: comment added (Tue, 01 Jan 2008 15:19:52 GMT)

Some changes in [132]

: comment added; milestone set (Fri, 04 Jan 2008 06:15:57 GMT)

: comment added; version set; owner, status changed (Sat, 05 Jan 2008 01:38:13 GMT)

: comment added; milestone changed (Sat, 05 Jan 2008 03:47:40 GMT)

: comment added; type changed (Sat, 05 Jan 2008 03:48:15 GMT)

: comment added (Sat, 05 Jan 2008 11:54:39 GMT)

From [151]:

Categorize reference to RFC1737 as informative (addresses #35)

: comment added; resolution set; status changed (Sat, 05 Jan 2008 12:30:13 GMT)

Fixed in [152]:

Resolve #35: categorize RFC1737 (URN) as informative, RFC4288 (media type registration procedure) as normative (closes #35). Also update and re-organize media type registration for application/http and message/http to use RFC4288 template (relates to #8).

Related Information

Issues List Index