The principal XML element that characterizes an ESS event is the category under which that event is labeled.
The category defines the theme of an event and the purpose of this section is to universalize all main stream events into general categories.
ESS event categories are essential- they create a virtual connection between all events that use ESS as a standard.
ESS categories start from generic main-stream theme definition and uncover more specific definitions. Each category has a specific unique identifier, this ID simplify ESS Processors feeds analysis to cross similarities with other events.
ESS <categories> structure
<categories> XML element must be defined in an ESS Feed Document, it is a mandatory ESS XML element.
<categories> must contain, at least, one <item> element. <item> element must only be comprised of two XML element types : <name> and <id>, <item> elements must have at least a <name> element of an immediate child. If it is present, the value of <id> element identifies a hierarchic identifier location in the ESS taxonomy. Processors may establish conventions for the interpretation of category ID, even if the user is free to define its own category by entering a <name>. But it is advisable to use ESS categories taxonomy for wide scale broadcasting and usage of the event feed.
Categories <item @attibutes>
|type|| The "type" attribute define the purpose of the event category, it can take the value:
|priority||The "priority" attribute refers to the order and the preference applied to each <item> XML elements. ESS processors should consider the natural position of the <item> element as the priority if this attribute is not defined.||Number||FALSE|
Categories <item> child elements
||Language-sensitive category shortens name. Should not be longer then 64 characters||String||TRUE|
||Unique hierarchical category identifier in ESS indicated taxonomy.||IRI RFC3987||FALSE|
||This optional XML element contain the category specific description. Using HTML tags inside this XML element is possible but should be limited to the minimum necessary because ESS processors could use this information in an environment that can not read HTML.||String||FALSE|
ESS categories sample
DTD description [http://essfeed.org/history/0.9 ]
A Basketball match can be defined by: Sport (C) > Team Sport (C2) > Basketball (C2BX) The ESS category ID for such an event is C2BX and as name Basketball.
A cinema listing can be defined as: Cinema (I) > Action Movie (I3) The ESS category ID for such an event is I3 and as name Cinema: action
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ess PUBLIC "-//ESS//DTD" "http://essfeed.org/history/0.9/index.dtd"> <ess xmlns="http://essfeed.org/history/0.9" version="0.9" lang="en"> ... <categories> <item type="competition"> <name>Football</name> <id>C2AH</id> </item> </categories> ... </ess>
Search a category
Complete listing of all event's categories will come soon.
Could not find wordpress article with a title like home
ESS standard under RFC validation process: RFC ESS Draft
- RFC 3076 : Canonical XML Version 1.0