EN 62524:2011

SLOVENSKI STANDARD
01-julij-2011
9HþSUHGVWDYQRVWQLVLVWHPLLQRSUHPD9HþSUHGVWDYQRVWQRH]DORåQLãWYRLQH
NQMLJH%UDOQLIRUPDW]DH]DORåQLãWYR,(&
Multimedia systems and equipment - Multimedia e-publishing and e-books - Reader's
format for e-publishing (IEC 62524:2009)
Multimediasysteme und -geräte – E-Publishing und E-Books für Multimedia-
Anwendungen – Reader-Format für E-Publishing (IEC 62524:2009)
Systèmes et appareils multimedia – Edition électronique multimedia et livres
électroniques – Format du lecteur pour édition électronique (CEI 62524:2009)
Ta slovenski standard je istoveten z: EN 62524:2011
ICS:
01.140.40 Založništvo Publishing
33.160.60 9HþSUHGVWDYQLPXOWLPHGLMVNL Multimedia systems and
VLVWHPLLQRSUHPD]D teleconferencing equipment
WHOHNRQIHUHQFH
35.240.30 Uporabniške rešitve IT v IT applications in information,
informatiki, dokumentiranju in documentation and
založništvu publishing
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 62524
NORME EUROPÉENNE
February 2011
EUROPÄISCHE NORM
ICS 33.160.99
English version
Multimedia systems and equipment -
Multimedia e-publishing and e-books -
Reader's format for e-publishing
(IEC 62524:2009)
Systèmes et appareils multimedia – Multimediasysteme und -geräte -
Edition électronique multimedia et livres E-Publishing und E-Books für Multimedia-
électroniques – Format du lecteur pour Anwendungen -
édition électronique Reader-Format für E-Publishing
(CEI 62524:2009) (IEC 62524:2009)

This European Standard was approved by CENELEC on 2011-01-02. CENELEC members are bound to comply
with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard
the status of a national standard without any alteration.

Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the Central Secretariat or to any CENELEC member.

This European Standard exists in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CENELEC member into its own language and notified
to the Central Secretariat has the same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus,
the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia,
Spain, Sweden, Switzerland and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Management Centre: Avenue Marnix 17, B - 1000 Brussels

© 2011 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 62524:2011 E
Foreword
The text of document 100/1376/CDV, future edition 1 of IEC 62524, prepared by technical area 10,
Multimedia e-publishing and e-books, of IEC TC 100, Audio, video and multimedia systems and
equipment, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as
EN 62524 on 2011-01-02.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN and CENELEC shall not be held responsible for identifying any or all such patent
rights.
The following dates were fixed:
– latest date by which the EN has to be implemented
at national level by publication of an identical
national standard or by endorsement (dop) 2011-10-02
– latest date by which the national standards conflicting
with the EN have to be withdrawn (dow) 2014-01-02
Annex ZA has been added by CENELEC.
__________
Endorsement notice
The text of the International Standard IEC 62524:2009 was approved by CENELEC as a European
Standard without any modification.
__________
- 3 - EN 62524:2011
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.

NOTE  When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year

IEC/TS 62229 2006 Multimedia systems and equipment - - -
Multimedia e-publishing and e-book -
Conceptual model for multimedia e-publishing

IEC 62524 ®
Edition 1.0 2009-02
INTERNATIONAL
STANDARD
Multimedia systems and equipment – Multimedia e-publishing and e-books –
Reader’s format for e-publishing

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
X
ICS 33.160.99 ISBN 978-2-88910-754-4
– 2 – 62524 © IEC:2009(E)
CONTENTS
FOREWORD.4

INTRODUCTION.6

1 Scope.7

2 Normative references .7

3 Terms and definitions .7

4 Position and requirements for reader’s format .8

4.1 Reader’s format in contents creation/distribution model.8

4.2 Requirements for reader’s format .8
4.3 File format.9
4.4 Features of the reader’s Format .9
4.4.1 General .9
4.4.2 Types of displayable elements.9
4.4.3 Layout and styling .9
4.4.4 Fonts .10
4.4.5 E-book specific features .10
5 Conformance level.10
Annex A (normative) C-XMDF reader's format .11
Bibliography.48

