496N/A#

0N/A# Project configuration

0N/A#

0N/A# Environment specific settings can be overridden in:

1466N/A# /config/settings/<environment>.yml

0N/A#

0N/A

919N/A# Name of the installation

919N/Aname: "MyOntohub"

919N/A

919N/A# Hostname of the installation

919N/Ahostname: example.com

0N/A

919N/A# Optional asset host for delivery of static files (css, images, javascripts)

919N/A# asset_host: assets.example.com

919N/A

0N/A# Sender address for outgoing mail

919N/Aemail: noreply@example.com

919N/A

919N/A# Mail delivery

919N/A# http://guides.rubyonrails.org/action_mailer_basics.html#action-mailer-configuration

919N/Aaction_mailer:

919N/A delivery_method: sendmail

919N/A

0N/A# The number of days a user can access

0N/A# the website without confirming his account.

0N/Aallow_unconfirmed_access_for_days: 3

0N/A

0N/A# Footer links and texts

1027N/Afooter:

1027N/A - text: Foo Institute

1027N/A - text: About

1027N/A href: http://about.example.com

1027N/A

1027N/A# Delivery of exceptions, disabled by default

1027N/Aexception_notifier:

0N/A enabled: false

911N/A email_prefix: "[ontohub exception]"

1466N/A sender_address: "exceptions@example.com"

496N/A exception_recipients:

1466N/A - exception-recipient@example.com

0N/A

911N/Agit:

496N/A verify_url: http://localhost/

0N/A

0N/Aallowed_iri_schemes:

0N/A - http

0N/A - https

0N/A - file

0N/A - gopher

0N/A - urn

0N/A

0N/Adisplay_head_commit: false

0N/Adisplay_symbols_tab: false

0N/A

1466N/Aexternal_repository_name: 'External'

1027N/Afallback_commit_user: 'ontohub_system'

0N/Afallback_commit_email: 'ontohub_system@ontohub.org'

0N/A

0N/A# Possible values for metadata, adapted from OMV

1466N/Aformality_levels:

0N/A - name: vocabulary #

0N/A description: "list of words"

496N/A - name: terminology

0N/A description: "list of concepts with definitions"

0N/A - name: taxonomy

1466N/A description: "terminology with subsumption hierarchy"

0N/A - name: lightweight_axiomatization

0N/A description: "taxonomy with some logical relations among the concepts"

- name: deep_axiomatization

description: "ontology with logical descriptions of the concepts"

license_models:

- name: Apple Public Source License (APSL)

url: http://www.opensource.apple.com/license/apsl/

- name: Open Software License (OSL)

url: http://opensource.org/licenses/OSL-3.0

- name: General Public License (GPL)

url: http://www.gnu.org/licenses/gpl.html

- name: IBM Public License (IBM PL)

url: http://opensource.org/licenses/IPL-1.0

- name: Common Public License (CPL)

url: http://www.eclipse.org/legal/cpl-v10.html

- name: Lesser General Public License (LGPL)

url: https://www.gnu.org/licenses/lgpl.html

- name: INTEL Open Source License (INTEL OSL)

url: http://opensource.org/licenses/Intel

- name: Modified BSD License (mBSD)

url: http://opensource.org/licenses/BSD-3-Clause

- name: Academic Free License (AFL)

url: http://opensource.org/licenses/AFL-3.0

ontology_types:

- name: Upper Level Ontology

description: describes general, domain-independent concepts e.g. space, time

documentation: http://www.example.com

- name: Core Ontology

description: describes the most important concepts in a specific domain (also: mid-level ontology)

documentation: http://www.example.com

- name: Domain Ontology

description: describes some domain of the world

documentation: http://www.example.com

- name: Application Ontology

description: describes some domain in an application-dependent manner

documentation: http://www.example.com

- name: Task Ontology

description: describes the concepts for a specific task

documentation: http://www.example.com

- name: Distributed Ontology

description: collection of ontologies, possibly distributed over the internet

documentation: http://www.example.com

tasks:

- name: SearchTask

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.

- name: AnnotationTask

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.

- name: QueryRewritingTask

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.

- name: FilteringTask

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.

- name: IntegrationTask

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.

- name: QueryFormulationTask

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.

- name: MediationTask

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.

- name: ConfigurationTask

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.

- name: PersonalizationTask

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.

- name: IndexingTask

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.

- name: MatchingTask

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.