Lorna Jane Mitchell

I don't think anyone is working on it yet, so be my guest! Check the docs https://developer.nexmo.com/concepts/guides/signing-messages and let us know if you have questions

Discussed in the weekly meeting, this is a good change to have, but the wording needs an update as per the suggestions in this thread.

I think we need to put out guidance before we start moving things, in case that makes someone feel they are "doing it wrong" because we rewrote the unwritten processes....

Document that we can make this category of edit (alongside typos and formatting changes) without a version bump, and then go ahead and make it. Am I missing something here?

I'm not sure I have all the context here but re tagging is usually confusing, so I would urge that we try to avoid strategy that needs it

I vote we patch release the 3.x versions instead of updating git tags (this way lies madness, I promise). I thought we were patching 3.0 and 3.1 anyway with clarifications,...

After further discussion, we agreed that the published spec versions should be and remain immutable. We'll fix the links in the next releases, and leave the published ones unchanged.

Yes, that's the plan. "Soon" will be relative, but I'm confident we can improve on the past release cadence.

Fixed in #3723 and #3754 and #3755 (thank you @handrews !) so I'll mark this as resolved.

I would suggest that the rendered HTML is the correct place for most use cases (and this URL is under our control, importantly), perhaps we should link to the source...