ISO/TS 24530-2:2006

TECHNICAL ISO/TS
SPECIFICATION 24530-2
First edition
2006-04-15
Traffic and Travel Information (TTI) — TTI
via Transport Protocol Experts Group
(TPEG) Extensible Markup Language
(XML) —
Part 2:
tpeg-locML
Informations sur le trafic et le tourisme (TTI) — Messages TTI via le
langage de balisage extensible (XML) du groupe d'experts du protocole
de transport (TPEG) —
Partie 2: tpeg-locML
Reference number
©
ISO 2006
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2006
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 ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2006 – All rights reserved

Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Abbreviated terms . 2
4 Format of this document. 3
4.1 Tables. 3
5 tpeg-locML. 4
5.1 location_container. 4
5.2 location_coordinates. 4
5.3 location_descriptions. 8
Annex A (normative) DTD for tpeg-locML — TPEG Location Referencing for applications
(tpeg-locML.dtd). 23
Annex B (normative) External entity references for tpeg-locML — TPEG Location Referencing for
applications (tpeg-locML.ent). 28

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
⎯ an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
⎯ an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting
a vote.
An ISO/PAS or ISO/TS is reviewed after three years with a view to deciding whether it should be confirmed for
a further three years, revised to become an International Standard, or withdrawn. In the case of a confirmed
ISO/PAS or ISO/TS, it is reviewed again after six years at which time it has to be either transposed into an
International Standard or withdrawn.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TS 24530-2 was prepared by the European Committee for Standardization (CEN) in collaboration with
Technical Committee ISO/TC 204, Intelligent transport systems, in accordance with the Agreement on
technical cooperation between ISO and CEN (Vienna Agreement).
Throughout the text of this document, read “.this European pre-Standard.” to mean “.this Technical
Specification.”.
ISO/TS 24530 consists of the following parts, under the general title Traffic and Travel Information (TTI) —
TTI via Transport Protocol Experts Group (TPEG) Extensible Markup Language (XML):
⎯ Part 1: Introduction, common data types and tpegML
⎯ Part 2: tpeg-locML
⎯ Part 3: tpeg-rtmML
⎯ Part 4: tpeg-ptiML
iv © ISO 2006 – All rights reserved

Introduction
TPEG in XML (tpegML) provides the solution to diverse requirements for the ultimate delivery of TPEG
applications (potentially simultaneously) via for example ARIB, ATSC, DAB, DVB and the Internet. This will
solve the minimal adaptation layers requirement and without doubling up on message carousels, which are
handled at different layers of the protocol stacks.
The original TPEG technology uses a byte-oriented stream format, which may be carried on almost any digital
bearer with an appropriate adaptation layer. TPEG messages are delivered from service providers to end-
users, and are used to transfer application data from the database of a service provider to an end-user’s
equipment.
TPEG binary was initially designed to meet a particular brief, from the EBU’s Broadcast Management
Committee; to develop a new protocol for Traffic and Travel Information, for use in the multimedia
broadcasting environment. TPEG applications were developed with service and transport features, which
enable travel-related messages to be coded, decoded, filtered and understood both by humans (visually
and/or audibly) and by agent systems. This brief was also endorsed by the EBU TTI Broadcast Strategy Team,
who recognized the vital importance of a bearer independent TTI protocol.
The development of TPEG binary technology is excellently matched both technically and economically to DAB
and possibly to internet bearers, where of the order of up to 10 kbits/s is considered acceptable. However
other bearers such as ARIB, ATSC and DVB may be able to offer much higher data rates with economic and
technical utility. Nevertheless these bearers are highly structured (layered) in their ability to handle transparent
data services and they include mechanisms suitable for carousel delivery, which would require a considerably
different TPEG data structure before real transparency could be achieved.
Another potential use of tpegML is provided to Service Providers who would have a standardised message
generation interface, yet be able to develop systems suited to their own requirements. This will enable Service
Providers to exchange pre-edited information regardless of their message generation systems and be
substantially language independent.
tpegML has been developed using the DTD approach, which allows the use of different language entity files to
easily provide a truly language independent service. This approach has the advantage that tpegML files can
be rendered in any language, provided the language entity file is available to the internet browser. This
document provides English language entity files only. For other languages the entity files in this document
only require direct translation.
The development of this ISO/TS 24530 series was undertaken jointly with European Broadcasting Union
B/TPEG Group, which has evolved into the TPEG Forum Standards Task Force. Attention is drawn to the
EBU sponsored TPEG Forum development principles, which require all inputs containing IPR to be declared
during drafting work. No such declarations have been made.

