[Pellet-users] Examples of When Pellet Runs Slowly

[JPQ]

This post was prompted by a post I made yesterday. The setup is somewhat
similar, but the subject matter is different.

Given the following:

1. Base.owl
       a. Two named OWL classes (simple Type-1 class descriptions) -
"Class_One", "Class_Two"

2. First_v3.owl - a single OWL class, First_Class
       a. First_v3.owl imports Base.owl
       b. A named OWL class ("First_Class")
               i. unionOf (Base:Class_One, Base:Class_Two)
              ii. Property restrictions
                     A. equivalentClass (firstClassDatatypeProperty all
xsd:integer)
                     B. equivalentClass (firstClassDatatypeProperty max 1)
       c. A datatype property - "firstClassDatatypeProperty"
               i. Domain & range not defined

3. Second_v3.owl - a single OWL class, Second_Class
       a. Second_v3.owl imports Base.owl        b. A named OWL class
("First_Class")
               i. unionOf (Base:Class_One, Base:Class_Two)
              ii. Property restrictions
                     A. equivalentClass (secondClassDatatypeProperty all
xsd:integer)
                     B. equivalentClass (secondClassDatatypeProperty
exactly 1)
       c. A datatype property - "secondClassDatatypeProperty"
               i. Domain & range not defined

4. First_and_Second_v3.owl is an OWL ontology that simply imports
First_v3.owl and Second_v3.owl

5. "first-class-individual" is asserted to be in the class extension of
"First_Class"

6. "second-class-individual" is asserted to be in the class extension of
"Second_Class"


The following describes variations in the property restrictions given in
2-b-ii and 3-b-ii. For readability purposes, two columns
("First_v3:First_Class" & "Second_v3:Second_Class") each contain the
property restriction variations listed.


          First_v3:First_Class
Second_v3:Second_Class



   1. all xsd:integer                                      all
   xsd:integer
   2. all xsd:string                                        all
   xsd:integer
   3. some xsd:integer                                  all xsd:integer
   4. all xsd:string / exactly 1                        all xsd:integer /
   exactly 1
   5. all xsd:integer / max 1                           all xsd:integer /
   exactly 1
   6. all xsd:string / max 1                             all xsd:integer
   / exactly 1
   7. some xsd:string / max 1                        all xsd:integer /
   exactly 1
   8. *** all xsd:integer / max 2                      all xsd:integer /
   exactly 1
   9. *** all xsd:integer / exactly 1                  all xsd:integer /
   max 2
   10. all xsd:integer / max 2                           all xsd:integer
   / max 2
   11. all xsd:integer / min 1                            all
   xsd:integer / exactly 1
   12. all xsd:integer / min 1                            all xsd:integer
   / min 1
   13. all xsd:integer / min 2                            all xsd:integer
   / exactly 1
   14. all xsd:integer / min 2                            all xsd:integer
   / min 2
   15. all xsd:integer / min 1                            all xsd:integer
   / max 1
   16. all xsd:integer / min 2                            all xsd:integer
   / max 1
   17. all xsd:integer / max 1                           all xsd:integer
   / min 2
   18. *** all xsd:integer / max 23                     all xsd:integer /
   min 11
   19. *** all xsd:integer / max 2                      all xsd:integer /
   min 2

The items marked with asterisks indicate those variations which had Pellet
running very slowly. Pellet (Pellet library plug-in, version 1.5.1) was run
within TopBraid Composer (version 2.4.2). At most I waited approximately one
hour to allow Pellet to complete its inferencing on the marked items.

I'm at a loss as to why this occurs with these small ontologies, and I would
greatly appreciate your feedback. Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.owldl.com/pipermail/pellet-users/attachments/20080325/0d3d9c66/attachment.htm