Opened 14 years ago

Closed 13 years ago

#35 closed editorial (fixed)

Normative and Informative references

Reported by: mnot@… Owned by: fielding@…
Priority: Milestone: 01
Component: non-specific Severity:
Keywords: Cc:

Description

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

Change History (9)

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

  • Component set to non-specific
  • Owner set to julian.reschke@…

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

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

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

Some changes in [132]

comment:4 Changed 13 years ago by mnot@…

  • Milestone set to unassigned

comment:5 Changed 13 years ago by fielding@…

  • Owner changed from julian.reschke@… to fielding@…
  • Status changed from new to assigned
  • version set to 00-draft

comment:6 Changed 13 years ago by fielding@…

  • Milestone changed from unassigned to 01

comment:7 Changed 13 years ago by fielding@…

  • Type changed from design to editorial

comment:8 Changed 13 years ago by julian.reschke@…

From [151]:

Categorize reference to RFC1737 as informative (addresses #35)

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

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

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).

Note: See TracTickets for help on using tickets.