An event is comprised of different concepts, one of the most important is to describe the people involved in the event. The number of people involved in the organization of an event depends upon the size and scale of the event. While organizing a small party may require only one or two people, organizing a very large event like the Olympics may require several thousand people.
Events have three main people components, which are represented in ESS by three "type" attributes within
People who work behind the scenes of the event.
People who work onstage or perform durring the event.
People who visit the event, event audience.
Defines the social medias used to promote, rate and share the event.
Defines the specific event feed writing issuer.
Defines the event contributor: assistant, special thanks...
ESS documents are composed by various main XML elements. ESS processors must consider each and every element's descriprion as valid and applicable to each and every other XML element within the same ESS document feed
(ess:feed). If it is not the case, it belong to an other XML
Organizer section can be in relation with
|type||The "type" attribute can take five values: "organizer", "performer", "attendee", "social", "author" or "contributor" to represent each people involved in the event as actors of the event, the promotion or as an attendee. ESS Processors should consider that "organizer" is the default attribute if it is not specified.||String||TRUE|
The "priority" attribute refer to the order and the preference to applied to each
- childs element
|Language-sensitive names should not be longer then 128 chars||String||TRUE|
|Unique and universal person identifier in a specific taxonomy, ESS processors should use the same value across all ESS document.||IRI RFC3987||FALSE|
|Define current person first name. Should not be longer then 128 characters.||String||FALSE|
|Define current person last name. Should not be longer then 128 characters.||String||FALSE|
|Define the organization name. If an organization name is defined, ESS processors should consider that current element is a structured organization (association, group, company). Should not be longer then 256 chars.||String||FALSE|
|Define a URL that points to a large image representation of current individual or company. Image should be web readable (jpg, gif, png, ...) and should not be smaller then 64px (width and height). ESS processors may used this value to represent current individual or company.||URI RFC2396||FALSE|
|Define a URL that point to a small icon representation of current individual or company. Image should be web readable (jpg, gif, png, ico, ...) and should not be larger then 64px (width and height). ESS processors may used this value in search engine icon results or detail representation.||URI RFC2396||FALSE|
|Defines a URL that point to a complete individual or organisation description||URI RFC2396||FALSE|
|Defines the complete address: street name, street number, building number. Should not be longer then 512 chars.||String||FALSE|
|Defines city location name. Should not be longer then 128 chars||String||FALSE|
|Defines postal code. Common international structure is a five number sequence.||String||FALSE|
|Defines event's region, state or department name. Should not be longer then 128 chars.||String||FALSE|
|Defines event's region, state or department code name (should be 2 chars).||String||FALSE|
|Defines event's country name. (e.g. : United States of Americas)||String||FALSE|
|Defines event's country code in the international format (should be 2 chars).||String ISO3166||FALSE|
|Defines current person email.||Email RFC822||FALSE|
|Defines current person phone.||String||FALSE|
|Only available for item type="attendee". Defines the minimum amount of attendees for this event. If it is not present, ESS processors should consider that 0 is the default value.||Number||FALSE|
|Only available for item type="attendee". Defines the maximum amount of attendees for this event. If it is not present, ESS processors should consider that UNLIMITED is the default value.||Number||FALSE|
|Only available for item type="attendee". Defines the age minimum of attendees for this event. If it is not present, ESS processors should consider that 0 is the default value.||Number||FALSE|
|Only available for item type="attendee". Defines the list of rules that the attendee should be aware of before attending the event.||Number||FALSE|
|This optional XML element contains the specific person description (artist biography, organizer summary...). Using HTML tags inside this XML element is possible but should be reduced to the minimum because ESS processors could use this information in an environment that can not read HTML.||String||FALSE|
ESS people sample
DTD description [http://essfeed.org/history/0.9 ]
xmlns="http://essfeed.org/history/0.9" version="0.9" lang="en">... >
>[email protected]> >Event organizer name> >John> >Doe> >Sample Ltd.> >123, 5th ave / 49st E - #504> >New York> >10012> >New York> >NY> >United States of Americas> >US> >http://sample.org/img/organizer/logo.jpg> >http://sample.org/img/organizer/icon.jpg> >http://sample.org/img/organizer/index.html> >[email protected]> >1 (646) 290 8899> >
>[email protected]> >Event performer name> >Janine> >Madonna> >Madonna llc.> >http://madonna.com/logo.jpg> >http://madonna.com/icon.jpg> >http://madonna.com/index.html> >
>Event attendees description> >0> >500> >0> >Smoking is not allowed in the stadium> >
>Social rating API to rate or share the event> >http://mySocialNetwork.org/api/get-and-set-rating/> >
>ESS Feed Powered by MyEventPromotionTool.com> >http://example.org/index.html> >http://example.com/images/icon.png> >[email protected]> >1 (646) 255 9999> >
>Janette Doe> > > ... >
ESS standard under RFC validation process: RFC ESS Draft
- RFC 2396 : Uniform Resource Identifiers (URI): Generic Syntax
- RFC 3023 : XML Media Types
- RFC 3987 : Internationalized Resource Identifiers (IRIs)
- ISO 3166 : ISO 3166