<br><br><div><span class="gmail_quote">2007/5/30, 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;">
Sorry forgot the most important part :)<br><br>----------------<br><br><br>Hi all,<br><br>I'd like you to take a look at the ontology sketch<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>
Thanks for the effort. I like the big picture. As always the devil is in the details :-)<br>
<br>
Just to avoid confusion: <br>
* Solid blue arrows = "is a child category of"<br>
* Dashed blue arrow = "is a child field of"<br>
* Purple arrow = "Field belongs to category" <br><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;">Points of interest:
<br>*** Sources<br> *Source hierarchy<br> *Which properties belong to content and which to source?<br><br>*** Multimedia ontology</blockquote><div><br><br>I think it would be good to able to differentiate between photos and other imagery. Visual cat can't be used for this since you would get videos under here too...
<br></div><br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">*** Contact ontology</blockquote><div><br>Do you have anything here, or is this just blank so far? Anyway I see that this can be tricky given that we want to support many protocols and home-, work-, and -mobile accounts (and be extensible as well). Here's aproposal:
<br><br>Contact.FullName<br>Contact.Name<br>Contact.MiddleName<br>Contact.Surname<br>Contact.Nickname<br><br>Contact.Nickname.<protocol> --> Contact.Nickname (screen name)<br>Contact.Account.<protocol> -->
Contact.Account (email address, msn login etc)<br><br>And a set of predefined protocols such as Phone.Home,Phone.Work, Email.,EmailJabber,IRC,MSN,Yahoo, etc. Fields such as Contact.Account.Phone.Home would derive from Contact.Account.Phone
.<br><br>This gets a little many-fielded but I fail to see how we can make it simpler.<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;">
*** Corner cases:<br> * Complex file formats like databases, mailboxes.<br> * Problematic classes like Source code.<br><br>*** DataObject properties<br> These are the most generic ones. We need to decide whether DataObject
<br>implements DC or DC is placed one level lower.</blockquote><div><br><br>I don't think that it makes sense to have (full) DC on DataObjects. Fx what is the dc:subject of an IRC-log? Maybe a subset of DC can go here...
<br><br>Speaking about DC I think (as has also been discussed in the past) that DC fields should be "abstract" in the sense that you can't assign values to them.<br></div><br><br>*** Document<br>Document.Layout
= {portrait,landscape}<br>Document.PaperType = {A4,A5,Letter, etc}<br><br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">*** Property interitance:
<br> As you may have noticed, there's no sent/recv date for messages and other<br>obvious fields are missing.</blockquote><div><br><SNIP> <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>For Email case, sent time = content creation time;<br>recv time = local copy ceation time(File creation time as repoted by the FS)</blockquote><div><br>Ok. If we do things like this these things have to be *clearly* specced out somewhere.
<br></div><br><br>Cheers,<br>Mikkel<br></div>