Proposal: Remove 'resultType' from core and put in an extension

[opengeospatial]

Proposal: Remove 'resultType' from core and put in an extension

[cportele]

I think you are right. Probably we should see how we support resultType=hits and other related capabilities like #13 and #16 consistently in an extension.

Having a capability to determine the total number of hits is often useful, so we should tackle this soon, if we move it out.

[pvretano]

Yeah, I think I agree with this too. We could probably think about doing something with HEAD to get this kinds of metadata from a server.

[cholmes]

Yes, fully agree that the capability to determine the total number of hits is extremely useful - it was one of my favorite additions.

Just want to be sure it's not required, and that it could easily be implemented in a microservice style architecture. I think there's potential for standardization of even more types of aggregations - like bucketing the stats to drive charts, or even spatial aggregations - return counts by regular geographies, for when a browser can't display all the data. But should be additional end points.

[cportele]

There seems to be consensus on this one. I will create a pull request...

[pvretano]

From teleconference 12-FEB-2018:

• rather than have a resultType extension perhaps this requirement could be satisfied using "microformats" with MIME types and then using the standard content negotiation mechanisms.