Static generation of HTML

[GoogleCodeExporter]

Hi, I trie to create a script which renders static html, like the protege 
export.  Therefore I copied the code and the lib folder from owlmanager to 
owlhtml and ran ant.

The only output I get however is:

Reasoner found: OWLlink reasoner (via HTPP)
Reasoner found: HermiT
Reasoner found: Structural Reasoner
Reasoner found: JFact
Reasoner found: Pellet
Reasoner found: FaCT++

and then it does nothing. Is it intended to be run as a script?

Here is the command again and the output:

java -cp 
:./build/owlhtml.jar:./lib/FaCTPlusPlus/FaCTPlusPlus.jar:./lib/pellet/pellet-el.
jar:./lib/pellet/pellet-datatypes.jar:./lib/pellet/rdfparser.jar:./lib/pellet/pe
llet-modularity.jar:./lib/pellet/rdfapi.jar:./lib/pellet/pellet-owlapiv3.jar:./l
ib/pellet/pellet-rules.jar:./lib/pellet/pellet-core.jar:./lib/pellet/xsdlib.jar:
./lib/pellet/pellet-explanation.jar:./lib/pellet/jgrapht-jdk1.5.jar:./lib/pellet
/pellet-query.jar:./lib/pellet/relaxngDatatype.jar:./lib/pellet/aterm-java-1.6.j
ar:./lib/suggestor.jar:./lib/HermiT/HermiT.jar:./lib/HermiT/project/lib/axiom-1.
2.8.jar:./lib/HermiT/project/lib/commons-logging-1.1.1.jar:./lib/HermiT/project/
lib/dk.brics.automaton-1.11-2.jar:./lib/HermiT/project/lib/jautomata-core-2.0-al
pha-1.jar:./lib/HermiT/project/lib/jautomata-core-2.0-alpha-1-src.jar:./lib/Herm
iT/project/lib/dk.brics.automaton-1.11-2-src.jar:./lib/jfact.jar:./lib/junit.jar
:./lib/owlapi-bin.jar:./lib/owllinkapi/lib/javax.servlet.jar:./lib/owllinkapi/li
b/commons-logging-1.1.1.jar:./lib/owllinkapi/lib/org.mortbay.jetty.jar:./lib/owl
linkapi/lib/org.mortbay.jmx.jar:./lib/owllinkapi/owllink-bin.jar:./lib/log4j.jar
:./owlhtml.jar  org.coode.html.OntologyExporter sso.owl      
Reasoner found: OWLlink reasoner (via HTPP)
Reasoner found: HermiT
Reasoner found: Structural Reasoner
Reasoner found: JFact
Reasoner found: Pellet
Reasoner found: FaCT++

Original issue reported on code.google.com by kur...@googlemail.com on 20 May 2011 at 6:04

[GoogleCodeExporter]

One more comment:
I really think, that you should make a cli tool in the style of javadoc.
The layout of the protege generated html is already very nice. I wanted to 
share the .htaccess for http://nlp2rdf.lod2.eu/schema/sso/

It does content negotiation:
if you look at the owl in your browser you get the html, otherwise the RDF:
http://code.google.com/p/nlp2rdf/source/browse/ontologies/schema/.htaccess

Please do not underestimate the impact of simple solutions. Having a Java Jar 
for the CLI that produces HTML documentation for ontologies is simple, but imho 
a really good feature.

Original comment by kur...@googlemail.com on 20 May 2011 at 7:42

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Sorry, I could not find the tagged version as a file download, there are only 
server wars. 
In the SVN there is one tag and 2 branches and all look similar to the code in 
trunk.
Thank you for your answer.

Original comment by kur...@googlemail.com on 25 May 2011 at 8:55

[GoogleCodeExporter]

Hi,

If you build the tagged version of the code it should have a script that will 
do just this. I moved away from the static html gen and P4 plugin as it was 
very restrictive wrt the browser interface.

Nick

Original comment by NickIsConfused@gmail.com on 25 May 2011 at 8:56

[GoogleCodeExporter]

Or, you can use Protege4.1 with the OWLDoc plugin (which is the same code).

Original comment by NickIsConfused@gmail.com on 25 May 2011 at 8:57

[GoogleCodeExporter]

Ok, I am about to give up on this project. I actually just want something very 
simple:
Type a command like "java -cp owlhtml.jar org.coode.html.OntologyExporter  -t 
string.owl" and get some html files for it. 
But first it seems I have to build tag releases without any build.xml or 
readme.txt, get strange manifest errors all the time and security exceptions 
and finally a NullPointer. BTW I tried the tag release AND the svn bleeding 
edge. 
I am really starting to look for alternatives, now. The goal of this project 
"to produce a war" is completely useless to me, as I will neither deploy a 
jetty/tomcat to host the war file nor use your infrastructure. Also, I won't 
load 20 ontologies into Protege manually and go to export. Here is what I would 
find acceptable:

1. Cooperation: You would accept me into the project and I would contribute to 
the owldoc cli part now and then. Normally, I am used to work with Maven and a 
Decentralised Version Control System (Mercurial is easier). As you are working 
with tomcat you should consider this also. e.g. the maven tomcat plugin, builds 
the war easily and deploys it on the tomcat server with only "mvn 
tomcat:deploy" . I guess you build the war and then upload it manually? In the 
end this could also lead to a point where this project might be included into 
the LOD2 stack:
http://lod2.eu/BlogPost/677-first-release-of-the-lod2-stack.html 
This would require a Debian package (which is easily produced with Maven). The 
first thing I would do however is migrate the project to Maven and get the 
command line working.
2. Forking the project on bitbucket. Same here: first Maven and then get the 
command line working. A service would be nice: 
http://myservice.com/owldoc/make?ontology=http://nlp2rdf.lod2.eu/schema/sso/sso.
owl which gives you a zip, that you can extract in a web dir.
3. Looking for another project

I already created a fork here: 
https://bitbucket.org/kurzum/ontology-browser-fork/overview, if you are up for 
option 1 please contact me. 

Original comment by kur...@googlemail.com on 7 Oct 2011 at 6:12

[GoogleCodeExporter]

And here is the 0.1 release 
https://bitbucket.org/kurzum/ontology-browser-fork/downloads/owldoc-cli-0.1.jar

Original comment by kur...@googlemail.com on 7 Oct 2011 at 8:48