Instantiation of such a characteristic addresses your other question. In your example:
A CharacteristicSpecification of the ProdSpecRelationship defines the options of required bandwidth, and an instantiation will define the bandwidth that is actually selected for the specific instance of TVProd.
Original Message:
Sent: Dec 06, 2023 11:06
From: Matthieu Hattab
Subject: Characteristic array under Relationship pattern in version 5 of TMF APIs
the product in the inventory has a reference to the Product Specification:

you can query that product spec with TMF620 V5 and then you can see the productspecificationrelationship and the characteristic that refines the
relationship.
I'm not sure the characteristic that refines the relationship should be instanciated in the product inventory. That characteristic is used to enforce a business rule.
if possible we should keep the api payload as lean as possible.
Why do you need it for?
------------------------------
Kind regards,
Matthieu Hattab
Lyse Platform
Original Message:
Sent: Dec 06, 2023 06:31
From: Opher Yaron
Subject: Characteristic array under Relationship pattern in version 5 of TMF APIs
I am coming back to my original question.
Thank you, @Jonathan Goldberg, for the information.
This JIRA (https://projects.tmforum.org/jira/browse/AP-2928) is indeed related, but seems to be more focused on the RelationshipCharacteristicSpecification in TMF620 than on the RelationshipCharacteristic in TMF637.
The only reference to TMF637 I can find there is this comment at the end:

But I find it confusing, because, as I wrote in my original post, the Swagger of TMF637 does NOT contain RelationshipCharacteristic.
@Matthieu Hattab - with regards to your message: "The inventory API already has references to the Product Offering and Product Specifications, so one could easily find the PS relationships from the product catalogue." I do not exactly understand what you mean. The way I understand it, the common pattern is to have all specifications in Catalog Management, and all instances in Inventory Management. For example, you can have RelatedEntitySpecification in some catalog, and RelatedEntity in the corresponding Inventory. Shouldn't it be the same with RelationshipCharacteristicSpecification/RelationshipCharacteristic?
------------------------------
Opher Yaron
Proximus SA
Original Message:
Sent: Nov 26, 2023 08:24
From: Jonathan Goldberg
Subject: Characteristic array under Relationship pattern in version 5 of TMF APIs
I looked further into this, there is an existing JIRA for this waiting to be executed.
https://projects.tmforum.org/jira/browse/AP-2928
------------------------------
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: Nov 26, 2023 07:46
From: Jonathan Goldberg
Subject: Characteristic array under Relationship pattern in version 5 of TMF APIs
It should probably be added to the inventory API, thanks for the catch Opher.
------------------------------
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: Nov 24, 2023 08:00
From: Opher Yaron
Subject: Characteristic array under Relationship pattern in version 5 of TMF APIs
Hello,
The question is whether version 5 of the APIs intends to contain a Characteristic array under the Relationship pattern.
I reviewed one pair of APIs that already have version 5 in Production - TMF620 Product Catalog and TMF637 Product Inventory.
In the Swagger of TMF620 I find:

In particular, ProductSpecificationRelationship contains a "characteristic" attribute of type CharacteristicSpecification.
However, in the Swagger of TMF637 I find:

In particular, ProductRelationship does not contain a "characteristic" attribute.
The two specifications seem incompatible to me. Do I miss something? If not, which one of these 2 APIs is 'correct'?
Thank you and best regards,
------------------------------
Opher Yaron
Proximus SA
------------------------------