TECHNICAL SPECIFICATION ISO/TS 24530-2:2006(E)

Traffic and Travel Information (TTI) — TTI via Transport
Protocol Experts Group (TPEG) Extensible Markup Language
(XML) —
Part 2:
tpeg-locML
1 Scope
This document establishes the XML encoding of the method of Location Referencing used by TPEG
applications.
TPEG applications contain the information required by a client TPEG decoder (i.e. both Location Referencing
and event information), to present all the information intended for the end-user when it was originated by the
service provider.
Location Referencing requires a service provider to give an impression or image, to the human end-user, of
where an event has taken place. This cannot be done easily because the human end-user may or may not be
familiar with the location. tpeg-loc has the added challenge of attempting to be as language independent as
possible. This is achieved by the use of tpeg-loc tables (essentially word-oriented data object dictionaries).
tpeg-loc is the recommended Location Referencing system for TPEG. It provides location data in a machine
readable form that allows a “thick” client such as a navigation system to map-match, on-the-fly, to locate the
event being described onto a digital map display. However, it is possible to additionally use other location
methods, such as the ‘Link-id’ method by suitably modifying the tpegML.dtd to include the relevant lines, e.g.:

%link-idML;
It is vital, for further understanding of this document, to have more than a passing understanding of the
tpeg-loc binary specification which describes, among other things, in a step-by step approach: point, link and
area definitions, and how they are structured to provide a full Location Referencing system.
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.
ISO/TS 24530-1, Traffic and Travel Information (TTI) — TTI via Transport Protocol Experts Group (TPEG)
Extensible Markup Language (XML) — Part 1: Introduction, common data types and tpegML
ISO/TS 24530-3, Traffic and Travel Information (TTI) — TTI via Transport Protocol Experts Group (TPEG)
Extensible Markup Language (XML) — Part 3: tpeg-rtmML
ISO/TS 24530-4, Traffic and Travel Information (TTI) — TTI via Transport Protocol Experts Group (TPEG)
Extensible Markup Language (XML) — Part 4: tpeg-ptiML
ISO/TS 18234-1, Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG)
data-streams — Part 1: Introduction, Numbering and Versions (SSF)
ISO/TS 18234-2, Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG)
data-streams — Part 2: Syntax, Semantics and Framing Structure (SSF)
ISO/TS 18234-6, Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG)
data-streams — Part 6: Location Referencing for applications
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
codes
3 Abbreviated terms
For the purposes of this document, the following abbreviations apply.
3.1
ARIB
Association of Radio Industries and Business (Japan)
3.2
ATSC
American Television Standards Committee (USA)
3.3
DAB
Digital Audio Broadcasting
3.4
DTD/dtd
Document Type Definition - lower case used for file naming
3.5
DVB
Digital Video Broadcasting
3.6
EBU
European Broadcasting Union
3.7
IPR
Intellectual Property Right(s)
3.8
PTI
Public Transport Information
3.9
RTM
Road Traffic Message
3.10
SSF
Syntax, Semantics and Framing Structure
2 © ISO 2006 – All rights reserved

3.11
TPEG
Transport Protocol Experts Group
3.12
tpegML
tpeg XML applications - use lower case to distinguish them from the TPEG binary applications which use
upper case
3.13
tpeg-loc
location referencing for applications
3.14
tpeg-ilc
descriptor formed according to tpeg-loc rules
3.15
TTI
Traffic and Travel Information
3.16
WGS84
World Geodetic System 1984
3.17
XML
Extensible Markup Language
4 Format of this document
This document is divided into Sections, each describes an XML element used in tpegML. Each element has
an introduction explaining what it is for, the DTD definition relevant to it, guidelines “extending” the DTD and
an example. The complete .dtd and .ent files are contained in Annexes A and B.
4.1 Tables
A large number of attributes used in elements in tpegML are based on tables in the TPEG specifications. To
encode this in XML there are defined general entity references for all the table entries. In this Technical
Specification series these entities are taken from the TPEG tables defined in the equivalent part of the
ISO/TS 18234-series.
For display in other languages these entity files only need to be replaced by directly translated equivalents.
These are named, for example locX_Y, where X is the table number and Y is the row number (e.g.
“loc01_01” is the entry in the Loc location_type table for large area). The DTD does not restrict the entity
references that can be used in an attribute so the ‘guidelines’ sections indicate which entities/tables should be
used for which attributes.
Table numbers use a leading zero below 10, whereas the row number within a table does not use a leading
zero. Table numbers are random and entries within a table are random – no priority order is implied.
5 tpeg-locML
This is defined fully in the tpeg-locML.dtd and tpeg-locML.ent files (see Annexes A and B).
5.1 location_container

