SIST-TS CEN/TS 14014:2015

Postal services - Hybrid mail - XML definition of encapsulation of letters for automated postal handling

The purpose of this Technical Specification is to define the syntax rules for a data stream for the submission of printing data to a Hybrid Mail operator or between Hybrid Mail operators. The Technical Specification defines a XML Schema Definition (XSD) describing the data stream.
The description is based upon the XML (eXtended Mark-up Language) definition of rules and semantics for defining an XSD. The purpose of this is to offer a generalised syntax description that can provide seamless integration with a number of existing applications generating data that is liable to be forwarded to or from a Hybrid Mail operator.
The use of an XSD will ensure that the documents confirm to the standard defined and that the output has the correct syntax. Software manufacturers can use an XSD to program applications that will produce correct outputs.
This Technical Specification defines the syntax for creating a data stream that will eventually be converted into a deliverable. The overall object (a batch) can be divided into one or more objects that again can be divided into objects. The hierarchy includes bundles that contain a common part and letters. Each object has a number of characteristics attached to it.
This diagram shows the structure of a HML (Hybrid Mail Language) document: each letter is self-contained (contains all the necessary information to be delivered on a certain destination).
Each letter can have one contact. Each contact can have multiple alternatives for delivery.
This Technical Specification does not define the specific services offered by local operators (Hybrid Mail operators).
This Technical Specification does not define the communication method used. It does only define the format of Hybrid Mail as such.

Postalische Dienstleistungen - Hybrid mail - XML Definition für die Verkapselung von Briefen zur automatischen Postbearbeitung

Services postaux - Courrier hybride - Définition XML de l’encapsulation des lettres pour un traitement postal automatique

Poštne storitve - Hibridna pošta - Definicija oblike dokumenta XML za stranke/uporabnike pri ponudniku: skupno uporabni seznam označb

General Information

• Status: Published
• Public Enquiry End Date: 04-Feb-2015
• Publication Date: 16-Jun-2015
• ICS: 03.240 - Postal services
• ICS: 35.240.69 - IT applications in postal services
• Technical Committee: I13 - Imaginarni 13
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 15-May-2015
• Due Date: 20-Jul-2015
• Completion Date: 17-Jun-2015
• Ref Project: CEN/TS 14014:2015 - Postal services - Hybrid mail - XML definition of encapsulation of letters for automated postal handling

Relations

• Replaces: SIST-TS CEN/TS 14014:2007 - Postal services - Hybrid Mail - XML definition of encapsulation of letters for automated postal handling
• Effective Date: 01-Jul-2015
• Replaces: SIST-TS CEN/TS 14014:2007 - Postal services - Hybrid Mail - XML definition of encapsulation of letters for automated postal handling
• Effective Date: 08-Jun-2022

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 14014:2015
01-julij-2015
1DGRPHãþD
SIST-TS CEN/TS 14014:2007
3RãWQHVWRULWYH+LEULGQDSRãWD'HILQLFLMDREOLNHGRNXPHQWD;0/]D
VWUDQNHXSRUDEQLNHSULSRQXGQLNXVNXSQRXSRUDEQLVH]QDPR]QDþE
Postal services - Hybrid mail - XML definition of encapsulation of letters for automated
postal handling
Postalische Dienstleistungen - Hybrid mail - XML Definition für die Verkapselung von
Briefen zur automatischen Postbearbeitung
Services postaux - Courrier hybride - Définition XML de l’encapsulation des lettres pour
un traitement postal automatique
Ta slovenski standard je istoveten z: CEN/TS 14014:2015
ICS:
03.240 Poštne storitve Postal services
35.240.99 8SRUDEQLãNHUHãLWYH,7QD IT applications in other fields
GUXJLKSRGURþMLK
SIST-TS CEN/TS 14014:2015 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TS CEN/TS 14014:2015

---------------------- Page: 2 ----------------------

SIST-TS CEN/TS 14014:2015

TECHNICAL SPECIFICATION
CEN/TS 14014

SPÉCIFICATION TECHNIQUE

