2007/5/12, 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 Saturday 12 May 2007 00:14:55 Mikkel Kamstrup Erlandsen wrote:<br>> Basically we have four desktop ontologies that I know of:<br>><br>> Strigi:<br>> <a href="http://websvn.kde.org/trunk/kdesupport/strigi/src/streamanalyzer/fieldprope">
http://websvn.kde.org/trunk/kdesupport/strigi/src/streamanalyzer/fieldprope</a><br>>rties/ Tracker : <a href="http://svn.gnome.org/viewcvs/tracker/trunk/data/services/">http://svn.gnome.org/viewcvs/tracker/trunk/data/services/
</a><br>> Spotlight:<br>> <a href="http://developer.apple.com/documentation/Carbon/Reference/MetadataAttribute">http://developer.apple.com/documentation/Carbon/Reference/MetadataAttribute</a><br>>sRef/index.html<br>
>Nepomuk: ? I couldn't find one... Sebastian, Jos, Phreedom?<br><br>Parts of Nepomuk are still being drafted. Naturally it's RDF-based. I can ask<br>Nepomuk if they are ok with releasing some parts of the draft, though you can
<br>consider Strigi onto a reasonable approximation of Nepomuk onto with some<br>workarounds due to:<br>* absense of file types(as of yet)<br>* ban on multiple-node descriptions of files.<br>* some extensions in situations where Strigi had to have something before
<br>Nepomuk<br>* some files like strigi_font or strigi_trash are way to specific and will be<br>moved out of the onto and into appropriate analyzers sometime soon.<br><br>Otherwise the design ideas/criterias for Strigi onto are the same as Nepomuk
<br>and this leads to a quite predictable result.<br><br>> I've looked a bit into these and I think the Strigi one is the one closest<br>> to what I had in mind. It has received a lot of thought and seems generally
<br>> coherent.<br><br>There are several minor corrections I'd like to make, but reluctant to do so<br>until I have a critical mass of fixes and,preferably, xesam draft since this<br>also involves analyzer code changes.
<br><br>Of course, I'll let you know what I'd like to have fixed and why.<br><br>Also, I'm prepared to explain any and all design decisions behind<br>Strigi/Nepomuk onto.<br><br>> It would be ideal to store the ontology drafts in a VCS, but we
<br>> have none yet - I don't know if the wiki would be disastrous or not... Any<br>> ideas on a temporary storage idea until we get a subversion module at fdo?<br><br>Wiki is ok. The only way I see this working is to authorize one person to make
<br>changes to the onto. It's too small and has too many internal dependencies to<br>allow ad-hoc editing. Changes should be proposed, discussed and only then<br>committed.<br><br>You still can use diff on wiki article contents and send patches for
<br>discussion/approval.</blockquote><div><br><br><br>Right. The key maintainer would still have to discuss things on the list I take it?<br><br>Anyway, I would like to propose that Evgeny is our ontology-man (if he has the time (I haven't really talked to him about it)).
<br><br>To all you other Xesames: I can tell that Evgeny really digs this whole ontology deal. Atleast better than me :-) He is the one responsible for the Strigi ontology. By talking to him on IRC it is clear to me that it is founded on a lot of thought and solid reasoning. On top of that it seems that he has insight into the Nepomuk world and I really think we need to be compatible with them.
<br></div><br>If you are at all in doubt of his technical merits I bet you can ping him on #xesam@FreeNode...<br></div><br>Cheers,<br>Mikkel<br>