Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Let's get a proper name for our "JSON request APIs"!
It has bothered me for some time that "JSON Facet API" is a horrible name for this feature. Also the request param &json.facet=... are awkward, as the existing facet api is the other way around $facet.foo.
So I propose a re-branding and a community mindset to treat these as primary query and facet APIs going forward, not an alternative for those who fancy JSON.
This is how we brand it now: