Warn users that the spec is outdated

[Malvoz]

Because this spec has been merged into the MapML spec (Maps4HTML/MapML-Specification#78), we should add a warning that this is outdated (similar to how it's done here and here), and refer users to the MapML specification instead.

[Malvoz]

@prushforth We'll also have to transfer issues in this repo to the MapML repo! Let me know if I should proceed with that.

[prushforth]

We'll also have to transfer issues in this repo to the MapML repo! Let me know if I should proceed with that.

Done, I believe. Including any of possible future use/value, imho.

[Malvoz]

Nice! I believe it is safe to archive this repository now, making it read-only. That's optional of course, but I don't see any reasons to keep this active.

[prushforth]

If I archive it will it yield a 404? Maybe we should stick a redirect in instead?

[Malvoz]

Here's the Github resources on archiving a repo: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.

It is possible to unarchive a repo once it's been archived: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/archiving-repositories.

[Malvoz]

@prushforth there's an example of an archived repo here: https://github.com/WICG/cross-origin-embedder-policy, and it's still live at https://wicg.github.io/cross-origin-embedder-policy/. It should be safe to go ahead and archive this repo.

[prushforth]

Ok, sounds like a plan.