changeset 8:40adbcb2a7cc

Added merge function and FaCT++ support. Improved OBO render
author Mikel Egaña Aranguren <mikel-egana-aranguren@toolshed.g2.bx.psu.edu>
date Tue, 11 Oct 2011 11:09:52 +0200
parents 756f1f5798bf
children 14bfd77f8520
files OPPL/FaCT++-OSX-v1.5.2/32bit/libFaCTPlusPlusJNI.jnilib OPPL/FaCT++-OSX-v1.5.2/64bit/libFaCTPlusPlusJNI.jnilib OPPL/FaCT++-linux-v1.5.2/32bit/FaCT++ OPPL/FaCT++-linux-v1.5.2/32bit/libFaCTPlusPlusJNI.so OPPL/FaCT++-linux-v1.5.2/64bit/FaCT++ OPPL/FaCT++-linux-v1.5.2/64bit/libFaCTPlusPlusJNI.so OPPL/FaCT++-linux-v1.5.2/Models.lisp/DataTypeTest/DataTypeTest.conf OPPL/FaCT++-linux-v1.5.2/Models.lisp/DataTypeTest/DataTypeTest.tbox OPPL/FaCT++-linux-v1.5.2/Models.lisp/DataTypeTest/Makefile OPPL/FaCT++-linux-v1.5.2/Models.lisp/Makefile.default OPPL/FaCT++-linux-v1.5.2/Models.lisp/create-new-test OPPL/FaCT++-linux-v1.5.2/Models.lisp/options.default OPPL/FaCT++-linux-v1.5.2/Models.lisp/query.default OPPL/FaCT++-linux-v1.5.2/README OPPL/FaCT++-linux-v1.5.2/licensing/FaCT++.license.txt OPPL/FaCT++-linux-v1.5.2/licensing/gpl.txt OPPL/FaCT++-linux-v1.5.2/licensing/lgpl-2.1.txt OPPL/README OPPL/Tool.java OPPL/oppl.xml OPPL/oppl_galaxy_tool.jar OPPL/oppl_galaxy_tool_lib/FaCTpp-OWLAPI-3.2-v1.5.2.jar OPPL/oppl_galaxy_tool_lib/commons-logging-1.1.1.jar OPPL/oppl_galaxy_tool_lib/junit-4.8.2.jar OPPL/oppl_galaxy_tool_lib/junit.jar OPPL/oppl_galaxy_tool_lib/log4j-1.2.15.jar OPPL/oppl_galaxy_tool_lib/oboformat.jar OPPL/oppl_galaxy_tool_lib/owlapi-bin_2.jar OPPL/oppl_galaxy_tool_lib/owllink-bin.jar
diffstat 29 files changed, 1796 insertions(+), 30 deletions(-) [+]
line wrap: on
line diff
Binary file OPPL/FaCT++-OSX-v1.5.2/32bit/libFaCTPlusPlusJNI.jnilib has changed
Binary file OPPL/FaCT++-OSX-v1.5.2/64bit/libFaCTPlusPlusJNI.jnilib has changed
Binary file OPPL/FaCT++-linux-v1.5.2/32bit/FaCT++ has changed
Binary file OPPL/FaCT++-linux-v1.5.2/32bit/libFaCTPlusPlusJNI.so has changed
Binary file OPPL/FaCT++-linux-v1.5.2/64bit/FaCT++ has changed
Binary file OPPL/FaCT++-linux-v1.5.2/64bit/libFaCTPlusPlusJNI.so has changed
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/Models.lisp/DataTypeTest/DataTypeTest.conf	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,148 @@
+[LeveLogger]
+
+;--- Logging file name
+ file = reasoning.log
+;--- Logging level (the less level you give, the less information will be logged)
+ allowedLevel = 0
+
+
+[Tuning]
+
+;---
+;--- Option 'IAOEFLG': text ---
+;---
+;* Option 'IAOEFLG' define the priorities of different operations in TODO list. Possible values are 7-digit strings with ony possible digit are 0-6. The digits on the places 1, 2, ..., 7 are for priority of Id, And, Or, Exists, Forall, LE and GE operations respectively. The smaller number means the higher priority. All other constructions (TOP, BOTTOM, etc) has priority 0.
+;* Default value: '1263005'
+
+; IAOEFLG = 1263005
+
+;---
+;--- Option 'absorptionFlags': text ---
+;---
+;* Option 'absorptionFlags' sets up absorption process for general axioms. It is 5-letters text field; 1st symbol -- 'n' or 'c' -- (doN't) use Concept absorption; 2nd symbol -- 'n', 'r' or 'e' -- (doN't) use (Extended) Role absorption; the rest is symbols C,R,S; their order setup order of Simplification, Concept and Role absorptions performed (if possible).
+;* Default value: 'ceSCR'
+
+; absorptionFlags = ceSCR
+
+;---
+;--- Option 'alwaysPreferEquals': boolean ---
+;---
+;* Option 'alwaysPreferEquals' allows user to enforce usage of C=D definition instead of C[=D during absorption, even if implication appeares earlier in stream of axioms.
+;* Default value: 'true'
+
+; alwaysPreferEquals = 1
+
+;---
+;--- Option 'dumpQuery': boolean ---
+;---
+;* Option 'dumpQuery' dumps sub-TBox relevant to given satisfiability/subsumption query.
+;* Default value: 'false'
+
+; dumpQuery = 0
+
+;---
+;--- Option 'orSortSat': text ---
+;---
+;* Option 'orSortSat' define the sorting order of OR vertices in the DAG used in satisfiability tests (used mostly in caching). Option has form of string 'Mop', see orSortSub for details.
+;* Default value: '0'
+
+; orSortSat = 0
+
+;---
+;--- Option 'orSortSub': text ---
+;---
+;* Option 'orSortSub' define the sorting order of OR vertices in the DAG used in subsumption tests. Option has form of string 'Mop', where 'M' is a sort field (could be 'D' for depth, 'S' for size, 'F' for frequency, and '0' for no sorting), 'o' is a order field (could be 'a' for ascending and 'd' for descending mode), and 'p' is a preference field (could be 'p' for preferencing non-generating rules and 'n' for not doing so).
+;* Default value: '0'
+
+; orSortSub = 0
+
+;---
+;--- Option 'testTimeout': integer ---
+;---
+;* Option 'testTimeout' sets timeout for a single reasoning test in milliseconds.
+;* Default value: '0'
+
+; testTimeout = 0
+
+;---
+;--- Option 'useAnywhereBlocking': boolean ---
+;---
+;* Option 'useAnywhereBlocking' allow user to choose between Anywhere and Ancestor blocking.
+;* Default value: 'true'
+
+; useAnywhereBlocking = 1
+
+;---
+;--- Option 'useBackjumping': boolean ---
+;---
+;* Option 'useBackjumping' switch backjumping on and off. The usage of backjumping usually leads to much faster reasoning.
+;* Default value: 'true'
+
+; useBackjumping = 1
+
+;---
+;--- Option 'useCompletelyDefined': boolean ---
+;---
+;* Option 'useCompletelyDefined' leads to simpler Taxonomy creation if TBox contains no non-primitive concepts. Unfortunately, it is quite rare case.
+;* Default value: 'true'
+
+; useCompletelyDefined = 1
+
+;---
+;--- Option 'useLazyBlocking': boolean ---
+;---
+;* Option 'useLazyBlocking' makes checking of blocking status as small as possible. This greatly increase speed of reasoning.
+;* Default value: 'true'
+
+; useLazyBlocking = 1
+
+;---
+;--- Option 'usePrecompletion': boolean ---
+;---
+;* Option 'usePrecompletion' switchs on and off precompletion process for ABox.
+;* Default value: 'false'
+
+; usePrecompletion = 0
+
+;---
+;--- Option 'useRangeDomain': boolean ---
+;---
+;* Option 'useRangeDomain' switch on and off native support for the range and domain. This option is of internal use only. It is crusial for reasoning performance to leave this option true.
+;* Default value: 'true'
+
+; useRangeDomain = 1
+
+;---
+;--- Option 'useRelevantOnly': boolean ---
+;---
+;* Option 'useRelevantOnly' is used when creating internal DAG representation for externally given TBox. If true, DAG contains only concepts, relevant to query. It is safe to leave this option false.
+;* Default value: 'false'
+
+; useRelevantOnly = 0
+
+;---
+;--- Option 'useSemanticBranching': boolean ---
+;---
+;* Option 'useSemanticBranching' switch semantic branching on and off. The usage of semantic branching usually leads to faster reasoning, but sometime could give small overhead.
+;* Default value: 'true'
+
+; useSemanticBranching = 1
+
+[Query]
+
+;--
+;-- targets for single satisfiability (is Target sat) or subsumption (if Target [= Target2 holds) test
+;--
+
+; Target = *TOP*
+; Target2 = *BOTTOM*
+
+;***
+;*** please do not change lines below
+;***
+
+;--
+;-- target KB
+;--
+TBox = DataTypeTest.tbox
+
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/Models.lisp/DataTypeTest/DataTypeTest.tbox	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,201 @@
+; updated 05-04-06
+
+;;TEST DATA 
+(defdatarole R);
+
+;GT and LT
+;testing simple satisfiable and unsatisfiable ranges
+(defconcept TTa1 (and (some R(gt (number 18))) (some R(lt(number 60)))))
+(defconcept TTa2 (and (some R(gt (number 60))) (some R(lt(number 18)))));unsat
+(defconcept TTa3 (and (some R(lt (number 18))) (some R(gt(number 60)))));unsat
+(defconcept TTa4 (and (some R(lt (number 60))) (some R(gt(number 18)))))
+(defconcept TTa5 (and (some R(gt (number 18))) (some R(lt(number 18)))));unsat
+(defconcept TTa6 (and (some R(lt (number 60))) (some R(gt(number 60)))));unsat
+;the 4 below should eventually simplify
+(defconcept TTb1 (and (some R(gt (number 18))) (some R(gt(number 60)))))
+(defconcept TTb2 (and (some R(gt (number 60))) (some R(gt(number 18)))))
+(defconcept TTb3 (and (some R(lt (number 18))) (some R(lt(number 60)))))
+(defconcept TTb4 (and (some R(lt (number 60))) (some R(lt(number 18)))))
+(defconcept TTb5 (and (some R(gt (number 18))) (some R(gt(number 18)))))
+(defconcept TTb6 (and (some R(lt (number 60))) (some R(lt(number 60)))))
+;testing ranges together with specific values
+(defconcept TTc1 (and (some R(gt (number 18))) (some R(number 60))))
+(defconcept TTc2 (and (some R(gt (number 60))) (some R(number 18))));unsat
+(defconcept TTc3 (and (some R(lt (number 18))) (some R(number 60))));unsat
+(defconcept TTc4 (and (some R(lt (number 60))) (some R(number 18))))
+(defconcept TTd1 (and (some R(number 18)) (some R(gt (number 60)))));unsat
+(defconcept TTd2 (and (some R(number 60)) (some R(gt (number 18)))))
+(defconcept TTd3 (and (some R(number 18)) (some R(lt (number 60)))))
+(defconcept TTd4 (and (some R(number 60)) (some R(lt (number 18)))));unsat
+(defconcept TTe1 (and (some R(number 18)) (some R(lt(number 18)))));unsat
+(defconcept TTe2 (and (some R(number 60)) (some R(gt(number 60)))));unsat
+(defconcept TTe3 (and (some R(lt (number 60))) (some R(number 60))));unsat
+(defconcept TTe4 (and (some R(gt (number 18))) (some R(number 18))));unsat
+
+;GE and LT
+;testing simple satisfiable and unsatisfiable ranges
+(defconcept ETa1 (and (some R(ge (number 18))) (some R(lt(number 60)))))
+(defconcept ETa2 (and (some R(ge (number 60))) (some R(lt(number 18)))));unsat
+(defconcept ETa3 (and (some R(le (number 18))) (some R(gt(number 60)))));unsat
+(defconcept ETa4 (and (some R(le (number 60))) (some R(gt(number 18)))))
+(defconcept ETa5 (and (some R(ge (number 18))) (some R(lt(number 18)))));unsat
+(defconcept ETa6 (and (some R(le (number 60))) (some R(gt(number 60)))));unsat
+;the 4 below should eventually simplify
+(defconcept ETb1 (and (some R(ge (number 18))) (some R(gt(number 60)))))
+(defconcept ETb2 (and (some R(ge (number 60))) (some R(gt(number 18)))))
+(defconcept ETb3 (and (some R(le (number 18))) (some R(lt(number 60)))))
+(defconcept ETb4 (and (some R(le (number 60))) (some R(lt(number 18)))))
+(defconcept ETb5 (and (some R(ge (number 18))) (some R(gt(number 18)))))
+(defconcept ETb6 (and (some R(le (number 60))) (some R(lt(number 60)))))
+;testing ranges together with specific values
+(defconcept ETc1 (and (some R(ge (number 18))) (some R(number 60))))
+(defconcept ETc2 (and (some R(ge (number 60))) (some R(number 18))));unsat
+(defconcept ETc3 (and (some R(le (number 18))) (some R(number 60))));unsat
+(defconcept ETc4 (and (some R(le (number 60))) (some R(number 18))))
+(defconcept ETd1 (and (some R(number 18)) (some R(gt (number 60)))));unsat
+(defconcept ETd2 (and (some R(number 60)) (some R(gt (number 18)))))
+(defconcept ETd3 (and (some R(number 18)) (some R(lt (number 60)))))
+(defconcept ETd4 (and (some R(number 60)) (some R(lt (number 18)))));unsat
+(defconcept ETe1 (and (some R(number 18)) (some R(lt(number 18)))));unsat
+(defconcept ETe2 (and (some R(number 60)) (some R(gt(number 60)))));unsat
+(defconcept ETe3 (and (some R(le (number 60))) (some R(number 60))))
+(defconcept ETe4 (and (some R(ge (number 18))) (some R(number 18))))
+
+;GE and LE
+;testing simple satisfiable and unsatisfiable ranges
+(defconcept EEa1 (and (some R(ge (number 18))) (some R(le(number 60)))))
+(defconcept EEa2 (and (some R(ge (number 60))) (some R(le(number 18)))));unsat
+(defconcept EEa3 (and (some R(le (number 18))) (some R(ge(number 60)))));unsat
+(defconcept EEa4 (and (some R(le (number 60))) (some R(ge(number 18)))))
+(defconcept EEa5 (and (some R(ge (number 18))) (some R(le(number 18)))))
+(defconcept EEa6 (and (some R(le (number 60))) (some R(ge(number 60)))))
+;the 4 below should eventually simplify
+(defconcept EEb1 (and (some R(ge (number 18))) (some R(ge(number 60)))))
+(defconcept EEb2 (and (some R(ge (number 60))) (some R(ge(number 18)))))
+(defconcept EEb3 (and (some R(le (number 18))) (some R(le(number 60)))))
+(defconcept EEb4 (and (some R(le (number 60))) (some R(le(number 18)))))
+(defconcept EEb5 (and (some R(ge (number 18))) (some R(ge(number 18)))))
+(defconcept EEb6 (and (some R(le (number 60))) (some R(le(number 60)))))
+;testing ranges together with specific values
+(defconcept EEc1 (and (some R(ge (number 18))) (some R(number 60))))
+(defconcept EEc2 (and (some R(ge (number 60))) (some R(number 18))));unsat
+(defconcept EEc3 (and (some R(le (number 18))) (some R(number 60))));unsat
+(defconcept EEc4 (and (some R(le (number 60))) (some R(number 18))))
+(defconcept EEd1 (and (some R(number 18)) (some R(ge (number 60)))));unsat
+(defconcept EEd2 (and (some R(number 60)) (some R(ge (number 18)))))
+(defconcept EEd3 (and (some R(number 18)) (some R(le (number 60)))))
+(defconcept EEd4 (and (some R(number 60)) (some R(le (number 18)))));unsat
+(defconcept EEe1 (and (some R(number 18)) (some R(le(number 18)))))
+(defconcept EEe2 (and (some R(number 60)) (some R(ge(number 60)))))
+(defconcept EEe3 (and (some R(le (number 60))) (some R(number 60))))
+(defconcept EEe4 (and (some R(ge (number 18))) (some R(number 18))))
+
+;GT and LE
+;testing simple satisfiable and unsatisfiable ranges
+(defconcept TEa1 (and (some R(gt (number 18))) (some R(le(number 60)))))
+(defconcept TEa2 (and (some R(gt (number 60))) (some R(le(number 18)))));unsat
+(defconcept TEa3 (and (some R(lt (number 18))) (some R(ge(number 60)))));unsat
+(defconcept TEa4 (and (some R(lt (number 60))) (some R(ge(number 18)))))
+(defconcept TEa5 (and (some R(gt (number 18))) (some R(le(number 18)))));unsat
+(defconcept TEa6 (and (some R(lt (number 60))) (some R(ge(number 60)))));unsat
+;the 4 below should eventually simplify
+(defconcept TEb1 (and (some R(gt (number 18))) (some R(ge(number 60)))))
+(defconcept TEb2 (and (some R(gt (number 60))) (some R(ge(number 18)))))
+(defconcept TEb3 (and (some R(lt (number 18))) (some R(le(number 60)))))
+(defconcept TEb4 (and (some R(lt (number 60))) (some R(le(number 18)))))
+(defconcept TEb5 (and (some R(gt (number 18))) (some R(ge(number 18)))))
+(defconcept TEb6 (and (some R(lt (number 60))) (some R(le(number 60)))))
+;testing ranges together with specific values
+(defconcept TEc1 (and (some R(gt (number 18))) (some R(number 60))))
+(defconcept TEc2 (and (some R(gt (number 60))) (some R(number 18))));unsat
+(defconcept TEc3 (and (some R(lt (number 18))) (some R(number 60))));unsat
+(defconcept TEc4 (and (some R(lt (number 60))) (some R(number 18))))
+(defconcept TEd1 (and (some R(number 18)) (some R(ge (number 60)))));unsat
+(defconcept TEd2 (and (some R(number 60)) (some R(ge (number 18)))))
+(defconcept TEd3 (and (some R(number 18)) (some R(le (number 60)))))
+(defconcept TEd4 (and (some R(number 60)) (some R(le (number 18)))));unsat
+(defconcept TEe1 (and (some R(number 18)) (some R(le(number 18)))))
+(defconcept TEe2 (and (some R(number 60)) (some R(ge(number 60)))))
+(defconcept TEe3 (and (some R(lt (number 60))) (some R(number 60))));unsat
+(defconcept TEe4 (and (some R(gt (number 18))) (some R(number 18))));unsat
+
+;Doubles - not supported
+(defconcept double1 (and (some R(gt (number 18.4))) (some R(lt (number 18.5)))));unsat
+(defconcept double2 (and (some R(lt (number 18.4))) (some R(gt (number 18.5)))));unsat
+
+;Testing range cross-over
+(defconcept between1 (and (some R(between (number 28) (number 60))) (some R(between (number 18) (number 50)))))
+(defconcept inrange1 (and (some R(in-range (number 18) (number 50))) (some R(in-range (number 28) (number 60)))))
+(defconcept between2 (and (some R(between (number 18) (number 28))) (some R(between (number 50) (number 60)))));unsat
+(defconcept inrange2 (and (some R(in-range (number 50) (number 60))) (some R(in-range (number 18) (number 28)))));unsat
+
+;Check that 1a and 1b, and 2a and 2b are equivalent
+(defconcept equiv1a (and (some R(gt (number 18))) (some R(lt (number 60)))))
+(defconcept equiv1b (some R(between (number 18) (number 60))))
+(defconcept equiv2a (and (some R(ge (number 18))) (some R(le (number 60)))))
+(defconcept equiv2b (some R(in-range (number 18) (number 60))))
+
+;Strings
+(defconcept str01 (and (some R(gt(string AWord))) (some R(lt(string BWord)))))
+(defconcept str02 (and (some R(lt(string AWord))) (some R(gt(string BWord)))));unsat
+(defconcept str03 (and (some R(gt(string WordA))) (some R(lt(string WordB)))))
+(defconcept str04 (and (some R(lt(string WordA))) (some R(gt(string WordB)))));unsat
+(defconcept str05 (and (some R(gt(string A))) (some R(lt(string A)))));unsat
+(defconcept str06 (and (some R(ge(string A))) (some R(le(string A)))))
+(defconcept str07 (and (some R(gt(string A))) (some R(gt(string B)))))
+(defconcept str08 (and (some R(lt(string A))) (some R(lt(string B)))))
+(defconcept str09 (and (some R(gt(string aa))) (some R(lt(string aaa)))))
+(defconcept str10 (and (some R(gt(string aaa))) (some R(lt(string aa)))));unsat
+(defconcept str11 (and (some R(gt(string AWord))) (some R(string BWord))))
+(defconcept str12 (and (some R(lt(string AWord))) (some R(string BWord))));unsat
+
+;Subsumption tests
+(defconcept subNumA (and (some R (ge (number 5))) (some R (le (number 10))))) ; subsumes TOP
+(defconcept subNumB (and (some R (ge (number 5))) (some R (lt (number 10))))) ; subsumes a
+(defconcept subNumC (and (some R (gt (number 5))) (some R (le (number 10))))) ; subsumes a
+(defconcept subNumD (and (some R (gt (number 5))) (some R (lt (number 10))))) ; subsumes b, c (a)
+(defconcept subNumE (some R (number 5)))				    ; subsumes b (a)
+(defconcept subNumF (some R (number 10)))			    ; subsumes c (a)
+(defconcept subStrA (and (some R (ge (string a))) (some R (le (string b))))) ; subsumes TOP
+(defconcept subStrB (and (some R (ge (string a))) (some R (lt (string b))))) ; subsumes a
+(defconcept subStrC (and (some R (gt (string a))) (some R (le (string b))))) ; subsumes a
+(defconcept subStrD (and (some R (gt (string a))) (some R (lt (string b))))) ; subsumes b, c (a)
+(defconcept subStrE (some R (string a)))				     ; subsumes b (a)
+(defconcept subStrF (some R (string b)))				     ; subsumes c (a)
+
+;Mix of types unsatisfiability test
+(defconcept mix1 (and (some R (gt (number 5))) (some R (lt (string five)))));unsat
+(defconcept mix2 (and (some R (gt (number 5))) (some R (lt (string 5)))));unsat
+
+;Check that negative type saturation works correcly
+(defconcept negSat1N (and (some R (number)) (not (some R (le (number 5)))) (not (some R (number 6))) (not(some R (ge (number 7))))));unsat
+(defconcept negSat2N (and (some R (number)) (not (some R (lt (number 5)))) (not (some R (number 6))) (not(some R (ge (number 7))))))
+(defconcept negSat3N (and (some R (number)) (not (some R (le (number 5)))) (not (some R (number 6))) (not(some R (gt (number 7))))))
+(defconcept negSat4N (and (some R (number)) (not (some R (lt (number 5)))) (not (some R (number 6))) (not (some R (number 5))) (not(some R (ge (number 7))))));unsat
+(defconcept negSat5N (and (some R (number)) (not (some R (le (number 5)))) (not (some R (number 6))) (not (some R (number 7))) (not(some R (gt (number 7))))));unsat
+(defconcept negSat1S (and (some R (string)) (not (some R (le (string a)))) (not (some R (string b))) (not(some R (ge (string c))))))
+
+;negative subsumption tests
+;C = E
+;D = F
+;I subsumes A
+;J subsumes C
+;H subsumes B
+;G subsumes D
+;F subsumes B
+;E subsumes A
+;M subsumes L
+(defconcept subSumpA (not (some R(lt (number 2)))))
+(defconcept subSumpB (not (some R(gt (number 5)))))
+(defconcept subSumpC (not (some R(le (number 2)))))
+(defconcept subSumpD (not (some R(ge (number 5)))))
+(defconcept subSumpE (and (not (some R(lt (number 2)))) (not (some R (number 2)))))
+(defconcept subSumpF (and (not (some R(gt (number 5)))) (not (some R (number 5)))))
+(defconcept subSumpG (and (some R(lt (number 5)))))
+(defconcept subSumpH (and (some R(le (number 5)))))
+(defconcept subSumpI (and (some R(ge (number 2)))))
+(defconcept subSumpJ (and (some R(gt (number 2)))))
+(defconcept subSumpK (and (not (some R(number 2))) (not (some R(number 3))) (not (some R(number 4))) (some R (ge (number 2))) (some R (le (number 4)))));unsat
+(defconcept subSumpL (and (not (some R(number 2))) (not (some R(number 3))) (not (some R(number 4)))))
+(defconcept subSumpM (some R(le (number 1))))
+(defconcept subSumpN (and (not (some R(number 2))) (some R (number 2))));unsat
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/Models.lisp/DataTypeTest/Makefile	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,13 @@
+# this is automatically generate makefile for KB
+
+all: sat
+
+clean:
+	rm -f dl.res Taxonomy.Roles Taxonomy.log reasoning.log
+	rm -f dl.res.diff Taxonomy.Roles.diff Taxonomy.log.diff reasoning.log.diff
+
+KB_CONF = DataTypeTest.conf
+KB = DataTypeTest.tbox
+
+sat classify:
+	FaCT++ $(KB_CONF)
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/Models.lisp/Makefile.default	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,8 @@
+# this is automatically generate makefile for KB
+
+all: sat
+
+clean:
+	rm -f dl.res Taxonomy.Roles Taxonomy.log reasoning.log
+	rm -f dl.res.diff Taxonomy.Roles.diff Taxonomy.log.diff reasoning.log.diff
+
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/Models.lisp/create-new-test	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,60 @@
+#!/bin/bash
+
+# Script for creating new test-suit.
+# In parameters: <suit-name> <source-tbox>
+# output:
+#  - create <suit-name> directory
+#  - copy <source-tbox> into <suit-name>/<suit-name>.tbox
+#  - create Makefile and conf-file
+
+# file names
+MKNAME=./$1/Makefile
+TBOXNAME=./$1/$1.tbox
+CONFNAME=./$1/$1.conf
+
+# .orig files path
+OFP=.
+
+Usage()
+{
+	echo
+	echo "Usage: create-new-test <suit-name> <source-tbox>"
+	echo " where: <suit-name>   -- unique name for new suit"
+	echo "        <source-tbox> -- test TBox file"
+	exit 1
+}
+
+Fatal()
+{
+  echo "Fatal: directory $1 already exists"
+  exit 1
+}
+
+# check for the parameters
+if test "$1" = ""; then
+  Usage
+elif test "$2" = ""; then
+  Usage
+fi
+
+# create new subdir
+mkdir $1 || Fatal
+
+# create Makefile for the test suit
+cp $OFP/Makefile.default $MKNAME
+echo "KB_CONF = $1.conf" >> $MKNAME
+echo "KB = $1.tbox" >> $MKNAME
+echo >> $MKNAME
+echo "sat classify:" >> $MKNAME
+echo "	FaCT++ \$(KB_CONF)" >> $MKNAME
+
+# create TBox file for the test suit
+cp $2 $TBOXNAME
+
+# create Config file for the test suit
+cp $OFP/options.default $CONFNAME
+cat $OFP/query.default >> $CONFNAME
+echo "TBox = $1.tbox" >> $CONFNAME
+echo >> $CONFNAME
+
+echo "Finished!"
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/Models.lisp/options.default	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,130 @@
+[LeveLogger]
+
+;--- Logging file name
+ file = reasoning.log
+;--- Logging level (the less level you give, the less information will be logged)
+ allowedLevel = 0
+
+
+[Tuning]
+
+;---
+;--- Option 'IAOEFLG': text ---
+;---
+;* Option 'IAOEFLG' define the priorities of different operations in TODO list. Possible values are 7-digit strings with ony possible digit are 0-6. The digits on the places 1, 2, ..., 7 are for priority of Id, And, Or, Exists, Forall, LE and GE operations respectively. The smaller number means the higher priority. All other constructions (TOP, BOTTOM, etc) has priority 0.
+;* Default value: '1263005'
+
+; IAOEFLG = 1263005
+
+;---
+;--- Option 'absorptionFlags': text ---
+;---
+;* Option 'absorptionFlags' sets up absorption process for general axioms. It is 5-letters text field; 1st symbol -- 'n' or 'c' -- (doN't) use Concept absorption; 2nd symbol -- 'n', 'r' or 'e' -- (doN't) use (Extended) Role absorption; the rest is symbols C,R,S; their order setup order of Simplification, Concept and Role absorptions performed (if possible).
+;* Default value: 'ceSCR'
+
+; absorptionFlags = ceSCR
+
+;---
+;--- Option 'alwaysPreferEquals': boolean ---
+;---
+;* Option 'alwaysPreferEquals' allows user to enforce usage of C=D definition instead of C[=D during absorption, even if implication appeares earlier in stream of axioms.
+;* Default value: 'true'
+
+; alwaysPreferEquals = 1
+
+;---
+;--- Option 'dumpQuery': boolean ---
+;---
+;* Option 'dumpQuery' dumps sub-TBox relevant to given satisfiability/subsumption query.
+;* Default value: 'false'
+
+; dumpQuery = 0
+
+;---
+;--- Option 'orSortSat': text ---
+;---
+;* Option 'orSortSat' define the sorting order of OR vertices in the DAG used in satisfiability tests (used mostly in caching). Option has form of string 'Mop', see orSortSub for details.
+;* Default value: '0'
+
+; orSortSat = 0
+
+;---
+;--- Option 'orSortSub': text ---
+;---
+;* Option 'orSortSub' define the sorting order of OR vertices in the DAG used in subsumption tests. Option has form of string 'Mop', where 'M' is a sort field (could be 'D' for depth, 'S' for size, 'F' for frequency, and '0' for no sorting), 'o' is a order field (could be 'a' for ascending and 'd' for descending mode), and 'p' is a preference field (could be 'p' for preferencing non-generating rules and 'n' for not doing so).
+;* Default value: '0'
+
+; orSortSub = 0
+
+;---
+;--- Option 'testTimeout': integer ---
+;---
+;* Option 'testTimeout' sets timeout for a single reasoning test in milliseconds.
+;* Default value: '0'
+
+; testTimeout = 0
+
+;---
+;--- Option 'useAnywhereBlocking': boolean ---
+;---
+;* Option 'useAnywhereBlocking' allow user to choose between Anywhere and Ancestor blocking.
+;* Default value: 'true'
+
+; useAnywhereBlocking = 1
+
+;---
+;--- Option 'useBackjumping': boolean ---
+;---
+;* Option 'useBackjumping' switch backjumping on and off. The usage of backjumping usually leads to much faster reasoning.
+;* Default value: 'true'
+
+; useBackjumping = 1
+
+;---
+;--- Option 'useCompletelyDefined': boolean ---
+;---
+;* Option 'useCompletelyDefined' leads to simpler Taxonomy creation if TBox contains no non-primitive concepts. Unfortunately, it is quite rare case.
+;* Default value: 'true'
+
+; useCompletelyDefined = 1
+
+;---
+;--- Option 'useLazyBlocking': boolean ---
+;---
+;* Option 'useLazyBlocking' makes checking of blocking status as small as possible. This greatly increase speed of reasoning.
+;* Default value: 'true'
+
+; useLazyBlocking = 1
+
+;---
+;--- Option 'usePrecompletion': boolean ---
+;---
+;* Option 'usePrecompletion' switchs on and off precompletion process for ABox.
+;* Default value: 'false'
+
+; usePrecompletion = 0
+
+;---
+;--- Option 'useRangeDomain': boolean ---
+;---
+;* Option 'useRangeDomain' switch on and off native support for the range and domain. This option is of internal use only. It is crusial for reasoning performance to leave this option true.
+;* Default value: 'true'
+
+; useRangeDomain = 1
+
+;---
+;--- Option 'useRelevantOnly': boolean ---
+;---
+;* Option 'useRelevantOnly' is used when creating internal DAG representation for externally given TBox. If true, DAG contains only concepts, relevant to query. It is safe to leave this option false.
+;* Default value: 'false'
+
+; useRelevantOnly = 0
+
+;---
+;--- Option 'useSemanticBranching': boolean ---
+;---
+;* Option 'useSemanticBranching' switch semantic branching on and off. The usage of semantic branching usually leads to faster reasoning, but sometime could give small overhead.
+;* Default value: 'true'
+
+; useSemanticBranching = 1
+
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/Models.lisp/query.default	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,16 @@
+[Query]
+
+;--
+;-- targets for single satisfiability (is Target sat) or subsumption (if Target [= Target2 holds) test
+;--
+
+; Target = *TOP*
+; Target2 = *BOTTOM*
+
+;***
+;*** please do not change lines below
+;***
+
+;--
+;-- target KB
+;--
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/README	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,126 @@
+This is a README file for the FaCT++ v1.1.6 reasoner distribution.
+
+This file contains following information
+
+1. Introduction
+2. Contents of distribution
+3. Installation
+4. Usage
+5. Known problems
+6. Contact information
+
+1. Introduction
+---------------
+
+FaCT++ is re-implementation of the well-known FaCT Description Logic (DL) 
+Reasoner. This reasoner currently supports the SROIQ(D) description Logic
+language, which corresponds to OWL DL ontology language standard.
+The current version is 1.1.6. This is source distribution package so it can
+be used on different platforms. It was tested on Windows, Linux and MacOS X.
+
+FaCT++ is distributed under GNU Public License (GPL). Full text of license
+can be found at http://www.gnu.org/licenses/gpl.txt. Libraries that are 
+provided by the FaCT++ are distributed under the GNU Lesser Public License
+(LGPL).
+
+2. Contents of distribution
+---------------------------
+
+  file              description
+  
+- src/             FaCT++ source code
+- bin/ and lib/    FaCT++ precompiled binaries
+- Models.lisp/     examples and infrastructure for FaCT++ lisp reasoner
+- licensing/       license information
+- README           this file
+
+3. Installation
+---------------
+
+3.1 Building system from sources
+--------------------------------
+
+For building system you will need GNU c++ compiler and GNU make (version 3.3
+and higher were tested). Change GENERAL_DEFINES macro in src/Makefile.include
+to make it suitable for your computer. Then just run "make".
+
+In order to compile DIG part you will also need an XML parsing library
+Xerces-c (freely avaliable at http://xml.apache.org/xerces-c/). Make sure
+that Xerces-c package is installed system-wide or you have environment
+variable XERCESCROOT which points to Xerces-c root directory.
+
+In order to compile OWL-API interface (src/FaCTPlusPlusJNI/) it is necessary
+to have JNI development files (jni.h) available.
+
+4. Usage
+--------
+
+4.1 Standalone FaCT++ with lisp-like interface
+----------------------------------------------
+
+Models.lisp directory of this distribution contains some files that
+support FaCT++ reasoning as well as examples of KBs.
+
+To use standalone reasoner user should usually perform the following steps:
+- create an ontology using the FaCT++ input language
+- create a working directory (i.e. TEST) for FaCT++ using the command
+        create-new-test TEST ontology
+  where "ontology" is the name of the file containing your FaCT++ ontology
+- inside TEST directory run
+        make
+        
+This will run FaCT++ reasoner on the newly created config-file for the
+given ontology. The results of FaCT++'s reasoning appear in following files:
+
+- Taxonomy.Roles contains information about the roles taxonomy;
+- Taxonomy.log contains information about the concept taxonomy (if it was requested);
+- dl.res contains full information about the ontology and some statistical 
+  information about the reasoning process;
+
+4.1.1 Ontology creation
+-----------------------
+
+There are three ways of creating an ontology for FaCT++
+
+- Hand-made ontology. This way is not recommended for the end user.
+- Using OilEd (http://oiled.man.ac.uk). Load an ontology to the OilEd
+  then choose Export|FaCT++ lisp.
+- From the OWL source using the OWL Ontology Converter 
+  (http://phoebus.cs.man.ac.uk:9999/OWL/Converter). Set the ontology URL to
+  the OWL ontology, choose FaCT++ as the output language, press Convert and then
+  copy the resulting ontology text to the FaCT++ ontology file.
+
+4.1.2 Reasoning process
+-----------------------
+
+There are a number of options that could influence the reasoning process. All 
+options, their format and description are given in the config file, which is
+generated by the create-new-test script.
+
+4.2 FaCT++ as an HTTP DIG reasoner
+----------------------------------
+
+Run FaCT++.Server with optional parameter "-port <port>". Default value of
+<port> is 3490.
+
+This reasoner will avaliable at http://<host>:<port>, where <host> is
+a name of a computer running FaCT++.Server.
+
+4.3 FaCT++ as an HTTP OWL reasoner
+---------------------------------
+
+Use FaCT++ as describe in section 4.2. Then connect your OWL editor like
+Protege (http://protege.stanford.edu/) to the FaCT++ using address 
+http://<host>:<port>
+
+5. Known problems
+-----------------
+
+6. Contact information
+----------------------
+
+For any problems concerning FaCT++ please contact Dmitry Tsarkov
+(tsarkov@cs.man.ac.uk).  Any questions, suggestions or bug reports are
+welcome!
+
+Last updated: 01/05/2007
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/licensing/FaCT++.license.txt	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,30 @@
+Copyright (c) The Victoria University of Manchester 2004
+
+This program is free software; you can redistribute it and/or modif
y
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or (at
+your option) any later version.
+
+This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+USA
+
+Any questions relating to this software should be directed to:
+
+Dmitry Tsarkov
+Department of Computer Science
+University of Manchester
+Room 2.90
+Kilburn Building
+Oxford Road
+Manchester
+M13 9PL
+UK
+
+email: tsarkov@cs.man.ac.uk
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/licensing/gpl.txt	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/OPPL/FaCT++-linux-v1.5.2/licensing/lgpl-2.1.txt	Tue Oct 11 11:09:52 2011 +0200
@@ -0,0 +1,504 @@
+		  GNU LESSER GENERAL PUBLIC LICENSE
+		       Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL.  It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+  This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it.  You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+  When we speak of free software, we are referring to freedom of use,
+not price.  Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+  To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights.  These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+  For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you.  You must make sure that they, too, receive or can get the source
+code.  If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it.  And you must show them these terms so they know their rights.
+
+  We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+  To protect each distributor, we want to make it very clear that
+there is no warranty for the free library.  Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+  Finally, software patents pose a constant threat to the existence of
+any free program.  We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder.  Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+  Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License.  This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License.  We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+  When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library.  The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom.  The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+  We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License.  It also provides other free software developers Less
+of an advantage over competing non-free programs.  These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries.  However, the Lesser license provides advantages in certain
+special circumstances.
+
+  For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard.  To achieve this, non-free programs must be
+allowed to use the library.  A more frequent case is that a free
+library does the same job as widely used non-free libraries.  In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+  In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software.  For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+  Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.  Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library".  The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+		  GNU LESSER GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+  A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+  The "Library", below, refers to any such software library or work
+which has been distributed under these terms.  A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language.  (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+  "Source code" for a work means the preferred form of the work for
+making modifications to it.  For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+  Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it).  Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+  
+  1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+  You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+  2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) The modified work must itself be a software library.
+
+    b) You must cause the files modified to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    c) You must cause the whole of the work to be licensed at no
+    charge to all third parties under the terms of this License.
+
+    d) If a facility in the modified Library refers to a function or a
+    table of data to be supplied by an application program that uses
+    the facility, other than as an argument passed when the facility
+    is invoked, then you must make a good faith effort to ensure that,
+    in the event an application does not supply such function or
+    table, the facility still operates, and performs whatever part of
+    its purpose remains meaningful.
+
+    (For example, a function in a library to compute square roots has
+    a purpose that is entirely well-defined independent of the
+    application.  Therefore, Subsection 2d requires that any
+    application-supplied function or table used by this function must
+    be optional: if the application does not supply it, the square
+    root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library.  To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License.  (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.)  Do not make any other change in
+these notices.
+
+  Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+  This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+  4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+  If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library".  Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+  However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library".  The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+  When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library.  The
+threshold for this to be true is not precisely defined by law.
+
+  If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work.  (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+  Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+  6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+  You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License.  You must supply a copy of this License.  If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License.  Also, you must do one
+of these things:
+
+    a) Accompany the work with the complete corresponding
+    machine-readable source code for the Library including whatever
+    changes were used in the work (which must be distributed under
+    Sections 1 and 2 above); and, if the work is an executable linked
+    with the Library, with the complete machine-readable "work that
+    uses the Library", as object code and/or source code, so that the
+    user can modify the Library and then relink to produce a modified
+    executable containing the modified Library.  (It is understood
+    that the user who changes the contents of definitions files in the
+    Library will not necessarily be able to recompile the application
+    to use the modified definitions.)
+
+    b) Use a suitable shared library mechanism for linking with the
+    Library.  A suitable mechanism is one that (1) uses at run time a
+    copy of the library already present on the user's computer system,
+    rather than copying library functions into the executable, and (2)
+    will operate properly with a modified version of the library, if
+    the user installs one, as long as the modified version is
+    interface-compatible with the version that the work was made with.
+
+    c) Accompany the work with a written offer, valid for at
+    least three years, to give the same user the materials
+    specified in Subsection 6a, above, for a charge no more
+    than the cost of performing this distribution.
+
+    d) If distribution of the work is made by offering access to copy
+    from a designated place, offer equivalent access to copy the above
+    specified materials from the same place.
+
+    e) Verify that the user has already received a copy of these
+    materials or that you have already sent this user a copy.
+
+  For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it.  However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+  It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system.  Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+  7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+    a) Accompany the combined library with a copy of the same work
+    based on the Library, uncombined with any other library
+    facilities.  This must be distributed under the terms of the
+    Sections above.
+
+    b) Give prominent notice with the combined library of the fact
+    that part of it is a work based on the Library, and explaining
+    where to find the accompanying uncombined form of the same work.
+
+  8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License.  Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License.  However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+  9. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Library or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+  10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+  11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded.  In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+  13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation.  If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+  14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission.  For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this.  Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+			    NO WARRANTY
+
+  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+           How to Apply These Terms to Your New Libraries
+
+  If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change.  You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+  To apply these terms, attach the following notices to the library.  It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the library's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This library is free software; you can redistribute it and/or
+    modify it under the terms of the GNU Lesser General Public
+    License as published by the Free Software Foundation; either
+    version 2.1 of the License, or (at your option) any later version.
+
+    This library is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+    Lesser General Public License for more details.
+
+    You should have received a copy of the GNU Lesser General Public
+    License along with this library; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the
+  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+  <signature of Ty Coon>, 1 April 1990
+  Ty Coon, President of Vice
+
+That's all there is to it!
+
+
--- a/OPPL/README	Sun Sep 18 12:57:22 2011 +0200
+++ b/OPPL/README	Tue Oct 11 11:09:52 2011 +0200
@@ -12,8 +12,8 @@
 
 1.- Stop galaxy.
 
