@Cecile Ludwichowski and
@Dirk Rejahl might have something to say here, as co-leads of the SID team.
I would suggest that you post SID-related queries in the Frameworx community
here.
But my $0.02 - each specific implementation of a catalog needs to decide how to implement its versioning policy, bearing in mind that software may be written to behave in a certain way according to versions, but also bearing in mind the community of users who will be authoring offerings - marketing people - who may not necessarily be au fait with schemes such as
http://semver.org/.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Jan 20, 2020 19:34
From: Greg Herringer
Subject: Offer Versioning
GB 922 gives the following guidance for versioning ProductSpecifications
"As ProductSpecifications are upgraded, and as the market and technology move on, they are subject to version control."
I am not seeing similar guidance at the ProductOffering level.
Does such guidance exist in the TMForum library?
Is it assumed the above good council would naturally extend to ProductOfferings?
In general, is it better to version ProductOfferings or create net new when the ProductOfferings undergo minor changes in the marketplace?
Some context to frame these questions:
There are numerous minor changes an author may make to a ProductOffering that don't warrant a "new ProductOffering":
- minor branding change
- edits to descriptive text
- addition of Characteristics that do not change the value proposition but may be useful for internal processing
- introduction of new CharacteristicValues for Characteristics driving internal processing as described above.
These would ideally be tagged as version changes so that consuming systems can make use of this information as needed. Does this require the systems to track ProductOffering identifiers as well as a versioning scheme or would ANY change result in a new ProductOffering identifier that is somehow linked to its predecessor?
Or is this a "do what you want" scenario?
#TMForumGeneral
------------------------------
Greg Herringer
IBM Canada
------------------------------