Re: [ontolog-forum] Event Ontology

Ansgar wrote:
"Further information on the ontology can be found on its web page...: 
http://isweb.uni-koblenz.de/eventmodel"
What i found there: "...a formal model of events, called Event-Model-F. The 
model is based on the foundational ontology DOLCE+DnS Ultralight (DUL) and 
provides comprehensive support to represent time and space, objects and 
persons, as well as mereological, causal, and correlative relationships 
between events."
It would be hard to realize your promises with such a foundation. See a real 
place of dolce in the system of upper ontologies, White Paper (Ontology and 
Semantics Standards: a master plan for merging), http://standardontology.org
Regards
Azamat Abdoullaev


----- Original Message ----- 
From: "Ansgar Scherp" <scherp@uni-koblenz.de>
To: <abdoul@cytanet.com.cy>
Cc: <semantic-web@w3.org>; <ontolog-forum@ontolog.cim3.net>
Sent: Thursday, September 03, 2009 2:28 AM
Subject: Re: [ontolog-forum] Event Ontology


> Dear Azamat and all
>
>
> It is very interesting that on this mailinglist a similar discussion 
> started that happened some time ago on the Linked Open Data mailinglist. 
> Thus, firstly I like to refer to the relevant thread on the LOD list:
> http://lists.w3.org/Archives/Public/public-lod/2009Jul/
That's engaging to read.
>
> In fact, the concept of events is well studied in foundational sciences 
> such as philosophy. This work was the input for the development of the 
> Event-Model-F. There is some brief description about that model in the LOD 
> mailinglist archive as well:
> http://lists.w3.org/Archives/Public/public-lod/2009Jul/0383.html
>
> The Event-Model-F provides comprehensive support to represent time and 
> space, objects and persons participating in events, and mereological, 
> causal, and correlative relationships between events. In addition, the 
> Event-Model-F provides a flexible means for event composition, modeling 
> event causality and event correlation, and representing different 
> interpretations of the same event.
> It will be presented this Friday at the Knowledge Capturing conference 
> (K-CAP) in Redondo Beach, CA.
>
> Further information on the ontology can be found on its web page, 
> including the ontology itself, documentation, and a Java-based API 
> implementation: http://isweb.uni-koblenz.de/eventmodel
>
> Best
>
> Ansgar
>
>
>> John Bottoms wrote:
>> "An interesting question might be: how do we migrate from detecting 
>> simple events to more complex ones. Or, we might discuss how those events 
>> are represented in an ontology so that they are anticipated and detected 
>> correctly."
>>
>> Indeed. Being the universal and ubiquitous real world phenomena, events 
>> deserve a full scale discussion. Events as happenings, occurrences and 
>> occasions are the most familiar things, as being everywhere and every 
>> time to everything. They are key elements in the very Nature, from 
>> subatomic to cosmic scale, as well as in life, mental life, social life, 
>> in technology and industry, mass media and computing, particularly. 
>> Natural events, physical events, chemical events, biological events, 
>> mental events, social events, political events, cultural events are just 
>> some types of generic Event.
>>
>> Imo, most confusion could be avoided with its adequate defining as "a 
>> change happening at a given place/time, followed and caused by some other 
>> events (changes, acts, or actions)."
>>
>> I am inclined to think that the current downgrading of event as a real 
>> world "nonevent" comes from its poor ontological study.
>>
>> Azamat Abdoullaev
>>
>>
>>
>>
>> ----- Original Message ----- From: "John Bottoms" 
>> <john@firststarpress.com>
>> To: "[ontolog-forum]" <ontolog-forum@ontolog.cim3.net>
>> Sent: Wednesday, September 02, 2009 7:01 PM
>> Subject: Re: [ontolog-forum] Vocabularies for file data, content 
>> events,errors
>>
>>
>> Azamat,
>>
>> There are some events that are easily detected. It is not hard
>> to tell when a firecracker has exploded. It is much harder to
>> find the bottom of a recession. It's all in the classifiers
>> or filters.
>>
>> An interesting question might be: how do we migrate from detecting
>> simple events to more complex ones. Or, we might discuss how those
>> events are represented in an ontology so that they are anticipated
>> and detected correctly. I am particularly interested in the linkage
>> between predicates and the metrics for detection.
>>
>> I just finished G.Lakoff's book on category theory, it is popular
>> writing but quite an interesting read, "Women, Fire and Dangerous
>> Things".
>>
>> -John Bottoms
>>  FirstStar
>>  Concord, MA
>>  T: 978-505-9878
>>
>> AzamatAbdoullaev wrote:
>>
>>> "events are primarily linguistic or cognitive in nature. That is, the 
>>> world
>>> does not really contain events. Rather, events are the way by which 
>>> agents
>>> classify certain useful and relevant patterns of change."
>>> http://motools.sourceforge.net/event/event.html
>>> I read many event ontologies, but this one is the most idiosyncratic, 
>>> softly
>>> speaking.
>>> Wonder if it is in the Linked Data Cloud. If yes, then it hardly will 
>>> give
>>> any refreshing rainwater.
>>> The world without events is the world without any precipitation as well 
>>> :).
>>> Thanks.
>>> Azamat Abdoullaev
>>> http://standardontology.org
>>>
>>>
>>> ----- Original Message ----- From: "Toby Inkster" <tai@g5n.co.uk>
>>> To: "Niklas Lindström" <lindstream@gmail.com>
>>> Cc: "Semantic Web" <semantic-web@w3.org>
>>> Sent: Wednesday, September 02, 2009 1:14 PM
>>> Subject: Re: Vocabularies for file data, content events, errors
>>>
>>>
>>> On 2 Sep 2009, at 10:37, Niklas Lindström wrote:
>>>
>>>
>>>> * simple file data properties, describing:
>>>>  - checksum+algorithm (and/or direct properties for md5, sha1/-2 
>>>> etc.),
>>>>  - filename/slug (unless dct:identifier is suitable enough?).
>>>
>>>
>>> foaf:sha1 exists, but that might not be much use if you if you want
>>> to...
>>>
>>>
>>>> * content-related events, such as "the act of reading from a
>>>> dataset/collection (e.g. a feed)", "create", "update" and specifically
>>>> "delete" (or "deletion")
>>>
>>>
>>> ... track changes to the document's hash over time.
>>>
>>>
>>>> Currently we use AtomOwl to represent versioned entries
>>>
>>>
>>>
>>> That's probably a pretty good start.
>>>
>>> If you add in an events ontology (and I'd recommend starting with
>>> Yves Raimond's one and building on top of it) then you should be able
>>> to define a EntryChange class as a subclass of Yves' ev:Event class
>>> with accompanying previousVersion (subproperty of ev:factor) and
>>> subsequentVersion (subproperty of ev:product).
>>>
>>> Building on Yves' ontology for tracking document changes is more or
>>> less what I've done here:
>>>
>>> http://ontologi.es/status
>>>
>>
>> _________________________________________________________________
>> Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
>> Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
>> Unsubscribe: mailto:ontolog-forum-leave@ontolog.cim3.net
>> Shared Files: http://ontolog.cim3.net/file/
>> Community Wiki: http://ontolog.cim3.net/wiki/
>> To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>> To Post: mailto:ontolog-forum@ontolog.cim3.net
>>
>>
>
>

Received on Thursday, 3 September 2009 14:34:49 UTC