language CDATA #REQUIRED
>
location_container: This is the location referencing method for TPEG. It combines machine readable and
human understandable location referencing information.
The language attribute shall use entity references of the form loc41_x.
Example:

…
…

5.2 location_coordinates












location_type CDATA #REQUIRED
>
location_coordinates: The location type attribute shall use entity references of the form loc01_x.
Example:


…
…


…
…


4 © ISO 2006 – All rights reserved

5.2.1 location_point

location_point: The elements can be grouped together in a number of ways according to the type of area or
point to be described.
Example:

…
…

5.2.2 mode_type_list


mode_type_list: This describes the modes of transport that this description applies to.
Example:

…

5.2.2.1 mode_of_transport





















mode_of_transport CDATA #REQUIRED
>
mode_of_transport: This describes a mode of transport. The mode attribute shall use entity references of the
form loc05_x.
Example:


5.2.3 WGS84

longitude CDATA #REQUIRED
latitude CDATA #REQUIRED
>
WGS84: This describes a location as a point, defined by a longitude and latitude pair, or an area, defined by a
longitude/latitude pair and an expansion element. The longitude and latitude attributes shall be in units of
degrees.
Example:

…

5.2.3.1 expansion

radius_of_circle CDATA #REQUIRED
>
expansion: This describes the radius of a circle around a point. The radius_of_circle attribute shall be in
metres.
Example:


5.2.3.2 height














height_descriptor CDATA #REQUIRED
height %intsili; #REQUIRED
>
height: This describes height information. The height_descriptor attribute should only use entity references of
the form loc04_x. The height attribute shall be in metres.
Example:


6 © ISO 2006 – All rights reserved

5.2.4 location_descriptor
















































descriptor_type CDATA #REQUIRED
descriptor %short_string; #REQUIRED
>
location_descriptor: This describes a location with a name. The descriptor_type attribute shall use entity
references of the form loc03_x.
Example:

…

5.2.4.1 language

language_code CDATA #REQUIRED
>
language: This describes the language of a textual element. The language_code attribute shall use entity
references of the form loc41_x.
Example:


5.2.5 direction



















direction_type CDATA #REQUIRED
>
direction: This describes a direction. The direction_type attribute shall use entity references of the form
loc02_x.
Example:


5.3 location_descriptions


location_descriptions: This is used to provide a human user with information on the location without any need
for co-ordinate references to a map.
More details on how these should be utilised can be found in ISO/TS 18234-6.
Example:

…
…
…

5.3.1 area_reference

country CDATA #REQUIRED
area_tree_version %intunti; #REQUIRED
>
8 © ISO 2006 – All rights reserved

area_reference: This describes an area in relation to all other possible areas within a single service.
Referencing is achieved through a defined area search tree. The country attribute shall use entity references
of the form loc40_x.
Example:

…

5.3.1.1 area_tree_entry

level %intunti; #REQUIRED
branch %intunli; #REQUIRED
predecessor_branch %intunli; #REQUIRED
>
area_tree_entry: This is one entry in the area_reference. Each area_tree_entry is associated with a unique
triplet of numbers, the area tree index. The area tree index consists of; tree level, branch (on this level) and
branch of predecessor level.
Example:

…
…
…

5.3.1.1.1 area_type














area_type CDATA #REQUIRED
>
area_type: This describes the type of an area. The area_type attribute shall use entity references of the form
loc06_x.
Example:


5.3.1.1.2 area_qualifier



























area_qualifier CDATA #REQUIRED
>
area_qualifier: This qualifies the area type. The area_qualifier attribute shall use entity references of the form
loc07_x.
Example:


5.3.1.1.3 area_descriptor

area_name %short_string; #REQUIRED
>
area_descriptor: This describes the area name.
Example:

…

5.3.2 network_description






10 © ISO 2006 – All rights reserved











































































































