W3C home > Mailing lists > Public > public-lod@w3.org > July 2009

Re: looking for an event ontology/vocabulary

From: Yves Raimond <yves.raimond@gmail.com>
Date: Wed, 29 Jul 2009 17:54:01 +0100
Message-ID: <82593ac00907290954n1b09b4aen6e7df32e052d6ee3@mail.gmail.com>
To: Pat Hayes <phayes@ihmc.us>
Cc: David Canos <davidcanos@gmail.com>, public-lod <public-lod@w3.org>

> Indeed. However, it suffers from one glaring defect, which may simply be a
> problem of documentation: i does not explain its terms. In particular, it
> refers to a 'factor' of an event, without anywhere saying anything, either
> in the axioms or in the documentation, to explain what this strange term is
> supposed to mean. It is not normal English usage to refer to a 'factor' of
> an event, so ordinary English usage is no guide. The documentation at
> http://motools.sourceforge.net/event/event.html#term_Factor
> says  an event:Factor is 'everything used as a factor in an event', which is
> completely useless as it provides no explanatory information whatsoever. If
> an explanation of event:Foodle was that it described all the foodles of an
> event, that would be similarly useless as documentation. Can you say WHAT
> YOU MEAN by a 'factor'? If that is too much to ask, can you give some
> EXAMPLES both of factors and of non-factors of an event?

Wow. No need to shout!!!!

Anyway, yes, the documentation is not particularly good, for the only
reason that most people got it from the examples (which is apparently
wrong or not enough, then?) and so we didn't got the incentive to
write a better one. Among those examples, you have:

* A score in a musical performance
* A musical instrument in a musical performance
* A piece of text in a reading
* A microphone in a recording

The disjoint statement between agent and factor defines factors as
something that doesn't have an active role in the event. Sorry it
isn't reflected in the html doc (yes, my small specgen script doesn't
capture everything).

Also, we are perfectly open for improvements, so if you have any
suggestions for improvement or better description of terms, feel free.
There is even an open SVN (motools project on Sourceforge, in the
event subdirectory), where you can directly commit stuff.

There are also a bit more details in my thesis.


> It is not enough to
> only give examples, as this does not help the reader understand the limits
> of your conceptual idea. For example, can something be both and agent and a
> factor in an event? (Can you say, briefly, why or why not?) And so on. I
> know this is not easy, and it may be impossible to give a 'definition' of
> the term, but surely you can give SOME guidance to the user, if you are
> claiming that this is so simple and obvious to use in such a wide range of
> applications.
>> and has been used in quite a
>> variety of context already, from music data to activities data. Also,
>> it is really simple, so really easy to grasp and extend.
> RIght now it is impossible to grasp, and I would have no confidence that any
> two extensions would be consistent.
> Pat
>> If you want
>> example of last.fm events described using this ontology, take a look
>> at the recommended events in the http://dbtune.org/last-fm/ wrapper.
>> Cheers,
>> y
>>> thanks in advance
> ------------------------------------------------------------
> IHMC                                     (850)434 8903 or (650)494 3973
> 40 South Alcaniz St.           (850)202 4416   office
> Pensacola                            (850)202 4440   fax
> FL 32502                              (850)291 0667   mobile
> phayesAT-SIGNihmc.us       http://www.ihmc.us/users/phayes
Received on Wednesday, 29 July 2009 16:54:41 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:29:44 UTC