Closed recalcitrantsupplant closed 9 months ago
Would it make more sense to include this info in the root /
endpoint instead?
Here's the current response from /
:
<http://localhost:8000> prez:currentTBOXCacheSize 3112,
3264,
3277 ;
prez:enabledPrezFlavour [ a prez:ProfilesPrez ;
prez:link "/p" ],
[ a prez:CatPrez ;
prez:availableSearchMethod prez:exactMatch,
prez:jenaFTName ;
prez:link "/c" ],
[ a prez:VocPrez ;
prez:availableSearchMethod prez:exactMatch,
prez:jenaFTName,
prez:skosPrefLabel,
prez:skosWeighted ;
prez:link "/v" ],
[ a prez:SpacePrez ;
prez:availableSearchMethod prez:exactMatch,
prez:jenaFTName ;
prez:link "/s" ] ;
prez:version "0.1.0.dev0" .
Also do we need to update this response? It still contains old search method config, and the tbox size adds another triple to this response every time it changes.
What if anything from the current root response is being used? If nothing, we can populate with endpoint info from the endpoint reference data and also the annotation data.
With the current search changes, only the version and (soon) the enabled prez flavours. Sounds good to include the endpoint reference data as well.
Too many commits in PR after rebasing, hard to see changes clearly. Will create new PR.
The listing predicates are now provided at
/annotation-predicates
as an RDF Linked List.Example response with default prez config:
closes #151