Hi all,

I just discovered the schemagen tool, and it looks incredibly useful
to me.  I've been experimenting for a while with the command line
options, and would now like to use a configuration file instead of
passing lots of command line arguments.  However, schemagen seems to
ignore configuration files specified with the -c argument.  For
instance, my Jena installation is in /usr/local/lib/Jena-2.6.4, so I'd
thought that the following test would work (where I'm using the sample
schemagen.rdf that comes with Jena):

$ JENAROOT=/usr/local/lib/Jena-2.6.4 /usr/local/lib/Jena-2.6.4/bin/schemagen \
    -c /usr/local/lib/Jena-2.6.4/lib-src/etc/schemagen.rdf \
    -i etc/ontologies/data.owl

The sample schemagen contains, e.g.,

<sgen:Config>
    <!-- specifies that the  source document uses OWL -->
    <sgen:owl rdf:datatype="&xsd;boolean">true</sgen:owl>
    <!-- specifies that we want the generated vocab to use OntClass,
OntProperty, etc, not Resource and Property -->
    <sgen:ontology rdf:datatype="&xsd;boolean">true</sgen:ontology>

so the resulting Java class should be use OntClass, OntProperty, and
so on, but that's not happening.  I just get the RDF level encoding
(where everything is a Resource).  If I use the --ontology command
line option, though, as in:

$ JENAROOT=/usr/local/lib/Jena-2.6.4 /usr/local/lib/Jena-2.6.4/bin/schemagen \
    -c /usr/local/lib/Jena-2.6.4/lib-src/etc/schemagen.rdf \
    -i etc/ontologies/data.owl \
    --ontology

I do get OntClasses, OntProperties, and so on.  Can anyone enlighten
me as to what I'm doing wrong?

Many thanks in advance,
//JT




-- 
Joshua Taylor, http://www.cs.rpi.edu/~tayloj/

Reply via email to