Hi<br><br> It looks like the problem is not a change of direction, but what to do with the current work. We can release a XESAM 1.0 but:<br><br>1) How many projects are going to implement it? <br>2) If the change to nepomuk based ontologies and sparQL happens and we call it XESAM 2.0... the specs will be _completely_ incompatible. <br>
<br> My point is that to release a spec just for the blessing of having a spec or because some work was already done doesn't sound right. <br><br> For the credibility of the project, i think it is as bad to release something and dont commit to it as dont release anything.<br>
<br>Ivan<br><br><div class="gmail_quote">On Sat, Apr 25, 2009 at 7:49 AM, Mikkel Kamstrup Erlandsen <span dir="ltr"><<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009/4/24 Arun Raghavan <<a href="mailto:arun@accosted.net">arun@accosted.net</a>>:<br>
<div class="im">> 2009/4/24 Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>>:<br>
> [...]<br>
>>> - Simplified DBus API: Strigi prefers less state in the API and the<br>
>>> Tracker team (that's us) want to someday have a proto that basically<br>
>>> proxies this API over UDP (so we want to reduce the amount of state<br>
>>> drastically too). We thoroughly discussed this during the Hackfest in<br>
>>> Berlin and we were almost in tears when we finally started agreeing on<br>
>>> the new direction. Let's not undo that.<br>
>>><br>
>>> Seriously.<br>
>><br>
>> Right :-) That cost us a lot of sword fighting, but the agreement is<br>
>> still there.<br>
>><br>
>> But from my perspective that doesn't leave Xesam 1.0 as irrelevant.<br>
>> But as I've hinted elsewhere I don't want to impose that one anyone.<br>
><br>
> After all the time and effort that we've put into this spec, it seems<br>
> a little overboard to just drop it as a lost cause. Especially when I<br>
> think a *lot* of the ground work to get first-class support for Xesam<br>
> 1.0 has already been done (correct me if I'm wrong).<br>
><br>
> Why not get the 1.0 implementations out there, and then work towards<br>
> getting 2.0 along in a way that converges towards the goals Philip<br>
> listed, in a shorter timeframe than 1.0 took? Especially since there<br>
> seems to be some agreement on these already. If that process seems to<br>
> be cumbersome, let's _fix_ it, rather than give up on the effort to<br>
> standardise the desktop search interface altogether.<br>
<br>
</div>I agree. However I think with all the delay we have suffered at this<br>
point it would be very bad for the project to engage in some long<br>
meta-discussion. If some parties do not feel inclined to implement 1.0<br>
I can live with that. It may happen that others implement the spec<br>
anyways. Just push onward. Like Ivan also mentioned in his latest<br>
email about the ontology it is much easier to do a healthy discussion<br>
having a stable base.<br>
<br>
If Nokia require a spec that does less roundtrips to do what they want<br>
then I think it is fair that they don't want to spend time on<br>
something they ultimately will have to redo.<br>
<br>
The bottom line: Let's JFD 1.0 and we can easily proceed on 2.0 in parallel.<br>
<br>
--<br>
Cheers,<br>
<font color="#888888">Mikkel<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Xesam mailing list<br>
<a href="mailto:Xesam@lists.freedesktop.org">Xesam@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/xesam" target="_blank">http://lists.freedesktop.org/mailman/listinfo/xesam</a><br>
</div></div></blockquote></div><br>