Open APIs

 View Only

  • 1.  TMF630 - API Design Guidelines - Usage of 'task resources'

    Posted Aug 30, 2018 00:23
    Task resource pattern defined in TMF630 DG 3.0 Part 1 states below 

    "There are use cases:

    • when a task request is simple and there is no need to persist the request but the server may choose to persist the request in any case, e.g. for accounting purposes
    • long running task when there is a need to persist the request in order to monitor it."
    Question: Is the monitor only the allowed way to retrieve information around task? Can async notification pattern (hub & listener) be used for task?

    "It is not recommended to delete a task but rather to cancel the task with PATCH."
    Question: What is the rationale behind this statement? Why is this restricted?



    ------------------------------
    Abdul Majid Hussain
    Telstra Corporation
    ------------------------------


  • 2.  RE: TMF630 - API Design Guidelines - Usage of 'task resources'

    TM Forum Member
    Posted Sep 05, 2018 15:43
    ​There is an example of task usage In TMF 664 Resource Function Activation and Configuration that you might to look at.

    ------------------------------
    Dave Milham
    TM Forum Chief Architect, TM Forum
    ------------------------------

    Original Message


  • 3.  RE: TMF630 - API Design Guidelines - Usage of 'task resources'

    TM Forum Member
    Posted Sep 14, 2018 06:41
    Hi @Dave Milham. 
    I could not see any example where we have included notifications around tasks. TMF664 has explained only Monitor handle for long running task.

    so my questions is still open as per what is mentioned in TMF630 DG 3.0 Part 1 

    "There are use cases:

    • when a task request is simple and there is no need to persist the request but the server may choose to persist the request in any case, e.g. for accounting purposes
    • long running task when there is a need to persist the request in order to monitor it."
    Question: Is the monitor only the allowed way to retrieve information around task? Can async notification pattern (hub & listener) be used for task?

    "It is not recommended to delete a task but rather to cancel the task with PATCH."
    Question: What is the rationale behind this statement? Why is this restricted?



    ------------------------------
    Abdul Majid Hussain
    Telstra Corporation
    ------------------------------

    Original Message


  • 4.  RE: TMF630 - API Design Guidelines - Usage of 'task resources'

    TM Forum Member
    Posted Sep 14, 2018 08:58
    ​Abdul
    On further reading I believe you are correct TFM664 was focussed long running transactions. The owner of the DG 3.0 needs to comment on you comment/ proposal

    ------------------------------
    Dave Milham
    TM Forum Chief Architect, TM Forum
    ------------------------------

    Original Message


  • 5.  RE: TMF630 - API Design Guidelines - Usage of 'task resources'

    TM Forum Member
    Posted Sep 17, 2018 03:55
    ​On further reading of this area which was led by a colleagues I see in
    IG1164 Requirements Analysis for the Ordering and Configuration of Services and Resources R18.0.0
    • Sc 3.2 Example: Monitor object used for asynchronous interactions. Open Issue: Currently, in the TM Forum API design guidelines, monitor objects can only be polled for their current state. An enhancement would allow for monitor objects to emit notifications to which interested managers can subscribe.

    So it looks as if this would need to be a JIRA CR

    ------------------------------
    Dave Milham
    TM Forum Chief Architect, TM Forum
    ------------------------------

    Original Message