Open APIs

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

  • I've used this approach (not in API context but SID) for translations. for example, product name, there was no way we would add extra attributes for each new language. for char we used language ISO code. ------------------------------ Matthieu Hattab ...

  • Hello David Did you take a look on Design Guidelines part 2 ? here : https://projects.tmforum.org/wiki/display/API/TMF630+API+Design+Guidelines+4.0.1+R20.0  You can extend your API using the @type pattern. Hope it helps Ludovic​ ------------------------------ ...

  • hi All, The below example is given in TMF630 for the extension of the REST API's using polymorphism. PhysicalResource: title: PhysicalResource type: object properties: id: type: integer Equipment: title: Equipment type: object allOf: - $ref: "#/definitions/PhysicalResource" - ...

  • If I was to adopt and implement an API,  how do the incremental changes get adopted?   Does the party requesting the change have to submit for review and wait for adoption? I'm concerned that if trying to get change to a core API take time, consumers ...

  • We really don't like key-value maps (i.e. Characteristic), since they basically allow the API definition to lose its strong typing. As a pattern we should have Characteristic only when there is a corresponding Characteristic Spec (as in the catalog/inventory ...

    1 person likes this.