2007/2/15, Joe Shaw <<a href="mailto:joeshaw@novell.com">joeshaw@novell.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>Jos van den Oever wrote:<br>> Shouldnt we start sharing parts of the code required to implement<br>> wasabi? I'm mainly thinking about a struct in c representing a parsed<br>> wasabi query and functions to de- and serialize these from either the
<br>> xml or the user language.<br>><br>> This should be no more than a couple of files that we can put in an<br>> xsd svn. Requirements to make it palletable for most: few deps and<br>> written in c. For C++ fans we can add a small wrapper.
<br>><br>> What do you think?<br><br>Definitely. For the spec to be useful (particularly the query language<br>part) we need either a reference implementation or a conformance test<br>(preferably both).</blockquote>
<div><br>Agreed. I have been thinking about doing something in Python, but held back a little to anticipate where a hand was needed (fx. glib bindings). However several people have already showed interest in glib bindings so I figure I can do something else (sorry qt guys - you qouldn't like my c++ :-D).
<br><br>What requirements would a reference implementation have? I'm thinking something like 30-50 files with a priori known metadata hardcoded into an "index" and small wasabi-compliant "search engine" that searches this index. To go with the bundle there could be a collection of queries with matching results. Given this it would be trivial to write a Python script that did a conformance test (on a search engine that had indexed the given files - and only them).
<br></div><br></div><br>Cheers,<br>Mikkel<br>