resources.samples.dictionary_from_remote_repository.config.ttl Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of gazetteer-lkb Show documentation

A Large Knowledge Based (LKB) Gazetteer

The newest version!

# Gazetteer_LKB dictionary configuration file.
#
# %temp% will be automatically replaced with the TEMP folder for the current user
# %relpath% will be replaced with the path to the dictionary folder.
#
@prefix rdfs: .
@prefix rep: .
@prefix hr: .
@prefix lkbg: .

# The dictionary will be loaded from a remote Sesame HTTP repository. 
# Its configuration follows. See the Sesame configuration for detals.
# http://www.openrdf.org/doc/sesame2/users/ch07.html#section-repository-config
[] a rep:Repository ;
   rep:repositoryImpl [
      rep:repositoryType "openrdf:HTTPRepository" ;
	  
	  # This URL is a public limitted SPARQL endpoint. All queries are truncated to 10000 results.
	  hr:repositoryURL 
	  
	  # This URL points to the unlimitted password-protected factforge endpoint.
	  # Ontotext partners can contact [email protected] to request credentials. 
	  # Please include the SPARQL that you indend to run.
	  # Set the credentials below.
      #hr:repositoryURL 
	  
	  
   ];
   rep:repositoryID "owlim" ;
   rdfs:label "FactForge" .
   
# The gazetteer-specific options follow.
lkbg:DictionaryConfiguration 
   # Whether the gazeetteer will be sensitive to case.
   # Possible values: caseinsensitive, casesensitive
   lkbg:caseSensitivity "caseinsensitive" ;
   
   #(optional) Authentication
   #If you are connecting to a repository guarded by HTTP basic authentication,
   #supply credentials as follows:
   #lkbg:username "" ;
   #lkbg:password "" ;
      
   # Whether the gazetteer will cache the dictionary after loading it from the data source.   
   # Put "enabled" to enable the cache, any other values will disable it.
   lkbg:caching "enabled" .
   
   # The cache will be automatically reloaded on initialization if the configuration have been    
   # modified since the last initialization. However, changes in the underlying datastore 
   # can't be detected and the cache will not be automatically reloaded in that case. 
   # Thus, if you expect changes in your datastore, disable the cache, or make use
   # of the modifications API.