From fe1498319aaacd173ac49c141bab87f65834b828 Mon Sep 17 00:00:00 2001 From: Brian Lowe Date: Tue, 27 Apr 2021 19:43:59 +0300 Subject: [PATCH] Add note to runtime.properties that TPF should not be used if VIVO contains restricted data. (#236) --- .../main/resources/config/example.runtime.properties | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/home/src/main/resources/config/example.runtime.properties b/home/src/main/resources/config/example.runtime.properties index e5a9da9d..260eb17f 100644 --- a/home/src/main/resources/config/example.runtime.properties +++ b/home/src/main/resources/config/example.runtime.properties @@ -407,7 +407,15 @@ Vitro.reconcile.defaultTypeList = http://vivoweb.org/ontology/core#Role, core:Ro # If you do not wish to use the claiming interface, set this property to nothing (empty) createAndLink.providers = doi, pmid - # Triple pattern fragments is a very fast, very simple means for querying a triple store. - # The triple pattern fragments API in VIVO puts little load on the server, providing a simple means for getting data from the triple store. The API has a web interface for manual use, can be used from the command line via curl, and can be used by programs. + # Triple Pattern Fragments is a very fast, very simple means for querying a + # triple store. The Triple Pattern Fragments API in VIVO puts little load on + # the server, providing a simple means for getting data from the triple store. + # The API has a web interface for manual use, can be used from the command + # line via curl, and can be used by programs. + # + # VIVO's Triple Pattern Fragments API does not require authentication and + # makes the full RDF graph available regardless of display or publish levels + # set on particular properties. Enable Triple Pattern Fragments only if your + # VIVO does not contain restricted data that should not be shared with others. # # tpf.activeFlag = true