[Pellet-users] Tracing the Cause of a Lengthy Inference

[Michael Smith]

On Tue, 2008-04-29 at 16:55 -0400, JPQ wrote:

> > Pellet from the command line?
> No, I ran it within TopBraid Composer. Unfortunately, I had
> difficultly running Pellet on the command line. The error messages
> seemed to indicate that Pellet was unable to resolve certain URIs, one
> of which is of the form "urn:this:that...". Honestly, I would prefer
> to run Pellet on the command line, but other than the command line
> help, I have been unable to locate any documentation. I would
> appreciate your pointing me in the right direction for any available
> documentation (other than the Javadocs API).

The Pellet FAQ [1] is a good place to find documentation.

To deal with unresolvable imports, the Pellet command line should
respect a Jena LocationMapper configuration file [2].  In your case, I
imagine you'll need to create (in the directory where you run Pellet), a
file called location-mapping.n3 with contents like the following


@prefix lm: <http://jena.hpl.hp.com/2004/08/location-mapping#>

[] lm:mapping
   [ lm:name "urn:this" ;     lm:altName "file:this.owl" ] ,
   [ lm:name "urn:that" ;     lm:altName "file:that.owl" ] . 



-- 
Mike Smith

Clark & Parsia

[1] http://pellet.owldl.com/faq/
[2] http://jena.sourceforge.net/how-to/filemanager.html