Figure 1 – Contents creation/distribution model .8
Figure A.1 – Relation between generic and reader's formats.11
Figure A.2 – A visual example of a text flow.22
Figure A.3 – Relationship between cell flow, cell and scene.26
Figure A.4 – Paragraph tag and an image.31
Figure A.5 – Flowing text interrupted by line break tag.33
Figure A.6 – Horizontal line tag and an image.34
Figure A.7 – Effect of horizontal tag.36
Figure A.8 – Text and image tag .38
Figure A.9 – Effect of align parameter .39
Figure A.10 – Image splitting .42

Table A.1 – File types .11
Table A.2 – Cxmdf_string type .12
Table A.3 – File types .14
Table A.4 – File naming conventions .15
Table A.5 – Media types .16
Table A.6 – The data structure of root file .16
Table A.7 – Special characters .22
Table A.8 – Data structure of text flow control file .23
Table A.9 – Data structure of block control information .25
Table A.10 – Treatment of block boundary.26
Table A.11 – Data structure of cell flow control file .27

62524 © IEC:2009(E) – 3 –
Table A.12 – Data structure of cell control information .28

Table A.13 – Parameters of a paragraph tag stored in block control information .32

Table A.14 – Parameter of a line break tag stored in the block control information.33

Table A.15 – Parameters of a font settings tag stored in the block control information .35

Table A.16 – Parameters of a ruby tag stored in the block control information .36

Table A.17 – Parameter stored in the block control information.36

Table A.18 – Parameters stored in the block control information .37

Table A.19 – Parameters of an image tag stored in the block control information .39

Table A.20 – Parameters of mask tag stored in the block control information .40
Table A.21 – Parameters of link jump tag stored in the block control information .41
Table A.22 – Parameters of a URL jump tag stored in the block control information .41
Table A.23 – Parameters of a mailer launch tag stored in the block control information .42
Table A.24 – Data structure of the MIG format .43
Table A.25 – Gif image support.44
Table A.26 – Possible tag nesting.45
Table A.27 – Conformance levels .46
Table A.28 – Tags eligible for each conformance level.46
Table A.29 – Files eligible for each conformance level.46

