settings.yml revision 5b096f8e55f16cabf226220f144aa484f34de68d
132N/A#
132N/A# Project configuration
132N/A#
132N/A# Environment specific settings can be overridden in:
132N/A# /config/settings/<environment>.yml
132N/A#
132N/A
132N/A# Name of the installation
132N/Aname: "MyOntohub"
132N/A
132N/A# Hostname of the installation
132N/Ahostname: example.com
132N/A
132N/A# Generalizing term "Ontology",ALternatives are M:Models and S:Specification
132N/AOMS: ontology
132N/A# In case of Model,this should be used.
132N/AOMS_qualifier: modeling
132N/A
132N/A# Optional asset host for delivery of static files (css, images, javascripts)
132N/A# asset_host: assets.example.com
132N/A
132N/A# Sender address for outgoing mail
132N/Aemail: noreply@example.com
132N/A
215N/A# Mail delivery
132N/A# http://guides.rubyonrails.org/action_mailer_basics.html#action-mailer-configuration
132N/Aaction_mailer:
132N/A delivery_method: sendmail
132N/A
132N/A# The number of days a user can access
132N/A# the website without confirming his account.
132N/Aallow_unconfirmed_access_for_days: 3
132N/A
132N/A# Limits for displaying file contents and diffs
132N/Amax_read_filesize: 524_288
132N/Amax_combined_diff_size: 1_048_576
132N/A
132N/A# Timeout for ontology parsing jobs in hours
132N/Aontology_parse_timeout: 6
132N/A
132N/A# Footer links and texts
132N/Afooter:
132N/A - text: Foo Institute
132N/A - text: About
132N/A href: http://about.example.com
132N/A
132N/A# Delivery of exceptions, disabled by default
132N/Aexception_notifier:
132N/A enabled: false
132N/A email_prefix: "[ontohub exception]"
132N/A sender_address: "exceptions@example.com"
132N/A exception_recipients:
132N/A - exception-recipient@example.com
132N/A
132N/A# Worker count
132N/Aworkers:
132N/A hets: 1
132N/A
132N/Agit:
132N/A verify_url: http://localhost/
132N/A default_branch: 'master'
132N/A push_priority:
132N/A commits: 1
132N/A changed_files_per_commit: 5
132N/A
132N/Aallowed_iri_schemes:
132N/A - http
132N/A - https
132N/A - file
132N/A - gopher
132N/A - urn
132N/A
132N/Adisplay_head_commit: false
132N/Adisplay_symbols_tab: false
132N/A
132N/Aexternal_repository_name: 'External'
132N/Afallback_commit_user: 'ontohub_system'
132N/Afallback_commit_email: 'ontohub_system@ontohub.org'
132N/A
132N/Aformat_selection: false
132N/A
132N/A# Possible values for metadata, adapted from OMV
132N/Aformality_levels:
132N/A - name: vocabulary
132N/A description: "list of words"
132N/A - name: terminology
132N/A description: "list of concepts with definitions"
132N/A - name: taxonomy
132N/A description: "terminology with subsumption hierarchy"
219N/A - name: axiomatization
1021N/A description: "ontology with axioms beyond a pure subsumption hierarchy"
220N/A # number of axioms per concept can be displayed
341N/A
341N/Alicense_models:
379N/A - name: Apple Public Source License (APSL)
411N/A url: http://www.opensource.apple.com/license/apsl/
487N/A - name: Open Software License (OSL)
706N/A url: http://opensource.org/licenses/OSL-3.0
706N/A - name: General Public License (GPL)
706N/A url: http://www.gnu.org/licenses/gpl.html
741N/A - name: IBM Public License (IBM PL)
741N/A url: http://opensource.org/licenses/IPL-1.0
706N/A - name: Common Public License (CPL)
706N/A url: http://www.eclipse.org/legal/cpl-v10.html
736N/A - name: Lesser General Public License (LGPL)
487N/A url: https://www.gnu.org/licenses/lgpl.html
704N/A - name: INTEL Open Source License (INTEL OSL)
487N/A url: http://opensource.org/licenses/Intel
704N/A - name: Modified BSD License (mBSD)
704N/A url: http://opensource.org/licenses/BSD-3-Clause
487N/A - name: Academic Free License (AFL)
487N/A url: http://opensource.org/licenses/AFL-3.0
487N/A
320N/Aontology_types:
336N/A - name: Upper Level Ontology
336N/A description: describes general, domain-independent concepts e.g. space, time
336N/A documentation: http://www.example.com
949N/A - name: Core Ontology
949N/A description: "describes the most important concepts in a specific domain (also: mid-level ontology)"
336N/A documentation: http://www.example.com
336N/A - name: Domain Ontology
336N/A description: describes some domain of the world
341N/A documentation: http://www.example.com
487N/A - name: Application Ontology
336N/A description: describes some domain in an application-dependent manner
336N/A documentation: http://www.example.com
336N/A
379N/Atasks:
379N/A - name: SearchTask
487N/A 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.
379N/A - name: AnnotationTask
379N/A 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.
411N/A - name: QueryRewritingTask
411N/A 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.
487N/A - name: FilteringTask
411N/A 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.
411N/A - name: IntegrationTask
411N/A 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.
320N/A - name: QueryFormulationTask
336N/A 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.
320N/A - name: MediationTask
336N/A 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.
320N/A - name: ConfigurationTask
949N/A 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.
132N/A - name: PersonalizationTask
949N/A 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.
949N/A - name: IndexingTask
949N/A 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.
949N/A - name: MatchingTask
949N/A 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.
949N/A