TECHNISCHE SPEZIFIKATION
May 2015
ICS 35.240.99; 03.240 Supersedes CEN/TS 14014:2006
English Version
Postal services - Hybrid mail - XML definition of encapsulation of
letters for automated postal handling
Services postaux - Courrier hybride - Définition XML de
l'encapsulation des lettres pour un traitement postal
automatisé
This Technical Specification (CEN/TS) was approved by CEN on 14 March 2015 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their
comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available
promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)
until the final decision about the possible conversion of the CEN/TS into an EN is reached.

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





EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 14014:2015 E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
Contents Page
Foreword .5
Introduction .6
1 Scope .7
2 Normative references .8
3 Terms and definitions .8
4 Symbols and abbreviated terms .9
5 Meta-syntax .9
6 Definition . 10
6.1 General . 10
6.2 General rule for HML documents . 12
6.2.1 General . 12
6.2.2 Comments . 12
6.2.3 Processing Instructions . 12
6.2.4 Name space . 12
6.2.5 Hybrid Mail Language (HML) Extensions: . 12
6.3 General elements . 12
6.3.1 General . 12
6.3.2 acknowledgement . 13
6.3.3 addressee . 13
6.3.4 batchname . 13
6.3.5 binary_data . 13
6.3.6 bundle . 13
6.3.7 common . 13
6.3.8 common_data . 13
6.3.9 contact . 13
6.3.10 declaration . 13
6.3.11 external_ref . 13
6.3.12 generation_application . 13
6.3.13 generation_date . 14
6.3.14 hml . 14
6.3.15 internal_ref . 14
6.3.16 letter . 14
6.3.17 letter_data . 14
6.3.18 mailee . 14
6.3.19 processing . 14
6.3.20 sender_id . 14
6.3.21 track_history . 14
Annex A (informative) List of elements . 15
A.1 Elements . 15
A.2 Complex types . 16
Annex B (informative) HML description . 17
B.1 Elements . 17
B.1.1 acknowledgement . 17
2

---------------------- Page: 4 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
B.1.2 addressee . 18
B.1.3 batchname . 18
B.1.4 binary_data . 19
B.1.5 bundle . 20
B.1.6 common . 21
B.1.7 common_data . 22
B.1.8 contact . 23
B.1.9 declaration . 24
B.1.10 external_ref . 24
B.1.11 generation_application . 25
B.1.12 generation_date . 26
B.1.13 hml . 26
B.1.14 internal_ref . 27
B.1.15 letter . 28
B.1.16 letter_data. 29
B.1.17 mailee . 30
B.1.18 processing . 31
B.1.19 sender_id . 32
B.1.20 track_history . 32
B.2 Complex types . 33
B.2.1 acknowledgementType . 33
B.2.2 addresseeType . 34
B.2.3 binary_dataType . 35
B.2.4 bundleType . 35
B.2.5 common_dataType . 36
B.2.6 commonType . 37
B.2.7 contactType . 38
B.2.8 data_type . 39
B.2.9 declarationType . 40
B.2.10 external_refType . 41
B.2.11 hmlType . 41
B.2.12 internal_refType . 42
B.2.13 letterType. 43
B.2.14 maileeType . 44
B.2.15 processingType . 45
B.2.16 restricted_dataType . 45
B.2.17 track_historyType . 46
Annex C (informative) Differences between this document and CEN/TS 14014:2006 . 47
3

---------------------- Page: 5 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
Annex D (informative) HML definition, copy of the HML XSD. 48
Bibliography . 58

4

---------------------- Page: 6 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
Foreword
This document (CEN/TS 14014:2015) has been prepared by Technical Committee CEN/TC 331 “Postal
services”, the secretariat of which is held by NEN.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
This document supersedes CEN/TS 14014:2006. An explanation of the differences between this Technical
Specification and CEN/TS 14014:2006 is given in Annex C.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus,
Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany,
Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.
5

