Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
This document should determine the characters required for names in the broader sense. This means names of individuals in accordance with the specifications of the civil status law as well as names of legal entities, products, patents, names of countries, towns and streets, as well as titles of documents or laws. Names in the broader sense can denominate specific objects, but also virtual constructs such as product groups or musical styles.
The normative part determines the subset of the characters and character sequences included in Unicode, that are required for IT applications for the electronic processing of names based on the Latin script. Thus, it needs to be supported by all IT applications compliant to the standard at least for all data fields intended for Latin names.
The normative part should also define a mapping of the normative letters to the capital letters A to Z that is possibly required. For this purpose, the recommendations of the respective standard ICAO 9303, Part 3 for machine-readable travel documents must being applied and extended. From this standard, an impetus can be given to add still missing characters to the ICAO mapping.
The standard should primarily be aimed at authorities and organisations operating IT applications for the inter-authority data exchange or the data exchange with citizens and economy.
It should cover in its entirety •the European official languages, so not only Latin characters, but also, for example, Greek and Cyrillic characters,
•European minority languages,
•Latin characters that may occur as a result of transliteration from another script – the basis for this must be the relevant ISO standards,
•characters used in European registers, such as civil status registers and commercial registers,
•characters required for data exchange between social insurance carriers, and
•characters required for the Europe-wide data exchange between authorities.
The standard should not include statements on historic characters nor the treatment of continuous text. It does not regulate the representation of characters (glyphs).
The standard should consider the already existing standard DIN 91379 “Characters and defined character sequences in Unicode for the electronic processing of names and data exchange in Europe”, which has already been bindingly stipulated in Germany for public administrations.
The legacy character sets ISO/IEC 8859-1, ISO/IEC 8859-15 and Windows 1252 should also be a basis for the compilation of characters within the standard. However, a few characters may not be added due to professional evaluation.
To ensure interoperability of all implementations of the standard, a normalisation form (i.e. NFC) and an encoding (i.e. UTF-8) for the Unicode characters must also be defined.
The standard should describe the conformity requirements for implementations of the standard.
An annex should recommend data types for restrictions on certain subsets of characters, which may be especially helpful for interface agreements. The data types help to achieve the goal, to get a conclusive list of permitted characters to implement robust algorithms and applications for personal identification and the creation of official documents and certificates.
Non-normative attached files to the standard should be given to:
•a technical implementation of data types,
•an XML file including all characters and character groups listed in the standard,
•an XML Schema including the determination of the structure of the XML file of all listed characters,
•a tabular overview of all characters and character groups listed in the standard that is easy for people to read,
•a mapping of the characters contained in the standard to legacy character sets for the implementation of transitional solutions that are as interoperable as possible, and (continued...)
Reģistrācijas numurs (WIID)
81087
Darbības sfēra
This document should determine the characters required for names in the broader sense. This means names of individuals in accordance with the specifications of the civil status law as well as names of legal entities, products, patents, names of countries, towns and streets, as well as titles of documents or laws. Names in the broader sense can denominate specific objects, but also virtual constructs such as product groups or musical styles.
The normative part determines the subset of the characters and character sequences included in Unicode, that are required for IT applications for the electronic processing of names based on the Latin script. Thus, it needs to be supported by all IT applications compliant to the standard at least for all data fields intended for Latin names.
The normative part should also define a mapping of the normative letters to the capital letters A to Z that is possibly required. For this purpose, the recommendations of the respective standard ICAO 9303, Part 3 for machine-readable travel documents must being applied and extended. From this standard, an impetus can be given to add still missing characters to the ICAO mapping.
The standard should primarily be aimed at authorities and organisations operating IT applications for the inter-authority data exchange or the data exchange with citizens and economy.
It should cover in its entirety •the European official languages, so not only Latin characters, but also, for example, Greek and Cyrillic characters,
•European minority languages,
•Latin characters that may occur as a result of transliteration from another script – the basis for this must be the relevant ISO standards,
•characters used in European registers, such as civil status registers and commercial registers,
•characters required for data exchange between social insurance carriers, and
•characters required for the Europe-wide data exchange between authorities.
The standard should not include statements on historic characters nor the treatment of continuous text. It does not regulate the representation of characters (glyphs).
The standard should consider the already existing standard DIN 91379 “Characters and defined character sequences in Unicode for the electronic processing of names and data exchange in Europe”, which has already been bindingly stipulated in Germany for public administrations.
The legacy character sets ISO/IEC 8859-1, ISO/IEC 8859-15 and Windows 1252 should also be a basis for the compilation of characters within the standard. However, a few characters may not be added due to professional evaluation.
To ensure interoperability of all implementations of the standard, a normalisation form (i.e. NFC) and an encoding (i.e. UTF-8) for the Unicode characters must also be defined.
The standard should describe the conformity requirements for implementations of the standard.
An annex should recommend data types for restrictions on certain subsets of characters, which may be especially helpful for interface agreements. The data types help to achieve the goal, to get a conclusive list of permitted characters to implement robust algorithms and applications for personal identification and the creation of official documents and certificates.
Non-normative attached files to the standard should be given to:
•a technical implementation of data types,
•an XML file including all characters and character groups listed in the standard,
•an XML Schema including the determination of the structure of the XML file of all listed characters,
•a tabular overview of all characters and character groups listed in the standard that is easy for people to read,
•a mapping of the characters contained in the standard to legacy character sets for the implementation of transitional solutions that are as interoperable as possible, and (continued...)
