extend json endpoint to other entity types

[giraygi]

json endpoint is only implemented for terms. It will be compared to v2 endpoints and if it is necessary, it will be implemented for ontologies, individuals and properties.

[giraygi]

It seems there is no need for this. Even the initial term based endpoint was not necessary. I compared https://api.terminology.tib.eu/api/v2/ontologies/aco/entities/https%253A%252F%252Fw3id.org%252Fac-ontology%252Faco%2523AudioExpression?lang=en and https://api.terminology.tib.eu/api/ontologies/aco/terms/https%253A%252F%252Fw3id.org%252Fac-ontology%252Faco%2523AudioExpression/json using https://jsondiff.com/

jsondiff.comjsondiff.com
JSON Diff - The semantic JSON compare tool
Validate, format, and compare two JSON documents. See the differences between the objects instead of just the new lines and mixed up properties.
3:19
There are some unimportant type differences and two fields called directAncestor and hierarchicalAncestor are missing in the 1st call
3:19
But those fields are empty in the second call.