ISSUE-3: Allow change in place in /TR
wd-tr-updates
Allow change in place in /TR
- State:
- CLOSED
- Product:
- Document life cycle (pre 2014 chapter 7, now chapter 6)
- Raised by:
- Wayne Carr
- Opened on:
- 2012-03-02
- Description:
- Some suggestions to get the TR publications to be closer to the most recent WG draft:
First Public Working Draft and Last Call Draft cannot be changed after publication because of the patent exclusion period associated with them. (But they can be followed at any time by a regular Working Draft.)
Candidate Rec if it has a substantive conformance changing edit has to go back to Last Call for the exclusion review, so Candidate Recs cannot be edited if it changes conformance. But for edits that don't change conformance, why not allow edits without issuing a different Candidate Rec? (so allow clarifying edits, but carefully indicate what changed after first publication - or even show the edits if the WG wants to).
Proposed Rec - same as Candidate Rec for non-conformance changing edits, except frozen with no edits during AC review where PR has to be stable. (be able to terminate AC review and restart if a needed change would make it irrelevant).
But for regular heartbeat Working Drafts publications in the TR list, why can't they be updated as often as the WG wants to?
(e.g. after the WG publishes a Last Call or Candidate Rec or Proposed Rec, they can keep publishing a regular TR Working Draft update to the TR list as often as they choose - every 2-3 weeks would mean the latest TR pub is close to the latest WG thinking).
Wouldn't that solve the problem of the most recent TR publication being far out of date? Why not make it very simple to publish a WD every few weeks? - Related Actions Items:
- No related actions
- Related emails:
- New Editor's draft, Chapter 7 (from chaals@yandex-team.ru on 2013-10-10)
Related notes:
Could you please explain the problem?
If A makes a reference to B, and B is likely to update, A could have TWO URLs and not just one: (1) which version of B was intended at the time A was last updated? and (2) where to get the 'latest' B, if there is one.
If you're the editor of A, you need to actually look at B if it's been updated and make sure the reference still works.
THis is simple, gives good information to the reviewers, and isn't that hard to implement.
I don't understand what 'updating /TR' solves.
[koalie]: issue is pending review, waiting for the updated TR page currently in progress
17 Sep 2013, 14:58:25[koalie]: SteveZ: summary: from the AB perspective, issue-3 is closed and remains in the CG tracker.
17 Sep 2013, 15:04:10There is a section on changing recommendations, and working drafts can't be changed (but can be re-issued more or less any time, modulo operational restrictions applied by W3C but outside the Process). There will be a section on updating CRs, and I will raise an issue about how it should work.
The rest of this issue seems to be gone...
Display change log
