Open APIs

Hi all,

When we are creating a new ProductOffering (POST) a ProductSpecificationRef can be sent. In our internal model, a product offering must have always a related product specification.

Can you clarify how this API should work when we receive a ProductSpecificationRef that doesn't exist? 

Thank you

Rui Ferreira

------------------------------
Rui Ferreira
Celfocus
------------------------------

From TMF model perspective (TMF620 Product Catalog Management), a Product Offering is one of:

• Bundle, in which case it has references to other offerings that it bundles (including the cardinalities), and no specification
• Simple, in which case it has a reference to specification, and no bundled offerings

I understand from your statement that you don't have bundling offerings?

But in any case if you are implementing the POST operation, it's up to you to decide how the implementation behaves. You might want to be able to create an empty shell offering as a draft, and later on add the specification reference.

Hope it helps

Hi all,

When we are creating a new ProductOffering (POST) a ProductSpecificationRef can be sent. In our internal model, a product offering must have always a related product specification.

Can you clarify how this API should work when we receive a ProductSpecificationRef that doesn't exist? 

Thank you

Rui Ferreira

------------------------------
Rui Ferreira
Celfocus
------------------------------

Hi Jonathan ,

And in the case of simple ones, the reference that we send in POST operation must be already created or if is not created we should create it?

We support bundles and simple offers, both of them must have (by our internal model) a product specification related.

Thank you

From TMF model perspective (TMF620 Product Catalog Management), a Product Offering is one of:

• Bundle, in which case it has references to other offerings that it bundles (including the cardinalities), and no specification
• Simple, in which case it has a reference to specification, and no bundled offerings

I understand from your statement that you don't have bundling offerings?

But in any case if you are implementing the POST operation, it's up to you to decide how the implementation behaves. You might want to be able to create an empty shell offering as a draft, and later on add the specification reference.

Hope it helps

Hi all,

When we are creating a new ProductOffering (POST) a ProductSpecificationRef can be sent. In our internal model, a product offering must have always a related product specification.

Can you clarify how this API should work when we receive a ProductSpecificationRef that doesn't exist? 

Thank you

Rui Ferreira

------------------------------
Rui Ferreira
Celfocus
------------------------------

Hi Rui,

when you create a new /ProductOffering object in your API with a POST, you can make the POST operation return the newly created object in the responce. 

That object could have the href attribute set to a reference to itself. This way you immediatly get a reference to the created object at hand.

Best Regards

Anton

Hi Jonathan ,

And in the case of simple ones, the reference that we send in POST operation must be already created or if is not created we should create it?

We support bundles and simple offers, both of them must have (by our internal model) a product specification related.

Thank you

From TMF model perspective (TMF620 Product Catalog Management), a Product Offering is one of:

• Bundle, in which case it has references to other offerings that it bundles (including the cardinalities), and no specification
• Simple, in which case it has a reference to specification, and no bundled offerings

I understand from your statement that you don't have bundling offerings?

But in any case if you are implementing the POST operation, it's up to you to decide how the implementation behaves. You might want to be able to create an empty shell offering as a draft, and later on add the specification reference.

Hope it helps

Hi all,

When we are creating a new ProductOffering (POST) a ProductSpecificationRef can be sent. In our internal model, a product offering must have always a related product specification.

Can you clarify how this API should work when we receive a ProductSpecificationRef that doesn't exist? 

Thank you

Rui Ferreira

------------------------------
Rui Ferreira
Celfocus
------------------------------

Rui - when you supply an <entity>Ref as part of a POST, the implication is that the referred entity already exists (since you are populating the <entity>Ref.id property).

Hi Rui,

when you create a new /ProductOffering object in your API with a POST, you can make the POST operation return the newly created object in the responce. 

That object could have the href attribute set to a reference to itself. This way you immediatly get a reference to the created object at hand.

Best Regards

Anton

Hi Jonathan ,

And in the case of simple ones, the reference that we send in POST operation must be already created or if is not created we should create it?

We support bundles and simple offers, both of them must have (by our internal model) a product specification related.

Thank you

From TMF model perspective (TMF620 Product Catalog Management), a Product Offering is one of:

• Bundle, in which case it has references to other offerings that it bundles (including the cardinalities), and no specification
• Simple, in which case it has a reference to specification, and no bundled offerings

I understand from your statement that you don't have bundling offerings?

But in any case if you are implementing the POST operation, it's up to you to decide how the implementation behaves. You might want to be able to create an empty shell offering as a draft, and later on add the specification reference.

Hope it helps

Hi all,

When we are creating a new ProductOffering (POST) a ProductSpecificationRef can be sent. In our internal model, a product offering must have always a related product specification.

Can you clarify how this API should work when we receive a ProductSpecificationRef that doesn't exist? 

Thank you

Rui Ferreira

------------------------------
Rui Ferreira
Celfocus
------------------------------

Thank you, Jonathan, so by my understanding in the case of a ProductOffering both ProductSpecification and BundleProductOffering should exist.

Rui - when you supply an <entity>Ref as part of a POST, the implication is that the referred entity already exists (since you are populating the <entity>Ref.id property).

Hi Rui,

when you create a new /ProductOffering object in your API with a POST, you can make the POST operation return the newly created object in the responce. 

That object could have the href attribute set to a reference to itself. This way you immediatly get a reference to the created object at hand.

Best Regards

Anton

Hi Jonathan ,

And in the case of simple ones, the reference that we send in POST operation must be already created or if is not created we should create it?

We support bundles and simple offers, both of them must have (by our internal model) a product specification related.

Thank you

From TMF model perspective (TMF620 Product Catalog Management), a Product Offering is one of:

• Bundle, in which case it has references to other offerings that it bundles (including the cardinalities), and no specification
• Simple, in which case it has a reference to specification, and no bundled offerings

I understand from your statement that you don't have bundling offerings?

But in any case if you are implementing the POST operation, it's up to you to decide how the implementation behaves. You might want to be able to create an empty shell offering as a draft, and later on add the specification reference.

Hope it helps

Hi all,

When we are creating a new ProductOffering (POST) a ProductSpecificationRef can be sent. In our internal model, a product offering must have always a related product specification.

Can you clarify how this API should work when we receive a ProductSpecificationRef that doesn't exist? 

Thank you

Rui Ferreira

------------------------------
Rui Ferreira
Celfocus
------------------------------