root element unique reference number identifying a single message. An xml-file my contain more than one message. original sending, update or cancelation of an existing message choice Y = Yes / N = No common carrier The "gross weight" of the identified equipment The tare weight of the identified equipment Shippers Own Indicator To identify size and type of the equipment Seal identifier Name of the seal issuer Customs Declaration Reference Number Carrier Identification ID Unique Identifier of a location/party Location Identification ID Location Gerneral - Schuppencode/Freilagerfläche Detail Location Code 01 e.g. container block Name identifying a vessel Condition: In case of sea mode of transport this data element should be completed with the identification of the vessel according to Lloyd's Register of Shipping (LRS). Radio Call Sign (RCS) for the vessel Location on a vessel where units can be stowed. The following formats for Stowage cells are recommended: container vessels as: Bay/Row/Tier in format: BBBRRTT or feeder vessels as: Hatch/Row/Tier in format: HHHRRTT. If Bay/Hatch number is less than 3 characters it must be filled with leading zeros, e.g. "0340210". Information Loading Status Code specifying the dangerous goods regulation Number of applicable Amendment to the specific regulation (e.g. "29" for Amendment No. 29); may be completed during a transition period in which two Amendments are valid Dangerous goods transport certificate type Dangerous Goods Transport Certificate Number Dangerous goods transport certificate additional remarks values I, II or III - corresponding to the dangerous goods class Recogniced chemical or biological name(s) for generic or "not otherwise specified" (N.O.S.) proper shipping names Placard-No. 13 or 15 Marine pollutant mark; values " " or "MP" ("MP" can be stated more precisely by "P" or "PP") Hazard Identification number shown on the orange-coloured plate Emergency schedule number (only two 3-byte numbers used actually) Emergency schedule number for the dangerous good class consisting of 2 parts e.g FireSchedule: "F-A" SpillageSchedule: "S-B" Indicator for dangerous goods packed in limited quantities Indicator for dangerous goods packed in excepted quantities Indicator for empty and uncleaned means of containment Indicator for transport of dangerous goods as waste Indicator for use of salvage package (means "Bergungsverpackung") Number of packages Outer type of package, coded according to specified code lists (e.g. UN/ECE Recommendation No. 21 Annex V or VI, Orange Book section 9.4) Description of the form in which goods are presented Packing Instruction, coded Number and type of packages gross weight, net weight, net weight explosive material for class 1 WeightUnit: allowed KGM Kilogram, GRM gram or TNE (Metric) Tonne signed (+/-) temperature of the flash point unit of the flash point temperature only for class 7 (radioactive) Radioactive Category Radioactive Radionuclides Radioactive MaxActivity ActivityValue Radioactive MaxActivity ActivityUnit Radioactive Transport Index Radioactive Criticality Safety Index Radioactive Package Radioactive Exclusive Use Indicator earliest date the safety valve can be opened - relevant for supercooled liquid gasses (class 2) Format YYYY-MM-DD WGK-code: 0 = not assigned, 1 = light marine pollutant, 2 = marine pollutant, 3 = extreme marine pollutant Four-category pollution categorization system of MARPOL Annex II "Regulations for the control of pollution by noxious liquid substances in bulk"; values "X", "Y", "Z", " "; for maritime transport only Additional information concerning the dangerous good Description of last loaded dangerous good (UN-Number, Proper Shipping Name, Class, SubRisks, PackingGroup; e.g. "UN 1098 ALLYLALCOHOL, 6.1(3), I") Additional information reqired in accordance with special provisions, certain classes, special transport conditions, ... (e.g. "Carriage in accordance with 2.2.52.1.9") Location of a branch office. UN/Locode; e.g. the location of the user's branch office. If there is no UN/LoCode available for this place, alternatively the name can be set. Communication data, e. g. the message's creation time or sender, recipient Up to 11 entries can be sent: SENDER - mandatory with DAKOSY-code RECIPIENT - mandatory with DAKOSY-Code. Maximum of nine entries is possible. EDI_PROVIDER Date and time of message creation. Format : 1999-05-31T13:20:00 Use local time. Value will be read "as it is". Please do not send an offset from the UTC. plain text without validation. Either phone number or e-mail address must be filled if the user-element is transmitted. Meta information for each message. Contains information concerning transaction type, communication parties etc. Specifies the transaction type (GM01, AB01 etc.). Only one transaction per file is allowed. Different types must be sent in separate files. Name of the application that built the message. unique reference per physical xml-file 0 - false (default); 1- true; transmission for test purpose Number of messages (elements) that are collected in the transmitted file. Code identifying the participant Alias code. Describes how the participant is identified in a system, e.g. DAK as DAKOSY-code. Other identifiers are not specified yet. Code identifying the participant just for informal use Needs only to be set if required by the specified role. Desribes the particpant's communication part as the message's sender, it's recipient etc. Required entries: RECIPIENT SENDER EDI_PROVIDER name of the party who is responsible for the underlying scheme. Code defined by the provider for the specified transaction. Single type which is represented by this file. A Transaction identified by its code may contain several types identified by their type. This hierarchy is known from EDIFACT-messages where e. g. the transaction GM01 (code) consists of CUSCAR and APERAK (type). Version of message definition