work in progress...

ESS:Categories

From ESS
Revision as of 19:50, 25 February 2012 by Admin ess (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

"Categories" definition

One of the principal element that caracterised an event is the category that define the event theme. The category is the most sensitive aspect of ESS standard protocol because the purpose of this section is to universalise all main stream events into generalist categories.
It is also one of the main reason why there is no other protocol that have for central objective to standardise Events. ESS Events Categories is the essential aspect that create a virtual connection between all events that use ESS as standard. ESS categories is a two dimention array that start from a generic main stream event theme definition and digg to a more specific definition (but not too precise). Each category have a specific identifier (categoryID) which make much more easier to use the event on a large scale.


For example:
A Basketball match can de defined by: Sport (C) > Team Sport (C2) > Basketball (C2BA) The ESS category ID for such an event is C2BA (worlwide and forever).
A cinema can define a movie by: Art > Film > Action Movie The ESS category ID for such an event is A25B (worlwide and forever).
At the same time a portal that federate ESS event feeds can easily display the kind of events that interest its readers (A25B). There is no longer human interaction to reach the information: the source create the feed, the subscriber syndicate to the feed and with the category ID there are both talking about the same subject.
The key of ESS success is the large community of people that help ESS open project to agregate more categories to each new standard version.


ESS categories structure

XML element MUST be defined in an ESS Feed Document, it is a mandatory ESS XML element.
must contain, at least, one element. elements must be only composed by three XML element types : "name", "id" and "description", elements MUST have at least a "name" element as imediat child. If it is present, the value of element identify a hierarchic identifier location in the ESS taxonomy. Processors may establish conventions for the interpretation of category ID, even if user is free to define its own category by entering a "name" and a "description". But it is adviced to use ESS categories taxonomy for a wide scale brodcasting and usage of the event feed.


Category's item elements

Each XML element must have as imediate child, at least, one XML element. The element must be the only type of XML element children of element. elements can be repeated an infinit number of time.
If several elements are defined, the prevalence can be defined by a "priority" attribute. If no "priority" attributes are defined ESS Processors may apply the writing cascading order (top to bottom).

XML name XML position Element description Content-Type Mandatory (boolean)
ess:feed:categories:item:id Hierarchic identifier location in the ESS indicated taxonomy. String False
ess:feed:categories:item:name Language-Sensitive trivial category short name. Should not be longer then 64 characters String True
ess:feed:categories:item:description Language-Sensitive category description that SHOULD NOT be longer then 512 chars. String False


ESS categories sample

>
   ...
   >
       priority="1">
         >C2AH>
         >Football> 
      >
       priority="2">
         >Specific Football Sport> 
         >
            
               Here is the category specific description that match the best the event subject.
            ]]>
         >
      >
   >
   ...
>

Search a category



External documentation

Ietf logo.png
  1. [RFC 3076] : Canonical XML Version 1.0

KML




Discussion


Leave your comment

Personal tools
Variants
Actions
Standard

 

Developers

 

Help us