Thanks Matthieu for your input
I would be hesitant to create such a linkage. Product specifications presumably describe "real" products that have some existence (and can be instantiated to the inventory).- Grouping characteristics seems to be a more abstract, perhaps nebulous, concept.
Taking your example of a car - the engine could certainly be modeled with a product spec, it is a separately identifiable component of the car. But other items (color, interior) seem to me to belong to the parent car product spec.
------------------------------
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 23, 2022 06:57
From: Matthieu Hattab
Subject: Grouping Characteristics
This may sound too simple to be true but is this grouping of characteristics one role of ProductSpecifications?
A ProductSpecification is a collection of characteristics. you can dedicated each ProductSpecification to any grouping you want. It also helps organize your UI by grouping characteristics in a logical way.
I remember we discussed it in a TMF meeting years ago with an example of a toyota Yaris.
The car can have a composite productspec (toyotayarisproductspec) made of atomic productspec. Each atomic productspec is dedicated to a car set of customization (colour, engine, interior etc) so you bundle productspecs.
Matthieu
------------------------------
Matthieu Hattab
Altibox AS
Original Message:
Sent: May 20, 2022 05:57
From: Sergey Lukin
Subject: Grouping Characteristics
Hi, in many APIs we use pattern Characteristics-value, is any "standard" way for grouping such characteristic?
for example some characteristics related to quality, and some to user-faced properties of productOffer.
------------------------------
Sergey N Lukin
Deutsche Telekom (Tel-IT)
------------------------------