network_operator_descriptor)*)>
network_layer CDATA #REQUIRED
link_type CDATA #REQUIRED
>
network_description: This describes links in networks. The defined structure of the element permits filtering
and selection based, for example, on road types and numbers, rail link types and numbers, water link types,
flight link types and numbers, and even on segment names and directions.
The network_layer attribute shall use entity references of the form loc08_x. The link_type attribute should use
entity references of the form shown in Table 1, (if there is no link_type for the given network_layer then this
attribute should not be present):
Table 1
Network_layer link_type
loc01_0 “unknown”
loc01_1 “road network” loc09_x
loc01_2 “bus network” loc10_x
loc01_3 “metro rail network” loc11_x
loc01_4 “tram network” loc12_x
loc01_5 “rail network” loc13_x
loc01_6 “telecabin” loc14_x
loc01_7 “water transport network” loc15_x
loc01_8 “airway network” loc16_x

12 © ISO 2006 – All rights reserved

Example:


5.3.2.1 link_number

link_number %intunti; #REQUIRED
>
link_number: This describes the number of a link.

Example:


5.3.2.2 link_number_suffix

character CDATA #REQUIRED
>
link_number_suffix: This describes a single character suffix for a link number.

Example:


5.3.2.3 segment_name


segment_name: This describes a segment of a link between two points.

Example:

…
…

5.3.2.4 from_descriptor

from_name %short_string; #REQUIRED
>
from_descriptor: This describes the name of a source location in a link segment.

Example:

…

5.3.2.5 to_descriptor

to_name %short_string; #REQUIRED
>
to_descriptor: This describes the name of a destination location in a link segment.

Example:

…

5.3.2.6 link_descriptor

link_name %short_string; #REQUIRED
>
link_descriptor: This describes the name of a link.

Example:

…

5.3.2.7 network_operator_descriptor

network_operator_name %short_string; #REQUIRED
>
network_operator_descriptor: This describes the name of a network operator.

Example:

…


5.3.3 node_description






node_type CDATA #REQUIRED
>
14 © ISO 2006 – All rights reserved

node_description: This describes single points or complex nodes, which are part of a network. The node_type
attribute shall use entity references of the form loc17_x.
Example:
…
…
…
…
…
…

5.3.3.1 node_descriptor

node_name %short_string; #REQUIRED
>
node_descriptor: This describes the name of a node.

Example:

…

5.3.3.2 reference_object
explicit_proximity_glue | intermediate_glue | orientation | distance | road_object | building | geographical_site |
sightseeing_attraction | reference_object_descriptor)*)>

reference_object: This describes a location by in a language-independent, descriptive manner. It does this by
referencing it to known locations or landmarks.
Example:

…
…
…
…
…
…
…
…
…
…
…
…

5.3.3.2.1 fuzzy_directionality_glue


























fuzzy_directionality_glue CDATA #REQUIRED
>
fuzzy_directionality_glue: This approximately describes the direction of an object in relation to another. The
fuzzy_directionality_glue attribute shall use entity references of the form loc18_x.
Example:


5.3.3.2.2 explicit_directionality_glue








explicit_directionality_glue CDATA #REQUIRED
>
explicit_directionality_glue: This explicitly describes the direction of an object in relation to another. The
explicit_directionality_glue attribute shall use entity references of the form loc19_x.
Example:


5.3.3.2.3 fuzzy_proximity_glue







16 © ISO 2006 – All rights reserved




fuzzy_proximity_glue CDATA #REQUIRED
>
fuzzy_proximity_glue: This approximately describes the proximity of an object to another. The
fuzzy_proximity_glue attribute shall use entity references of the form loc20_x.
Example:


5.3.3.2.4 explicit_proximity_glue









explicit_proximity_glue CDATA #REQUIRED
>
explicit_proximity_glue: This explicitly describes the proximity of an object to another. The
explicit_proximity_glue attribute shall use entity references of the form loc21_x.
Example:


5.3.3.2.5 intermediate_glue










intermediate_glue CDATA #REQUIRED
>
intermediate_glue: This describes the location of an object relative to another. The intermediate_glue attribute
shall use entity references of the form loc22_x.
Example:


5.3.3.2.6 orientation















orientation CDATA #REQUIRED
>
orientation: This describes an orientation or direction. The orientation attribute shall use entity references of
the form loc27_x.
Example:


5.3.3.2.7 distance

metres %numag; #REQUIRED
>
distance: This describes a distance in metres.

Example:

5.3.3.2.8 road_object









...