2008/10/16 Sebastian Trüg <span dir="ltr"><<a href="mailto:strueg@mandriva.com">strueg@mandriva.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div class="Wj3C7c">On Monday 06 October 2008 22:58:06 Mikkel Kamstrup Erlandsen wrote:<br> > Hi,<br> ><br> > A few of us made a more or less complete draft of a Xesam Metadata<br> > API. I just brushed it up a bit. You can now find it here:<br> > <a href="http://xesam.org/main/XesamMetadataAPI" target="_blank">http://xesam.org/main/XesamMetadataAPI</a><br> ><br> > Please comment.<br> <br> </div></div>Hm, the way I see it this is basically an RDF API. Thus, I am coming back to<br> the "Model" part of the Soprano API [1] which I already proposed a while<br> back.<br> It allows to add Statements which are triples (or quadruples actually but you<br> could forget about that).<br> So please have a look and tell me if there are real differences because I<br> don't think so. Except for details such as the Node class which only makes<br> things more flexible.<br> We don't have to use exactly that but why not reuse it and only change it<br> slightly to adjust it to our needs? After all, this is an API which is<br> already in use.<br> <br> [1]<br> <a href="http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/soprano_server_dbus.html" target="_blank">http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/soprano_server_dbus.html</a><br> <div><div></div></div></blockquote><div><br>I think I need some more documentation (or a little help) to grok that API... <br><br> - It is unclear to me how this Model abstraction is going to be used<br><br> - What does all the ((isss)(isss)(isss)(isss)) arguments mean?<br> </div></div><br>And still, as we discussed in the past[2], I don't think exposing RDF in the API that way is the right way to go about this.<br><br>The Soprano API does contain some nice things that are not in the proposed Xesam Metadata API though. Namely iterators and signals for changes. It does however also have some shortcomings one prominent one being that it is not batch oriented.<br> <br>[2]: <a href="http://lists.freedesktop.org/archives/xesam/2008-January/000048.html">http://lists.freedesktop.org/archives/xesam/2008-January/000048.html</a><br clear="all"><br>-- <br>Cheers,<br>Mikkel<br>