To be clear, JSONPath as described in TMF630 Part 6, is an optional method for advanced query patterns. Simple queries, of the form you suggest, are described in TMF630 Part 1. You can only get so far with that though, and unfortunately anything involving Characteristics, a very common requirement, is beyond that capability. JSONPath may be complex, however that is a feature, not a bug.
------------------------------
Vance Shipley
SigScale
------------------------------
Original Message:
Sent: Nov 24, 2024 06:31
From: jinish pillai
Subject: Simpler URL for Get operation
Hello All ,
Although TMF630 outlines the way a URL shall be used for a get operation , it is much easier to make use of simpler query parameters like below one instead of a JSON path .
/tmf-api/productInventory/v4/product?customerIdentifier=123456
Can we consider the API with simpler query params like above to be TMF compliant ?
This discussion is in continuation to original thread which was discussed in the below
https://engage.tmforum.org/discussion/tmf-get-query-operations
Regards
Jinish Pillai
------------------------------
jinish pillai
Tata Consultancy Services
------------------------------