ETSI TS 102 818 V3.2.1 (2019-06)

TECHNICAL SPECIFICATION
Hybrid Digital Radio (DAB, DRM, RadioDNS);
XML Specification for Service and
Programme Information (SPI)
2 ETSI TS 102 818 V3.2.1 (2019-06)

Reference
RTS/JTC-DAB-93
Keywords
audio, broadcasting, DAB, digital, DNS, DRM,
EPG, hybrid, radio
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2019.
© European Broadcasting Union 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 818 V3.2.1 (2019-06)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 10
3.3 Abbreviations . 10
4 Introduction . 11
5 Common data types, groups and elements . 13
5.1 Basics . 13
5.1.1 Character encoding . 13
5.1.2 Text . 13
5.2 Schema types . 13
5.2.1 CRID type . 13
5.2.2 shortCRID type . 14
5.2.3 MIME type. 14
5.2.4 timepoint type . 14
5.2.5 duration type . 15
5.2.6 bearerURI type . 15
5.3 genre element . 15
5.4 keywords element . 16
5.5 link element . 16
5.6 nameGroup elements . 17
5.7 descriptionGroup elements . 18
5.8 multimedia element . 18
5.9 mediaDescription element . 19
5.10 memberOf element . 19
5.11 bearer element . 19
5.11.1 General . 19
5.11.2 Digital Audio Broadcasting (DAB/DAB+). 20
5.11.3 Digital Radio Mondiale (DRM) . 20
5.11.4 IP-based . 20
5.12 geolocation element . 20
5.13 epg element . 22
6 Service Information . 22
6.1 Introduction . 22
6.2 serviceInformation element . 24
6.3 services element . 25
6.4 serviceProvider element . 25
6.5 service element . 25
6.6 radiodns element . 26
6.7 serviceGroupMember element . 27
6.8 serviceGroups element . 27
6.9 serviceGroup element . 27
7 Programme Information . 28
7.1 Introduction . 28
7.2 epg element . 29
7.3 schedule element . 29
ETSI
4 ETSI TS 102 818 V3.2.1 (2019-06)
7.4 scope element . 29
7.5 serviceScope element . 29
7.6 programme . 30
7.7 programmeEvent . 30
7.8 location element . 31
7.9 time element . 32
7.10 relativeTime element . 33
7.11 onDemand element . 33
7.12 presentationTime element . 34
7.13 acquisitionTime element . 34
8 Group Information . 35
8.1 Introduction . 35
8.2 epg element . 35
8.3 programmeGroups element . 36
8.4 programmeGroup element . 36
9 Delivery of SPI over DAB/DRM . 37
9.1 General . 37
9.2 Document conventions . 37
9.2.1 General . 37
9.2.2 Service Information documents . 37
9.2.2.1 General . 37
9.2.2.2 DAB . 38
9.2.2.3 DRM . 38
9.2.3 Programme Information (Schedule) documents . 38
9.2.4 Group Information documents . 38
9.3 Delivery of multimedia assets . 38
9.4 Filecasting . 39
10 Delivery of SPI over IP . 39
10.1 Introduction . 39
10.2 SI document discovery . 40
10.2.1 General . 40
10.2.2 Lookup using the Authoritative FQDN . 40
10.2.2.1 Introduction . 40
10.2.2.2 Services not supporting client identification . 41
10.2.2.3 Services supporting client identification . 41
10.2.3 Link contained within the HTML content of the service website . 41
10.2.4 Placed in a defined location on the service website . 42
10.3 PI document discovery . 42
10.4 GI document discovery . 43
10.5 Guidance for document retrieval . 43
10.5.1 General . 43
10.5.2 Compression . 44
10.5.3 Language . 44
10.5.4 Document Size . 44
10.5.5 Client Identification . 44
Annex A (normative): URI schemes . 46
A.1 URI scheme for postal addresses . 46
A.2 URI scheme examples . 46
Annex B (normative): spi_31.xsd . 47
Annex C (informative): Guidance for usage of linked content . 57
C.1 General . 57
C.2 Website links examples . 57
C.2.1 Programme links example . 57
C.2.2 Service links example . 58
ETSI
5 ETSI TS 102 818 V3.2.1 (2019-06)
C.3 Podcasts/on-demand content . 58
C.4 External identities . 58
C.5 Contact details . 59
Annex D (informative): Logo usage . 60
D.1 Introduction . 60
D.2 Basic implementation . 60
D.3 Extended implementation . 62
D.3.1 General . 62
D.3.2 Content negotiation . 63
D.3.3 Caching . 63
D.4 Logo scaling . 63
Annex E (informative): Broadcast/IP service follow ing. 65
E.1 General . 65
E.2 Initial bearer selection . 65
E.3 Bearer switching behaviour . 65
E.4 Implementation . 66
E.5 Bearer matching . 66
Annex F (informative): Compatibility with ETSI TS 102 818 (V1.5.1) . 67
Annex G (informative): Converting DAB and DRM PTy to TV-Anytime genres . 69
Annex H (informative): Extension of core SPI schema by use of namespacing . 70
History . 72

