2007/5/2, Evgeny Egorochkin <<a href="mailto:phreedom.stdin@gmail.com">phreedom.stdin@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;">
On Wednesday 02 May 2007 15:46:15 jamie wrote:<br>> On Wed, 2007-05-02 at 14:13 +0200, Sebastian Trüg wrote:<br>> > Hmm, so now you ignore RDF?<br>> > Don't get me wrong, it is your project, so in the end it is your
<br>> > decision. I am just a little confused why we have this wiki page then. :)<br>><br>> Im too busy (until mid-may) to comment on the spec in much detail<br>><br>> perhaps we can arrange an online discussion mid may to flesh this all
<br>> out<br>><br>> I have a few concerns with the nature of the proposed desktop file spec.<br>><br>> I agree its important the desktop file should be easily convertible to<br>> rdf but we do want to eliminate the complexity (and extra overhead of
<br>> rdf) as much as possible from it - that is the point of having the<br>> desktop file.<br><br>I think still this compexity issue is not an issue at all. The reason I think<br>so is:<br>1) most of metametadata definitions will be provided by Xesam
<br>2) code to parse this in the database will be written only once<br>3) If a dev needs an exotic field, somebody can help. It's not much of work.</blockquote><div><br>Don't underestimate where newcomer devs poke around. I clearly remember myself a good while back poking around with some fancy gnome-vfs code, some objects read as .desktop files, and even if I didn't know anything about those at that time I could readily work with them. Who knows - if that had been some obscure format (sorry I don't mean that rdf is obscure :-)) I might have stopped there and might not have been here today...
<br><br>So even if most apps will use a helper lib don't forget that we should also make it easy for people to poke around. Didn't we all start that way?<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;">
So what is more important is flexibility, extensibility and compatibility.</blockquote><div><br>Don't the .desktop-approach have that? <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;">
Also, it is important to act fast, otherwise the goal of compatibility is<br>unattainable since much of the code gets written around metadata spec.<br>Analyzers are written to extract data and feed in to the indexer in a specific
<br>format. It becomes a real problem if our projects do this in a different way.</blockquote><div><br>100% right. This is a problem that is hard to address. The only solution is just to not despair and just keep the train rolling, panic solutions are deemed to end up disastrous at some point.
<br><br>Cheers,<br>Mikkel <br></div><br></div><br>