settings.yml revision 36dbe6db12e6e58acfe2ca3f03af7732b6c5600d
a847d9812b328c048773e705606b10875a929034Eugen Kuksa# Project configuration
a4344d37747b6733bbd0d8df738b614cb385316cTim Reddehase# Environment specific settings can be overridden in:
d1f0cb74e8bc61e9185488a431b86816cb1cc7edSascha Graef# /config/settings/<environment>.yml
5ec1c6ff5da427d945d7fb708567ce3526c4c741Tim Reddehase# Name of the installation
5ec1c6ff5da427d945d7fb708567ce3526c4c741Tim Reddehasename: "MyOntohub"
5ec1c6ff5da427d945d7fb708567ce3526c4c741Tim Reddehase# Hostname of the installation
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehasehostname: #nil - overwrite in the settings.local.yml
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehase# Generalizing term "Ontology",ALternatives are M:Models and S:Specification
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehase# In case of Model,this should be used.
10be32b36246121321399ec3ab26d4d723d550e3Tim ReddehaseOMS_qualifier: modeling
6f84d8dbc4edca35b7e69c8296a257ea17e3b74fTim Reddehase# Optional asset host for delivery of static files (css, images, javascripts)
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehase# Sender address for outgoing mail.
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehase# The host will be appended automatically if it does not contain an @ character.
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehaseemail: noreply
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehase# Mail delivery
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehase# http://guides.rubyonrails.org/action_mailer_basics.html#action-mailer-configuration
10be32b36246121321399ec3ab26d4d723d550e3Tim Reddehaseaction_mailer:
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehase # possible values for delivery_method (see ActionMailer documentation):
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehase # :smtp, :sendmail, :file, :test
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehase delivery_method: :sendmail
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehase perform_deliveries: true
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase raise_delivery_errors: true
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase smtp_settings:
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase address: 'mail'
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # Supply the fully qualified domain name in the settings.local.yml at:
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase domain: # nil
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase enable_starttls_auto: true
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase password: # nil
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase authentication: # nil
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase# The number of days a user can access
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase# the website without confirming his account.
4949048bda09e116ee3627383e831455954cbe41Tim Reddehaseallow_unconfirmed_access_for_days: 3
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase# Limits for displaying file contents and diffs
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehasemax_read_filesize: 524_288
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehasemax_combined_diff_size: 1_048_576
db8aaeeeb3b24f487a5d02c60d18e96e55f6ba85Tim Reddehase# Timeout for ontology parsing jobs in hours
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehaseontology_parse_timeout: 6
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehaseasynchronous_execution:
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # possible values for log level (in ascending order of verbosity):
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # UNKNOWN, FATAL, ERROR, WARN, INFO, DEBUG
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase log_level: WARN
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase# Footer links and texts
db8aaeeeb3b24f487a5d02c60d18e96e55f6ba85Tim Reddehase - text: Foo Institute
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase - text: About
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase# Delivery of exceptions, disabled by default
db8aaeeeb3b24f487a5d02c60d18e96e55f6ba85Tim Reddehaseexception_notifier:
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase enabled: false
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase email_prefix: "[ontohub exception]"
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase sender_address: "exceptions@example.com"
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase exception_recipients:
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase - exception-recipient@example.com
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase# The following paths can be absolute paths
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase# or relative paths (relative to the project root)
db8aaeeeb3b24f487a5d02c60d18e96e55f6ba85Tim Reddehase # General data.
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase # git repositories (names of repositories are numbers/ids)
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase git_repositories: # nil - then data/repositories is used
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # named symlinks to the git repositories
db8aaeeeb3b24f487a5d02c60d18e96e55f6ba85Tim Reddehase symlinks: # nil - then data/git_daemon is used
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # cache for files that needed to be checked out from the git repositories
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase commits: # nil - then data/commits is used
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # This is the path to the hets executable we use in `rake hets:*` and for the
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # process manager in production mode (god)
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase executable_path: /usr/bin/hets
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase # The URLs to the hets instances without trailing slash.
4949048bda09e116ee3627383e831455954cbe41Tim Reddehase # The number of instances is not allowed to be greater than the number of
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa # hardware processor cores.
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa instance_urls:
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa # The time between update-checks of registered hets-instances in minutes
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa time_between_updates: 360
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa default_branch: 'master'
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa push_priority:
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa changed_files_per_commit: 5
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa committer_name: 'ontohub_system'
1f3a52128a4c9a5830936e25b071ce6a81fec1beEugen Kuksa committer_email: 'ontohub_system@ontohub.org'
273b30f33fe1a753893887c8eb94f8078cc96928Eugen Kuksa# The name of the repository in which the externally imported ontology files are
9ade3006d75c25cfa77d51526e4a6cdd2370be5cEugen Kuksaexternal_repository_name: 'External'
9ade3006d75c25cfa77d51526e4a6cdd2370be5cEugen Kuksaaccess_token:
9ade3006d75c25cfa77d51526e4a6cdd2370be5cEugen Kuksa expiration_minutes: 360
9ade3006d75c25cfa77d51526e4a6cdd2370be5cEugen Kuksaallowed_iri_schemes:
9ade3006d75c25cfa77d51526e4a6cdd2370be5cEugen Kuksadisplay_head_commit: false
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksadisplay_symbols_tab: false
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksaformat_selection: false
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa# Your secret key for verifying the integrity of signed cookies.
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa# If you change this key, all old signed cookies will become invalid!
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa# Make sure the secret is at least 64 characters and all random,
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa# no regular words or you'll be exposed to dictionary attacks.
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa# This is just an example value.
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa# Overwrite this in your settings.local.yml or settings/production.local.yml!
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksasecret_token: '6b198bfe3759ee41524d3a0d7547890a2d277f44f2ce472921ced9bac1833830028bbcacf58fdac0b482265042baa8df4de86a86ad63711ef5b50f70e57d5a07'
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa# Possible values for metadata, adapted from OMV
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksaformality_levels:
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehase - name: vocabulary
7c0f71e3e6e26af2cc91112fdbe3905879bfd893Tim Reddehase description: "list of words"
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase - name: terminology
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase description: "list of concepts with definitions"
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase - name: taxonomy
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase description: "terminology with subsumption hierarchy"
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase - name: axiomatization
7c0f71e3e6e26af2cc91112fdbe3905879bfd893Tim Reddehase description: "ontology with axioms beyond a pure subsumption hierarchy"
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa # number of axioms per concept can be displayed
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehaselicense_models:
b7fe8f3179594e2ebccf6ee9f562e9c2e17aab96Eugen Kuksa - name: Apple Public Source License (APSL)
7c0f71e3e6e26af2cc91112fdbe3905879bfd893Tim Reddehase url: http://www.opensource.apple.com/license/apsl/
7c0f71e3e6e26af2cc91112fdbe3905879bfd893Tim Reddehase - name: Open Software License (OSL)
d11de492e18415f91e383e1567beb4e1385d5938Tim Reddehase - name: General Public License (GPL)
7c0f71e3e6e26af2cc91112fdbe3905879bfd893Tim Reddehase - name: IBM Public License (IBM PL)
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase - name: Common Public License (CPL)
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase url: http://www.eclipse.org/legal/cpl-v10.html
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase - name: Lesser General Public License (LGPL)
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase - name: INTEL Open Source License (INTEL OSL)
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase - name: Modified BSD License (mBSD)
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase url: http://opensource.org/licenses/BSD-3-Clause
7c0f71e3e6e26af2cc91112fdbe3905879bfd893Tim Reddehase - name: Academic Free License (AFL)
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehaseontology_types:
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase - name: Upper Level Ontology
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase description: describes general, domain-independent concepts e.g. space, time
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase - name: Core Ontology
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase description: "describes the most important concepts in a specific domain (also: mid-level ontology)"
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase - name: Domain Ontology
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase description: describes some domain of the world
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase - name: Application Ontology
503ccb65bd740225668eb51be966d60fb4ae29e1Tim Reddehase description: describes some domain in an application-dependent manner
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa - name: SearchTask
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa description: the task characterizes how ontologies are used to refine common keywordbased search algorithms using domain knowledge in form of subsumption relations. Ontology-driven search is usually performed automatically by means of reasoning services handling particular aspects of an ontology representation language.
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa - name: AnnotationTask
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa description: the ontology is used as a controlled vocabulary to annotate Semantic Web resources. This task includes the usage of a semantically rich ontology for representing arbitrarily complex annotation statements on these resources. The task can be performed manually or (semi-)automatically.
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa - name: QueryRewritingTask
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa description: complementary to the query formulation dimension, this task applies ontologies to semantically optimize query expressions by means of the domain knowledge (constraints, subsumption relations etc.) The task can be interpreted as a particular art of filtering information. The task is performed automatically; however, it assumes the availability of patterns describing the transformations at query level.
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa - name: FilteringTask
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa description: the task describes at a very general level how ontologies are applied to refine the solution space of a certain problem, such as information retrieval or personalization. The task is targeted at being performed semi-automatically or automatically.
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa - name: IntegrationTask
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa description: the task characterizes how ontologies provide an integrating environment, an inter-lingua, for information repositories or software tools. In this scenario the ontology is applied (semi-)automatically to merge between heterogeneous data pools in the same or in adjacent domains.
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa - name: QueryFormulationTask
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa description: the ontology is used in information retrieval settings as a controlled vocabulary for representing user queries. Usually the task is performed automatically in that the concepts of the ontology is are listed in a query formulation front-end in order to allow users to specifies their queries.
575f7ed30e509f1a650d73927f607e7b5b11a6dbEugen Kuksa - name: MediationTask
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehase description: the ontology is built to reduce the ambiguities between communicating human or machine agents. It can act as a normative model which formally and clearly defines the meaning of the terms employed in agent interactions. In the context of programmed agents, the task is envisioned to be performed automatically.
81a6387a4ab56a24194ecbabd6609c6bcca568b7Tim Reddehase - name: ConfigurationTask
98ba1c38b1cce99ecc61117259f2ae05ffe98469Tim Reddehase description: the ontology is designed to provide a controlled and unambiguous means to represent valid configuration profiles in application systems. As the aim of the ontology is to support the operationalization of particular system-related processes; this task is performed automatically in that the ontology is processed in an automatic manner by means of reasoners or APIs.
98ba1c38b1cce99ecc61117259f2ae05ffe98469Tim Reddehase - name: PersonalizationTask
98ba1c38b1cce99ecc61117259f2ae05ffe98469Tim Reddehase description: the ontology is used mainly for providing personalized access to information resources. Individual user preferences w.r.t. particular application settings are formally specified by means of an ontology, which, in conjunction with appropriate reasoning services, can be directly integrated to a personalization component for filtering purposes. The usage of ontologies in personalization tasks might be carried out in various forms, from a direct involvement of the user who manually specifies ontological concepts which optimally describe his preferences, to the ontological modelling of user profiles.
d51cee8257d50d1f2d7c0818d968b32096f6b795Tim Reddehase - name: IndexingTask
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase description: in this scenario, the goal of the ontology is to provide a clearly defined classification and browsing structure for the information items in a repository. Again, the task can be performed manually by domain experts or as part of an application in an automatic or semi-automatic way.
23f0ab4a423943eb59109df37074ef0c330d07c0Tim Reddehase - name: MatchingTask
db8aaeeeb3b24f487a5d02c60d18e96e55f6ba85Tim Reddehase description: the goal of matching is to establish links between semantically similar data items in information repositories. In contrast to the previous task, matching does not include the production of a shared final schema/ontology as a result of aggregating the matched source elements to common elements. W.r.t. the automatization level the range varies from manual to fully-automatical execution.