IEC 62605:2016

IEC 62605 ®
Edition 2.0 2016-02
INTERNATIONAL
STANDARD
Multimedia systems and equipment – Multimedia e-publishing and e-books –
Interchange format for e-dictionaries
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 20 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 15 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 65 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
IEC 62605 ®
Edition 2.0 2016-02
INTERNATIONAL
STANDARD
Multimedia systems and equipment – Multimedia e-publishing and e-books –

Interchange format for e-dictionaries

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 33.160.60; 35.240.20; 35.240.30 ISBN 978-2-8322-3102-9

– 2 – IEC 62605:2016 © IEC 2016
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
2 Normative references. 8
3 Terms and definitions . 8
4 Position and requirements for interchange format for e-dictionaries . 8
4.1 Interchange format for e-dictionaries in contents creation/distribution model . 8
4.2 Requirements for interchange format for e-dictionaries. 9
5 File formats . 9
6 Semantics . 10
Annex A (normative) XMDF-LeXML format . 11
A.1 General . 11
A.2 Overview of the format’s structure . 11
A.3 Elements and attributes . 12
A.3.1 General . 12
A.3.2 Page_ID . 12
A.3.3 Object_ID . 12
A.3.4 Char_ID . 12
A.3.5 Reading . 12
A.3.6 Filename . 13
A.3.7 Standard character . 13
A.3.8 Standard character string . 13
A.3.9 Extended character . 14
A.3.10 Extended character string . 14
A.3.11 External character . 14
A.3.12 External character string . 16
A.3.13 External extended character string . 16
A.3.14 Coordinates . 16
A.3.15 Polygonal_region . 17
A.3.16 Color . 17
A.3.17 Date . 18
A.3.18 Time . 18
A.3.19 Country . 18
A.3.20 Personal_name . 18
A.3.21 Organization_name . 20
A.3.22 Address . 20
A.3.23 Permission . 22
A.3.24 Keyword . 24
A.3.25 Telephone_number . 24
A.3.26 Mail_address . 25
A.4 Description format details . 25
A.4.1 General . 25
A.4.2 Book information modules . 26
A.4.3 Content management module . 41
A.4.4 Event info module . 59

A.4.5 Parts data module . 66
A.4.6 Object instances . 72
A.5 Available color names . 119
A.6 Localization. 120
A.6.1 Possible additions . 120
A.6.2 Standard characters . 120
A.6.3 Characters usable for reading . 121
A.6.4 Line breaking methods . 121
A.6.5 Sorting rules for . 122
A.6.6 Additional attributes for . 123
A.6.7 Normalization methods for . 124
A.6.8 Character encoding conversions . 124
A.7 Adaptation . 124
A.8 Specification of the XMDF-LeXML format in the RELAX NG syntax . 124
Annex B (normative) LeXML format . 160
B.1 General . 160
B.2 Elements for content structure . 160
B.2.1 Parameter entity definition . 160
B.2.2 Root elements . 162
B.2.3 headword-related elements . 166
B.2.4 Main-text related elements . 169
B.2.5 Subheadword related elements . 174
B.2.6 Other block elements . 178
B.2.7 Media related elements . 182
B.2.8 Other structural elements . 184
B.3 Inline elements . 190
B.3.1 Labels . 190
B.3.2 pronunciation/accent – related elements . 192
B.3.3 Part-of-speech related and other elements . 194
B.3.4 Other dictionary-specific elements . 195
B.3.5 Text-decoration related elements. 205
B.3.6 Typesetting-related elements . 210
B.3.7 Other elements . 213
B.4 Specification of the LeXML format in the DTD syntax . 220
Bibliography . 234

Figure 1 – Contents creation/distribution model . 8
Figure 2 – Contents creation/distribution model (modified) . 9
Figure 3 – Relationship between concepts . 9
Figure A.1 – XML tree structure . 11
Figure A.2 – Example of valign="middle" . 74
Figure A.3 – Example of dropped capital . 80
Figure A.4 – Left and right margin of a paragraph . 80
Figure A.5 – Horizontal writing in vertical text . 88
Figure A.6 – Ruby . 89
Figure A.7 – Example of search page object instance rendering . 115

– 4 – IEC 62605:2016 © IEC 2016
Table A.1 – Base characters for reading . 13
Table A.2 – Standard character set . 13
Table A.3 – Usable characters for a telephone number . 25
Table A.4 – Characters usable for email addresses . 25
Table A.5 – Characters usable for the lookup key . 58
Table A.6 – Color names . 120
Table A.7 – Examples of additional standard character sets . 121
Table A.8 – Example of additional characters usable for readings . 121
Table A.9 – Example of additional sorting rules . 122
Table A.10 – Example of additional language specific attributes for . 123

INTERNATIONAL ELECTROTECHNICAL COMMISSION
______________
MULTIMEDIA SYSTEMS AND EQUIPMENT –
MULTIMEDIA E-PUBLISHING AND E-BOOKS –
INTERCHANGE FORMAT FOR E-DICTIONARIES

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 itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
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.
International Standard IEC 62605 has been prepared by technical area 10: Multimedia e-
publishing and e-book technologies, of IEC technical committee 100: Audio, video and
multimedia systems and equipment.
This second edition cancels and replaces the first edition published in 2011. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition.
a) Ref element is added to facilitate cross reference between entries.
b) A new version of LeXML format, which is one of the base formats of the first edition, has
been expanded and becomes Annex B. (The existing format becomes Annex A.)

– 6 – IEC 62605:2016 © IEC 2016
The text of this standard is based on the following documents:
CDV Report on voting
100/2430/CDV 100/2506/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.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC website 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 version of this publication may be issued at a later date.

INTRODUCTION
Markets for multimedia e-books and e-publishing require standardization of formats for e-book
data interchange among associated people, authors, data preparers, publishers and readers.
The formats are classified into submission format, interchange format and reader’s format.
The submission format supports an interaction between authors and data preparers. The
reader’s format depends on e-publishing equipment. The interchange format provides an
interchange format for data preparers and publishers and therefore should be e-publishing
equipment independent.
The International Electrotechnical Commission (IEC) draws attention to the fact that it is
claimed that compliance with this document may involve the use of patents.
IEC takes no position concerning the evidence, validity and scope of this patent right.
The holder of this patent right has assured the IEC that he/she is willing to negotiate licences
under reasonable and non-discriminatory terms and conditions with applicants throughout the
world. In this respect, the statement of the holder of this patent right is registered with IEC.
Information may be obtained from:
Sharp Corporation,
22-22 Nagaike-cho,
Abeno-ku,
Osaka 545-8522,
Japan
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights other than those identified above. IEC shall not be held responsible for
identifying any or all such patent rights.
ISO (www.iso.org/patents) and IEC (http://patents.iec.ch) maintain on-line data bases of
patents relevant to their standards. Users are encouraged to consult the data bases for the
most up to date information concerning patents.

– 8 – IEC 62605:2016 © IEC 2016
MULTIMEDIA SYSTEMS AND EQUIPMENT –
MULTIMEDIA E-PUBLISHING AND E-BOOKS –
INTERCHANGE FORMAT FOR E-DICTIONARIES

1 Scope
This International Standard specifies the interchange format for e-dictionaries among
publishers, content creators and manufacturers.
This International Standard does not address the following aspects:
• data formats for reading devices;
• elements necessary for final print reproduction only;
• rendering issues related to physical devices;
• security issues such as DRM for documents.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. 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
manufacturer
organization or person that manufactures hardware and/or software of the e-book
4 Position and requirements for interchange format for e-dictionaries
4.1 Interchange format for e-dictionaries in contents creation/distribution model
The conceptual model for multimedia e-publishing (IEC TS 62229) defines a contents
creation/distribution model shown in Figure 1.
Author <--(1)--> Data preparer <--(2)--> Publisher --(3)--> Reader
IEC
Key
(1) content data in submission format
(2) content data in interchange format
(3) content data in reader’s format
Figure 1 – Contents creation/distribution model

It should be noted that the role of manufacturers of e-dictionary hardware and software
overlaps that of the publisher in Figure 1. Therefore, a slightly modified model will be
assumed for this International Standard, as shown in Figure 2.
Author <--(1)--> Data preparer <--(2)--> Publisher (manufacturer) --(3)--> Reader
IEC
Figure 2 – Contents creation/distribution model (modified)
This International Standard specifies the interchange format between data preparers and
publishers, i.e. a format for (2) in Figure 2, though it may be used as a reader's format.
4.2 Requirements for interchange format for e-dictionaries
An interchange format for e-dictionaries needs to address the following.
• Description of keywords, links from the keywords to entries (link data) and the order of the
entries.
• Description of articles for each entry (entry data). This includes text, image, and other
multimedia functionalities generally required for e-books.
• Description of bibliographical data and other data. This should include the name of the
author and the publisher, the title of the content and the explanatory note. The relationship
between these concepts is visually represented in Figure 3.
• Description of contents written in various languages.
Entry 1
keyword 1
title
keyword 2
author name
keyword 3 and
publisher name
:
explanatory note
keyword n
Entry n
:
Entries and
Link data
Keywords
Bibliographical data, etc.
their order
IEC
Figure 3 – Relationship between concepts
5 File formats
This International Standard defines two XML-based formats. One is based on XMDF (as
described in IEC 62448:2013, Annex B) and LeXML. The format is hereafter called
XMDF-LeXML format. The other is based solely on LeXML 3.0. They are presented in
Annex A and Annex B, respectively.
NOTE LeXML is proposed by Digital ASSIST Ltd. Its original specifications are found at
http://www.d-assist.com/index.html (in Japanese).

– 10 – IEC 62605:2016 © IEC 2016
6 Semantics
Elements of the XMDF-LeXML format can be rendered in accordance with appropriate style
specifications, which are outside the scope of this International Standard.

Annex A
(normative)
XMDF-LeXML format
A.1 General
The XMDF-LeXML format is an interchange format for e-dictionaries multimedia e-book data
interchange, targeted at data preparers and publishers rather than the reader, with an
emphasis on mobile devices as a target platform. Much like HTML, this format does not split
the document in fixed pages, but determines the layout according to the viewer device’s
display size, the font in use, and so on. In this annex, such contents will be referred to as
flowing content, as opposed to paged content.
A.2 Overview of the format’s structure
Flowing contents are usually composed of several concatenated flows. This annex makes no
particular requirement concerning the way the flowing content should be split into individual
flows. This decision is left to the data preparer, to accommodate the various types of contents.
For instance, a newspaper may have one flow per article, a novel one per chapter, and so on.
It is also possible not to split the content, and to have only one flow. However, it should be
noted that particularly large flows, or an extremely large number of flows, may impact on
runtime performance, depending on the specific version of the viewer in use, the available
memory, and so on.
The XML tree structure of the format is shown in Figure A.1.




Content

management
data

There may be
Root
several of flow data

Points to a file name

Object instance

Parts data Object instance

Object entry can
be repeated
several times
IEC
Figure A.1 – XML tree structure

– 12 – IEC 62605:2016 © IEC 2016
The actual contents of each flow, in other words, what will be displayed by the viewer, is
recorded in the object instance. The object instance is registered in object_entry, and
associated with an ID number and other auxiliary data, turning it into playable/displayable
data. Flow_data determines its content by pointing at such registered objects. In addition,
information on functionalities such as page link is recorded in event_info.
The main part of Annex A is generic, and may be used for any country and language.
However, some parts may have language specific behavior. Localization-related issues are
detailed in Clause A.6.
A.3 Elements and attributes
A.3.1 General
The different types of values that may be used in the various elements or attributes are
explained below. The elements and attributes detailed below will be valid throughout this
annex, and will be referenced by other constructs. In the following explanations, alphanumeric
characters refer to numerals from 0 to 9 and alphabetic letters from a to z and A to Z.
A.3.2 Page_ID
Page_ID specifies a unique identification number for the flow data of the flowing contents. It is
a string starting by the "PG" characters, followed by alphanumeric characters.
Example:


A.3.3 Object_ID
Object_ID specifies a unique identification number for objects used in the flowing contents. It
is a string starting by the "OB" characters, followed by alphanumeric characters.
Example:


A.3.4 Char_ID
Char_ID specifies an identification number for positions (character strings, etc.) within text
and dictionary data objects. It is an alphanumeric string which is to be given uniquely in the
text (see A.4.6.2) and dictionary data object instance (see A.4.6.3). Char IDs with the same
value in different object instances are regarded as separate and don't affect each other.
Example:

Clickherefor details.

A.3.5 Reading
For sorting purposes, reading may be useful to specify the reading of each word. Restricting
the characters allowed for this purpose to a limited set makes it easier to define the sorting
method. Such characters should be determined on a per language basis. All languages can

use the characters listed in Table A.1 as a common base, while the localization (see
Clause A.6) will describe the language specific extensions to it.
Table A.1 – Base characters for reading
a
Name Corresponding characters
Basic alphabet A to Z (U+0041 to U+005A)
A to z (U+0061 to U+007A)
Numerals 0 to 9 (U+0030 to U+0039)
Others space (U+0020),  ((U+0028), ) (U+0029)
a
[Attributes]ll values are in Unicode.

Example:
π
A.3.6 Filename
Filenames should be written using the following convention. The path is relative to the file in
which this reference is made. Network paths should not be used. For portability concerns, it is
recommended that only ACSII characters be used. Both the slash and backslash characters
are acceptable as directory separators. It is also recommended not to use excessively long
filenames, as those might not be supported by the host operating system.
Example:


A.3.7 Standard character
The standard character set of the document, as set by the default_ccs attribute of the
element (see A.4.2), is to be chosen from a well defined list, so as to ease the development of
viewing software. However, this list may change for different localized versions of the XMDF-
LeXML format. Any e-book data has to define its standard character set as one of or a
combination of character set(s) listed in Table A.2 and those defined for a specific localization
(see A.6.2).
Table A.2 – Standard character set
Character set name Description
"ISO 646-IRV" Characters in the range of US-ASCII

A.3.8 Standard character string
A string composed of Standard characters is called a Standard character string. Unless
specified otherwise, the spacing characters (space (U+0020), linefeed (U+000D, U+000A,
U+000D+U+000A), tabulation (U+0009)) are to be handled as follows:
Space (U+0020) to be displayed as is.
Linefeed (U+000D, U+000a, U+000D+U+000A) not to be displayed, but simply ignored.
Tabulation (U+0009) to be displayed as if it were a single space.

– 14 – IEC 62605:2016 © IEC 2016
Furthermore, because of restriction in the XML format, linefeeds (U+000D, U+000A,
U+000D+U+000A) and tabulations (U+0009) in attribute values should be replaced by spaces
when converting to the distribution format.
A.3.9 Extended character
Characters which have Unicode code points while not being among those listed below are
referred to as Extended characters.
Standard characters
Surrogate pair range (U+D800 to U+DFFF)
BOM (Byte Order Mark) (U+FFFE,U+FEFF)
NON CHARACTER (U+FFFF)
Control characters (characters between U+0000 and U+001F except tabulation (U+0009) and
linefeed (U+000A, U+000D), as well as DEL (U+007F)).
If an e-book indeed uses any Extended character in its data, the name of a character set that
covers those Extended characters should be appended to the default_ccs attribute of the
element. Note that all Extended characters used in the document do not need to be
covered by the same character set, as it is possible to specify several character sets.
A.3.10 Extended character string
A string composed of Standard characters and Extended characters is called an Extended
character string. Unless specified otherwise, the spacing characters (space (U+0020),
linefeed (U+000D, U+000A, U+000D+U+000A), tabulation (U+0009)) are to be handled the
same way as in Standard character strings.
A.3.11 External character
To display a character which is neither a Standard character nor an Extended character, it is
possible to use the element described below.
inserts an External character. The viewer may display it according to the
following methods.
a) Display the character set by the alt_set and alt_code attributes.
b) Display the image set by the alt_img or alt_vimg attributes.
c) Display the alternative letter set by the alt attribute.
Its syntax is given in Relax NG compact format below and explained in the following text.
NOTE For definitions that appear in the Relax NG compact representation of each element in this annex, see
Clause A.8.
external_char = element external_char { attlist_external_char, text }
attlist_external_char &=
attribute alt_set { text }?,
attribute alt_code { text }?,
attribute alt_img { text }?,
attribute alt_vimg { text }?,
attribute img_type { text }?,
attribute alt { text }?
[Attributes]
alt_set: Together with the alt_code attribute, it allows designating the External
character to be used. This alt_set attribute indicates the font name, while
the alt_code attribute indicates the character code point within the font. The
alt_set attribute is written in the following way:
alt_set = "font1,font2, ."
The alt_set attribute may hold several font names, separated by ","
(U+002C). In that case, the viewer should use the first font of the list that is
available (either from the platform, or included in the contents data itself) to
display the character.
alt_code: Selects a character code point in the font specified by the alt_set attribute.
It may be written either as a decimal number or a hexadecimal number,
prefixed by "0x". In case several fonts have been defined in the alt_set
attribute, the character code shall represent the same character in all of
them. This attribute can be omitted.
alt_img: Defines an alternative character image. Written as a Filename. Before
opening the file indicated by this attribute, the img_type attribute should be
checked for authorized file types. Note that it may be used only when
is used in a text object instance. When both alt_img and
alt_vimg are used, the file types shall match. This can be omitted. When
this attribute is set, display should be done according to the following
methods:
d) Monochrome images
Black pixels represent the letter, and white pixels the background. The
font color and background color are to be displayed according to the
color attribute of the element.
e) Images with levels of gray
Black pixels represent the letter, and white pixels the background. The
font color and background color are to be displayed according to the
color attribute of the element. The color of "gray" pixels shall
be computed as an intermediate value between the font color and the
background color.
f) Color images
Displayed as is.
alt_vimg: Defines an alternative character image to be used when the text is
displayed vertically (as can be the case in some languages, such as
Japanese). Written as a Filename. When omitted, the image defined in the
alt_img attribute should be used both for horizontal and vertical layout.
Before opening the file indicated by this attribute, the img_type attribute
should be checked for authorized file types. Note that it may be used only
when is used in a text object instance. When both alt_img
and alt_vimg are used, the file types shall match. This can be omitted.
When this attribute is set, the display should be done according to the same
methods as with alt_img.
img_type: Defines the mime type of the images files set in the alt_img and alt_vimg
attributes. Currently, only PNG and JPEG are supported, and should be
written as:
"image/png"
– 16 – IEC 62605:2016 © IEC 2016
"image/jpeg"
When either alt_img, alt_vimg or both are set, this attribute is required. As
with these two attributes, it can only be used in an element
inside a text object instance.
alt: Alternative character string. Written as a Standard character string. May be
omitted.
Example:
alt_vimg="ou_v.img" img_type="image/jpeg" alt="鴎"/>



A.3.12 External character string
An External character string is a string composed of Standard characters, External characters,
or both. Unless specified otherwise, spacing characters (space (U+0020), linefeed (U+000D,
U+000A), tabulation (U+0009)) should be handled the same way as they are handled in
Standard character strings.
Example:
森外
内田百

A.3.13 External extended character string
An External extended character string is a string of Standard characters, Extended characters,
External characters, or a combination of any of the above. Unless specified otherwise,
spacing characters (space (U+0020), linefeed (U+000D, U+000A), tabulation (U+0009))
should be handled the same way as they are handled in Standard character strings.
A.3.14 Coordinates
Data type to be used to store coordinates, dimension and other similar information composed
of an x and a y value. It is written as "(x, y)". The name of the attribute which uses this type of
data depends on the element.
The coordinate system explained below will be used in this annex. The origin is at the top left
corner, the x axis oriented rightwards, and the y axis downwards. As the system of
coordinates used by the viewer to map things on the screen is implementation-dependent, it
will not be discussed here.
Local coordinate system:
The coordinate system local to an object takes its origin in the upper left
corner of the circumscribed rectangle, and has the same orientation as the
general coordinate system. Positions within an object should be expressed in
the local coordinate system.
Example:


A.3.15 Polygonal_region
Data format to store the apexes of a polygon, or any other ordered sequence of vertexes.
Each vertex is stored in a element. When defining the shape of a polygon, the edges
shall not cross. If they do, the viewer’s behavior is unspecified. Its syntax is given in Relax
NG compact format below and explained in the following text.

vertex = element vertex { attlist_vertex, empty }
attlist_vertex &= attribute position { text }

[Attribute]
position: the position of the apex, expressed as Coordinates. This attribute shall not
be omitted.
Example:
 



A.3.16 Color
Data type to define colors. The following attributes are defined.
[Attributes]
color_space: Specifies the color space to be used. Currently, only RGB is accepted. If
this attribute is omitted, the viewer should act as if RGB was set.
color: Specifies the color name. Color names or numerical values may be used.
Acceptable color names are listed in Table A.6. The default value depends
on the actual element and context. Numerical values are to be written in the
following syntax.
In RGB: written as #RRGGBB. With RR, GG, BB being hexadecimal
numbers, ranging from 00 to FF. Grayscale pixel values are represented by
setting RR, GG and BB to the same value.
opacity: level of opacity. Ranging from 0 (transparent) to 100 (opaque). Presently,
the only admitted value is 100, and in case the attribute is omitted, it
defaults to 100.
Example:





– 18 – IEC 62605:2016 © IEC 2016
A.3.17 Date
Data format to store dates. It uses the same representation as ISO 8601. For instance,
1994-11-05T08:15:30-05:00 corresponds to November 5, 1994, 8:15:30 am, US Eastern
Standard Time. Abbreviated forms are also accepted. Please refer to
http://www.w3.org/TR/NOTE-datetime for details.
Example:
1994

A.3.18 Time
Data format to specify durations. Written as "XXdXXhXXmXXsXXXms", where X stands for a
digit between 0 and 9. For instance, "10d5h30m10s015ms" would mean 10 days, 5 hours,
30 minutes, 10 seconds and 15 milliseconds. Abbreviated forms such as "5m30ms" or "1s"
are possible. There is no upper bound to the number of days.
Example:


A.3.19 Country
Data format to specify a country name. Written according to the ISO 3166-1 alpha 3 standard,
in lower case.
Example:
jpn

A.3.20 Personal_name
Data format to store people’s names, such as the document author. It is stored under the
element. Its syntax is given in Relax NG compact format below and
explained in the following text. Several child elements are used to define the various parts of
the name: first name, middle name and last name. This information shall be entered via the
elements defined below. At least one of , , and
shall be specified.
personal_name =
element personal_name {
attlist_personal_name,
((first_name?, middle_name?, last_name?)
| (first_name?, last_name?, middle_name?)
| (last_name?, first_name?, middle_name?)

| (last_name?, middle_name?, first_name?))
}
attlist_personal_name &= empty

[Child elements]
Sets the first name. Written as an External character string. May be omitted.
Its syntax is given in Relax NG compact format below and explained in the
following text.
first_name = element first_name { attlist_first_name, TextWithGaiji }
attlist_first_name &= attribute reading { text }?

[Attribute]
reading: Pronunciation of the first name, written as a Reading. May
be omitted.
Sets the middle name. Written as an External character string. May be
omitted. Its syntax is g
...