Versionsdatum dieses Schemas Rootelement Timestamp of the creation of the CIM in the host system/banking server. The CIMTmStmp is only relevant for requests including a DateRange element. In this case all CIMs shall be transmitted whose time stamp lies within the requested DateRange and which are still valid at the time of the request. The validity period must be disclosed to the EBICS-server by the originator of the CIM. Unique identification of the CIM according to RFC4122 Universally Unique Identifier (UUID). Headline in the form of CDATA. The headline shall be presented by the client with the attributes "bold" and "arial 14". HTML-tags are not allowed in the headline. Message-body in the form of CDATA. The maximum length of the HTML text is 1680 characters. Only the follwoing HTML tags are allowed: o paragraph control: paragraph (p), line break (br), preformatted text (pre) o lists: list item (li), unordered list (ul), ordered list (ol) o references: internal and external links (a href=) o font-attributes: bold (b), italic (i), underscored (u), strikethrough (s), subscripted (sub), superscripted (sup) o layout: (font) with the attributes "color", "face" and "size" Shorthand for empty tags is allowed. All other tags shall be ignored by the client. Only if a CIM request message was received from the client one or more CIMs will be downloaded in response. If the CIM request message did not include a DateRange element all current CIMs which were not sent to the requesting client previously will be downloaded. (The logic is the same as in the case of account-informations.) Unique identification of the message. Structure: digits 1 to 16 timestamp in the format YYYYMMDDHHMMSShh plus 4 mandatory random numbers and up to 15 additional random numbers optionally Timestamp of the creation of the message in the EBICS Server.