[Xesam] Validator

[Antoni Mylka]

Sebastian, Xesamies,

AFAIU we haven't agreed on anything. I just sat down and hacked together
200 lines of code that expose the validator we had in nepomuk via an
(hopefully) easy to use ant task. It can be a part of the 'official'
build or not.

Once again, what's important for me is backward-compatibility, or at
least consciousness when making backward-incompatible changes and the
ability to asess their impact.

That's why a plea to Ivan. I suck at C. I tried looking at the source
code of your validator but I don't understand it.

Could you please describe your validator in terms similar to:'

https://sourceforge.net/apps/trac/oscaf/wiki/Validator

Basically two things
1. what triples are in the graph you're validating
2. what are the rules that define 'invalid' triple combinations

IMHO, we should make it plain before we make any claims on 'stability'
or 'backward-compatiblity'. What tools we use, is not that important. I
can even brush up on C/C++ if that's what it takes. :)

Antoni Mylka
antoni.mylka at gmail.com

Sebastian Trüg pisze:
> so you agreed on using java tools then?
> And Ivan, you will not provide an alternative?
> 
> Cheers,
> Sebastian
> 
> On Monday 27 July 2009 00:29:15 Antoni Mylka wrote:
>> Xesamies,
>>
>> After the discussion with Ivan, I've uploaded a little specification of
>> the validator we used in Nepomuk:
>>
>> https://sourceforge.net/apps/trac/oscaf/wiki/Validator
>>
>> Now I updated the validator code and wrote an ant task that encapsulates
>> it. Basically what you need to do is put a following bit of xml inside
>> build.xml:
>>
>> <onttest>
>> 	<ontologies dir="${oscaf.trunk.folder}">
>> 		<exclude name="**/README"/>
>> 		<exclude name="**/doc/**"/>
>> 		<exclude name="**/pimo/**"/>
>> 		<exclude name="**/tmo/**"/>
>> 		<exclude name="**/base/**"/>
>> 	</ontologies>
>> 	<baseontologies dir="${oscaf.trunk.folder}">
>> 		<include name="**/base/*"/>
>> 		<exclude name="**/README"/>
>> 	</baseontologies>
>> 	<testcases dir="tests" />
>> </onttest>
>>
>> The ontologies, base ontologies and test cases are specified as ant
>> FileSets: http://ant.apache.org/manual/CoreTypes/fileset.html It allows
>> for pretty fancy file choosing schemes.
>>
>> I've uploaded a tarball with the sources of the ant task, all
>> dependencies and a build.xml script that compiles the java source,
>> validates all NIE ontologies and a single example file. It's here:
>>
>> http://www.dfki.uni-kl.de/~mylka/nie-ant.tar.bz2
>>
>> Please
>> - download, untar
>> - edit the build.xml to point it at the oscaf ontologies trunk folder
>> - type 'ant'
>> - and see the validation report (or some other problem in which case
>> send me an email).
>>
>> Right now it detects 519 problems in NIE. All of them are due to missing
>> base ontologies:
>> - W3C Geo
>> - Masahide Kanzaki EXIF
>> - a little hack that states that all XSD datatypes are rdf datatypes
>>
>> The missing base ontologies are included in the tarball.
>>
>> I would like to create a tools/java folder in SVN and upload the
>> build.xml, the jars and the testcases there. I wouldn't change anything
>> in the 'ontologies' folder. If anyone is allergic to java he/she won't
>> have to check it out at all.
>>
>> More testcases will come in near future. Stay tuned.
>>
>> Any objections?
>>
>> Antoni Mylka
>> antoni.mylka at gmail.com
>>
>> _______________________________________________
>> Xesam mailing list
>> Xesam at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/xesam
> _______________________________________________
> Xesam mailing list
> Xesam at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xesam
>