litvinovg/vitro
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add note to example.runtime.properties that TPF should not be used if Vitro contains restricted data.

Browse source
This commit is contained in:
Brian Lowe 2021-04-09 18:15:57 +03:00
parent cdfb18a455
commit b6062fe4a0
1 changed files with 11 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
home/src/main/resources/config/example.runtime.properties
View file

@ -154,7 +154,15 @@ proxy.eligibleTypeList = http://www.w3.org/2002/07/owl#Thing
# #
# languages.selectableLocales = en, es, fr # languages.selectableLocales = en, es, fr
# Triple pattern fragments is a very fast, very simple means for querying a triple store. # Triple Pattern Fragments is a very fast, very simple means for querying a
# 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 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.
#
# Vitro'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
# Vitro does not contain restricted data that should not be shared with others.
#
# tpf.activeFlag = true # tpf.activeFlag = true