Merge branch 'staging'

ontohub · Jan 3, 2014 · 8f0b16d · 8f0b16d
2 parents 987f223 + c5413e9
commit 8f0b16d
Show file tree

Hide file tree

Showing 8 changed files with 92 additions and 94 deletions.
diff --git a/config/settings.yml b/config/settings.yml
@@ -57,3 +57,74 @@ external_repository_name: 'External'
 fallback_commit_user: 'ontohub_system'
 fallback_commit_email: 'ontohub_system@ontohub.org'
 
+# Possible values for metadata, adapted from OMV
+formality_levels:
+  - name: schema
+  - name: taxonomy
+  - name: terminology
+  - name: thesaurus
+  - name: vocabulary
+
+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: Task Ontology
+    description: describes the concepts for a specific task
+    documentation: http://www.example.com
+  - name: Upper Level Ontology
+    description: describes general, domain-independent concepts e.g. space, time
+    documentation: http://www.example.com
+  - name: Application Ontology
+    description: describes some domain in an application-dependent manner
+    documentation: http://www.example.com
+  - name: Core Ontology
+    description: describes the most important concepts in a specific domain
+    documentation: http://www.example.com
+  - name: Domain Ontology
+    description: describes some domain of the world
+    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.
diff --git a/db/migrate/20140103213700_change_type_for_task_description.rb b/db/migrate/20140103213700_change_type_for_task_description.rb
@@ -0,0 +1,13 @@
+class ChangeTypeForTaskDescription < ActiveRecord::Migration
+  def up
+    change_table :tasks do |t|
+      t.change :description, :text
+    end
+  end
+
+  def down
+    change_table :tasks do |t|
+      t.change :description, :string
+    end
+  end
+end
diff --git a/db/seeds/007-ontology_types.rb b/db/seeds/007-ontology_types.rb
diff --git a/db/seeds/008-projects.rb b/db/seeds/008-projects.rb
diff --git a/db/seeds/009-tasks.rb b/db/seeds/009-tasks.rb
diff --git a/db/seeds/010-license_models.rb b/db/seeds/010-license_models.rb
diff --git a/db/seeds/011-formality_levels.rb b/db/seeds/011-formality_levels.rb
diff --git a/lib/tasks/generate.rake b/lib/tasks/generate.rake
@@ -16,4 +16,12 @@ namespace :generate do
       end
     end
   end
+
+  desc 'Import the values for metadata'
+  task :metadata => :environment do
+    Settings.formality_levels.each { |t| FormalityLevel.create!(t.to_h) }
+    Settings.license_models.each { |t| LicenseModel.create!(t.to_h) }
+    Settings.ontology_types.each { |t| OntologyType.create!(t.to_h) }
+    Settings.tasks.each { |t| Task.create!(t.to_h) }
+  end
 end