This document is an excerpt from the EUR-Lex website
Document 01999L0037-20220324
Council Directive 1999/37/EC of 29 April 1999 on the registration documents for vehicles
Consolidated text: Council Directive 1999/37/EC of 29 April 1999 on the registration documents for vehicles
Council Directive 1999/37/EC of 29 April 1999 on the registration documents for vehicles
01999L0037 — EN — 24.03.2022 — 006.001
This text is meant purely as a documentation tool and has no legal effect. The Union's institutions do not assume any liability for its contents. The authentic versions of the relevant acts, including their preambles, are those published in the Official Journal of the European Union and available in EUR-Lex. Those official texts are directly accessible through the links embedded in this document
COUNCIL DIRECTIVE 1999/37/EC of 29 April 1999 on the registration documents for vehicles (OJ L 138 1.6.1999, p. 57) |
Amended by:
|
|
Official Journal |
||
No |
page |
date |
||
L 10 |
29 |
16.1.2004 |
||
L 363 |
344 |
20.12.2006 |
||
L 158 |
356 |
10.6.2013 |
||
DIRECTIVE 2014/46/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 3 April 2014 |
L 127 |
129 |
29.4.2014 |
|
DIRECTIVE (EU) 2022/362 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 24 February 2022 |
L 69 |
1 |
4.3.2022 |
Amended by:
L 236 |
33 |
23.9.2003 |
COUNCIL DIRECTIVE 1999/37/EC
of 29 April 1999
on the registration documents for vehicles
Article 1
This Directive shall apply to the vehicle registration documents issued by the Member States.
It shall not prejudice the right of Member States to use, for the temporary registration of vehicles, documents which may not meet the requirements of this Directive in every respect.
Article 2
For the purposes of this Directive:
‘vehicle’: shall mean any vehicle as defined in Article 2 of Council Directive 70/156/EEC of 6 February 1970 on the approximation of the laws of the Member States relating to the type-approval of motor vehicles and their trailers ( 1 ) and in Article 1 of Council Directive 92/61/EEC of 30 June 1992 relating to the type-approval of two or three-wheel motor vehicles ( 2 );
‘registration’: shall mean the administrative authorisation for the entry into service in road traffic of a vehicle, involving the identification of the latter and the issuing to it of a serial number, to be known as the registration number;
‘registration certificate’: shall mean the document which certifies that the vehicle is registered in a Member State;
‘holder of the registration certificate’: shall mean the person in whose name a vehicle is registered;
‘suspension’: means a limited period of time in which a vehicle is not authorised by a Member State to be used in road traffic following which – provided the reasons for suspension have ceased to apply – it may be authorised to be used again without involving a new process of registration;
‘cancellation of a registration’: means the cancellation of a Member State’s authorisation for a vehicle to be used in road traffic.
Article 3
Member States may authorise the services they appoint to this end, in particular those of the manufacturers, to fill in the technical parts of the registration certificate.
Member States shall record electronically data on all vehicles registered on their territory. Those data shall include:
all mandatory elements in accordance with point II.5 of Annex I as well as the elements of points II.6(J) and II.6(V.7) and (V.9) of that Annex, where the data are available;
other non-mandatory data listed in Annex I or data from the certificate of conformity as provided for in Directive 2007/46/EC of the European Parliament and of the Council ( 3 ), where possible;
the outcome of mandatory periodic roadworthiness tests in accordance with Directive 2014/45/EU of the European Parliament and of the Council ( 4 ) and the period of validity of the roadworthiness certificate.
The processing of personal data in the context of this Directive shall be carried out in accordance with Directives 95/46/EC ( 5 ) and 2002/58/EC ( 6 ) of the European Parliament and of the Council.
Article 3a
The suspension shall be effective until the vehicle has passed a new roadworthiness test. On successful completion of the roadworthiness test, the competent authority shall without delay re-authorise the use of the vehicle in road traffic. No new process of registration shall be necessary.
Member States or their competent authorities may adopt measures to facilitate the retesting of a vehicle the authorisation of which for use in road traffic has been suspended. Those measures may include the grant of permission to travel on public roads between a place of repair and a test centre for the purpose of a roadworthiness test.
Article 4
For the purposes of this Directive, the registration certificate issued by a Member State shall be recognised by the other Member States for the identification of the vehicle in international traffic or for its re-registration in another Member State.
Article 5
Where the registration certificate consists of Parts I and II, and Part II is missing, the competent authorities in the Member State where the new registration has been requested may decide, in exceptional cases, to re-register the vehicle, but only after having obtained confirmation, in writing or by electronic means, from the competent authorities in the Member State where the vehicle was previously registered, that the applicant is entitled to re-register the vehicle in another Member State.
Article 6
The Commission shall be empowered to adopt delegated acts in accordance with Article 7 in order to amend:
Article 7
Article 8
When Member States adopt these provisions, they shall contain a reference to this Directive or be accompanied by such reference at the time of their official publication. The methods of making such reference shall be laid down by Member States.
The Commission shall communicate to the Member States all the models for registration certificates used by the national administration.
Article 9
Member States shall assist one another in the implementation of this Directive. They may exchange information at bilateral or multilateral level in particular so as to check, before any registration of a vehicle, the latter’s legal status, where necessary in the Member State in which it was previously registered. Such checking may in particular involve the use of an electronic network, comprising data from national electronic databases to facilitate the exchange of information.
Article 10
This Directive shall enter into force on the day of its publication in the Official Journal of the European Communities.
Article 11
This Directive is addressed to the Member States.
ANNEX I
PART I OF THE REGISTRATION CERTIFICATE ( 8 )
I. |
This part may be implemented in either of two formats: as a paper document or as a smart card. The characteristics of the paper document version are specified in Chapter II and those of the smart card version in Chapter III. |
II. |
Specifications of Part I of the Registration Certificate in paper format
|
III. |
Specifications of Part I of the Registration Certificate in smart card format (Alternative to the specimen in paper format described in Chapter II)
III.1 Card format and data legible with the eye Being a microprocessor card, the chip card shall be designed in accordance with the standards mentioned in Chapter III.5. The data stored on the card should be legible with normal reading devices (such as for tachograph cards). Printed on the front and back of the card shall be at least the data specified in Chapters II.4 and II.5; these data shall be legible with the eye (minimum character height: 6 points) and printed on as follows. (Examples of possible lay-outs are presented in Figure 1 at the end of this section.) A. Basic imprint The basic data shall contain the following: Front
(a)
To the right of the chip location: in the language(s) of the Member State issuing the Registration Certificate
—
the words ‘European Community’;
—
the name of the Member State issuing the Registration Certificate;
—
the words ‘Part I of the Registration Certificate’, or, if the certificate consists of one part only, the words ‘Registration Certificate’ printed in large type;
—
another (e.g. previous national) designation of the equivalent document (optional);
—
the name of the competent authority (alternatively, also in the form of a personalisation imprint as per Letter B);
—
the unambiguous consecutive number of the document as used within the Member State (alternatively, also in the form of a personalisation imprint as per Letter B);
(b)
Above the chip location: the distinguishing mark of the Member State issuing the Registration Certificate, white in a blue rectangle and surrounded by twelve yellow stars:
(c)
Member States might consider adding, at the lower edge in small type and in their national language(s), the note: ‘This document should be produced to any authorised person requesting it.’
(d)
The basic colour of the card is green (Pantone 362); alternatively, a green-to-white transition is possible.
(e)
A symbol representing a wheel (see proposed lay-out in Fig.1) shall be printed within the printing area in the bottom left corner of the card front. In other respects, the provisions of Chapter III.13 shall apply. B. Personalisation imprint The personalisation imprint shall contain the following information: Front
(a)
the name of the competent authority — see also Letter Aa)
(b)
the name of the authority issuing the Registration Certificate (optional)
(c)
the unambiguous consecutive number of the document as used within the Member State — see also Letter Aa)
(d)
The following data from Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised Community codes:
Back The back shall bear at least the remaining data specified in Chapter II.5; in accordance with Chapter II.7, individual national codes may be added to the preceding harmonised Community codes. In detail, these data are:
Optionally, additional data from II.6 (with the harmonised codes) and II.7 may be added on the back of the card. C. Physical security features of the smart card The threats to the physical security of documents are:
—
Production of false cards: creating a new object which bears great resemblance to the document, either by making it from scratch or by copying an original document.
—
Material alteration: changing a property of an original document, e.g. modifying some of the data printed on the document.
The material used for Part I of the Registration Certificate shall be made secure against forgery by using at least three of the following techniques:
—
microprinting,
—
guilloche printing*,
—
iridescent printing,
—
laser engraving,
—
ultraviolet fluorescent ink,
—
inks with viewing angle — dependent colour*,
—
inks with temperature — dependent colour*,
—
custom holograms*,
—
variable laser images,
—
optical variable images.
Member States are free to introduce additional security features. As a basis, the techniques indicated with an asterisk are to be preferred as they enable the law enforcement officers to check the validity of the card without any special means.
III.2. Data storage and protection Preceded by the harmonised common codes (where appropriate, in connection with the individual codes of the Member States according to Chapter II.7), the following data shall or may be additionally stored on the card surface bearing the legible information as per Chapter III.1:
(A)
Data as per Chapters II.4 and II.5 All data specified in Chapters II.4 and II.5 shall be mandatorily stored on the card.
(B)
Other data as per Chapter II.6 Moreover, the Member States are free to store more data as per Chapter II.6, to the necessary extent.
(C)
Other data as per Chapter II.7 Optionally, additional information may be stored on the card. The data from the letters A and B is stored in two corresponding files with transparent structure (see ISO/IEC 7816-4). The Member States may specify the storage of data from Letter C according to their requirements. There are no read restrictions on these files. Write access to these files shall be restricted to the national competent authorities (and their authorised agencies) in the Member State issuing the smart card. Write access is permitted only after an asymmetric authentication with session key exchange for protecting the session between the vehicle registration card and a security module (e.g. a security module card) of the national competent authorities (or their authorised agencies). Thereby card verifiable certificates according to ISO/IEC 7816-8 are exchanged before the authentication process. The card verifiable certificates contain the corresponding public keys to be retrieved and to be used in the following authentication process. These certificates are signed by the national competent authorities and contain an authorisation object (certificate holder authorisation) according to ISO/IEC 7816-9 in order to encode role specific authorisation to the card. This role authorisation is related to the national competent authority (e.g. to update a data field). The corresponding public keys of the national competent authority are stored as trust anchor (root public key) in the card. The specification of the files and commands needed for the authentication process and the writing process is under the responsibility of the Member States. The security assurance has to be approved by common criteria evaluation according to EAL4+. The augmentations are as follows: 1. AVA_MSU.3 Analysis and testing for insecure states; 2. AVA_VLA.4 Highly resistant.
(D)
Verification data for authenticity of registration data The issuing authority calculates its electronic signature about the complete data of a file containing the data of the letter A or B and stores it in a related file. These signatures allow the authenticity of the stored data to be verified. The cards shall store the following data:
—
electronic signature of registration data related to letter A,
—
electronic signature of registration data related to letter B,
For verification of these electronic signatures the card shall store:
—
certificates of the issuing authority calculating the signatures about the data of letters A, B.
Electronic signatures and the certificates shall be readable without restriction. Write access to electronic signatures and certificates shall be restricted to the national competent authorities. III.3. Interface External contacts should be used for interfacing. A combination of external contacts with a transponder is optional. III.4. Storage capacity of the card The card shall have sufficient capacity to store the data mentioned in Chapter III.2. III.5. Standards The chip card and reading devices used shall comply with the following standards:
III.6. Technical Characteristics and Transmission Protocols The format shall be ID-1 (normal size, see ISO/IEC 7810). The card shall support transmission protocol T=1 in compliance with ISO/IEC 7816-3. Additionally other transmission protocols may be supported, e.g. T=0, USB or contactless protocols. For bit transmission the ‘direct convention’ shall be applied (see ISO/IEC 7816-3).
(A)
Supply voltage, programming voltage The card shall work with Vcc = 3V (+/0.3V) or with Vcc = 5V (+/0,5V). The card shall not require a programming voltage at pin C6.
(B)
Answer to reset The Information Field Size Card byte shall be presented at the ATR in character TA3. This value shall be at least ‘80h’ (=128 bytes).
(C)
Protocol parameter selection The support of Protocol parameter selection (PPS) according to ISO/IEC 7816-3 is mandatory. It is used for selecting T=1, if T=0 is additionally present in the card, and to negotiate the Fi/Di parameters for achieving higher transmission rates.
(D)
Transmission protocol T = 1 The support of chaining is mandatory. The following simplifications are allowed:
—
NAD Byte: not used (NAD should be set to ‘00’),
—
S-Block ABORT: not used,
—
S-Block VPP state error: not used.
The information field size device (IFSD) shall be indicated from the IFD immediately after ATR, i.e. the IFD shall transmit the S-Block IFS Request after ATR and the card shall send back S-Block IFS. The recommended value for IFSD is 254 bytes. III.7. Temperature range The registration certificate in smart card format shall properly function under all climatic conditions usually prevailing in the territories of the community and at least in the temperature range specified in ISO 7810. The cards shall be capable of operating correctly in the humidity range 10 % to 90 %. III.8. Physical lifetime If used in accordance with the environmental and electricity-related specifications, the card must function properly for a period of ten years. The material of the card must be chosen in such a way that this lifetime is ensured. III.9. Electrical characteristics During operation, the cards shall conform to Commission Directive 95/54/EC of 31 October 1995 ( 13 ), related to electromagnetic compatibility, and shall be protected against electrostatic discharges. III.10. File structure Table 1 lists the mandatory elementary files (EF) of the application DF (see ISO/IEC 7816-4) DF.Registration. All these files have a transparent structure. The access requirements are described in Chapter III.2. The file sizes are specified by the Member States according their requirements.
Table 1
III.11. Data structure The stored certificates are in the X.509v3 format according ISO/IEC 9594-8. The electronic signatures are stored transparently. The registration data is stored as BER-TLV data objects (see ISO/IEC 7816-4) in the corresponding elementary files. The value fields are coded as ASCII character as defined by ISO/IEC 8824-1, the values ‘C0’-‘FF’ are defined by ISO/IEC 8859-1 (Latin1 character set), ISO/IEC 8859-7 (Greek character set) or ISO/IEC 8859-5 (Cyrillic character set). The format of dates is YYYYMMDD. Table 2 lists the Tags identifying the data objects corresponding to the registration data of the Chapters II.4 and II.5 together with additional data from Chapter III.1. Unless otherwise stated, the data objects listed in Table 2 are mandatory. Optional data objects may be omitted. The column of the Tag indicates the level of nesting.
Table 2
Table 3 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.6. The data objects listed in Table 3 are optional.
Table 3
Structure and format of the data according Chapter II.7 are specified by the Member States. III.12. Reading the registration data A. Application selection The application ‘Vehicle Registration’ shall be selectable by a SELECT DF (by name, see ISO/IEC 7816-4) with its application identifier (AID). The AID value is requested from a laboratory selected by the European Commission. B. Reading data from files The files corresponding to Chapter II, Letters A, B and D, shall be selectable by SELECT (see ISO/IEC 7816-4) with the command parameters P1 set to ‘02’, P2 set to ‘04’ and the command data field containing the file identifier (see Chapter X, Table 1). The returned FCP template contains the file size which can be useful for reading these files. These files shall be readable with READ BINARY (see ISO/IEC 7816-4) with an absent command data field and Le set to the length of the expected data, using a short Le. C. Verification of data authenticity To verify the authenticity of the stored registration data, the corresponding electronic signature may be verified. This means that besides the registration data also the corresponding electronic signature may be read from the registration card. The public key for signature verification can be retrieved by reading the corresponding issuing authority certificate from the registration card. Certificates contain the public key and the identity of the corresponding authority. The signature verification may be performed by another system than the registration card. The Member States are free to retrieve the public keys and certificates for verifying the issuing authority certificate. III.13. Special provisions Irrespective of the other provisions herein, the Member States, after notifying the European Commission, may add colours, marks or symbols. In addition, for certain data of Chapter III.2 Letter C, the Member States may allow XML format and may allow access via TCP/IP. Member States may, with the agreement of the European Commission, add other applications for which no harmonised rules or documents exist yet at EU level (e.g. roadworthiness certificate), on the vehicle registration card to realise additional vehicle related services. |
ANNEX II
PART II OF THE REGISTRATION CERTIFICATE ( 14 )
I. |
This part may be implemented in either of two formats: as a paper document or as a smart card. The characteristics of the paper document version are specified in Chapter II and those of the smart card version in Chapter III. |
II. |
Specifications of Part II of the registration certificate in paper format
|
III. |
Specifications of Part II of the Registration Certificate in smart card format (Alternative to the specimen in paper format described in Chapter II)
III.1. Card format and data legible with the eye Being a microprocessor card, the chip card shall be designed in accordance with the standards mentioned in Chapter III.5. Printed on the front and back of the card shall be at least the data specified in Chapters II.4 and II.5; these data shall be legible with the eye (minimum character height: 6 points) and printed on as follows. (Examples of possible lay-outs are presented in Figure 2 at the end of this section) A. Basic imprint The basic data shall contain the following: Front
(a)
To the right of the chip location: in the language(s) of the Member State issuing the Registration Certificate
—
the words ‘European Community’,
—
the name of the Member State issuing the Registration Certificate,
—
the words ‘Part II of the Registration Certificate’ printed in large type,
—
another (e.g. previous national) designation of the equivalent document (optional),
—
the name of the competent authority (alternatively, also in the form of a personalisation imprint as per Letter B),
—
the unambiguous consecutive number of the document as used within the Member State (alternatively, also in the form of a personalisation imprint as per Letter B).
(b)
Above the chip location: the distinguishing mark of the Member State issuing the Registration Certificate, white in a blue rectangle and surrounded by twelve yellow stars:
(c)
Member States might consider adding, at the lower edge in small type and in their national language(s), the note: ‘This document should be kept in a safe place outside the vehicle.’
(d)
The basic colour of the card is red (Pantone 194); alternatively, a red-to-white transition is possible.
(e)
A symbol representing a wheel (see proposed lay-out) shall be printed within the printing area in the bottom left corner of the card front. In other respects, the provisions of Chapter III.13 shall apply. B. Personalisation imprint The personalisation imprint shall contain the following information: Front
(a)
the name of the competent authority — see also Letter Aa).
(b)
the name of the authority issuing the Registration Certificate (optional).
(c)
the unambiguous consecutive number of the document as used within the Member State — see also Letter Aa).
(d)
The following data from Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised Community codes.
Back The back shall bear at least the remaining data specified in Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised community codes. In detail, these data are:
Optionally, additional data from II.6 (with the harmonised codes) and II.7 may be added on the back of the card. C. Physical security features of the smart card The threats to the physical security of documents are:
—
Production of false cards: creating a new object which bears great resemblance to the document, either by making it from scratch or by copying an original document.
—
Material alteration: changing a property of an original document, e.g. modifying some of the data printed on the document.
The material used for Part II of the registration certificate shall be made secure against forgery by using at least three of the following techniques:
—
microprinting,
—
guilloche printing*,
—
iridescent printing,
—
laser engraving,
—
ultraviolet fluorescent ink,
—
inks with viewing angle — dependent colour*,
—
inks with temperature — dependent colour*,
—
custom holograms*,
—
variable laser images,
—
optical variable images.
Member States are free to introduce additional security features. As a basis, the techniques indicated with an asterisk are to be preferred as they enable the law enforcement officers to check the validity of the card without any special means.
III.2. Data storage and protection Preceded by the harmonised common codes (where appropriate, in connection with the individual codes of the Member States according to Chapter II.7), the following data shall or may be additionally stored on the card surface bearing the legible information as per Chapter III.1:
(A)
Data as per Chapters II.4 and II.5 All data specified in Chapters II.4 and II.5 shall be mandatorily stored on the card.
(B)
Other data as per Chapter II.6 Moreover, the Member States are free to store more data as per Chapter II.6, to the necessary extent.
(C)
Other data as per Chapter II.7 Optionally, further vehicle-related data of general interest may be stored on the card. The data from the Letters A and B is stored in two corresponding files with transparent structure (see ISO/IEC 7816-4). The Member States may specify the storage of data from Letter C according their requirements. There are no read restrictions on these files. Write access to these files shall be restricted to the national competent authorities (and their authorised Agencies) in the Member State issuing the smart card. Write access is permitted only after an asymmetric authentication with session key exchange for protecting the session between the vehicle registration card and a Security Module (e.g. a Security Module Card) of the national competent authorities (or their authorised Agencies). Thereby Card Verifiable certificates according to ISO/IEC 7816-8 are exchanged before the authentication process. The Card Verifiable certificates contain the corresponding public keys to be retrieved and to be used in the following authentication process. These certificates are signed by the national competent authorities and contain an authorisation object (certificate holder authorisation) according to ISO/IEC 7816-9 in order to encode role specific authorisation to the card. This role authorisation is related to the national competent authority (e.g. to update a data field). The corresponding public keys of the national competent authority are stored as trust anchor (root public key) in the card. The specification of the files and commands needed for the authentication process and the writing process is under responsibility of the Member States. The security assurance has to be approved by Common Criteria Evaluation according to EAL4+. The augmentations are as follows: 1. AVA_MSU.3 Analysis and testing for insecure states; 2. AVA_VLA.4 Highly resistant.
(D)
Verification data for authenticity of registration data The issuing authority calculates its electronic signature about the complete data of a file containing the data of the Letter A or B and stores it in a related file. These signatures allow the authenticity of the stored data to be verified. The cards shall store the following data:
—
electronic signature of registration data related to Letter A,
—
electronic signature of registration data related to Letter B.
For verification of these electronic signatures the card shall store:
—
certificates of the issuing authority calculating the signatures about the data of Letters A, B.
Electronic signatures and the certificates shall be readable without restriction. Write access to electronic signatures and certificates shall be restricted to the national competent authorities. III.3. Interface External contacts should be used for interfacing. A combination of external contacts with a transponder is optional. III.4. Storage capacity of the card The card shall have sufficient capacity to store the data mentioned in Chapter III.2. III.5. Standards The chip card and reading devices used shall comply with the following standards:
III.6. Technical characteristics and transmission protocols The format shall be ID-1 (normal size, see ISO/IEC 7810). The card shall support transmission protocol T = 1 in compliance with ISO/IEC 7816-3. Additionally other transmission protocols may be supported, e.g. T=0, USB or contactless protocols. For bit transmission the ‘direct convention’ shall be applied (see ISO/IEC 7816-3). A. Supply voltage, programming voltage The card shall work with Vcc = 3V (+/0.3V) or with Vcc = 5V (+/0.5V). The card shall not require a programming voltage at pin C6. B. Answer to reset The Information Field Size Card byte shall be presented at the ATR in character TA3. This value shall be at least ‘80h’ (=128 bytes). C. Protocol parameter selection The support of protocol parameter selection (PPS) according to ISO/IEC 7816-3 is mandatory. It is used for selecting T=1, if T=0 is additionally present in the card, and to negotiate the Fi/Di parameters for achieving higher transmission rates. D. Transmission protocol T = 1 The support of chaining is mandatory. The following simplifications are allowed:
—
NAD Byte: not used (NAD should be set to ‘00’),
—
S-Block ABORT: not used,
—
S-Block VPP state error: not used.
The information field size device (IFSD) shall be indicated from the IFD immediately after ATR, i.e. the IFD shall transmit the S-block IFS request after ATR and the card shall send back S-block IFS. The recommended value for IFSD is 254 bytes. III.7. Temperature range The registration certificate in smart card format shall properly function under all climatic conditions usually prevailing in the territories of the community and at least in the temperature range specified in ISO 7810. The cards shall be capable of operating correctly in the humidity range 10 % to 90 %. III.8. Physical lifetime If used in accordance with the environmental and electricity-related specifications, the card must function properly for a period of ten years. The material of the card must be chosen in such a way that this lifetime is ensured. III.9. Electrical characteristics During operation, the cards shall conform to Directive 95/54/EC, related to electromagnetic compatibility, and shall be protected against electrostatic discharges. III.10. File structure Table 1 lists the mandatory elementary files (EF) of the application DF (see ISO/IEC 7816-4) DF.Registration. All these files have a transparent structure. The access requirements are described in Chapter III.2. The file sizes are specified by the Member States according their requirements.
Table 4
III.11. Data structure The stored certificates are in the X.509v3 format according ISO/IEC 9594-8. The electronic signatures are stored transparent. The registration data is stored as BER-TLV data objects (see ISO/IEC 7816-4) in the corresponding elementary files. The value fields are coded as ASCII character as defined by ISO/IEC 8824-1, the values ‘C0’-‘FF’ are defined by ISO/IEC 8859-1 (Latin1 character set) or ISO/IEC 8859-7 (Greek character set) or ISO/IEC 8859-5 (Cyrillic character set). The format of dates is YYYYMMDD. Table 2 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.4 and II.5 together with additional data from Chapter III.1. Unless otherwise stated, the data objects listed in Table 2 are mandatory. Optional data objects may be omitted. The column of the Tag indicates the level of nesting.
Table 5
Table 6 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.6. The data objects listed in Table 6 are optional.
Table 6
Structure and format of the data according Chapter II.7 are specified by the Member States. III.12. Reading the registration data A. Application selection The Application ‘Vehicle Registration’ shall be selectable by a SELECT DF (by name, see ISO/IEC 7816-4) with its Application identifier (AID). The AID value is requested from a laboratory selected by the European Commission. B. Reading data from files The files corresponding to Chapter II, letters A, B and D, shall be selectable by SELECT (see ISO/IEC 7816-4) with the command parameters P1 set to ‘02’, P2 set to ‘04’ and the command data field containing the file identifier (see Chapter X, Table 1). The returned FCP template contains the file size which can be useful for reading these files. These files shall be readable with READ BINARY (see ISO/IEC 7816-4) with an absent command data field and Le set to the length of the expected data, using a short Le. C. Verification of data authenticity To verify the authenticity of the stored registration data, the corresponding electronic signature may be verified. This means that besides the registration data also the corresponding electronic signature may be read from the registration card. The public key for signature verification can be retrieved by reading the corresponding issuing authority certificate from the registration card. Certificates contain the public key and the identity of the corresponding authority. The signature verification may be performed by another system than the registration card. The Member States are free in retrieving the public keys and certificates for verifying the issuing authority certificate. III.13. Special provisions Irrespective of the other provisions herein, the Member States, after notifying the European Commission, may add colours, marks or symbols. In addition, for certain data of Chapter III.2 Letter C, the Member States may allow XML format and may allow access via TCP/IP. Member States may, with the agreement of the European Commission, add other applications for which no harmonised rules or documents exist yet at EU level (e.g. roadworthiness certificate), on the vehicle registration card to realise additional vehicle related services. |
( 1 ) OJ L 42, 23.2.1970, p. 1. Directive as last amended by Commission Directive 98/14/EC (OJ L 91, 25.3.1998, p. 1).
( 2 ) OJ L 225, 10.8.1992, p. 72. Directive as amended by the 1994 Act of Accession.
( 3 ) Directive 2007/46/EC of the European Parliament and of the Council of 5 September 2007 establishing a framework for the approval of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles (OJ L 263, 9.10.2007, p. 1).
( 4 ) Directive 2014/45/EU of the European Parliament and of the Council of 3 April 2014 on periodic roadworthiness tests for motor vehicles and their trailers and repealing Directive 2009/40/EC (OJ L 127, 29.4.2014, p. 51).
( 5 ) Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data (OJ L 281, 23.11.1995, p. 31).
( 6 ) Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector (OJ L 201, 31.7.2002, p. 37).
( 7 ) Directive 2000/53/EC of the European Parliament and of the Council of 18 September 2000 on end-of-life vehicles (OJ L 269, 21.10.2000, p. 34).
( 8 ) The certificate consisting of one part only will bear the words ‘Registration Certificate’, and there will be no reference in the text to ‘Part I’.
( 9 ) Commission Implementing Regulation (EU) 2020/683 of 15 April 2020 implementing Regulation (EU) 2018/858 of the European Parliament and of the Council with regards to the administrative requirements for the approval and market surveillance of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles (OJ L 163, 26.5.2020, p. 1).
( 10 ) Council Directive 70/220/EEC of 20 March 1970 on the approximation of the laws of the Member States relating to measures to be taken against air pollution by gases from positive-ignition engines of motor vehicles (OJ L 76, 6.4.1970, p. 1), Directive as last amended by Commission Directive 2002/80/EC (OJ L 291, 28.10.2002, p. 20).
( 11 ) Council Directive 88/77/EEC of 3 December 1987 on the approximation of the laws of the Member States relating to the measures to be taken against the emission of gaseous pollutants from diesel engines for use in vehicles (OJ L 36, 9.2.1988, p. 33). Directive as last amended by Commission Directive 2001/27/EC (OJ L 107, 18.4.2001, p. 10).
( 12 ) Directive 1999/62/EC of the European Parliament and of the Council of 17 June 1999 on the charging of heavy goods vehicles for the use of certain infrastructures (OJ L 187, 20.7.1999, p. 42).
( 13 ) Commission Directive 95/54/EC of 31 October 1995 adapting to technical progress Council Directive 72/245/EEC on the approximation of the laws of the Member States relating to the suppression of radio interference produced by spark-ignition engines fitted to motor vehicles and amending Directive 70/156/EEC on the approximation of the laws of the Member States relating to the type-approval of motor vehicles and their trailers (OJ L 266, 8.11.1995 p. 1).
( 14 ) This Annex is concerned only with Registration Certificates consisting of Parts I and II.