– 4 – 62524 © IEC:2009(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
MULTIMEDIA SYSTEMS AND EQUIPMENT –

MULTIMEDIA E-PUBLISHING AND E-BOOKS –

READER’S FORMAT FOR E-PUBLISHING

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62524 has been prepared by technical area 10: Multimedia e-
publishing and e-books, of IEC technical committee 100: Audio, video and multimedia

systems and equipment.
The text of this standard is based on the following documents:
CDV Report on voting
100/1376/CDV 100/1487/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

62524 © IEC:2009(E) – 5 –
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in

the data related to the specific publication. At this date, the publication will be

• reconfirmed,
• withdrawn,
• replaced by a revised edition, or

• amended.
A bilingual edition of this document may be issued at a later date.

– 6 – 62524 © IEC:2009(E)
INTRODUCTION
Markets for multimedia e-book and e-publishing require standardization of formats for e-book

data interchange among related parties; authors, data preparers, publishers and readers. The

formats are classified into submission format, generic format and reader’s format. The

submission format has to support an interaction between authors and data preparers. The

generic format has to provide an interchange format for data preparers and publishers and

therefore should be reading-device-independent. The reader’s format depends on e-

publishing equipment.
62524 © IEC:2009(E) – 7 –
MULTIMEDIA SYSTEMS AND EQUIPMENT –

MULTIMEDIA E-PUBLISHING AND E-BOOKS –

READER’S FORMAT FOR E-PUBLISHING

1 Scope
This International Standard specifies a reader’s format for multimedia e-publishing employed

for e-book data interchange among publishers and readers, satisfying a number of readers’
requirements such as being non-revisable, equipment-adaptive and application-adaptive.
NOTE This International Standard does not address the following issues:
• elements necessary for final print reproduction only;
• rendering issues related to physical devices;
• metadata issues for document management;
• security issues such as DRM for document.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
IEC/TS 62229:2006, Multimedia systems and equipment – Multimedia e-publishing and e-
book – Conceptual model for multimedia e-publishing
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
data preparer
organization or person that prepares an e-book
NOTE An editor is an example of preparer.

3.2
multimedia e-book
multimedia content consisting of text, graphics, sound and/or video data
3.3
publisher
organization or person that issues and distributes an e-book
3.4
reader
the final user who reads the e-book
3.5
reader’s format
format for multimedia e-book contents rendered and presented by reading device

– 8 – 62524 © IEC:2009(E)
3.6
reading device
equipment or program used to render and display e-books

4 Position and requirements for reader’s format

4.1 Reader’s format in contents creation/distribution model

The conceptual model for multimedia e-publishing (IEC 62229) defines a contents

creation/distribution model shown in Figure 1.

Author <--(1)--> Data preparer <--(2)--> Publisher --(3)--> Reader
IEC  190/09
Figure 1 – Contents creation/distribution model
In the third step of the distribution chain, the publisher creates the final version of the
document in the reader’s format, based on data obtained from the generic format in the
previous step, and finally distributes it to the reader. There can be several distinct reader’s
formats, adapted to the various reading devices and distribution schemes. Because of reading
devices’ potential limitations, some reader’s format may lack support for certain features of
the corresponding generic format. It is the publisher’s role to determine how to convert an e-
book to a less capable format.
4.2 Requirements for reader’s format
The reader’s format can satisfy the following requirements of readers:
a) non-revisable
As the reader’s format is the final form of the document, which will be used only for
viewing, there is little point in it being revisable. What matters most is that the file should
be easy to process, even if this makes editing the data more difficult. Being revisable can
even be considered a problem, since it makes the format needlessly complex.
b) equipment-adaptive, application-adaptive
The reader’s format is directly processed while the reader browses the book. For that
reason, to maximize the reader’s comfort, the format should be specifically designed to
match the capabilities of the device, in terms of CPU power, memory foot-print, display
size, etc. For example, a format targeted at a device with weak processing abilities should,
in order to keep the memory and CPU requirements low: (1) Use a light special purpose
binary structure, rather than processing-intensive formats like XML, (2) store the pre-
calculated position of the elements, rather than compute the layout on the fly. On the
other hand, if the target reading device is a high end processing system like a PC, a

format allowing for rich multimedia effects would be preferred, since it can easily be
handled.
c) legibility
To achieve a sufficient level of reading comfort, it is important that the reader’s format
pays attention to legibility on the reading device. In that regard, the following
implementation methods can be considered.
• Fixed page layout
The format defines the document so that each page of the document may be rendered
identically on any reading device. In this type of layout, it is common to record directly
in the file the actual position of all displayable elements. Generally, as the publisher
can specify precisely the final aspect, he will set the layout that is deemed to be the
most comfortable for the reader. Consequently, complex designs can be achieved, as
long as the display is as large as, or maybe larger, than the designer expected, making
it possible to reach excellent levels of legibility. On the other hand, if the actual display
is smaller than the one the document was designed for, it must be zoomed out,

62524 © IEC:2009(E) – 9 –
possibly making some characters unreadable, or the reader has to scroll around the

document, reducing the reading comfort.

• Flowing layout
In this type of layout, the reading device dynamically determines, according to the

screen size, where line breaks should be inserted, and compute the resulting position
of the various elements. The final layout therefore depends on the screen size, font
type, font size, etc. The reading device usually has a set of rules to handle word

wrapping or hyphenation (ends of lines). Even though this layout model cannot achieve

designs as sophisticated as fixed page layouts, it can guarantee that the text will

remain clearly readable, whatever the screen size. It also usually gives more

customization options to the reader, letting him set parameters as the font size or

colour, making it more easily adaptable to individual readers’ preferences. On the
other hand, the publisher somewhat loses control over the final appearance of the
document.
• Others
Intermediate solutions also exist. For example, a format could specify what is
essentially a fixed layout when the screen is large enough to display the defined layout
at the current zoom level, but also allow, when zooming in, to change the layout (by
collapsing the margins or changing the paragraphs size, for example), so that the
characters can indeed be zoomed in, without making the page larger than the screen.
4.3 File format
A reader’s format may have a specific data structure depending on the reading device. When
rendering functionality is supported by reading devices, both logical structure and style
specification are recommended for flexibility of presentation. When no rendering functionality
is supported by reading devices, the reader’s format should have a final form structure.
The format may also be adapted to the mode of distribution.
• Complete single download: A whole e-book is copied or downloaded at a time to the
reading device. In that case, the e-book can usually be stored in a single file.
• Continuous download: Chunks are downloaded on demand, during the rendering. This is
useful for device with readily available connectivity, but limited storage capacity. This may
be achieved by splitting the document in several small files.
4.4 Features of the reader’s Format
4.4.1 General
The features of the reader’s format may vastly vary with the targeted reading devices,
depending on their capabilities. For this reason, while creating contents for a particular

reading device, the publisher may have to omit some features, or, on the contrary, add others
to compensate.
4.4.2 Types of displayable elements
Actual rendering capacities of the rendering device may vary, but reader’s formats should at
least support text and static images. In addition, animations made of a sequence of static
images, sound, movies and other multimedia data may be supported too.
4.4.3 Layout and styling
Reader’s format, as the final document, shall contain all the styling information needed for
proper screen rendering. As stated in 4.2 c), there are mainly two types of layout: the fixed
page layout, and the flowing layout. In each case, the way to specify the style may be quite
different. When opting for a fixed page layout, the most common solution is to store the final
position and style of each displayable element. On the other hand, formats with a flowing

– 10 – 62524 © IEC:2009(E)
layout will have settings such as line spacing, character spacing, indentation and margins,

which will be used for computing the layout on the fly by the reading device.

4.4.4 Fonts
In most formats, it is possible to set various text properties, such as font, size, colour, bold or

italic, etc.
Moreover, in the case of fixed layout, to ensure that the page is rendered as intended, the

font itself may be embedded in the document. On the other hand, in the case of flowing layout,

while it is common to use the fonts bundled with the system, font data can sometimes be

embedded in the document to ensure that all the needed glyphs will be available at read-time.
4.4.5 E-book specific features
• Link jump
Allows to jump to a predefine position within the document or to a web site, upon clicking
on, or otherwise activating a certain part of the document.
• Effects
Specifies special visual effects for certain parts of the document, like fade-in or wipe.
5 Conformance level
Generally, reader’s formats are designed to closely match the reproduction capabilities of the
reading devices. As reading devices can be quite diverse in reproduction capabilities, it is to
be expected that the capabilities of each reader’s formats differ accordingly. To ease
communication and understanding between the various actors of the e-book publishing market,
this International Standard establishes a 3-level classification, namely, minimum, medium and
rich conformance levels, to help categorize the different reader’s formats.
This International Standard requires that each format define such 3-tier classification in itself.
While this standard stipulates a very rudimentary capability for minimum conformance level,
other details of the 3 levels are left to the description of each format to allow for diversity
among different formats.
a) Minimum conformance level
Targeted at devices with low reproduction capabilities.
This standard requires that at least a line of text data be displayed for a viewer to satisfy
minimum conformance level.
b) Medium conformance level
Intermediate level between minimum and rich conformance levels.
c) Rich conformance level
Targeted at devices with high reproduction capabilities.

62524 © IEC:2009(E) – 11 –
Annex A
(normative)
C-XMDF reader's format
A.1 About compact XMDF
The present International Standard describes an e-book format targeted at mobile phones.

Similarly to HTML, text is not divided into pages, but dynamically arranged according to the

screen and font size. This type of layout will be called flowing layout.
Compact XMDF documents may be divided into several parts, for distribution or retail
purposes.
A compact XMDF document is usually made of several flows. These data structures are
meant to match a meaningful division of the document, such as chapters. Flows are displayed
in the order specified in the content data. The viewer should do a page break when moving
from a flow to the next one. The specific way a document is to be divided into flows is not
specified, and is left to the document preparer’s discretion. Chapters of a novel or articles of a
newspaper are good examples of possible divisions. Note that it is perfectly acceptable not to
organize the document in several flows, and store every thing in only one flow. There are two
types of flows: formatted text flows, and image base cell flows. In this text, when the type of
the flow is obvious from the context, or not relevant to the discussion at hand, they may be
simply referred to as flows.
To meet both the requirements of ease of edition during the preparation phase, and ease of
processing by the software viewer, there are two corresponding format, as described in
Table A.1.
Table A.1 – File types
Type Details
Generic format Format used for creation and edition of the document. It is meant to be easy to
modify with a text editor, and is based on XML and CSV files.
Reader’s format Format used for distribution purposes. It is designed to be easy to process by the
viewer software, and is a binary format.

Both formats have equivalent semantics, and the generic format is to be translated to the
reader’s format prior to distribution, possibly using conversion software.
Conversion
Generic format Reader’s format
IEC  191/09
Figure A.1 – Relation between generic and reader's formats
This standard describes the binary reader’s format.

– 12 – 62524 © IEC:2009(E)
A.2 Terms and definitions
For the purposes of this annex, the following terms and definitions apply.

A.2.1
checksum
sum one by one of all the bytes of the file (the checksum itself excluded) stored as a 4 byte

field
A.2.2
cxmdf_char type
an integer ranging from 0 to 255, stored in one byte
A.2.3
cxmdf_int type
an integer ranging from 0 to 4 294 967 295, stored in four bytes in big-endian order
A.2.4
cxmdf_short type
an integer ranging from 0 to 65 535, stored in two bytes in big-endian order
A.2.5
cxmdf_Sshort type
an integer ranging from −32 768 to 32 767, stored in two bytes in big-endian order
A.2.6
cxmdf_string type
data type used to store character strings
See Table A.2 for details.
Table A.2 – Cxmdf_string type
Type/number of
Content Details
bytes
Cxmdf_char Length of the Records the number of bytes used to store the string.
string
n String The number of bytes of this field is determined by the
previous field. If 0, then this field does not exist. The string
is to be interpreted according to the encoding specified in
the character encoding flag of the root file (see A.4.1).

A.2.7
flow number
flows are numbered in order, starting at 0; the first flow is 0, the second is 1; the third is 2 and
so on
A.2.8
half width and full width characters
characters called half width are the usual range of Latin characters, and similarly sized
characters; full width characters, primarily used by CJK languages, are typically twice as large,
even in mono space fonts
NOTE Most half width characters, including the space character, have a full width version, visually distinct, used
for typographic purposes.
62524 © IEC:2009(E) – 13 –
A.2.9
horizontal and vertical writing

text can be displayed in horizontal, left-to-right lines, beginning at the top of the page and

going down, or in vertical top-to-bottom lines, beginning at the right of the page, and going left

NOTE The vertical mode is primarily used for CJK languages.

A.2.10
image number
images are numbered in their order of registration starting from 0, within the range specified

in the root file as number of image data (see A.4.1)

A.2.11
in-line note character
in-line note characters are characters used to denote the reading, or pronunciation of other
data or for other purposes (in-line notes)
NOTE Characters used in in-line notes are language and application dependent. This International Standard
distinguishes in-line note characters from standard characters due to the possibility that the viewer needs special
processing to handle in-line notes because of their character size, layout etc.
A.2.12
sound number
sounds are numbered in their order of registration starting from 0, within the range specified
in the root file as number of sound data (see A.4.1)
A.2.13
standard character
standard characters are characters of the set specified in the root file (see A.4.1) with the
standard character string flag
A.2.14
standard character string
strings made of standard characters
A.2.15
tag
basic unit of control information, used to carry the display settings to be applied to flows’ text,
such as paragraphs, font settings, pictures to be inserted, and so on
NOTE Tags are composed of a number identifying the feature they are related to, and parameters to give the
setting’s details.
A.2.16
unused region
region not used in this standard, which the C-XMDF viewer program is to ignore
A.3 File organization
A.3.1 Compact XMDF format
The compact XMDF format is made of several files. This clause introduces the different file
types, and the naming conventions.
A.3.2 File types
Compact XMDF documents are made of files of types shown in Table A.3.

