Opened 8 years ago

Closed 8 years ago

#75 closed defect (fixed)

Historical registrations and RFC 2119 lang

Reported by: evnikita2@… Owned by: masinter@…
Priority: minor Milestone:
Component: 4395bis Version:
Severity: - Keywords:



Section 5:

Any scheme that is no longer in common use MAY be designated as

I suppose "SHOULD" is more appropriate here. But RFC 2119 might also be
inappropriate to be used here as well, and "should" may be OK as well.

Change History (4)

comment:1 Changed 8 years ago by stpeter@…

I suggest "Any scheme that is no longer in common use can be designated as historical".

comment:2 Changed 8 years ago by masinter@…

What I'd like to do is a broader change, such that the IANA URI/IRI scheme registry had a column 'status', and that the Status could be Provisional, Permanent, Historical, rather than two registries (one Provisional, one Permanent)

and that a request to change the Status was a matter of expert review, and could be initiated by anyone. This would allow a 'Historical' status by expert review, without moving things around.

I'll work on wording changes to accomplish this.

comment:3 Changed 8 years ago by masinter@…

  • Owner set to masinter@…
  • Status changed from new to assigned

comment:4 Changed 8 years ago by masinter@…

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

Edits made a few weeks ago have these in it, will appear on next ID.

Note: See TracTickets for help on using tickets.