Be careful and always make sure that you share information only through the secure website of the Slovak public administration. A secure page always starts with https:// before the domain name of the website.
Information on how the subject of a message, sender name and recipient name are displayed for specific Sk-Talk message classes can be found in the eDesk SkTalk2 Mapping file [.zip, 19.7 kB].
G2G – Sk-Talk Message Schemas for Asynchronous Communication with the ÚPVS
The documentation for the Sk-Talk Message Schemas for Asynchronous Communication with ÚPVS is published pursuant to Section 11(g) of Decree No. 78/2020 Coll.Opens in a new window on standards for public administration information technologies and consists of four documents:
The list of permissible Sk-Talk 3 Class and Object Class values is available in the Sk-Talk_3-Class List file [.zip, 54 kB, 3 September 2025] in two formats (.ods, .xlsx). Note: The current list of Sk-Talk 2 Class values can be found in the historical documentation. Historical documentation does not form part of the Sk-Talk Message Schemas Documentation.
Pursuant to Section 6.1.6 of Decree No. 78/2020 Coll. on Standards for Public Administration IT, we publish the maximum permissible size of an electronic message that may be sent via the integration interface of the Central Public Administration Portal:
The maximum size of a Sk-Talk message that can be processed is 50 MB (51,200 kB).
Note: Due to the use of Base64 encoding for objects, files with a total size of approximately 34 MB can generally be transmitted, as Base64 encoding increases file size by approximately one third.
The highest supported version of the XML Schema Definition Language (XSD) for defining the data structure of an electronic form (pursuant to Section 2.3.5 of Annex 1 to Decree No. 78/2020 Coll.) is version 1.0.
Pursuant to Annex 1Opens in a new window, Section 7.3.6 of Decree No. 78/2020 Coll.Opens in a new window on Standards for Information Technologies in Public Administration, the documentation of electronic form validations performed in the Electronic Forms Module, together with the date on which they become effective, is published on the Central Government Portal:
Electronic form validations will become effective as of 12 November 2023.
Any changes to the validation rules in the Electronic Forms Module must be approved in advance by MIRRI and published sufficiently in advance of their actual implementation. Depending on the expected impact on existing implementations, the announcement of the activation of new rules will normally be published at least 3 months in advance, or 6 months or more in advance where necessary. In the case of more significant changes, the notice may be published 12 months or more in advance. Each validation rule specifies the date from which it becomes effective. This date can be detected automatically, making it possible to determine when the rule will be activated.
Electronic form identifier (the dc:identifierelement in meta.xml, pursuant to Section 2.2.1 of Annex 1);
Electronic form administrator identifier (the dc:publisherelement, pursuant to Section 2.2.1);
Electronic form provider identifier (the dc:creatorelement, pursuant to Section 2.2.1 of Annex 1);
The value of the targetNamespaceattribute in the data structure definition (XSD) of an electronic form (Section 2.3.11 of Annex 1);
Schema references in the XMLDataContainer in the UsedPresentationSchemaReferenceand UsedXSDReferenceelements, and the form identifier in the Identifierattribute (Annex 7, Sections D.4.1, D.4.2.1 and D.4.3.1).
List of Electronic Forms Modified Without a Version Change
Pursuant to Annex 1, Section 3.1.1 of Decree No. 78/2020 Coll., under certain conditions, components of a form may be modified without changing its version. Therefore, as of 27 December 2023, a list of electronic forms that have been modified without a version change has been published:
The Electronic Forms Module currently supports the electronic form publication container exclusively in version 1.0. Therefore, pursuant to Section 7.3.2 of Annex 1 to Decree No. 78/2020 Coll.Opens in a new window, only values corresponding to version 1 may be specified in the container, for example, "urn:manifest:1.0".
Pursuant to Section 7.3 of Annex 1 to Decree No. 78/2020 Coll. on Standards for Information Technologies in Public Administration, XSD schemas for individual versions of the electronic form publication container are published in the Central Metainformation SystemOpens in a new window.
At present, the published XSD schemas are available only for version 1.0 of the electronic form publication container. Since versions 1.1 and 1.2 of the container cannot currently be used, electronic forms cannot use features supported exclusively by these higher versions. Such features include, for example, multiple comma-separated values in the media-destinationattribute in the manifest.xmlfile or the new structure of the meta.xmlfile.
Code Lists for Electronic Form Publication Container Values
In accordance with Section 7.5.4 of Annex 1 to Decree No. 78/2020 Coll.Opens in a new window, we publish the permitted attribute values for the electronic form publication container in the Electronic Forms Module:
media-destination attribute– The code list of presentation schema purposes for permitted values of the media-destinationattribute with the x-prefix is published in the Central Metainformation SystemOpens in a new window (CL000001), in accordance with Annex 1, Section 7.9.6(f) of Decree No. 78/2020 Coll.
media-destination-type-description attribute– Currently, no values have been registered beyond the mandatory values defined in the Decree on Standards: HTML, XHTML, TXT and XSLFO (Annex 1, Section 7.5.4(d) of Decree No. 78/2020 Coll.).
target-environment attribute– A code list of electronic form environments for the permitted values of the target-environmentattribute has not yet been created, as no request to register a specific value has been submitted by form administrators to date (Annex 1, Section 7.5.4(j) of Decree No. 78/2020 Coll.). If this attribute is omitted, the presentation schema is intended for transformation by the Central Government Portal modules. In practice, the value "upvs", which appeared in the examples in the previous version of Decree No. 55/2014 Coll. on Standards for Information Systems in Public Administration, is not used.
xslfo-reference-procesor attribute– Only one value is defined: "Apache FOP 1.1"(Annex 1, Section 7.5.4(k) of Decree No. 78/2020 Coll.).
In accordance with Decree No. 78/2020 CollOpens in a new window. on Standards for Information Technologies in Public Administration (Annex 1, Section 3.1.3), we publish a link to download the reference XSL-FO software used to correctly transform XSL-FO files into PDF presentations of electronic forms. This software is Apache FOP 1.1.Opens in a new window
The current configurationOpens in a new window of Apache FOP 1.1 [.zip, 3.6 kB] used by the Central Government Portal is also available.
This software is used by the Central Government Portal for every transformation of data entered in an electronic form into PDF format. It is also used to generate paper copies of electronic official documents.
The following command can be used to generate a PDF presentation from data entered in accordance with an electronic form, using the print presentation schema and the reference XSL-FO software Apache FOP 1.1: