1、July 2012 Translation by DIN-Sprachendienst.English price group 13No part of this translation may be reproduced without prior permission ofDIN Deutsches Institut fr Normung e. V., Berlin. Beuth Verlag GmbH, 10772 Berlin, Germany,has the exclusive right of sale for DIN Specifications.ICS 35.240.99The
2、re are various procedures for developing a DIN SPEC: This document has been developed in accordance with the PAS procedure.!$P“1924596www.din.deDDIN SPEC 91287Data interchange between information systems in civil hazardpreventionEnglish translation of DIN SPEC 91287:2012-07Datenaustausch zwischen In
3、formationssystemen in der zivilen GefahrenabwehrEnglische bersetzung von DIN SPEC 91287:2012-07change de donnes entre systmes dinformation sous civil danger prventionTraduction anglaise de DIN SPEC 91287:2012-07www.beuth.deDocument comprises 27 pagesIn case of doubt, the German-language original sha
4、ll be considered authoritative.01.14 DIN SPEC 91287:2012-07 2 A comma is used as the decimal marker. Contents Page Foreword . 3 Introduction 4 1 Scope . 4 2 Terms and definitions 5 3 Abbreviations 6 4 Requirements 6 4.1 General . 6 4.2 Message handling . 6 4.3 Message format. 6 5 Message . 7 5.1 Gen
5、eral information 7 5.2 Derivation of the Location data type. 7 5.3 Message header (machine-machine: Head) . 8 5.4 Message content (machine-machine: Content) . 8 5.4.1 General information 8 5.4.2 Initial event (machine-machine: StartEvent) 9 5.4.3 Situation (machine-machine: Situation) . 9 5.4.4 Situ
6、ation assessment (machine-machine: EstimatedSituation) 11 5.4.5 Procedure (machine-machine: Procedure) 13 5.5 Format 14 6 Information security . 20 Annex A (informative) Clarification of the context 21 Annex B (informative) XML examples 22 A.1 Initial event 22 A.2 Situation . 23 A.3 Situation assess
7、ment . 25 A.4 Procedure 25 Bibliography . 27 DIN SPEC 91287:2012-07 3 Foreword This DIN Specification was developed as part of the research project “Standardization Potential in the field of Protection of Transportation Infrastructures”. The project is sponsored by the German Federal Ministry of Edu
8、cation and Research as part of its “Research for Civil Security” program. The development of the document was coordinated by the authors named below, who are solely responsible for its content (in the original German-language version): Dipl.-Ing. Marco Pla, University of Paderborn, Department of Mec
9、hanical Engineering/Computer Application and Integration in Design and Planning Dipl.-Wirt.-Ing. Christian Lindemann, University of Paderborn, Department of Mechanical Engineering/Computer Application and Integration in Design and Planning The following individuals and companies took an active part
10、in developing the document: Dipl.-Geogr. Patrick Hasenfu, PSI Transcom GmbH Dr.-Ing. Haluk arlan, PSI Transcom GmbH Dipl.-Ing. (FH) Martina Kaster, VOMATEC International GmbH Dipl.-Inf. (BA) Silas Graffy, VOMATEC International GmbH The topic of this DIN Specification is not the subject of a German,
11、European or international standardization project. DIN SPEC 91287:2012-07 4 Introduction This DIN Specification describes a data interchange format for information systems used in civil hazard prevention. It contains semantic and syntactic requirements for the exchange of data. The purpose of this d
12、ocument is to establish basic interoperability between information systems. The main focus of the document is to define a format for exchanging data between the information systems of different organizations which already communicate with each other. This format will provide developers of these syst
13、ems with a basis for designing a data interface to ensure a semantically unambiguous exchange of information. Because the actual information to be exchanged can be widely different in nature, this document deals with it on a comparatively high abstraction level. The document specifies general catego
14、ries which cover most of the information that is exchanged. These information categories will be added to in subsequent versions of the document. The DIN Specification is also intended to facilitate planning of implementation outlay, to reduce the number of proprietary interfaces and to speed up com
15、munication processes. The aim is to satisfy the external information requirements of legitimately interested organizations so that they can update their own operational pictures and make them more precise. It is not the objective of this specification to provide a shared operational picture in one c
16、entral information system. The established procedures in Germany for handling information in civil hazard prevention information systems have developed from existing federal or locally evolved structures. They very effectively reflect local conditions and are highly efficient. However, once systems
17、go beyond local borders, the requirement for more differentiated procedures creates obstacles to cooperation. This specification was developed to meet the challenge of allowing a standardized exchange of data while allowing different local procedures to be retained. The specification therefore consi
18、ders conditions in Germany and (potentially) the rest of Europe, as well as the resulting set-up and process organization, and the organization that is already established. To cater for the very different types of processes and messages exchanged in this context, this specification deliberately uses
19、 a flexible, semi-structured descriptive form rather than a more highly structured form. 1 Scope This DIN Specification defines the requirements for the structure and content of data exchanged between information and support systems in civil hazard prevention. This specification applies to the trans
20、fer of data between information and support systems in civil hazard prevention. It might be used, for example by fire services, rescue services, hospitals, police forces, technical emergency relief services, national investigative police agencies, national civil protection and disaster assistance ag
21、encies, other civil protection services, the armed forces, infrastructure operators, company fire brigades, veterinary offices, ministries and similar organizations. This DIN Specification applies to the development of an interface for communication between information systems (technically known as
22、machine-machine communication). It is aimed at software architects and developers who specify and implement interfaces to information and support systems outside their organizations. DIN SPEC 91287:2012-07 5 Knowledge of the basic concepts of software development and data communication is only neede
23、d for implementing in software, not for understanding this DIN Specification. The data structure defined in this DIN Specification facilitates the exchange of information between organizations for the purposes of notification, and of reporting and acknowledging information. It is explicitly not inte
24、nded to be used for time-critical alerting of emergency services. Information of a binding nature, such as issued orders, shall be transferred using the usual, established communication channels (for example by telephone). The specified data format can be used on all intervention levels of the organ
25、ization in civil hazard prevention. This DIN Specification does not standardize the exchange of information on resources. For this, please refer to the work done by the “XKatastrophenhilfe” project 1. Neither does the specification include the transfer of documents, images, videos or other digital d
26、ata. This is planned in a subsequent version. In its differentiation from other formats such as EDXL or TSO, this specification takes particular account of the requirements of state or civil organizations in Germany that are active in every field of civil hazard prevention. This DIN Specification is
27、 not intended as an implementation guideline, but defines the structure of the data to be transferred. The communication media, protocols and processes used for data transfer are not taken into account in this specification. 2 Terms and definitions For the purposes of this document, the terms and de
28、finitions in 2 apply. For reasons of clarity, the following terms are explained in more detail. 2.1 intervention levels ranges from normal operation to all escalation levels 2.2 information system IT system to support those organizations in charge of intervention in the assigned civil hazard prevent
29、ion NOTE This system receives information, evaluates it and forms the basis for coordinating connected services such as intervention control or crisis team support systems. 2.3 operational picture representation of the situation in regard of general conditions, the team itself and damage, used withi
30、n an information system in civil hazard prevention 2.4 machine-machine communication exchange of information between two computers 2.5 human-machine communication exchange of information between human users and computers 2.6 message information exchanged between two participating information systems
31、 NOTE The information is exchanged using a defined format. DIN SPEC 91287:2012-07 6 2.7 civil hazard prevention operations to combat non-military hazards, in which many different organizations co-operate EXAMPLE Non-military hazards include events such as natural disasters, accidents and fires. 3 Ab
32、breviations EDXL Emergency Data Exchange Language ETRS89 European Terrestrial Reference System 1989 POI Point of interest TSO Tactical situation object UFT-8 8-bit Universal Character Set Transformation Format UUID Universally unique identifier XML Extensible Markup Language 4 Requirements 4.1 Gener
33、al The requirements described in this clause apply to all information listed in clause 5 and are to be fulfilled by each communication partner. Only basic requirements for communication are defined; the detailed design of communication is not part of this DIN Specification. The format described in 5
34、.5 shall be used for exchanging data. 4.2 Message handling a) The information system should use its own data to compile the information to be exchanged. b) It shall be ensured that messages exchanged between the participating organizations are traceable. 4.3 Message format c) The content of the mess
35、age transferred via the interface shall be encoded in UTF-8 as described in 3 so as not to be subject to restrictions in the content of human-readable fields. d) Time stamp and time span information with time zones (referred to here as DateTime and Duration) shall be encoded according to ISO 8601. e
36、) Key data for unique identification (referred to here as UUID) shall be encoded according to 5. DIN SPEC 91287:2012-07 7 5 Message 5.1 General information Each transferred message contains exactly one section as described in 5.3 (Head) and exactly one section belonging to one of the information cat
37、egories in 5.4 (Content), in that order. In the following tables, a distinction is made between readability for humans (M), machines (C) or both (MC), so that the addressed target group is clear. The data types listed in the following tables are specified according to 3, 5 and ISO 639-3:2007. 5.2 De
38、rivation of the Location data type The complex Location data type, which is required in addition to the familiar data types, is derived in Table 1. Table 1 Structure of the Location data type Derived data types Description Elementary data type Readability M/C/MC Coordinate ETRS89 coordinate, represe
39、nted in the Universal Transverse Mercator system The notation uses the format of longitude zone, latitude zone, easting and northing Tuple of (Integer, Char, Double, Double) C Circle Georeferenced circular zone with a centre and a radius in m Tuple of (Coordinate, Double) C Polygon Georeferenced pol
40、ygon (the first and last geocoordinates are the same), which can also represent a chain of lines (open polygon) and a single line (a chain consisting of only one line, and thus only two geocoordinates) List of (Coordinate) C Georef Reference(s) defining the location of a collection of georeferenced
41、elements List of (Circle, Polygon) C GeorefText Reference defining the location in the form of descriptive text Includes post code, road, house number, district, state, country, point of interest (POI) Individual tuple elements can be optionally completed Tuple of (String, String, String, String, St
42、ring, String, String) M Location Reference defining the location Includes georeferenced elements as well as information described in text form such as post code, road, house number, district, state, country or POI Tuple of (Georef, GeorefText) MC DIN SPEC 91287:2012-07 8 5.3 Message header (machine-
43、machine: Head) The header of a message is described in Table 2. Table 2 Description of the message header Item Designation Description Data type Mandatory/ optional Readability M/C/MC 1 MessageID Unique identifier of the message The sender creates a new one for each message UUID M C 2 Sended Time of
44、 sending DateTime M C 3 SenderRole Role, function or system sending the message String M C 4 SenderOrg Organization sending the message String M C 5 ReceiverRole Role, function or system receiving the message String O C 6 ReceiverOrg Organization receiving the message String M C 7 MessageIDRef Refer
45、ence to previous message Using this field allows messages to be linked to each other UUID O C 8 OriginRef Establishment of an artificial reference system using origin codes Intended for human-to-human communication Example: each system optionally makes its own deployment number known to external sys
46、tems. String O C 9 Language Language of the message as per ISO 639-3:2007 String O C 5.4 Message content (machine-machine: Content) 5.4.1 General information There are various categories of information that can be transferred in a message. This categorization is based on grouping together semantical
47、ly related content. The different categories are each specified in the following subclauses. DIN SPEC 91287:2012-07 9 5.4.2 Initial event (machine-machine: StartEvent) The initial event to be transferred in a message is defined in more detail in Table 3. Table 3 Description of the initial event mess
48、age content Item Designation Description Data type Mandatory/ optional Readability M/C/MC 1 Subject Subject String M M 2 Occurrence Time of occurrence of the event DateTime O C 3 Description Description of the initial event String O M 4 Cause Description of the cause String O M 5 EventLocation Reference defining the location Refers to the description of the initial event in machine-readable form and using human-readable categories such as post code, road, house number, district, state, cou
