Sorry for replying on the old thread. While i was going through this thread, i find it a little difficult to correlate between your explanation here and TMF620 List Product Specifications API.
Screenshots from the doc regarding this API:
Product Specification with isBundle = true
And it has list of product specifications.
As against my understanding, it (bundling product specification) has product characteristics attached to it. As per what i understand from your previous explanation, bundling product specification is just a virtual entity that groups bundled product specifications and these bundled product specifications are nothing but simple/atomic product specifications which has characteristics attached to it.
My another question is, when to use composite product specification vs product specification relation.
Can you shred some light on these items please ?
Sorry for replying on the old thread
what thread? it looks like you created a new post.
Regarding your interpretation of modeling characteristics, I agree that a composite ProductSpec (incorporating product characteristics, service spec, and resource spec) seems counterintuitive. An analogy from the "GB922 - Product" Information Model's product offering composite pattern might clarify this:
A BundledProductOffering is not directly associated with any ProductSpecification. Instead it contains ProductOfferings, each of which may in turn be a SimpleProductOffering that is associated with a ProductSpecification,
I'd expect the composite ProductSpec to align with this concept. Also, reviewing the conformance profile for the API might shed light on existing rules for the composite pattern.
the entity relationships pattern has more use cases at product offering level (static upsell etc) than at product spec levelMy 2 cents.
Thanks for your insights.
Sorry, i was actually referring to https://engage.tmforum.org/communities/community-home/digestviewer/viewthread?GroupId=31&MessageKey=0f0eb1a8-058a-495e-8668-482135f77492&CommunityKey=d543b8ba-9d3a-4121-85ce-5b68e6c31ce5&ReturnUrl=%2fbrowse%2fallrecentposts