DIN CEN/TS 15873-2009 邮电业.开放标准接口.OCR/VCS词典生成用地址数据文件格式 英文版 CEN/TS 15873:2009

标准号：DIN CEN/TS 15873-2009
中文标准名称：邮电业.开放标准接口.OCR/VCS词典生成用地址数据文件格式 英文版 CEN/TS 15873:2009
英文标准名称：Postal Services - Open Standard Interface - Address Data File Format for OCR/VCS Dictionary Generation; English version CEN/TS 15873:2009
标准类型：M80
发布日期：1999/12/31 12:00:00
实施日期：1999/12/31 12:00:00
中国标准分类号：M80
国际标准分类号：03.240;35.240.60
适用范围：This document defines a file format for the generation of postal address directories. It is designed to hold allinformation necessary to support address reading software including data required for forwarding applications.In typical postal automation systems these files will be processed by directory generation software whichcreates application specific Ioadable data. This data -- usually referred to as operational directory isheavily compressed and contains access tables tailored for the specific reading software.Not in the scope of this document are topics external to file like compression, checksums, the interface fortransmission to the supplier, modification permissions, error handling on inconsistent data and undo inupdates PurposeThe format has been designed with the following requirements in mind: must be able to hold the following data: addresses composed of address components (including aliases and range-data); person and organization names; address codes typically used as sort codes; links between addresses e.g. for use in forwarding; should not restrict character encoding; easily customizable for specific applications; should allow complete as well as incremental updates, i.e. change-only data; it must be possible to split data in multiple flies for better handling.The ideas behind this format are as follows: The format is based on XML The basic XML structure is general, Project (the term project is used throughout this document to describe a specific application such as address data for a specific country or postal organization) specifics are coded as attributes, This should make it easier to build project independent parsers and tools, Address data can be structured hierarchically, An address component appearing in a lot of addresses shall be written once as parent node in all addresses it is used in the XML address tree, Beyond the pure address data, there are general as well as optional project specific attributes on the level of address components and string parts. In favour of faster parser execution and smaller file sizes the names of XML elements appearhrg very often are short strings. Semantics are defined only in a basic manner and have to be completed in the project specific tailoring process. E.g. a street without numbers in the data may be interpreted as a street which has no numbers, or where all numbers are valid. Due to this users must be aware that the interoperability of this Technical Specification may be limited to be applied to the specific project.