Open APIs

I have see that when we define characteristics associated with an item we can include several and for each one we can define the cardinalty for a better definition of the attributes of the entity to be defined.

But when we try to define the relationships among resources or services specs we found that we can reference other specifications but we cannot reference in the spec the cardinality. 

To do it, should I define the spec with an special name in the type field or maybe create max and minCardinality elements in the relationships?

In EntitCatalogManagement we can use the association elements

In ServiceCatalogManagement we can use the ServiceSpecRelationShip 


------------------------------
Xose Ramon Sousa Vazquez
Optare Solutions
------------------------------

Hi Xose
Before we look at a possible enhancement in the model, it would be instructive to understand what the use case is for variable cardinalities in these relationships. Perhaps you could give specific use cases.
You will notice that in Product Catalog we have these cardinalities on offering relationships, since these can indeed vary (end-customer can say choose 1, 2, or 3, according to the set cardinalities). But what is the case for variable cardinalities in the more fundamental elements.
@Kamal Maghsoudlou may have additional insights to this.

Hope it helps​

------------------------------
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 08, 2020 08:54
From: Xose Ramon Sousa Vazquez
Subject: Specs relationships

I have see that when we define characteristics associated with an item we can include several and for each one we can define the cardinalty for a better definition of the attributes of the entity to be defined.

But when we try to define the relationships among resources or services specs we found that we can reference other specifications but we cannot reference in the spec the cardinality.

To do it, should I define the spec with an special name in the type field or maybe create max and minCardinality elements in the relationships?

In EntitCatalogManagement we can use the association elements

In ServiceCatalogManagement we can use the ServiceSpecRelationShip

------------------------------
Xose Ramon Sousa Vazquez
Optare Solutions
------------------------------

Thanks for your comments. 

Many product/service and resource specifications has relationships with other specifications and in many digital services, the platofrms are open to new elements to be included (by developers as an example). It is not defined how many entities will be created, this depends on many factors (capacity constraints) and it they are enabled or not. 

For example a NFV platform that includes services from developers. For its management we need to support ResourceFunctions but in an unbounded fashion. 

Regards

------------------------------
Xose Ramon Sousa Vazquez
Optare Solutions
------------------------------

Original Message:
Sent: May 10, 2020 02:54
From: Jonathan Goldberg
Subject: Specs relationships

Hi Xose
Before we look at a possible enhancement in the model, it would be instructive to understand what the use case is for variable cardinalities in these relationships. Perhaps you could give specific use cases.
You will notice that in Product Catalog we have these cardinalities on offering relationships, since these can indeed vary (end-customer can say choose 1, 2, or 3, according to the set cardinalities). But what is the case for variable cardinalities in the more fundamental elements.
@Kamal Maghsoudlou may have additional insights to this.

Hope it helps​

------------------------------
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 08, 2020 08:54
From: Xose Ramon Sousa Vazquez
Subject: Specs relationships

I have see that when we define characteristics associated with an item we can include several and for each one we can define the cardinalty for a better definition of the attributes of the entity to be defined.

But when we try to define the relationships among resources or services specs we found that we can reference other specifications but we cannot reference in the spec the cardinality.

To do it, should I define the spec with an special name in the type field or maybe create max and minCardinality elements in the relationships?

In EntitCatalogManagement we can use the association elements

In ServiceCatalogManagement we can use the ServiceSpecRelationShip

------------------------------
Xose Ramon Sousa Vazquez
Optare Solutions
------------------------------