<br><br><div><span class="gmail_quote">2007/5/21, Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2007/5/19, Jos van den Oever <<a href="mailto:jvdoever@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jvdoever@gmail.com</a>>:<div><span class="q"><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 all,<br><br>I was rereading the xesam-query.xsd and have the following remarks about it.<br><br>- There is no target namespace. This must be fixed before it becomes final.<br>- The attribute 'type' on <query> is redundant since one also use a
<br>selection for it.</blockquote></span><div><br>Why is the type attrib redundant? Fx searching for stuff of type (or "category" in our current terminology) Document and Xesam:Content.Creator=Jos needs it AFAI can see.
<br></div><br>The namespace should be fixed, that is certain. I believe the wiki page also state that... It would just be nice to know if we get those project pages on fdo or not before we settle on a namespace.<br><br>I have some other "diff"-proposals for the search spec somewhere, I'll post them in a sec...
</div></blockquote><div><br><br>Here are my proposed updates to the search spec (in addition to Jos' and Fabrice's):<br><br>1) rename iface to org.freedesktop.xesam.Search (capitalize the last word "search") according to dbus interface naming conventions
<br><br>2) spec out that client should take care to close their session objects, but that it it the servers responsibility to clear them up anyway. This can be done by logging caller name in NewSession and listening to NameOwnerChanged on
org.freedesktop.DBus on old_name->empty string.<br><br>3) Only allow UTF-8 XML in query language<br><br>4) There is no way to do the 'w' switch from user search language in xml query language. I propose to do this via a <string> attribute.
<br><br>5) And a bigger issue, that is a tough call... Should we use real dbus objects for sessions/searches? According to Havoc Pennington it doesn't take a roundtrip to the bus to register a new object, so spawning lots of search objects shouldn't flood the bus (not with object-registration requests at least).
<br><br>Cheers,<br>Mikkel<br></div><br></div>