Thank you Jonathan. I wish we had a better answer. Also, Upgrade document doesn't has a section for : What was changed or change control info in the beginning.
This shall help a lot, each time you upgrade to highlight major changes.
Original Message:
Sent: Aug 11, 2024 02:47
From: Jonathan Goldberg
Subject: v4 to v5 migration
Hi Amitesh
As a general observation, in any software design and development there is a fine balance between preserving the current and improving the new. Of course I cannot speak officially for TM Forum, but you will understand perhaps that a backlog of design defects and improvements has built up, and a major version is the opportunity to roll these out. By definition, a major version can break compatibility (see https://semver.org/). It is then up to adopting organizations to decide whether and when to adopt the new version.
I cannot answer your specific queries on Service Problem, but in general the characteristic pattern was improved by making the value strongly-typed and having concrete subclasses for different types (e.g. NumberCharacteristic, StringCharacteristic)
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: Aug 09, 2024 17:25
From: Amitesh Gupta
Subject: v4 to v5 migration
Hi @Jonathan Goldberg,
Our project has few TMF656 Open API implementation in v4.0.0. We are also doing a feasibility study of whether we need to migrate to 5.0.
During Feasibility, We are finding following obstacles when upgrading the Resource Model from V4.0.0 to V5.0.0, which is breaking our existing implementation:
1.In V4.0.0, ServiceProblem.relatedEntity is 0-to-*. Which means it is optional and may have 1 to many relationship between ServiceProblem and relatedEntity. It is basically an Array type
In V5.0.0, ServiceProblem.relatedEntity was 0-to-1. Which means it is still optional but may have 1 to 1 relationship between ServiceProblem and relatedEntity. It is now no more an array type and ServiceProblem can have only upto 1 relatedEntity
2. In V4.0.0, Characterstics has a property named value. It has been removed from V5.0.0
3. In V4.0.0, Affected Location is referring to related Place which is renamed to RelatedPlaceRefOrValue in V5.0.0. And the id field has been removed.
4. Similarly, the id field has been removed form originator Party, affected Location, responsible Party
Please suggest why these major changes were made and how we can fix these without breaking our existing working software. We'll end up breaking if we migrate to 5.0.0.0 version. thanks
------------------------------
Amitesh Gupta
Comcast Technology Solutions
Original Message:
Sent: May 06, 2024 08:21
From: Jonathan Goldberg
Subject: v4 to v5 migration
Hi Sajeev
We have an internal page, so anyone who is a member of the Open API project can view it here:
https://projects.tmforum.org/wiki/display/AP/Open+API+Changes+Between+v4+and+Gen5
there's also a presentation attached to the page that gives additional insights.
Unfortunately these assets have not been approved for publication at this time, as far as I know.
------------------------------
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: May 02, 2024 23:32
From: Sajeev Sahajanandan
Subject: v4 to v5 migration
Hi All,
Our project has few TMF Open API implementation in v4.0. I am trying to do a feasibility study of whether we need to migrate to 5.0.
In the OPEN API table I could find the specs, swagger and other details.
I am not able to find any release notes for 5.0 that talks about what are all the changes when compared to the previous version 4.0.
Could you please let me know if there is such a document for every open API that talks about the new changes?
------------------------------
Sajeev Sahajanandan
AT&T Inc.
------------------------------