W3C home > Mailing lists > Public > semantic-web@w3.org > September 2009

Re: Vocabularies for file data, content events, errors

From: AzamatAbdoullaev <abdoul@cytanet.com.cy>
Date: Wed, 2 Sep 2009 14:17:41 +0300
Message-ID: <FED5BD5AE6E54C21B66CA59F52E475CB@personalpc>
To: <semantic-web@w3.org>
Cc: "[ontolog-forum] " <ontolog-forum@ontolog.cim3.net>
"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

-- 
Toby A Inkster
<mailto:mail@tobyinkster.co.uk>
<http://tobyinkster.co.uk>
Received on Wednesday, 2 September 2009 11:18:37 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 21:45:31 GMT