OpenLegislation

Annex I

United Kingdom

Original text. Later amendments are not shown.

Point 1.3 of Part 1 of the Schengen consultation network (technical specifications) is replaced by the following:

‘1.3.

DEFINING MESSAGE CHARACTERISTICS

For every message to be sent via the network, the following structural characteristics should be met:

  • The ‘From’ item of the message contains the senders applications address.

    For example:

    From: [email protected]

  • The ‘To’ item of the message contains the recipients application address.

    For example:

    To: [email protected]

    Implementation tip: be aware that it is possible to make use of multiple recipients delimited by commas. But if the application does so, on received FORMs R it has to determine the FORM R sender, because it will receive references to identical message-identifiers (heading ‘000’). Sending separate messages to each partner State with different ‘000’ headings is less confusing.

  • The ‘Subject’ item of the message contains a ‘file number’ and a full stop (‘.’) followed by the form-type identifier (Letter: ‘A’, ‘B’, ‘C’, ‘E’, ‘F’, ‘G’, ‘H’ or ‘R’). For the respective forms, the ‘file number’ equals the content of its heading: ‘001’ in FORM ‘A’, ‘B’, ‘C’, ‘F’, ‘G’, ‘H’ and the content of heading ‘048’ in a FORM E. For heading definitions see 2.1.2.

    Examples:

    • Subject:AUT0000010106AJKT00.B

    • Subject:FRA2007022457471104.E

    If a Member State receives a message with an incorrectly formulated subject, it has to discard that message without processing it. If the problem persists it has to be solved bilaterally by the technical staff.

  • The mail body has to be structured as follows:

    • ‘text/plain’ is used as the ‘Media Type’ or ‘Mime Type’ see RFC2046 (http://tools.ietf.org/html/rfc2046),

    • ‘ISO-8859-15’ is used as the ‘charset’.

  • Hence in the ‘Header’ of every mail, the following line will appear:

    Content-Type: text/plain; charset = ISO-8859-15.’.