ITEM request delivers json (instead of HTML)

[kgaeb]

is there any reason why the following request delivers automatically a json instead of html?

http://localhost:8086/ogcapisimple/collections/Navaids/items/ILS-GP_4?f=text/html

The returned record is the correct one, but I would have expected to receive a html!

[LukasGaebler]

As requested there are only HTML pages for:

• the collections: http://localhost:8080/ogcapisimple/collections?f=text%2Fhtml
• the items: http://localhost:8080/ogcapisimple/collections/insp_aerodromenode/items?f=text%2Fhtml

[kgaeb]

We need to discuss this! Pls call me!

[kgaeb]

The specification doesn't require or favour a response encoding (for the OGC API Simple it is either HTML or JSON). This results in a situation where some requests are answered in JSON AND HTML, but others are only in JSON. This makes client software, users and/or developers under these circumstances potentially hard to implement further requests.

For the OGC API Simple this would be as follows:
as mentioned above (#120 (comment)) HTML responses are only available for ".../collections" and ".../items" requests. All others will always respond with a JSON, independently of the agreed "f=..." parameter. To overcome this flaw in the specification, the documentation of the API (Swagger) should be very clear about this circumstances and should mentioned that!