Open APIs

 View Only
Login to Join

About this Community:

Use this community as your go-to resource to discuss anything and everything relating to TM Forum Open APIs:

  • learn how to implement them
  • post ideas and requirement for new types of APIs
  • share how you are using APIs
  • discuss domain specific applications

This is an open discussion area. TM Forum also has collaborative project work on Open APIs. To find out more click here

Latest Discussion Posts

  • Profile Picture

    RE: Rust Open Source Library

    By: Ryan Ruckley , 13 hours ago

    Andy et al, Thanks for your support, I have received internal approval to proceed and I have now published my library on crates.io (Rust library repositiory): https://crates.io/crates/tmflib ------------------------------ Ryan Ruckley Principal ...

    3 people like this.
  • Profile Picture

    RE: Contract length implementation

    By: Matthieu Hattab , yesterday

    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". ...

  • Profile Picture

    RE: TMF688 Event Versioning

    By: Jonathan Goldberg , yesterday

    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": ...

  • Profile Picture

    RE: TMF688 Event Versioning

    By: Andreas Lobenwein , yesterday

    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 ...

  • Profile Picture

    RE: TMF688 Event Versioning

    By: Jonathan Goldberg , 2 days ago

    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 ...

Announcements