On Fri, Aug 7, 2015 at 9:23 AM, Travis Leithead
<travis.leith...@microsoft.com> wrote:
> This is, at a minimum, incremental goodness. It's better than leaving the 
> prior L1 published document around--which already tripped up a few folks on 
> my team recently. I strongly +1 it.

There are alternatives!  In particular, you can publish a gravestone
revision.  Bikeshed has boilerplate for this you can steal the wording
of:

```
<details open class='annoying-warning'>
  <summary>This Document Is Obsolete and Has Been Replaced</summary>
  <p>
    This specification is obsolete and has been replaced by the
document at <a href="[REPLACEDBY]">[REPLACEDBY]</a>.
    Do not attempt to implement this specification.
    Do not refer to this specification except as a historical artifact.
</details>
```

Just publish a new WD containing *only* that as the content, and
you're golden.

For bonus points, publish revisions of all the dated webidl1 specs,
with that as an actual warning (no need to wipe out their contents).
Look at the styling of the message on
<https://tabatkins.github.io/specs/respimg/> for a good example that
makes it impossible to miss that you're looking at an obsolete spec.

~TJ

Reply via email to