First, I agree with Martynas, with reservations.
> There is already schema:Event, dbpedia:Event and a whole Event ontology (actually just one of them):
This has been instructive.
It is still important to know the current rules. In LODE, event is
"Definition: "Something that happened," as might be reported in a news
article or explained by a historian.
An event consists of some temporal and spatial boundaries subjectively
imposed on the flux of reality or imagination, that we wish to treat as
an entity for the purposes of making statements about it. In particular,
we may wish to make statements that relate people, places, or things to
Note that, unlike some definitions of "event," this definition does not
specify that an event involves a change of state, nor does it attempt to
distinguish events from processes or states."
Event in DCMI is defined as: "Metadata for an event provides descriptive
information that is the basis for discovery of the purpose, location,
duration, and responsible agents associated with an event. Examples
include an exhibition, webcast, conference, workshop, open day,
performance, battle, trial, wedding, tea party, conflagration."
There is another event ontology at
http://motools.sourceforge.net/event/event.html with a definition of:
"Event - An arbitrary classification of a space/time region, by a
cognitive agent. An event may have actively participating agents,
passive factors, products, and a location in space/time." This seems to
be primarily for "human-inspired events", especially music performances.
In schema.org, event is defined as: "An event happening at a certain
time and location, such as a concert, lecture, or festival. Ticketing
information may be added via the 'offers' property. Repeated events may
be structured as separate Event objects." http://schema.org/Event
The rules for current cataloging practice are in two places. The first,
http://www.loc.gov/aba/publications/FreeSHM/H0405.pdf is general and
procedural in nature. The more substantive rules are at
What distinguishes cataloging practice is that they divide events into
those that can be authors and those that cannot, e.g. the explosion of
Krakatoa involved no people and cannot author anything. WWII, although
it involved a lot of people and a lot of organization, also cannot
author anything, but both are still events. When it comes to festivals,
exhibitions, tournaments and similar human-gettogethers, these are
actually special types of corporate bodies and it becomes more difficult
to determine whether they can author anything. The cataloging rules
above provide those guidelines and please trust me: it can get very
Therefore, from this short overview, one of the main problems is how the
different communities define an "event".
It seems that Bibframe is supposed to be for those webmasters out there
who are making all of these wonderful new tools and who are just
chomping at the big to get the data that is locked inside our
bibliographic records so that they can add our data to their tools.
Right now, there is such a range of definitions for event that I don't
know how a web master could ever create anything coherent, especially
adding how it has been used in library catalogs (which is much more
complex than the other methods). As Martynas asked, is the solution to
make a whole new ontology? Making a whole new one just means that the IT
folks will have to sort it out later.
That does not seem to be a solution.
James Weinheimer [log in to unmask]
First Thus http://blog.jweinheimer.net
First Thus Facebook Page https://www.facebook.com/FirstThus
Personal Facebook Page https://www.facebook.com/james.weinheimer.35
Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/
Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts
The Library Herald http://libnews.jweinheimer.net/
[delay +30 days]