[XESAM] Ontology snapshot

[Fabrice Colin]

On 6/3/07, Evgeny Egorochkin <phreedom.stdin at gmail.com> wrote:
> * video class is actually video+audio
> * since it's impossible to properly inherit both image and audio properties
> for audio+video, Image properties get inherited and the most important audio
> properties get copied from audio class, but are not directly related to
> their "prototypes".
>
On first look, this doesn't seem so cumbersome.

> User Annotation:
>
> Need feedback on user annotation/user-provided metadata.
> Everything I can come up with is:
> *keywords
> *title( file name can be considered title as well, since it's exactly this:
>         user's title for the content)
> *description
> *comment
> *rating
> *Usage intensity(possibly several fields like how many times opened, total
>         usage/edit/view time)
>
> Some of these are source-specific
>
> On top of this some apps have user annotation info stored in a separate DB.
> i.e.  while file source is the file system, usage stats are stored somewhere
> else.
>
> Another point to consider: there can be several users. Or can't?
>
Yes, there can be, bu I wouldn't worry about this. Who can edit which field is
better left to the application.

> >*** Need feedback BADLY on sources and user annotation. Wake up people!
>
Sorry, I don't understand why some of the above are source specific.

> Thumbnails:
>
> What to do with them?
>
They would fall under Image. Isn't that good enough ?

A few other comments follow :

Aren't Message.primaryRecipient and Message.recipient actually the same
thing ?

Is Software for packages ? If so, I would prefer the name SoftwarePackage.
Requires would be useful as property.

There's a typo in the comment of Source.md5Hash.

I haven't followed the conversation very closely, so please excuse me if this
has been answered already : if I understand correctly, a File can't also be a
Document ?

Fabrice