-------------------------------
Storefront Extensions to HTML (SETH) v0.5
-------------------------------

<serviceInfo>

A SETH user agent must accept and properly handle the serviceInfo element in an HTML header as follows:

Example:
<serviceInfo name="service_name" version="1.0"/>

The name attribute can be any case-sensitive alphanumeric string (names can include "-" and "_") up to 255 characters.

The version attribute can be any alphanumeric string (can also include "." and "-") up to 255 characters corresponding to the version of the service currently in operation. Any serviceInfo elements which do not contain a name or version value must be ignored.

<breadcrumbs>

A SETH user agent must accept and properly handle the breadcrumbs element in an HTML header as follows:

Example:
<breadcrumbs>
  <link name="Channels" url="http://hostname/channels"/>
  <link name="Channel A" url="http://hostname/channels/a"/>
  <link name="Show 1" url="http://hostname/tvshows/1"/>
</breadcrumbs>

The breadcrumbs element may contain multiple link elements. Each link element contains a name and url attribute. These attributes represent the display name and url of a node along the navigation path to the current navigation position within the storefront. The order of the link elements is significant, and should be interpreted by the user agent as beginning with the farthest node and each successive link represent a node progressively nearer to current navigation position.

Name and url attributes can be any case-sensitive alphanumeric string (names can include ".`,~!@#$%^&*()_+-={}[]|\?/:" and " ") up to 255 characters. Urls may be either relative or fully qualified. Any link elements which do not contain any name or url values must be ignored.

<searchBase>

A SETH user agent must accept and properly handle the searchBase element in an HTML header as follows:

Example:
<searchBase scope="tvshows"/>

The scope attribute can be any alphanumeric string (can also include "." and "-") up to 255 characters corresponding to the search scope which is applicable to the current navigation position. The string may include "," chars, however in this case a user agent must interpret the string as a comma separated list of scope values. A SETH user agent must be capable of handling at a minimum first scope identifier within a comma separated list. Any searchBase elements which contain no scope value must be ignored.