-2.- Copy oppl_galaxy_tool.jar and oppl_galaxy_tool_lib/ to 
-/galaxy-dist/tool-data/shared/jars/.
+2.- Copy oppl_galaxy_tool.jar, FaCT++-linux-v1.5.2/ FaCT++-OSX-v1.5.2/ 
+and oppl_galaxy_tool_lib/ to /galaxy-dist/tool-data/shared/jars/.
 
 3.- Create directory /galaxy-dist/tools/OPPL/.
 
@@ -43,15 +43,33 @@
 Ontology Pre Processor Language
 	>> Execute an OPPL file against an OWL file 
 
+An ontology produced by another galaxy tools can also be used
+
 
 
 FORESEEN FEATURES
 =================
 
 Choose which inferred axioms to add to the output ontology (Right now 
-only subsumption is available).
+only subsumption between named classes is available).
+
+OWLLink support.
+
+
+
+KNOWN BUGS AND ISSUES
+=====================
 
-FaCT++ and OWLLink support.
+Currently Galaxy interprets any information thrown to stderr as a tool
+error, which is bad since OPPL (And many other tools) throw info to 
+sdterr even if working properly. In OPPL Galaxy, stderr is redirected to 
+/dev/null to avoid the problem, but that means that OPPL Galaxy does not 
+fail gracefully (It simply stops). A wrapper will be implemented.
+
+http://wiki.g2.bx.psu.edu/Future/Job%20Failure%20When%20stderr
+
+OBO rendering does not work properly if the URIs lack the fragment or
+if an object property lacks an rdfs:label.
 
 
 
