[Xesam] Desktop ontology svn layout

[Antoni Mylka]

Sebastian Trüg pisze:
> On Monday 29 June 2009 09:35:58 Sebastian Trüg wrote:
>> On Monday 29 June 2009 02:32:45 Leo Sauermann wrote:
>>> ok, so we agree.
>>>
>>> still - use N3 and do two files, trig sucks.
>> due to missing tool support?
>> Two files means having build tools that merge them. These cannot be based
>> on java!
> 
> actually I think this is not correct. We could have the files generated on the 
> server. Then I think it is OK to use java tools. However, if the files should 
> be generated at build-time, then we should use scripts, python or perl or bash 
> or whatever.
> 
> Is there someone with scripting skills here?
> I am thinking about 3 input files:
> 1. the common namespaces which we use for all ontologies
> 2. the actual N3 source of the ontology itself
> 3. the metadata n3 file
> 
> I am working on that now.

But this is exactly what the nepomuk ant-script did

1. common namespaces:
https://sourceforge.net/apps/trac/oscaf/browser/branches/legacy/nie_plus/nie.mapping.properties
2. ontology itself:
https://sourceforge.net/apps/trac/oscaf/browser/branches/legacy/nie_plus/output/nie.rdfs
3. metadata (generated by the ant script)
https://sourceforge.net/apps/trac/oscaf/browser/branches/legacy/nie_plus/generate-nie-html-docs.xml

I know I come late to this discussion but it seems to me that all the
use-cases for the build system you all mentioned could be achieved with
a simple adaptation of the nepomuk java setup. These are all plain CLI
applications ran from the ant script. It would be trivial to drop the
ant script and call those apps from python/ruby/shell (I personally
prefer ruby).

It seems that you prefer to write the tools from scratch in
perl/python/whatever rather than adapt the NIEOntologyUtils java code.
Are there any real technical/legal reasons not to use java?

It seems to me that from your (meaning the gnome/kde community) POV the
choice is either to work yourself into WTF-y piece of code in a language
you don't use/like and then trudge along with it or to write a proper
tool from scratch using technologies you like. If this is the only
problem than the decision is understandable. In such case though it all
boils down to the fact that there are about 10 active non-java hackers
on this list and that I haven't done (yet) what I said I would do in my
mail from 9th of June. [1]

Just wanted to know if it still makes sense to work on the java tools.

All kinds of comments welcome.

Antoni Mylka
antoni.mylka at gmail.com

[1]
http://lists.freedesktop.org/archives/xesam/2009-June/000456.html