With all this valuable discussion on terminology, I think we may have lost the original question by @Nils Boysen.
Nils, please clarify exactly what you mean by domain name in this context. I could guess (perhaps) that you are modeling an internet connectivity product, and your product specification includes a characteristic called domain name. But perhaps you mean something different. Best to provide a full business example for your dilemma (if you can do so without "leaking" IP).
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: Jul 28, 2023 09:17
From: Matthieu Hattab
Subject: Buy ProductOffering - instantiate product bundle now - bundled products later
Hi Lutz,
You are right to mention the API definition:
bundledProductOffering = "A type of ProductOffering that belongs to a grouping of ProductOfferings". Here the bundledProductOffering is the component contained the bundle.
But... a little further in the PDF:
bundledProductOfferingOption = "A set of numbers that specifies the lower and upper limits for a ProductOffering that can be procured as part of the related BundledProductOffering"
Here, BundledProductOffering refer to the bundle, like in the SID definition.
maybe terms and definition can be harmonised in the future.
------------------------------
Kind regards,
Matthieu Hattab
Lyse Platform
Original Message:
Sent: Jul 28, 2023 07:59
From: Lutz Bettge
Subject: Buy ProductOffering - instantiate product bundle now - bundled products later
I think the definitions you give refer to the SID classes, differentiating whether the ProductOffering has subordinate ProductOfferings or not.
In OpenAPI TMF620, the "BundeldProductOffering" is something different, it is NOT "a grouping of ProductOfferings" that has subordinate ProductOfferings, but it is a reference to one ProductOffering that is made available as part of a bundle, which is represented by the parent ProductOffering.
So it is not something that bundles, but it is the something that is bundled.
------------------------------
Lutz Bettge
Deutsche Telekom AG
Original Message:
Sent: Jul 28, 2023 07:05
From: Matthieu Hattab
Subject: Buy ProductOffering - instantiate product bundle now - bundled products later
Hello,
Please use the correct terms as defined by TM Forum. it really helps us understand your question.
| Productoffering |
is what the CSP make available to the market and is an abstract class that is materialised in 2 forms, see below |
|
|
A type of ProductOffering that represents a grouping of ProductOfferings made available to the market. The grouping may consist of other BundledProductOffering(s) or SimpleProductOffering(s). |
|
|
A type of ProductOffering that does not have any subordinate ProductOfferings, that is, an SimpleProductOffering is a leaf-level ProductOffering. |
| product |
A product is an instantiation of a ProductOffering in the [customer] product inventory which keeps the business terms under which the customer purchased the product offering and is an abstract class that is materialised in 2 forms, see below |
|
|
A Product bundle in an instantiation of the BundledProductOffering |
|
|
A Product component in an instantiation of the SimpleProductOffering. Note that, despite the term "component" it doesn't mean the product is part of the bundle! "ProductComponent" can represent a handset sold as standalone or sold as part of a bundle.
I wish TMF had a class name to represent a product offering that is a component of a productBundle. I often use the term "bundle component", to indicate that the product (offering) is sold as a part of a bundle but that term is not official. |
I didn't see a question in your post, what would you like to know?
The SID and the API are capable of representing:
- simple or bundles product offering
- product offering contained in a bundle (including their cardinality (min, max, default quantities), see Litz response.
and this is available both in the product catalogue and in the product inventory.
customer know exactly what they allowed to buy and how many; both at the initial purchase and later when they modify their products.
------------------------------
Kind regards,
Matthieu Hattab
Lyse Platform
Original Message:
Sent: Jul 26, 2023 12:31
From: Nils Boysen
Subject: Buy ProductOffering - instantiate product bundle now - bundled products later
Hi,
I'm trying to model a ProductOfferingBundle that contains a lot of
BundledProductOfferings at a discount.
The BundledProductOfferings need a domain name when they are instantiated. When
the ProductOfferingBundle is instantiated not all of the domain names are known
jet.
The customer should be able to instantiate one of the discounted
BundledProductOfferings whenever they need (want to add a domain).
The customer should be able to check how many BundledProductOfferings are left.
Any help would be much appreciated.
Thank you.
------------------------------
Nils Boysen
TO BE VERIFIED
------------------------------