[Pellet-users] Problem Inferencing an XLink Ontology

[JPQ]

Hi, folks.

Recently, I created an XLink ontology, which is imported by a second
ontology within TopBraid Composer. The second ontology loads without error;
all references are resolvable. Unfortunately, when I run Pellet over the
second ontology, it continues to run in the realization stage. I ran Pellet
over another ontology of similar size and complexity, and it completed
inferencing within a reasonable amount of time. This second use case had no
need for the XLink ontology.

My guess is the problem may be related to the XLink ontology. A bit of
background on the XLink ontology...

TBC's import engine is presently unable to import an XML Schema that does
not contain schema definitions liftable to OWL classes. The xlinks.xsd
schema is one such schema, consisting solely of attributes and atttribute
groups. This lead me to create an XLink ontology. Basically, the attributes
are lifted to OWL datatype properties. The question was what to do with the
attribute groups. They could be expressed as OWL datatype properties, also.
However, we are then once again left with an OWL ontology where the
properties are not referenced by OWL classes. An alternate approach is to
define the attribute groups as OWL classes and use property restrictions on
the various datatype properties. This happens to work well for the XLink
ontology, since the attribute groups in the XLink schema describe attribute
usage patterns for the global attributes in the schema.

So, at this point I have an XLink ontology that complies with the concepts
outlined in the XLink reference documentation, and this ontology imports
into a second ontology without incident. I'm at a loss as to why Pellet runs
"indefinitely".

I'd appreciate your feedback on this problem. Thank you.


Regards,


Anthony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.owldl.com/pipermail/pellet-users/attachments/20080422/bd7f8b72/attachment.htm