2007/2/20, Jos van den Oever <<a href="mailto:jvdoever@gmail.com">jvdoever@gmail.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;"> 2007/2/20, Joe Shaw <<a href="mailto:joeshaw@novell.com">joeshaw@novell.com</a>>:<br>> Hi,<br>><br>> On Tue, 2007-02-20 at 21:23 +0100, Jos van den Oever wrote:<br>> > Hehe, now _you_ are taking this spec further then intended. ;-) <br>> > I'll not get into this. On the KDE side this is something for<br>> > Sebastian Trueg (Nepomuk) to consider.<br>><br>> Heh.  Fair enough.  Should we keep it simply to the search-side of<br>> things, then? <br><br>The intention is to define a way to define metadata fields.</blockquote><div><br>Do you mean this literally - ie a mechanism for defining metadat fields? Or do you mean that we should define the fields themselves (as I would tend to). <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This is<br>required for searching and useful for metadata read/write too. So lets <br>come up with the properties we allow metadata fields to have. I think<br>what we have so far is what is required for searching too. So this<br>will not be about an API for reading and writing.</blockquote><div><br>Yes. We can postpone the API for now. The most important is the field definitions and groupings of these. <br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I would like to say that this will allow us to have common unit tests<br>for the data extractors. This is a nice boon. </blockquote><div><br> Huzaa! Cheers,<br>Mikkel<br></div><br></div>