work in progress...

History

From ESS
Revision as of 15:15, 25 February 2012 by Admin ess (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Format ESS
Ess-feed-icon.png
.ess, .xml
application/ess+xml
version 0.9

Contents

Origine

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.

Evolution

During the time events have been widly used in the IT world though diferent environement, but as events are at the border-line of other big "concept" the commun misunderstanding came from completly including the "event" concept into other standards.

Events placed on a calendar

An event is not only about calendar. The most commun misunderstanding is to combine events with calendar elements, an Event is at the same time more simple and more complex. An event share with calendar the aspect that a date is required but an event is not only a date and a calendar around the date is also more complex (the date can be share with people, share with other events, the date have several status: busy free, participant of the event interact with the calendar, and so on...).


Calendar have its world and its standards, Events need its world and its standards, they share some aspects that are necessary: simply to place an event in a calendar, but it is not the same conceptual object. By definition a calendar element is a fix point in time, and an Event have to be a changing feed that grow with several other types of information during time :

  1. people interaction: social rate, validate the source
  2. events interactions,
  3. geographical interactions
  4. media files that describe the event.




- Boardcasting an event have to be described as a feed (with images, videos),

so many events are described as a blog post with a name and a description and a date but it is almost impossible to use this data for an "industrial IT usage" - RSS feeds - Atome feeds Only a part of what compose an event have to see with a calendar, reducing an event to a calendar element


Events placed on a map

An event is not only about a Map. - An event can be placed on in a calendar, so calendar standard have implemented a structurised event in their protocol

  • iCal
  • vCalendar


Events interacts with people

An event is not only about what people say about the event. - An event can implies a place, so some standard dedicated to places mix what is specific to a place to what is in fact an event

  • Google Places, where restaurant can be a place with a standard to describe the place, but also a every day event that is generated by the intention of going to the restaurant.
  • Google Map with Google Places...

- An event implies people, so some standard includes it their protocol elements that describe events

  • vCard
  • xCard





ESS open to the futur

ESS Processors

Events broadcasting

Events search-engine

Events unknown new utilisation...



Discussions


Leave your comment

Comments

admin_ess bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla

Personal tools
Namespaces
Variants
Actions
Standard

 

Developers

 

Help us