Rename 'SvgRenderingTemplate2023' type to 'SvgRenderingTemplate'

[dmitrizagidulin]

I strongly feel that we should drop the year from the template type. (it's not a crypto suite, there's no need to denote "freshness" in the type, and we're moving away from years in crypto suites too).

[TallTed]

I'm generally OK with moving away from years, but versioning often matters, even apart from "freshness". Are we certain that SvgRenderingTemplate will never have two competing versions, such that we'll wish there were SvgRenderingTemplateV1 and SvgRenderingTemplateV2 or the like?

[BigBlueHat]

If we're going to version these, the year approach doesn't seem too terrible.

[TallTed]

the year approach doesn't seem too terrible

As long as we're reasonably certain there will never be two versions in one year with a breaking change between them.

[davidlehn]

I don't think the intent with the year suffix was to process with semantic versioning code. Mostly was to give people a general era and sequence idea, but I forget the full reasoning we had years ago. The hope was these types of things change rarely, but there's no harm in adding a 2023v2, 2023B, or similar as needed.

[dmitrizagidulin]

To me, the likelihood of there being two different templates within a year (or even a decade), with the same name, is very low. If one really needs to do a breaking change, just name it something else.

[BigBlueHat]

@dmitrizagidulin SvgRenderingTemplateSorryAboutEarlier? 😁

[dmitrizagidulin]

@dmitrizagidulin SvgRenderingTemplateSorryAboutEarlier? 😁

lol YES! Much better!