---------------------- Page: 7 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
Introduction
Hybrid Mail is the technology whereby input in one communication medium is converted for delivery on
another communication medium according to the sender’s instructions and/or the recipient’s capabilities. The
typical application of Hybrid Mail is to provide a Hybrid Mail operator with printing data as well as processing
and delivery instructions, and request the operator to secure the print, enveloping and delivery of the physical
letters. Hybrid Mail operators may also exchange data.
The transfer of data to a Hybrid Mail operator or between Hybrid Mail operators requires that the printing data
be linked to a number of data items related to the management, production, finishing, etc. of the data to be
printed. Such data items secure that all relevant information is accompanying the printing data. Also it will
enable the Hybrid Mail operator to automate his processes with customers and other Hybrid Mail operators.
There is a need for a standardised yet flexible way to present the data to the Hybrid Mail operator or to
exchange data between Hybrid Mail operators. This will enable customers and Hybrid Mail operators to have
a seamless exchange of information. It will allow makers of applications for document creation (letters,
marketing mailing, etc.) and output management from other applications (accounting systems, production
management, etc.), to add here to the same data presentment and to offer the seamless data interchange.
6

---------------------- Page: 8 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
1 Scope
The purpose of this Technical Specification is to define the syntax rules for a data stream for the submission
of printing data to a Hybrid Mail operator or between Hybrid Mail operators. The Technical Specification
defines an XML Schema Definition (XSD) describing the data stream.
The description is based upon the XML (eXtended Mark-up Language) definition of rules and semantics for
defining an XSD. The purpose of this is to offer a generalised syntax description that can provide seamless
integration with a number of existing applications generating data that is liable to be forwarded to or from a
Hybrid Mail operator.
The use of an XSD will ensure that the documents confirm to the standard defined and that the output has the
correct syntax. Software manufacturers can use an XSD to program applications that will produce “correct”
outputs.
This Technical Specification defines the syntax for creating a data stream that will eventually be converted into
a deliverable. The overall object (a batch) can be divided into one or more objects that again can be divided
into objects. The hierarchy includes bundles that contain a common part and letters. Each object has a
number of characteristics attached to it.
This diagram shows the structure of a HML (Hybrid Mail Language) document: each letter is self-contained
(contains all the necessary information to be delivered on a certain destination).

Figure 1 — Structure of a HML (Hybrid Mail Language)
7

---------------------- Page: 9 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
Each letter can have one contact. Each contact can have multiple alternatives for delivery.
This Technical Specification does not define the specific services offered by local operators (Hybrid Mail
operators).
This Technical Specification does not define the communication method used. It does only define the format
of Hybrid Mail as such.
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.
ISO/IEC 10646, Information technology — Universal Coded Character Set (UCS)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
mailbag
data structure that contains bundles as well as administrative and other data common to all bundles
Note 1 to entry: One HML document will contain one mailbag. A mailbag may contain one or several bundles.
3.2
bundle
data structure that contains letters that are processed as a group as well as administrative and other data
common to these letters. A bundle is equivalent with a batch. Usually a sender is sending a mailbag with only
one batch
Note 1 to entry: A bundle may contain one or more letters.
3.3
letter
data structure that contains the data to be rendered as one integral piece of information which is to be
delivered to one recipient in physical or electronic format
3.4
contact
data structure that contains delivery information for letters
Note 1 to entry: The contact may be relevant to only one letter or may be shared between several letters.
3.5
target language
language to be defined in this document and to be later used for writing documents, and the result of a
possible translation of existing data structure(s). In the present document the target language is HML
Note 1 to entry: Clause 4 gives further description of the syntax of the target language.
8

---------------------- Page: 10 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
4 Symbols and abbreviated terms
For the purposes of this Technical Specification, the following symbols and abbreviated terms apply.
AFP Advance Function Presentation – PDL defined by IBM
HML Hybrid Mail Language
IEC
International Electrotechnical Commission http://www.iec.ch
ISO International Organization for Standardization
PCL
Print Control Language – PDL defined by HP
PDF Portable Document Format – PDL defined by Adobe
PDL Print Description Language
PI Processing Instruction – part of the XML standard
SGML Standard Generalized Mark-up Language
UCS Universal Coded Character set
URL
Universal Resource Locator
W3C World Wide Web Consortium – see http://www.w3.org/
XML eXtensible Mark-up Language
XSD XML Schema Definition
XSL eXtensible Stylesheet Language
5 Meta-syntax
This clause introduces a syntactic notation, later used in this Technical Specification. The notation is adopted
to define the syntactic rules of the target language: in this sense, the notation is a meta-syntax for the syntax
of the target language.
HML is based on XML version 1.1 as described in [XML-2006]. This is a subset of Standard Generalized Mark
up Language (SGML) as defined in ISO 8879.
For the sake of generality, in the following the term target language will be used for specifying the language to
be defined and to be later used for writing documents.
In this Technical Specification the target language is HML.
Syntactic rules of the target language are defined by means of syntactic clauses, classified as either element
declarations, attribute list declarations or comments. In the following, the first two of these syntactic clauses
will be described in detail. Here, only their abstract characteristics are introduced.
Element declarations define elements, which are logical parts of the documents.
Elements may contain other elements, to be considered as sub-parts of the first ones. To describe this
relationship among elements, element declarations can define elements in terms of other elements.
The whole document itself is considered as an element, and is described by an element declaration: this
element is the unique root, which all the other elements start from.
On the other side, elements not further subdivided in parts are simply streams of characters allowed in the
documents. They are defined as well by element declarations.
9

