At a first glance, jsoniq looks very nice.
For simple access patterns (by primary key) it may be still overkill,
however, NoSQL vendors could still keep APIs for such queries where
query parsing & planning overhead is undesired.

But anyway, having a “standard” query language at least for JSON document databases would be help as users wouldn’t need to learn a new language/concept for each database.

I hope jsoniq will get more adoption than UNQL got.

 Yes, indeed. I like the direction in which this is going. A much more “programmatic” approach. I think this is easier to understand when dealing with lists and arrays. Jan has developed AQL in a very similar direction: https://www.arangodb.com/2012/06/20/querying-a-nosql-database-the-elegant-way