From 1af2f50b9b938bd2f3c13eb64cc05c573cd62b35 Mon Sep 17 00:00:00 2001 From: Andrew Su Date: Thu, 3 Oct 2024 10:33:47 -0700 Subject: [PATCH] Update component_builders_roadmap.md -- adjust BioThings SDK wording (#99) --- docs/development-guide/tutorials/component_builders_roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development-guide/tutorials/component_builders_roadmap.md b/docs/development-guide/tutorials/component_builders_roadmap.md index d0bd744..e425c1a 100644 --- a/docs/development-guide/tutorials/component_builders_roadmap.md +++ b/docs/development-guide/tutorials/component_builders_roadmap.md @@ -12,7 +12,7 @@ The purpose of this document is to provide a concrete one-stop, step-by-step roa For data owners who would like to make their data accessible within Translator as Knowledge Providers, there are several turnkey options to consider: -* [BioThings SDK](biothings-sdk.md): good for directly wrapping external 3rd party online databases that have non-TRAPI compliant web service API's. +* [BioThings SDK](biothings-sdk.md): good for creating JSON-based REST APIs that can be semantically annotated using the SmartAPI x-bte standard. * [Plater](https://github.com/TranslatorSRI/Plater): good for wrapping a local Neo4j database loaded with Biolink Model compliant knowledge graph(s). * [PLOVER](plover.md): serves _in-memory_ hosted Biolink Model compliant datasets, without the complication of maintaining a backend graph database.