Retiring the main document

[egekorkan]

fixes #433

I am not adding any styling. If we agree with the content, this should be a follow-up PR.

---

Preview | Diff

[netlify]

✅ Deploy Preview for wot-binding-templates ready!

Name	Link
🔨 Latest commit	e3d2a59
🔍 Latest deploy log	https://app.netlify.com/projects/wot-binding-templates/deploys/68b9149096ab820008b89ccd
😎 Deploy Preview	https://deploy-preview-434--wot-binding-templates.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[egekorkan]

This PR should not be merged. We should publish a new "version" of the document that only has an abstract and status section. The text in this PR can be moved into the status section. We note that this is not an official retirement process as it does not apply to note track documents (see that https://www.w3.org/policies/process/#tr-end is only for REC track documents).

[egekorkan]

Now it should be good but we should decide what the abstract should contain. The status already describes what will happen and I have left the abstract intact except for its final paragraph.

[danielpeintner]

LGTM

See one minor thing I am not sure about...

[egekorkan]

TD Call 21.08: @ashimura will talk with @plehegar on the correct wording for retired document as officially there is no retirement for the Note Track documents. Alternatives are "abandoned", "discontinued".

[egekorkan]

Also added changes to take w3c/wot-binding-registry#27 into account

[egekorkan]

Merging as agreed in https://www.w3.org/2025/09/03-wot-minutes.html#e263