Hi Antoni<br><br><div class="gmail_quote">On Mon, Jul 27, 2009 at 5:39 PM, Antoni Mylka <span dir="ltr"><<a href="mailto:antoni.mylka@gmail.com">antoni.mylka@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ivan Frade pisze:<br>
<div class="im">> 1) Release a tarball with the ontologies + HTML documentation so<br>
> distributions can build packages from it, and tracker, strigi,<br>
> kde-nepomuk depend on that package.<br>
> For this we should use python/C and autotools. We have already a<br>
> "soft validator" in C, plus a basic HTML generation also in C.<br>
><br>
> This is the point we discuss on GCDS, and agree on the svn layout, use<br>
> autotools and write the HTML generation.<br>
<br>
</div>No problem as far as I'm concerned. Two questions though<br>
- what was the agreed way to add examples/testcases to the 'ontologies'<br>
folder.</blockquote><div><br> No, the idea is just to release the ontology files in a TRIG format in a well-known directory ($(PREFIX)/ontologies IIRC) + some HTML doc (so you can browse the ontology docs offline)<br><br>
No examples or test-cases for the ontology. There is no code: just the ontology definition.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
- do you intend to generate header files / vocabulary constants /<br>
whatever is the c equivalent to a class similar to<br>
<a href="http://tinyurl.com/nxfe5c" target="_blank">http://tinyurl.com/nxfe5c</a>, or leave that up to application developers?<br>
<div class="im"></div></blockquote><div><br> No, the package only provide the ontologies. Each project decides what to do with them: tracker uses the ontologies to generate the DB schema, other projects have a generic triplet store and use the ontology in their own way... The same applies to libraries: it is not clear how to expose SparQL in a programatic way, so each library can decide how to generate its own API.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>> I couldn't check the wiki page, but i guess antoni wrote down what is<br>
> his validator checking so i can cross-check what is missing in the C<br>
> version.<br>
<br>
</div>Is there something wrong with the trac wiki?</blockquote><div><br> For some reason i cannot access to the links published in the mailing list (it asks for password). I can access going to the project web page and accessing trac from there.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
> What is blocking me now to write a proper HTML generator is to decide<br>
> what language to use. I can complete the C code, or rewrite the things<br>
> in python (nicer HTML template engines, easier string handling...).<br>
> Python looks nicer but i am not sure there is a turtle parser...<br>
<br>
</div>By all means I'm for python/ruby (actually ruby more, but python will<br>
not be much of a problem either). All of them have redland bindings, and<br>
raptor does claim to support turtle.</blockquote><div><br> I never used ruby but i feel comfortable in python. I need to check the redland bindings.</div></div><br>regards,<br><br>Ivan<br>