Open APIs

 View Only
  • 1.  TMF670 - Multiple Return Objects vs TMF632

    TM Forum Member
    Posted 17 days ago

    The TMF670 Payment Methods API has multiple payment types (based on PaymentMethod) that can be posted and retrieved and it uses one endpoint to do this. Whereas, the TMF632 Party API separate endpoints for Individual and Organization that are both based on Party.

    Does anyone know what the reasoning was for implementing the same concept differently between these two APIs?

    The GitHub repo for this one is a bit messed up, so it is making me wonder if the 4.0.0 spec file that is in there is the right one. I tried to verify it against the Open API Table, but TMF670 isn't in the production table anymore (shouldn't it be?) and the history table actually links to a 3.0.0 version of the spec instead of the 4.0.0 version that is noted in the table.

    Can someone verify that the 4.0.0 spec in GitHub for TMF670 is valid? (I submitted a PR for fixing what I hope is just a directory structure/file naming issue.)

    ​​​

    ------------------------------
    Jacob King
    MetroNet
    ------------------------------



  • 2.  RE: TMF670 - Multiple Return Objects vs TMF632

    TM Forum Member
    Posted 16 days ago
    Hi Jacob
    First, some admin stuff.
    • The public GitHub repositories are not up-to-date as far as I am aware. The current TMF publication mechanism for Open API assets works only via the API table, and points to assets on a dedicated S3 bucket.
    • TMF management decided that APIs at version below 4 would no longer be on the main Open API table, but rather on the archive/history page, here. Specifically for TMF670, a new version is in progress and some beta assets are on the early access page here.
    Regarding the difference between Party and Payment Method, I can only speculate, but maybe it's to do with the fact that there are only two concrete subclasses of Party, and these are sufficiently different and important to have their own endpoints. Additionally, I think that Payment Method was refactored at some point from a model where the main entity contained the diverse payment methods to a model where the main entity is polymorphic.
    However I haven't been there right from the start, maybe older veterans than me could weigh in (@Stephen Harrop, @Ludovic Robert)​​.

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