---------------------- Page: 11 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
In this way, element declarations express the inner structure of documents: this structure can be easily
reconstructed by going through the chain of element declarations, starting from the one that declares the root
element.
An element declaration is defined by the following syntactical construction:


 
 

where element_name is the name of the element defined and contentspec is the list of elements which
constitute the set of elements which defines the named element.
Attribute list declarations define characteristics of elements.
In describing the notation, some rules will be followed.
In the syntactic clauses:
— syntactic items independent of the particular target language (i.e. keywords, symbols and so on) are
written in regular font (that is, without using bold or italic forms);
— identifiers used as placeholders for other things to be later made actual in the syntax of the target
language (as for example syntactic items dependent of the particular target language) are written in italic
font.
In the examples:
— syntactic items independent of the particular target language (i.e. keywords, symbols and so on) are
written in regular font (that is, without using bold or italic forms);
— syntactic items dependent of the particular target language (as for example constant names of the target
language) are written in italic font.
An attribute declaration is defined by the following syntactical construction:
default="default_decl"/>
where the element_name identifies which element the attributes belong to, attribute_name is the name of the
attribute, attribute_type is the type of the attribute and default_decl informs whether the attribute has a default
value that is used if the attribute is not present.
For a more detailed description of the syntax of XML please see [XML-2006]
6 Definition
6.1 General
In this clause, syntactic rules of HML are given in XML. They completely define the concrete syntax of HML.
The structure of the HML XSD is illustrated in Figure 2:
10

---------------------- Page: 12 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)

Figure 2 — Illustration of the structure of the HML XSD
11

---------------------- Page: 13 ----------------------

SIST-TS CEN/TS 14014:2015
CEN/TS 14014:2015 (E)
6.2 General rule for HML documents
6.2.1 General
HML is based on eXtensible Markup Language (XML) version 1.1 as described in [XML-2006]. This is a
subset of Standard Generalized Markup Language (SGML) as defined in ISO 8879.
As HML is specified as an XSD, the general rules for XML compliant XSD’s apply to HML. However this
chapter specifies how a compliant HML document shall be processed when using the following components
from the XML standard, which are not unique to HML:
— Comments
— Processing Instructions
— Name Spaces
6.2.2 Comments
Comment ::= ''
A conforming HML system shall make the comments in a conforming HML document available to external
processors on request.
6.2.3 Processing Instructions
PI ::= '' Char*)))? '?>'
PITarget ::= Name - (('X' | 'x') ('M' | 'm') ('L' | 'l'))
A conforming HML system shall ensure that the processing instructions are presented to the relevant
processor if this is available. This can either be pre- or postprocessor. Otherwise the processing instructions
shall be ignored.
6.2.4 Name space
The use of name spaces in HML shall comply with the W3C recommendations – see [XML-names-2004]. The
processing of names from other name spaces than the HML name space shall be accepted and either be
handled by the HML system or alternatively by a pre- or postprocessor.
6.2.5 Hybrid Mail Language (HML) Extensions:
In the future new equipment shall be controllable in Hybrid Mail operations. To include new features to make
use of this equipment and to fulfil the Hybrid Mail Language it is allowed to include new elements.
The way of doing this is make use of the defined way as mentioned in Chapter 2.8 of the [XML-2004]: the
document type declaration can point to an external subset containing mark-up declarations.
6.3 General elements
6.3.1 Gen
...