@@ -104,7 +122,8 @@
 You should have received a copy of the GNU General Public License
 along with this program.  If not, see <http://www.gnu.org/licenses/>.
 
-OPPL, OWL API and Pellet have their own licenses.
+OPPL API, OWL API, Pellet, HermiT, FaCT++ and OBOformat have their own 
+licenses.
 
 Galaxy is distributed as open source under the conditions of the 
 Academic Free License (http://www.opensource.org/licenses/academic.php).
--- a/OPPL/Tool.java	Sun Sep 18 12:57:22 2011 +0200
+++ b/OPPL/Tool.java	Tue Oct 11 11:09:52 2011 +0200
@@ -17,12 +17,17 @@
 
 package es.upm.fi.dia.oeg.oppl.galaxy;
 
+import java.io.BufferedWriter;
 import java.io.File;
-import java.io.FileNotFoundException;
+//import java.io.PrintWriter;
+//import java.io.FileNotFoundException;
+import java.io.IOException;
+import java.io.OutputStreamWriter;
+import java.net.URISyntaxException;
 import java.util.ArrayList;
 import java.util.List;
 import java.util.Scanner;
-import java.util.logging.Level;
+//import java.util.logging.Level;
 import java.util.logging.Logger;
 
 import org.coode.oppl.ChangeExtractor;
@@ -30,29 +35,46 @@
 import org.coode.oppl.OPPLScript;
 import org.coode.oppl.ParserFactory;
 import org.coode.oppl.exceptions.QuickFailRuntimeExceptionHandler;
-import org.coode.oppl.log.Logging;
+//import org.coode.oppl.log.Logging;
 import org.coode.owlapi.obo.parser.OBOOntologyFormat;
 import org.coode.parsers.ErrorListener;
 import org.coode.parsers.LoggerErrorListener;
+//import org.obolibrary.obo2owl.Owl2Obo;
+//import org.obolibrary.oboformat.model.OBODoc;
+//import org.obolibrary.oboformat.writer.OBOFormatWriter;
 import org.semanticweb.owlapi.apibinding.OWLManager;
 import org.semanticweb.owlapi.io.RDFXMLOntologyFormat;
 import org.semanticweb.owlapi.io.SystemOutDocumentTarget;
+import org.semanticweb.owlapi.model.AddAxiom;
 import org.semanticweb.owlapi.model.IRI;
+import org.semanticweb.owlapi.model.OWLAnnotation;
+import org.semanticweb.owlapi.model.OWLAnnotationProperty;
 import org.semanticweb.owlapi.model.OWLAxiom;
 import org.semanticweb.owlapi.model.OWLAxiomChange;
+import org.semanticweb.owlapi.model.OWLClass;
 import org.semanticweb.owlapi.model.OWLDataFactory;
+import org.semanticweb.owlapi.model.OWLLiteral;
+//import org.semanticweb.owlapi.model.OWLObjectProperty;
 import org.semanticweb.owlapi.model.OWLOntology;
+import org.semanticweb.owlapi.model.OWLOntologyChange;
 import org.semanticweb.owlapi.model.OWLOntologyCreationException;
 import org.semanticweb.owlapi.model.OWLOntologyIRIMapper;
 import org.semanticweb.owlapi.model.OWLOntologyManager;
 import org.semanticweb.owlapi.model.OWLOntologyStorageException;
+//import org.semanticweb.owlapi.owllink.OWLlinkHTTPXMLReasonerFactory;
 import org.semanticweb.owlapi.reasoner.InferenceType;
 import org.semanticweb.owlapi.reasoner.OWLReasoner;
 import org.semanticweb.owlapi.reasoner.OWLReasonerFactory;
 import org.semanticweb.owlapi.util.InferredAxiomGenerator;
 import org.semanticweb.owlapi.util.InferredOntologyGenerator;
 import org.semanticweb.owlapi.util.InferredSubClassAxiomGenerator;
+import org.semanticweb.owlapi.util.OWLEntityRenamer;
+import org.semanticweb.owlapi.util.OWLOntologyMerger;
 import org.semanticweb.owlapi.util.SimpleIRIMapper;
+import org.semanticweb.owlapi.vocab.OWL2Datatype;
+import org.semanticweb.owlapi.vocab.OWLRDFVocabulary;
+
+import uk.ac.manchester.cs.factplusplus.owlapiv3.FaCTPlusPlusReasonerFactory;
 
 import com.clarkparsia.pellet.owlapiv3.PelletReasonerFactory;
 
@@ -64,18 +86,20 @@
 public class Tool {
 
 	/**
-	 * @throws FileNotFoundException 
 	 * @throws OWLOntologyCreationException 
 	 * @throws OWLOntologyStorageException 
+	 * @throws IOException 
+	 * @throws URISyntaxException 
 	 */
-	public static void main(String[] args) throws FileNotFoundException, OWLOntologyCreationException, OWLOntologyStorageException {		
+	public static void main(String[] args) throws OWLOntologyCreationException, OWLOntologyStorageException, IOException, URISyntaxException {		
 		// Get the arguments from command-line
 		String OWLFilePath = args [0]; 
 		String OPPL_script_file = args [1];
 		String Output_format = args [2]; // OWL|OBO
-		String Add_inferred = args [3]; // Add_inferred|Whatever
-		String imports_file_path = args [4]; // Flat tab delimited file: URI	Document URI
-		String reasoner_type = args [5]; // Pellet|HermiT
+		String Add_inferred = args [3]; // AddInferred|Whatever
+		String imports_file_path = args [4]; // NoImports|Flat tab delimited file: URI	Document URI
+		String reasoner_type = args [5]; // Pellet|FaCTPlusPlus|HermiT
+		String merge_URI = args [6]; // NoMerge|URI for merged ontology
 		
 		// Load the main ontology		
 		File owl_file = new File(OWLFilePath);
@@ -97,21 +121,33 @@
 			}
 			imports_input.close();
 		}
-		OWLDataFactory factory = manager.getOWLDataFactory();
 		OWLOntology OWL_ontology = manager.loadOntologyFromOntologyDocument(owl_file);
 		
 		// Reasoner
 		OWLReasonerFactory reasonerFactory = null;
 		OWLReasoner reasoner = null;
+		
+		// Pellet
 		if(reasoner_type.equals("Pellet")){
 			reasonerFactory = new PelletReasonerFactory(); 
 			reasoner = reasonerFactory.createReasoner(OWL_ontology);
 		}
+		// FaCTPlusPlus
+		else if (reasoner_type.equals("FaCTPlusPlus")){
+			reasonerFactory = new FaCTPlusPlusReasonerFactory();
+			reasoner = reasonerFactory.createReasoner(OWL_ontology);
+		}
+		// HermiT
 		else{
 			reasonerFactory = new Reasoner.ReasonerFactory();
 			reasoner = reasonerFactory.createReasoner(OWL_ontology);
 		}
 		
+		// OWLLink: The problem is that Racer, for example, listens in 8080, the same port as Galaxy
+		// I have to change Racer settings and OWLLink settings
+//		OWLlinkHTTPXMLReasonerFactory factory = new OWLlinkHTTPXMLReasonerFactory();
+//		reasoner = factory.createReasoner(OWL_ontology);
+		
 		// Load the flat file with script in memory
 		String OPPL_script_source = "";
 		File file = new File(OPPL_script_file);
@@ -136,20 +172,100 @@
 		manager.applyChanges(changes);
 		
 		// Add the inferred axioms as asserted axioms to the original ontology
-		if(Add_inferred.equals("Add_inferred")){
+		if(Add_inferred.equals("AddInferred")){
 			reasoner.precomputeInferences(InferenceType.CLASS_HIERARCHY);
 			List<InferredAxiomGenerator<? extends OWLAxiom>> gens = new ArrayList<InferredAxiomGenerator<? extends OWLAxiom>>();
 			gens.add(new InferredSubClassAxiomGenerator());
 			InferredOntologyGenerator iog = new InferredOntologyGenerator(reasoner, gens);
 			iog.fillOntology(manager, OWL_ontology);	
 		}
+		
+		// Print the ontology to the standard output so other galaxy tools can operate on it
+		
+		// Do not merge ontologies
+		if(merge_URI.equals("NoMerge")){
+			saveOntology(manager, OWL_ontology, Output_format);
+		}
+		// Merge ontologies
+		else{	
+			OWLOntologyMerger merger = new OWLOntologyMerger(manager);
+			IRI mergedOntologyIRI = IRI.create(merge_URI);
+			OWLOntology merged = merger.createMergedOntology(manager, mergedOntologyIRI);
+			saveOntology(manager, merged, Output_format);
+		}
+	}
+	
+	private static void saveOntology (OWLOntologyManager manager, OWLOntology ontology, String Format) throws OWLOntologyStorageException, IOException, URISyntaxException {
+		
+		// OBO format
+		if(Format.equals("OBO")){
+			
+			// OWL API generates bad OBO but OBOformat doesn't work either so I correct the OWL API problems (More predictable) in a temporary file
+			// Very inefficient but no time for another solution
+			
+			OWLDataFactory factory = manager.getOWLDataFactory();
+			
+			OWLEntityRenamer renamer = new OWLEntityRenamer (manager, manager.getOntologies());
+			OWLAnnotationProperty label = factory.getOWLAnnotationProperty(OWLRDFVocabulary.RDFS_LABEL.getIRI());
+			
+			for(OWLClass cls : ontology.getClassesInSignature()){
+				// Remove annotations (OWL API generates bad OBO annotations)
+				
+				// Keep rdfs:label
+				String class_name = null;
+				for (OWLAnnotation annotation : cls.getAnnotations(ontology, label)) {
+	                if (annotation.getValue() instanceof OWLLiteral) {
+	                    OWLLiteral val = (OWLLiteral) annotation.getValue();
+	                    class_name = val.getLiteral();
+	                }
+	            }
+							
+//				I have to remove all the annotations cause I don't know which ones are rendered properly
+				manager.removeAxioms(ontology,ontology.getAnnotationAssertionAxioms(cls.getIRI()));
+				
+				// Add rdfs:label again
+				OWLAnnotation labelAnno = factory.getOWLAnnotation(factory.getOWLAnnotationProperty(
+				OWLRDFVocabulary.RDFS_LABEL.getIRI()),factory.getOWLLiteral(class_name,OWL2Datatype.XSD_STRING));
+				OWLAxiom ax = factory.getOWLAnnotationAssertionAxiom(cls.getIRI(), labelAnno);
+				manager.applyChange(new AddAxiom(ontology, ax));
+				
+				// Rename entities
+				String cls_IRI = cls.getIRI().toString();
+				String cls_proper_IRI = cls_IRI.replace("_", ":");
+				List<OWLOntologyChange> changes = renamer.changeIRI(cls, IRI.create(cls_proper_IRI));
+				manager.applyChanges(changes);
+			}
+			
+			File file = new File("tmp.obo");
+			manager.saveOntology(ontology, new OBOOntologyFormat(), IRI.create(file.toURI()));
+			BufferedWriter bw = new BufferedWriter(new OutputStreamWriter(System.out));		
+			Scanner input = new Scanner(file);
+			String buffer = "";
 
-		// Print the ontology to the standard output so other galaxy tools can operate on the output	
-		if(Output_format.equals("OBO")){
-			manager.saveOntology(OWL_ontology, new OBOOntologyFormat(), new SystemOutDocumentTarget());
+			while(input.hasNext()){
+				String nextLine = input.nextLine();
+				if(nextLine.contains("[Term]") || nextLine.contains("[Typedef]")){
+					if(buffer.isEmpty()){
+						bw.write(buffer);
+						bw.newLine();
+					}
+				}
+				if(!nextLine.contains("is_a: Thing") && !nextLine.contains("auto-generated-by:") && !nextLine.contains("id_space:") && !nextLine.contains("! ----")){
+					if(!nextLine.isEmpty() && !buffer.contains("relationship:")){
+						bw.write(nextLine);
+						bw.newLine();
+					}
+				}
+				buffer = nextLine;
+			}
+			input.close();
+			bw.close();
+			file.delete();
 		}
+		
+		//OWL format
 		else{
-			manager.saveOntology(OWL_ontology, new RDFXMLOntologyFormat(), new SystemOutDocumentTarget());
+			manager.saveOntology(ontology, new RDFXMLOntologyFormat(), new SystemOutDocumentTarget());
 		}
 	}
 }
--- a/OPPL/oppl.xml	Sun Sep 18 12:57:22 2011 +0200
+++ b/OPPL/oppl.xml	Tue Oct 11 11:09:52 2011 +0200
@@ -1,39 +1,87 @@
-<tool id="oppl" name="Execute an OPPL file against an ontology" version="1.0.4">
+<tool id="oppl" name="Execute an OPPL file against an ontology" version="1.0.5">
 	<description>It executes an OPPL script against the input ontology and generates a new ontology with the changes described in the OPPL script</description>
 
 	<!-- The command execution of the conditional is tacky, I think, but it works! -->
 	<!-- Galaxy is not happy with OPPL throwing info into stderr, and I have redirected stderr to /dev/null, which is a bad solution since OPPL galaxy does not inform properly when it fails -->
 	<!-- More info on the stderr issue: http://wiki.g2.bx.psu.edu/Future/Job%20Failure%20When%20stderr -->
+	
+
+	<!-- For big ontologies I use -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 If that's too much for your machine simply delete or modify at will -->
 
 	<command>
-		#if $import_opts.imports_select==False #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred NoImports $reasoner > $output 2>/dev/null
-		#else #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred $imports $reasoner > $output 2>/dev/null
+		#if $import_opts.imports_select==False #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred NoImports $reasoner NoMerge > $output 2>/dev/null
+		#else #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred $imports $reasoner $merged > $output 2>/dev/null
+		#end if
+	</command> 
+	
+	
+	<!-- If you are planning to use FaCT++ you have to uncomment bellow (And comment the one above) and replace the -Djava.library.path with the appropiate JNI library path for your platform:FaCT++-linux-v1.5.2/64bit, FaCT++-linux-v1.5.2/32bit, FaCT++-OSX-v1.5.2/64bit, ...... -->
+	<!-- Using this setting doesn't upset the rest of the reasoners so you may as well leave it on if you plan to switch between FaCT++, Pellet and HermiT -->
+	
+	<!--<command>
+		#if $import_opts.imports_select==False #java -Djava.library.path=${__tool_data_path__}/shared/jars/FaCT++-linux-v1.5.2/64bit -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred NoImports $reasoner NoMerge > $output 2>/dev/null
+		#else #java -Djava.library.path=${__tool_data_path__}/shared/jars/FaCT++-linux-v1.5.2/64bit -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred $imports $reasoner $merged > $output 2>/dev/null
 		#end if
-	</command>
+	</command>-->
+	
+	
+	<!-- For debugging simply remove 2>/dev/null Or uncomment bellow. It will fail always (Due to OPPL messages) but at least it will be informative -->
+	
+	<!--<command>
+		#if $import_opts.imports_select==False #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred NoImports $reasoner no_merge > $output
+		#else #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred $imports $reasoner $merged > $output 
+		#end if
+	</command>-->
+	
 		
-	<!-- For big ontologies use something like java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar -->
+	<!-- EXPERIMENTS AND HOUSE KEEPING-->
+	<!--<command>java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred $imports $reasoner $merged > $output 2>/dev/null</command> -->
+	<!--<command>
+		#if $import_opts.imports_select==False #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred NoImports $reasoner NoMerge > $output 2>/dev/null
+		#else 
+		  #if $merge_opts.merge_select==False #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred NoImports $reasoner NoMerge > $output 2>/dev/null
+		  #else #java -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_galaxy_tool.jar $input $OPPL $format $inferred $imports $reasoner $merged > $output 2>/dev/null
+		  #end if
+		#end if
+	</command>-->
 
 	<inputs>
 		<param format="text" name="input" type="data" label="Input ontology file"/>
 		<param format="text" name="OPPL" type="data" label="OPPL file"/>
 		<conditional name="import_opts">
 			<param name="imports_select" type="boolean" value="False" truevalue="imports_yes" falsevalue="imports_no" label="Tick the box if the loaded ontology includes OWL imports"/>
-			<when value="imports_no"/>
+
+			<!-- EXPERIMENTS AND HOUSE KEEPING-->
+			<!--<when value="imports_no"/> -->
 			<!--<when value="imports_no">
-				<param type="hidden" name="imports" value="NoImports"/>
+				<param type="hidden" name="merged" value="no_merge"/>
 	    		</when>-->
+			
 			<when value="imports_yes">
-                		<param format="text" name="imports" type="data" label="OWL imports URI mapping file"/>
+				       		
+				<param format="text" name="imports" type="data" label="OWL imports URI mapping file"/>
+				
+				<!-- EXPERIMENTS AND HOUSE KEEPING-->
+				<!--<conditional name="merge_opts">
+				    <param name="merge_select" type="boolean" value="False" truevalue="merge_yes" falsevalue="merge_no" label="Tick the box to merge ontologies"/>
+				    <when value="merge_yes">
+				      <param name="merged" type="text" size="100" value="http://oppl-galaxy/merged" label="Type an URI or use the default URI" />  
+				    </when>
+				</conditional>-->  
+				<!--<param format="text" name="merged" type="data" label="OWL "/>-->
+				
             		</when>
 		</conditional>
 		<param name="format" type="select" label="Choose ontology output format">
 			<option value="OWL" selected="true">OWL</option>
 			<option value="OBO">OBO</option>
 		</param>
-		<param name="inferred" type="boolean" value="False" truevalue="Add_inferred" falsevalue="Gora_ni" label="Add inferred subsumption axioms to output ontology"/>
+		<param name="inferred" type="boolean" value="False" truevalue="AddInferred" falsevalue="Gora_ni" label="Add inferred subsumption axioms to output ontology"/>
+		<param name="merged" type="text" size="100" value="NoMerge" label="To merge the ontologies, type an URI for the new ontology (Leave NoMerge for not merging)" />
 		<param name="reasoner" type="select" label="Choose reasoner">
 			<option value="Pellet" selected="true">Pellet</option>
 			<option value="HermiT">HermiT</option>
+			<option value="FaCTPlusPlus">FaCT++</option>
 		</param>
 
 	</inputs>
@@ -48,6 +96,7 @@
 			<param name="format" value="OWL"/>
 			<param name="inferred" value="False"/>
 			<param name="reasoner" value="Pellet"/>
+			<param name="merged" value="no_merge"/>
 			<output name="out_file" file="test_new.owl"/>	
 		</test>
 	</tests>
@@ -55,7 +104,7 @@
 
 **About OPPL-Galaxy**
 
-  OPPL-Galaxy can be used to execute an OPPL script against an ontology, generating a new ontology. OPPL (Ontology Pre Processor Language) is a high level scripting language, based in the Manchester OWL Syntax, to automate the manipulation of an ontology. An OPPL script (See test.oppl) defines a query to be performed against the ontology, and some actions (Adding or removing axioms) that affect the entities that will be retrieved. Those entities can be named or defined by a variable. OPPL is a powerful method for defining and executing modelling patterns that are repeated in an ontology, saving time and effort.  
+  OPPL-Galaxy can be used to execute an OPPL script against an ontology, generating a new ontology. OPPL (Ontology Pre Processor Language) is a high level scripting language, based in the Manchester OWL Syntax, to automate the manipulation of an ontology. An OPPL script (See test.oppl) defines a query to be performed against the ontology, and some actions (Adding or removing axioms) that affect the entities that will be retrieved. Those entities can be named or defined by a variable. OPPL is a powerful method for defining and executing modelling patterns that are repeated in an ontology, saving time and efforts.  
 
 **Formats**
 
@@ -77,7 +126,9 @@
  
   The inferred subsumption axioms can be added to the output ontology as asserted axioms. 
 
-  The reasoner can be Pellet or HermiT. Sometimes, if an execution fails it can be fixed by using a different reasoner. 
+  The reasoner can be Pellet, HermiT FaCT++. Sometimes, if an execution fails it can be fixed by using a different reasoner. 
+
+  If OWL imports are used, all the ontologies (Main one and imported ones) can be merged in a single ontology for the output.
 
 **More information**
 
@@ -90,6 +141,10 @@
   http://clarkparsia.com/pellet
 
   http://hermit-reasoner.com/
+  
+  http://code.google.com/p/factplusplus/
+  
+  http://code.google.com/p/oboformat/
 
 **Contact**
 
Binary file OPPL/oppl_galaxy_tool.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/FaCTpp-OWLAPI-3.2-v1.5.2.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/commons-logging-1.1.1.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/junit-4.8.2.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/junit.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/log4j-1.2.15.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/oboformat.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/owlapi-bin_2.jar has changed
Binary file OPPL/oppl_galaxy_tool_lib/owllink-bin.jar has changed