SMPTE RA Submissions

[SteveLLamb]

Per ST meeting(s), high priority - in Release build as artifact.

[SteveLLamb]

Add link to release notes, parse, add as generated link.

note - on the editor of the release to manually add for now.

Exam: https://registry.smpte-ra.org/view/development/proposals/115_FS_2025-01-16--ST2067-201-IMF-IAB-L0-Rev/115_FS_2025-01-16--ST2067-201-IMF-IAB-L0-Rev.202506160700/

[thomasheritage]

Linking to the dated version of the Submission is helpful for tracking edits etc, although note that links like this won't resolve if the Submission is updated (because only the latest version of the Submission can be accessed at https://registry.smpte-ra.org) or gets merged into the Registers. Maybe that's OK.

One option might be to link to the Submission on GitHub (although not everyone will have access to the repo by default, as things stand) e.g.

https://github.com/SMPTE/st2123-registers/tree/1422ba27599cf2c13bd8a7bd58784d76d1c40cae/00_working_docs/proposed_edits_as_xml/proposals/115_FS_2025-01-16--ST2067-201-IMF-IAB-L0-Rev

This is the link given by visiting https://github.com/SMPTE/st2123-registers/tree/master/00_working_docs/proposed_edits_as_xml/proposals/115_FS_2025-01-16--ST2067-201-IMF-IAB-L0-Rev and then clicking the "Copy permalink" button

I'm not sure what would be best.