<br><br><div><span class="gmail_quote">2007/6/9, Evgeny Egorochkin <<a href="mailto:phreedom.stdin@gmail.com">phreedom.stdin@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;">
Source attached. Cute picture:<br><a href="http://www.freedesktop.org/wiki/PhreedomDraft?action=AttachFile&do=view&target=viz.png">http://www.freedesktop.org/wiki/PhreedomDraft?action=AttachFile&do=view&target=viz.png
</a></blockquote><div><br><br>Great work. This is really starting to look like something.<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;">
--------------<br>Design decisions proposed:<br><br>Split ontology into Xesam Core, Xesam Convenience and Xesam Mappings<br><br>Xesam Core expresses the full semantics of the ontology i.e. it is<br>self-sufficient and describes all the useful information we plan indexing.
<br><br>Xesam Convenience contains semantically irrelevant fields which are<br>subchildren of Xesam Core fields and provide nothing except more<br>human-friendly names and descriptions.<br><br>Xesam Mappings provides mapping for external standards like EXIF and vCard.
<br>For each such standard a base set of fields and categories capturing the most<br>relevant features of the standard is provided in Xesam Core.<br>The full standard or a more complete implementation is provided via Xesam
<br>Mappings.<br>The reason: excessive complexity or multiple irrelevant features of the<br>standard.<br><br>Xesam Core is the primary goal for now. The rest will follow as the need<br>arises/time allows</blockquote><div>
<br>Ok, I think this (onto split proposal) is a good idea to avoid *trying* to create the all-encompassing onto in the first take.<br><br>My only gripe is that I don't like the word "Convenience", how about "Extended" instead?
<br><br>So +1 from me if we call Xesam Convenience Xesam Extended instead :-)<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;">
VCard compatibility:<br>It is not feasible to implement the full vcard functionality. The following<br>simplifications are made:<br>* name is a single field</blockquote><div><br>I guess we can split the name up in subfields (forname, surname, middlename) in Xesam Extended or something..?
<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;">* postal addresses are single fields</blockquote><div><br>This makes sense. It would take a lot of fields to model a nationality-neutral postal address scheme.
<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;">* some obscure features are dropped like modem phone number for the sake of<br>
simplicity</blockquote><div><br>Good <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;">New design limitations:<br>1) Source and Content hierarchies are kept separate, that is no Class can
<br>inherit source and content at once<br>2) Each file is assigned at max one content and one source.</blockquote><div><br>Good - as we all agreed on :-) <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;">
------------<br>Issues:<br><br>Maybe we need a better name for MailboxItem and ArchiveItem?</blockquote><div><br>I think we should scrap the Item part of those words. This cat name is not describing what the object *is* but what the object comes from. With the Item postfixes it sounds like the object with Source=ArchiveItem comes from an item withing an archive (fx a jpg in a pdf in a zip).
<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;">Still not decided on how to PIM stuff.</blockquote><div><br>Could we rename Todo to Task instead then? Sounds less nerdy :-)
<br><br>Fields on the Task cat could be Summary, Priority, DueDate. Stuff like a Summary and Description can be derived from fields in the Content cat.<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;">
Need to revamp media ontology.<br><br>Can we count on backends being able to figure out list lengths? i.e. if we<br>have Software.depends relation, do we need Software.dependCount? I think no.<br>Either we have a *count property for things we don't describe, or we have a
<br>list of things and no *count property.</blockquote><div><br>Hmmm... This is a tricky case. The query language cannot handle this atm. - Ie searching for all SourceCode items with more than 10 depencies fx - unless the number of deps is explicitely stored in a field.
<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;">Should we elaborate comment stats for SourceCode along the way of text stats<br>
or commentCharacterCount is sufficient?</blockquote><div><br>It is sufficient for the only use case I can come up with. Finding under-documented stuff. I think we should keep it at this.<br></div><br>Questions:<br></div><br>
Afaik PDFs (and other office docs) can be password protected. Perhaps isPassWordPretected should be moved to contents?<br><br>Is there any general field that names the origin of a file? Fx a the url of a downloaded file?<br>
<br>You've added MediaList and AudioList. Would it not make sense to have a generic List object? Fx a series of images or documents might form a slideshow. Perhaps a better metaphor would be Collection. Fx. most IDEs has a project-metaphor where a bunch of files is a part of a project. With the collection metaphor we could model this.
<br><br>Now I'm at it - why not a Project cat? It could be a subcat of my suggested Collection cat. Projects have names, versions, etc... I have several programs that install project files.<br><br>Does Audio not have any fields or is it just trimmed down for display purposes?
<br><br>Cheers,<br>Mikkel<br>