Let me clarify a little: I think the name GraphQL for sure makes sense from a technical point of view. But from a marketing point of view, it has been a nightmare and makes it _unusually_ difficult for others to initially grasp.
So what you mean is that name of GraphQL minimizes one of its important aspect:
the ability to query a service/product/app whatever are the actual persistence mechanisms
and even so if part of the response is computed on the fly.
Now, I better understand, why you would prefer a name like ProductQL
or even ProductAPI in order to emphasise the will for this tool
to be the single point of interaction from the outside with a product.