ETSI
6 ETSI TS 102 818 V3.2.1 (2019-06)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by Joint Technical Committee (JTC) Broadcast of the European
Broadcasting Union (EBU), Comité Européen de Normalisation ELECtrotechnique (CENELEC) and the European
Telecommunications Standards Institute (ETSI).
NOTE 1: The EBU/ETSI JTC Broadcast was established in 1990 to co-ordinate the drafting of standards in the
specific field of broadcasting and related fields. Since 1995 the JTC Broadcast became a tripartite body
by including in the Memorandum of Understanding also CENELEC, which is responsible for the
standardization of radio and television receivers. The EBU is a professional association of broadcasting
organizations whose work includes the co-ordination of its members' activities in the technical, legal,
programme-making and programme-exchange domains. The EBU has active members in about
60 countries in the European broadcasting area; its headquarters is in Geneva.
European Broadcasting Union
CH-1218 GRAND SACONNEX (Geneva)
Switzerland
Tel: +41 22 717 21 11
Fax: +41 22 717 24 81
The Eureka Project 147 was established in 1987, with funding from the European Commission, to develop a system for
the broadcasting of audio and data to fixed, portable or mobile receivers. Their work resulted in the publication of
European Standard, ETSI EN 300 401 [13], for DAB (see note 2) which now has worldwide acceptance.
NOTE 2: DAB is a registered trademark owned by one of the Eureka Project 147 partners.
The DAB family of standards is supported by World DAB, an organization with members drawn from broadcasting
organizations and telecommunication providers together with companies from the professional and consumer
electronics industry.
The RadioDNS Project was established in 2010 to standardize the combination of broadcast radio systems with
additional applications, content and meta-data delivered over fixed or mobile IP networks. The project produced a
specification using DNS to locate the broadcaster's Internet domain which is in use worldwide, and now standardized as
ETSI TS 103 270 [18]. RadioDNS operates the authoritative name servers for the radiodns.org domain, and has
members drawn from broadcasting organizations, manufacturers and service providers.
NOTE 3: "RadioDNS Hybrid Radio" and the RadioDNS Hybrid Radio logo are registered trademarks of
RadioDNS Limited, a not-for-profit company owned by its members.
ETSI
7 ETSI TS 102 818 V3.2.1 (2019-06)
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
8 ETSI TS 102 818 V3.2.1 (2019-06)
1 Scope
The present document defines the XML schema data model for Service and Programme Information (SPI) and methods
for delivery by broadcast digital radio - DAB and DRM - and IP.
In respect to the previous version of the present document, provision is added for client authorisation for IP delivered
metadata. The use of the present document allows content to be created once by the service provider for delivery by
both mechanisms and allows manufacturers to implement devices with many common elements.
It is envisaged that this data format could be used both for transmitting service and schedule data to SPI applications on
devices and as the basis for exchanging information between service providers, network operators and content
providers.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 102 822-4: "Broadcast and On-line Services: Search, select, and rightful use of content
on personal storage systems ("TV-Anytime"); Part 4: Phase 1 - Content referencing".
[2] ISO 8601: "Data elements and interchange formats - Information interchange - Representation of
dates and times".
[3] IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1".
[4] W3C Recommendation 4 February 2004: "Extensible Markup Language (XML) 1.0 (Third
Edition)".
[5] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies".
[6] IETF RFC 3066: "Tags for the Identification of Languages".
[7] Void.
[8] IETF RFC 3966: "The tel URI for Telephone Numbers".
[9] IETF RFC 3191: "Minimal GSTN address format in Internet Mail".
[10] IETF RFC 6068: "The 'mailto' URI scheme".
[11] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
[12] IETF RFC 4289: "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration
Procedures".
[13] ETSI EN 300 401: "Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile,
portable and fixed receivers".
[14] ISO/IEC 10646: "Information technology - Universal Multiple-Octet Coded Character Set (UCS)".
ETSI
9 ETSI TS 102 818 V3.2.1 (2019-06)
[15] Void.
[16] ETSI TS 102 822-3-1: "Broadcast and On-line Services: Search, select, and rightful use of content
on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 1: Phase 1 - Metadata
schemas".
[17] ETSI ES 201 980: "Digital Radio Mondiale (DRM); System specification".
[18] ETSI TS 103 270: "Radio DNS Hybrid Radio; Hybrid lookup for radio services".
[19] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1:
Country codes".
[20] "GeoRSS: Geographically Encoded objects for RSS feeds".
NOTE: Available at http://www.georss.org.
[21] ETSI TS 102 371 (V3.1.1 and later): "Digital Audio Broadcasting (DAB); Digital Radio Mondiale
(DRM); Transportation and Binary Encoding Specification for Service and Programme
Information (SPI)".
NOTE: This reference is made to V3.1.1 and possible later versions.
[22] IETF RFC 2782 (2000): "A DNS RR for specifying the location of services (DNS SRV)".
[23] IETF RFC 5724: "URI Scheme for Global System for Mobile Communications (GSM) Short
Message Service (SMS)".
[24] ETSI TS 103 177: "Digital Audio Broadcasting (DAB); Filecasting; User application
specification".
[25] ETSI TS 101 756: "Digital Audio Broadcasting (DAB); Registered tables".
[26] IETF RFC 4078: "The TV-Anytime Content Reference Identifier (CRID)".
[27] ISO/IEC 11172-3: "Information technology -- Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s -- Part 3: Audio".
[28] ISO/IEC 13818-3: "Information technology -- Generic coding of moving pictures and associated
audio information -- Part 3: Audio".
[29] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TS 102 818 (V1.5.1): "Digital Audio Broadcasting (DAB); Digital Radio Mondiale (DRM);
XML Specification for Electronic Programme Guide (EPG)".
[i.2] ETSI TS 102 371 (V1.3.1): "Digital Audio Broadcasting (DAB); Digital Radio Mondiale (DRM);
Transportation and Binary Encoding Specification for Electronic Programme Guide (EPG)".
ETSI
10 ETSI TS 102 818 V3.2.1 (2019-06)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
bearer: method of carriage of the radio service
service: linear radio service
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AAC Advanced Audio Coding
AF Alternate Frequency
AM Amplitude Modulation
AMSS Amplitude Modulation Signalling System
CA Conditional Access
CDATA Character DATA
CRID Content Reference ID
CS Classification Schemes
DAB Digital Audio Broadcasting
DNS Domain Name Server
DRM Digital Radio Mondiale
EBU European Broadcasting Union
EPG Electronic Programme Guide
FM Frequency Modulation
FQDN Fully Qualified Domain Name
FTP File Transfer Protocol
GI Group Information
HE High Efficiency
HTTP Hyper Text Transfer Protocol
IANA Internet Assigned Numbers Authority
IP Internet Protocol
ISO International Organization for Standardization
JTC Joint Technical Committee
MIME Multipurpose Internet Mail Extensions
MOT Multimedia Object Transfer
MPEG Moving Picture Experts Group
PAD Programme Associated Data
PI Programme Information
PNG Portable Network Graphics
PPI Pixels Per Inch
RDS Radio Data System
RFC Request For Comments
RSS Rich Site Summary
SI Service Information
SMS Short Messaging Service
SPI Service and Programme Information
SRV SeRVice (record)
TCP Transmission Control Protocol
TCP/IP Transmission Control Protocol/Internet Protocol (but this is a conjunction of TCP and IP)
TV TeleVision
ETSI
11 ETSI TS 102 818 V3.2.1 (2019-06)
UI User Interface
URI Uniform Resource Identifier
URL Uniform Resource Location
UTC Co-ordinated Universal Time
UTF Unicode Transform Format
XML eXtensible Markup Language
XSD eXtensible markup language Schema Definition language
XSLT eXtensible Stylesheet Language Transformation
4 Introduction
It is intended that service providers will use the present document to provide service information and programme
listings information for audio services, whether delivered by analogue or digital broadcast systems or via IP, and that
device manufacturers will use this metadata to provide a mechanism for the user to select services, programmes and
related content for live or on-demand listening.
The present document allows rich metadata to be added to service descriptions, permitting attractive visualizations for
user interfaces. Programme listings may be forward and backward in time, and on-demand content, whether part of the
linear schedule or stand-alone content, may be described; again with rich metadata.
A key requirement is that the metadata is suited to a range of devices with differing display capabilities, resources and
back-channel capabilities. To achieve this, a flexible structure has been defined, as shown in figure 1.
The SPI data is broken down into Service Information (services) and Programme Information (schedules, programmes,
and programme events). Additionally programmes and programme events can be linked together into groups (e.g. for
grouping programmes together into serials or series), which may have additional Group Information.
The SPI data is designed to be extensible, allowing it to be used as a core set of metadata that may be augmented with
additional information within specific namespaces for third party applications, as further explained in Annex H.
ETSI
12 ETSI TS 102 818 V3.2.1 (2019-06)
Service information
Information about one or more services
SERVICE
BEARER
Information about the bearers of a service
Programme information
SCHEDULE Information about a schedule for one or more services
Information about a programme and a link to its service
PROGRAMME
Information about an event
EVENT
Group information
Information about a group
GROUP
Information about a group and links to parent groups
GROUP
...
A programme links to its parent groups
PROGRAMME
Figure 1: Structure of SPI metadata
The present document is split into three parts:
• Service Information (SI);
• Programme Information (PI);
• Group Information (GI).
The present document defines common data types in clause 5, service information in clause 6, programme information
in clause 7 and group information in clause 8.
ETSI
13 ETSI TS 102 818 V3.2.1 (2019-06)
The SPI and any supporting files may be delivered by two methods:
• DAB/DRM broadcasting systems (see clause 9).
• TCP/IP (see clause 10).
There are several use cases for service providers using the present document:
1) The service provider has analogue broadcasting platforms only (e.g. FM with RDS, AM with AMSS) or has no
broadcast platforms (internet only).
2) The service provider has digital broadcasting platforms only (e.g. DAB and/or DRM).
3) The service provider has both analogue and digital broadcasting platforms.
In case 1, all the XML documents are accessed via TCP/IP.
In case 2, the service provider may provide all the XML documents over the broadcast platform only; or he may provide
all the documents in parallel via the broadcast platform and TCP/IP to additionally support connected devices; or he
may provide the Service Information (SI) document over the broadcast platform and the remaining documents via
TCP/IP; or some other combination.
In case 3, the service provider may provide all the XML documents over the broadcast platform to support his digital
platforms independently of a TCP/IP connection, and in parallel via TCP/IP to support his analogue platforms and all
connected devices; or some other combination.
In order to support these three cases, a common set of XML documents are generated.
5 Common data types, groups and elements
5.1 Basics
5.1.1 Character encoding
The ISO/IEC 10646 [14] character set using UTF-8 character encoding shall be used in all XML documents defined in
the present document.
NOTE: The ISO/IEC 10646 [14] character set contains all characters of the "Complete EBU Latin based
repertoire".
5.1.2 Text
Any text sections in attributes or elements should be careful to avoid using any of the reserved XML characters:
& < > " '
These characters should be encoded using the predefined entity references (& < > " ') or
enclosed in a CDATA section (e.g. ).
5.2 Schema types
5.2.1 CRID type
A unique identifier for a programme, programmeEvent, programmeGroup or memberOf in the format of a Content
Reference ID (CRID) as defined in the TV-Anytime specification [1].
This shall be in the following form:
crid:///
ETSI
14 ETSI TS 102 818 V3.2.1 (2019-06)
Where authority is a registered Internet domain name that the CRID author has permission to use and is case
insensitive. The data is a free format string (URI compliant and case insensitive) that is meaningful to the given
authority and should uniquely identify the content within that authority [26].
EXAMPLE 1: crid://www.example.com/4472/1148985
EXAMPLE 2: crid://www.example.co.uk/breakfast
5.2.2 shortCRID type
A complementary identifier to the CRID type, used with the same elements.
The shortCRID is a 24-bit integer, expressed as a decimal value within the element content, with a range of 0 to
16 777 215 inclusive. The following rules shall be applied whenever shortCRIDs are used:
• The shortCRID shall only be unique within a single SPI service (see note), therefore a device shall process it in
some way on decoding to ensure that it is globally unique.
• The shortCRID shall not be re-used within that SPI service for a minimum of six months.
NOTE: An "SPI service" is defined as SPI data for one or more services, provided from a single source. This
could be SPI data from a particular FQDN, or from a broadcast MOT carousel.
5.2.3 MIME type
This indicates the MIME [5] of contained data or links and shall be used where it is applicable. The registered list of
MIME types is available from the IANA list of Mime Types (IETF RFC 2046 [11] and IETF RFC 4289 [12]).
However, an application is permitted to use values not in this list as long as they conform to the requirements set out in
IETF RFC 2046 [11].
EXAMPLE 1: audio/mpeg
EXAMPLE 2: text/html
EXAMPLE 3: image/png
EXAMPLE 4: application/x-myapplication
EXAMPLE 5: application/xml+pi
5.2.4 timepoint type
This is a time field in local time. It is based on the ISO 8601 [2] extended format: YYYY-MM-DDThh:mm:ss where
"YYYY" is the year, "MM" the month and "DD" the date. The letter "T" is the date/time separator and "hh", "mm" and
"ss" represent the hour, minute and second respectively. To indicate the time zone, i.e. the difference between the local
time and UTC, the difference immediately follows the time and consists of a sign, + or - , followed by hh:mm. If the
difference between local time and UTC is 0, then a"Z" may be used in place of "+00:00".
EXAMPLE 1: 2013-06-07T15:05:00+01:00
EXAMPLE 2: 2014-02-03T23:03:15Z
ETSI
15 ETSI TS 102 818 V3.2.1 (2019-06)
5.2.5 duration type
Duration is based on the ISO 8601 [2] format: PTnHnMnS, where "T" represents the date/time separator, "nH" the
number of hours, "nM" the number of minutes and "nS" the number of seconds. The values of the hours, minutes and
seconds components are not restricted but allow an arbitrary integer. Reduced precision and truncated representations of
this format are allowed provided they conform to the following:
• The lowest order items may be omitted. If omitted their value is assumed to be zero.
• If the number of hours, minutes or seconds in any expression equals zero, the number and its corresponding
designator may be omitted. However, at least one number and its designator shall be present.
The designator "PT" shall always be present.
Durations of greater than 18 hours should be avoided for reasons of backwards compatibility with broadcast binary
encoding.
EXAMPLE 1: PT2H
EXAMPLE 2: PT1H12M
EXAMPLE 3: PT12M30S
5.2.6 bearerURI type
This is a string describing the identifier of a bearer element according to the format described in ETSI TS 103 270 [18].
5.3 genre element
This indicates the genre of a programme, programmeEvent, programmeGroup or service. The genre scheme is
based on that used by TV-Anytime [16].The supported classification schemes are:
• IntentionCS.
• FormatCS.
• ContentCS.
• OriginationCS.
• IntendedAudienceCS.
• ContentAlertCS.
• MediaTypeCS.
• AtmosphereCS.
The text content of the element, if used, should contain the name of the genre. This is purely intended to make the
element more human-readable.
ETSI
16 ETSI TS 102 818 V3.2.1 (2019-06)
The type attribute indicates the type of the genre. The types of genres are defined as follows:
Its attributes are detailed below:
Attribute Description Type Status
href Indicates the genre, the Classification Scheme xs:anyURI Required
(CS) and the genre scheme used.
type Indicates the type of the genre, from the list below: xs:enumeration Optional,
main. The specified genre is the main, or primary. defaults to
secondary. The specified genre is secondary main
genre, such as a subgenre.
other. The specified genre is an alternative genre,
such as one defined or used by third parties.

EXAMPLE:
...