– 14 – 62524 © IEC:2009(E)
Table A.3 – File types
File type Content
Root file The first file that the viewer software must access. It contains bibliographic data,

determines whether there is an index or not, how many flows, images or sound are

used, and so on. There is always one root file.

Text flow body file The file storing the unformatted text of a text flow. There is one such file per text flow.

All formatting information is stored separately in the text flow control file.

Text flow control file Used when displaying a text flow, this file contains formatting information to be applied

to the raw text of the text flow body file. It provides information on paragraphs, font
style, inserted picture, links, and so on. There is one such file per text flow.

Cell flow control file The file used to describe the content of cell flows. It stores information on which
picture to use, on the transition effects, hyperlinks, and so on. There is one such file
per cell flow. Unlike text flows, this is the only file needed.
Index body file File storing the unformatted text of the index, similarly to text flow body files.
Index control file File storing the formatting information of the index. It has the same structure as text
flow control files.
Picture file Files storing the images used in text of cell flows. As of publication of this standard,
JPEG, PBM, GIF and MIG (see A.6) can be used.
Sound file Files storing the sounds used as background music in the flows. As of the current
specification, MFi (not supported on all devices), SMF and SP-MIDI (not supported on
all devices) can be used.
A.3.3 File naming conventions
All files composing a compact XMDF document are named according to the convention
detailed in Table A.4. As explained in A.4.1, there is no field in a compact XMDF document to
record the name of the different files used. File names, which are needed to access them or
download them from the server, are determined by convention instead.

62524 © IEC:2009(E) – 15 –
Table A.4 – File naming conventions

File type Naming convention File name example Abbreviation Notes

Root file root.cxf (fixed) Only the preceding name none

Text flow body f+ flow number +.txt File name for the flow t+ flow number See A.2 about flow

file number 2: numbers
f2.txt
Text flow f+ flow number +.ctl File name for the flow c+ flow number See A.2 about flow
control file number 0: numbers

f0.ctl
Cell flow control File name for the flow k+ flow number See A.2 about flow
f+ flow number +.kom
file number 3: numbers
f3.kom
Index body file index.txt (fixed) Only the preceding name none
Index control index.ctl (fixed) Only the preceding name none
file
Picture file i+ image number + File name for the picture [JPEG] See A.2 about image
extension number 15, of jpeg type: numbers
j+ image number
i15.jpg The extension depends on
[PBM]
the format in which the
image is encoded.
p+ image number
JPEG : .jpg
[MIG]
PBM : .pbm
i+ image number
MIG : .mig
[GIF]
GIF : .gif
g+ image number
Sound file s+ sound number + File name for the sound [MFi] See A.2 about sound
extension number 15, of mld type: numbers
m+ sound number
s15.mld The extension depends on
[SMF/SP-MIDI]
the format in which the
sound is encoded. As of
s+ sound number
publication of this
standard, the following
formats can be used.
MFi: .mld
SMF/SP-MIDI: .mid
Based on these rules, to determine the name of all files, the only information needed is: the
number of flows, the type of each flow, the number of images, the format of each image, the
number of sounds, the format of each sound and the availability of the index. For example, a

document defined as having
• 3 text flows (in the order : text, text, cell),
• 3 images, all of which are jpegs,
• 2 sounds, the first being MFI, and the second SMF,
• an index,
would be composed of the following 12 files.
root.cxf, f0.txt, f1.txt, f0.ctl, f1.ctl, ｆ 2.kom, index.txt, index.ctl, i0.jpg, i1.jpg, i2.jpg, s0.mld,
s1.mid
Note that as all compact XMDF documents use the same convention, there will be duplicated
file names between different documents. Care shall be taken not to mix up the files.

– 16 – 62524 © IEC:2009(E)
A.3.4 Media types of the files

