Il 19/06/2026 18:54, Pawel Kowalik ha scritto:
Hi Mario,
On 19.06.26 18:47, Mario Loffredo wrote:
[ML] This is an example of how the given backward-incompatible change
can be handled by changing the extension identifier, thus maximizing
the scope of the change.
In both cases, a transition must be managed to deprecate an extension
feature. However, in the first example, the transition aims to
deprecate risk_ext.score; in the second example, the transition aims
to deprecate the entire risk_ext member (and any other extension
features).
Deprecation of risk_ext.score without change of extension identifier
is a complex decision, as in fact it would be breaking for unaware
client so in fact would again require a change of extension identifier.
Why would it break clients ?
What would be the difference between deprecating risk_ext1 in favor of
risK_ext2 and deprecating risk_ext.score by adding
risk_ext.normalizedScore and then managing the transition from
risk_ext.score to risk_ext.normalizedScore ?
Best,
Mario
Kind Regards,
Pawel
--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
Address: Via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
