ESS (for Event Standard Syndication) is a family of web feed formats used to publish frequently updated or constent events such as cinema, exposition, festival, manifestation in art or music in a standardized format. An ESS document (which is called a "feed", "web feed" or "channel") includes full or summarized text, plus metadata such as publishing dates, description, price and authorship.
ESS feeds benefit publishers by letting them syndicate content automatically. A standardized XML file format allows the information to be published once and viewed by many different programs. They benefit readers who want to subscribe to timely updates from favorite websites or to aggregate feeds from many sites into one place.
The aim of the feed is to be used by other program such as feed-reader, calendar, interactive map or included in other websites.
As its historical father the RSS, ESS files are essentially XML formatted plain text, the ESS file itself is relatively easily read both by automated processes and by humans alike. An example file could have contents such as the following. This could be placed on any appropriate communication protocol for file retrieval, such as http or ftp, and reading software would use the information to present a neat display to the end user.
Le format RSS est un format XML, d'où la première ligne de l'exemple ci-dessous.
My Event Ceci est un exemple de flux RSS 2.0 8,800,808,809,8056,8566,10255 Sat, 07 Sep 2002 00:00:01 GMT Sat, 07 Sep 2002 00:00:01 GMT 40.71675 -74.00674http://www.my-event-exemple.org http://www.my-event-exemple.org/img/my-event_256x256.png
Actualité N°1 Ceci est ma première actualité Sat, 07 Sep 2002 00:00:01 GMThttp://www.example.org/actu1 http://www.my-event-exemple.org/img/my-event_128x128.png
Reading a paper from last year’s Knowledge Capture (K-CAP 2009) academic conference, I came across some references to various “event standards”. All of these were very domain specific, but 2 seemed they might have more generic uses.
One was Events-ML G2 from the International Press Telecommunications Council for registering “events as in conferences, meetings etc” (rather than the sorts of events the CEP world is mainly interested in). The event schema therefore includes properties such as phone and contact details, implicitly recording the observer’s data on the event (as opposed to some observer identifier from which that and other data could be gleaned, presumably). On the other hand they did have a nice test form!).
Event in Event Ontology There was also an “Event Ontology” defined as part of a Music Ontology (!) project. Things started well when the authors stated:
This ontology is centered around the notion of event, seen here as the way by which cognitive agents classify arbitrary time/space regions, which is essentially the view expressed by Allen and Fergusson [or its HTML version via Google].
The next quote was less impressive though, seemingly going beyond abstraction and on into the realm of philosophy…
[..] 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.
Reviewing their definition of event we see relationships between event and:
place and time factors and products agents (acting on the events) Presumably from the musician’s point of view, a set of notes (as events) may combine into a musical chord (an event product) - or in other words, agents combine events and context (”factors”) to define complex events (”products”). So not a million miles away from the EPTS’ labors on the EPTS Glossary, newly refreshed in a draft version 2…
Mon site Ceci est un exemple de flux RSS 2.0 Sat, 07 Sep 2002 00:00:01 GMThttp://www.example.org
Actualité N°1 Ceci est ma première actualité Sat, 07 Sep 2002 00:00:01 GMThttp://www.example.org/actu1 Deleted