The different files that compose a compact XMDF document have media types shown in

Table A.5. They are used, for example, when downloaded form a contents server.

Table A.5 – Media types
File type media type notes
Root file application/x-cxmdf
Text flow body text/plain
file
Text flow control application/x-cxmdf-ctl
file
Cell flow control application/x-cxmdf-koma
file
Index body file text/plain
Index control file application/x-cxmdf-ctl Identical to text flow control file
Picture file JPEG : image/jpeg Set to the appropriate media type, depending on
the actual image format.
PBM : image/pbm
MIG : image/x-cxmdf-mig
GIF : image/gif
Sound file MFi: Set to the appropriate media type, depending on
the actual sound format.
audio/mfi
SMF/SP-MIDI:
audio/midi
A.4 Details of the reader’s format
A.4.1 Root file
This is the file that the viewer software must read first. It contains the number and type of
flows, the availability of an index, the number and type of images and sounds, bibliographic
data, and so on. Any compact XMDF document has one and only one root file.
Its data structure is shown in Table A.6
Table A.6 – The data structure of root file

Type/Number of
Content Details
bytes
4 Compact XMDF ID Identifies the file as a compact XMDF document. It is defined as
number the four characters: CMDF. On any other value, the viewer
software should abort reading the file.
4 Compact XMDF Identifies the version of the compact XMDF format used by the
version number current document, as a sequence of four characters. As of
publication of this standard, it is set to 1,40. On any non-
supported value, the viewer software should abort reading the
file.
Cxmdf_char Number of standard The number of character sets that can be used by the standard
character sets character strings. Cannot be 0. If more than 1 character set is
specified, their union must be used.
Cxmdf_char Standard character set Indicates the character set used by the standard character
flag strings. As of the current specification, the following values
can be used: (See A.7.1 for other values)
0x00:
JIS X 0201 and JIS X 0208: 1997)
0x01:
The Big5 character set.
62524 © IEC:2009(E) – 17 –
Type/Number of
Content Details
bytes
0x02:
The GB2312 character set
0x03:
The ISO-IR-149 character set
0x04:
The US-ASCII character set
0x05
The ISO-8859-15 character set
On unaccepted values, the viewer software should abort reading
the file.
… … “Standard character set flag” repeated, according to “Number of

standard character sets”
Cxmdf_char Character encoding Defines the character encoding used in the document. It applies
flag to all character strings in the document, including bibliographic
data, the body of text flows or of the index. As of the current
specification, the following value can be used.
0x01: UTF-16 (Big-Endian without BOM)
On any other value, the viewer software should abort reading
the file.
Cxmdf_char Content type Defines which types of flow can be used in the document
bit7(MSB)
Text flows
0: Text flows are not used
1: Text flows are used
bit6:
Cell flows
0: Cell flows are not used
1: Cell flows are used
bit5 - 0:
These bits are not used, and are always set to 0.
Cxmdf_short Unused region Reserved for future extensions. Set to 0x0000. On any other
value, the viewer software should abort reading the file.
Cxmdf_int Total size The total size of this Compact XMDF document, in bytes,
consisting of the sum of the size of all its files: root file, index
and text flow body and control files, cell flow files, images and
sounds.
Cxmdf_int Flow body total size The total size of all the text flow body files used in this compact
XMDF document, in bytes.
Cxmdf_int Total image size The total size of all the image files used in this compact XMDF
document, in bytes.
Cxmdf_int Total sound size The total size of all the sound files used in this compact XMDF
document, in bytes.
Cxmdf_int Recommended To guarantee a comfortable reading experience, at least this
Download size size should be available to the viewer software to download the
flows immediately preceding and following the current flow.
Cxmdf_char Screen size settings Determines whether the intended screen size at the time of
flag content creation is stored or not.
0x00: not stored, 0x01: stored

Cxmdf_short /0 Recommended x size The intended screen width at the time of content creation. Only
stored in screen size settings flag is set to 0x01.

Cxmdf_short /0 Recommended x size The intended screen height at the time of conte
...