...
LC's Suggest API has received minor enhancements over the years, but is largely the same as implemented back in 2009-2010, when the service was still hosted at lcsh.info. Its output format is identical. It is formally undocumented (and how it has managed this long without being formally documented is a bit of a mystery) but LC readily and willingly shares information about not only its existence but how it works. LC's Suggest API is a left-anchored, wild-carded search of preferred labels, codes (for example a search for "deu" will return "German" from the ISO-6392 dataset), or tokens (such as "sh12345," which is an LCCN). Results are ordered alphabetically (based on codepoint). There is some support for limiting based on MADS/RDF type (PersonalName, Topic, Geographic, etc.). Notably, it does not search variant/alternate labels. Under the hood, the code is 100% distinct from the code that runs the Search API, mostly so it can better focus on its purpose, which is to return typeahead suggestions as quickly as possible. The service's output is outdated, a form of JSON that is difficult to work with given today's typeaheads. It is also limited to only the URI and label of the hit.
Share-VDE API
1. Description of Share-VDE databases available on Stardog triplestore.
2. Instructions for Share-VDE libraries on how to access databases on Stardog triplestore, with some query example.
3. Stardog indications on HTTP APIs.
We are currently working on SVDE backend infrastructure that will support an ad hoc set of APIs specific to SVDE.