Open APIs

in TMF637 5.0 product.status supports the following values

      enum:        - created        - pendingActive        - cancelled        - active        - pendingTerminate        - terminated        - suspended        - 'aborted '

Why is there an explicit trailing space on aborted and why is the traling space only here and not in e.g. TMF622? I assume, this is a simple typo that I like to be fixed.

On that note, it would be nice to also introduce a product status life cycle section in TMF637 that explains intended usage a bit better.

Hi,

Don't look at the values, they are just there for illustration purposes. And they change depending who wrote them and where. In GB922, product status has different status values (planned, designed, activated, disconnected). we use different values. You should just define the values you need.

on your last comment, It is odd, indeed, since many TMF API guides have a dedicated "life cycle management" section.

The next best step for you is to go to TMF JIRA to raise a ticket for this API.

in TMF637 5.0 product.status supports the following values

      enum:        - created        - pendingActive        - cancelled        - active        - pendingTerminate        - terminated        - suspended        - 'aborted '

Why is there an explicit trailing space on aborted and why is the traling space only here and not in e.g. TMF622? I assume, this is a simple typo that I like to be fixed.

On that note, it would be nice to also introduce a product status life cycle section in TMF637 that explains intended usage a bit better.

Hi Matthieu,

As per this thread from 2019:
LifecycleStatus value in json data of Conformance tests | Open APIs

the values of enums are not just for information, but are normative (i.e. should be supported by the implementation to guarantee interoperability).

Was this directive changed?

Plamen

Hi,

Don't look at the values, they are just there for illustration purposes. And they change depending who wrote them and where. In GB922, product status has different status values (planned, designed, activated, disconnected). we use different values. You should just define the values you need.

on your last comment, It is odd, indeed, since many TMF API guides have a dedicated "life cycle management" section.

The next best step for you is to go to TMF JIRA to raise a ticket for this API.

in TMF637 5.0 product.status supports the following values

      enum:        - created        - pendingActive        - cancelled        - active        - pendingTerminate        - terminated        - suspended        - 'aborted '

Why is there an explicit trailing space on aborted and why is the traling space only here and not in e.g. TMF622? I assume, this is a simple typo that I like to be fixed.

On that note, it would be nice to also introduce a product status life cycle section in TMF637 that explains intended usage a bit better.

I don't know but it's not realistic at all.
At my company, we have several BSS for different product lines or customer types. They all use different product status and some can be in English, and some are in Norwegian.

When we present list of products to customer-facing engagement channels, we have a service (exposing TMF637) which normalises product data model and product status. Each BSS exposes their own Product inventory API (sometimes also with TMF637). I guess we do follow some "norm" but only at the edge.

Actually, one vendor that uses TMF637 was "certified" by TM Forum. but they don't use the same product status at all. Not sure if "certified" and "conformant" is the same thing. but that's what I observed!

Hi Matthieu,

As per this thread from 2019:
LifecycleStatus value in json data of Conformance tests | Open APIs

the values of enums are not just for information, but are normative (i.e. should be supported by the implementation to guarantee interoperability).

Was this directive changed?

Plamen

Hi,

Don't look at the values, they are just there for illustration purposes. And they change depending who wrote them and where. In GB922, product status has different status values (planned, designed, activated, disconnected). we use different values. You should just define the values you need.

on your last comment, It is odd, indeed, since many TMF API guides have a dedicated "life cycle management" section.

The next best step for you is to go to TMF JIRA to raise a ticket for this API.

in TMF637 5.0 product.status supports the following values

      enum:        - created        - pendingActive        - cancelled        - active        - pendingTerminate        - terminated        - suspended        - 'aborted '

Why is there an explicit trailing space on aborted and why is the traling space only here and not in e.g. TMF622? I assume, this is a simple typo that I like to be fixed.

On that note, it would be nice to also introduce a product status life cycle section in TMF637 that explains intended usage a bit better.