Open APIs

we also use ProductTerm to model the agreement/contract period in cart, inventory... We sub-class ProductTerm for different purposes (binding, price guarantee, discounts...) If a term has a lifecycle, then we also define a duration using "validFor". ...

I'm not sure about your suggestions, Andreas. Possibly the most robust way would be to add a version property to the event schema itself. So it would appear in the payload directly , such as: "eventType": "ProductOfferingCreateEvent", "version": ...

Hi Jonathan, thx for looking into this question. What do you think about using the @schemaLocation attribute in TMF688 Event Structure for indicating the "version" implicitly by including it into the URI path of the location value? For me it looks ...

Hi Andreas These are great questions, and it does seem that the Open API guidelines did not cover this. BTW this is not related specifically to the event API TMF688, but rather to any message-mediated asynchronous interaction, such as the older hub ...

Hi Jan For a simple Product (without specific Agreement ), the duration of the contract is indeed modeled by ProductTerm (in the inventory) and OrderTerm (while the product is still being ordered). At the catalog level, we have ProductOfferingTerm ...