Requirements for the formatting of articles. Guidelines for the publication of open data by state bodies and local governments and technical requirements for the publication of open data Requirements for the publication of a set of open data
Conditions for publication in the collection of conference materials
Materials will be published AFTER the conference based on the results of the sections. The collection will include only those articles whose authors will make a presentation during the conference.
REQUIREMENTS FOR ARTICLES:
Dear Colleagues! Please note: the editorial board of the collection reserves the right not to include in the collection articles that do not meet the requirements (including the volume of text, the design of tables and illustrations).
The file name with the article must contain only Latin letters. The file name must contain the author's last name. When registering online, you are allowed to attach ONLY archived files in .zip and .rar format.
To prepare the article must be used Microsoft Word text editor and Times New Roman font .
The maximum length of an article is 8 full pages; minimum - 6 full pages (from 16 to 20 thousand printed characters).
Page settings:
paper size - A4 (21 cm x 29.7 cm)
orientation - portrait
fields:
top - 2.4 cm
lower - 2 cm
left - 3 cm
right - 2 cm
· from edge to footer:
upper 1.2 cm
lower 1.25 cm
The material of the article should be presented in the following sequence:
· Title (title of the article)
The title should be in capital letters, bold font (font size 13 pt) and centered. Please note that there is no period at the end of the title!
Font - bold, font size - 13 pt, centered.
· Name of the organization
The name of the organization must be in lowercase letters.
Font - regular, font size - 13 pt, centered.
· The name of the country
The country name must be in capital letters.
Font - regular, font size - 13 pt, centered.
· Annotation
An abstract of no more than 10 lines should briefly outline the subject of the article and the main conclusions contained in it.
Font - regular, font size - 12 pt.
Formatting by aligning to the width of the page.
· Article text
Font size - 12 pt, line spacing - single, red line - 1 cm.
Formatting by justification.
The style is normal. When typing text, you should not strictly hyphenate words with a hyphen.
Conventions and abbreviations found in the text should be disclosed the first time they appear in the text.
Sections and subsections of the article are numbered in Arabic numerals, highlighted in bold and not placed on a separate line.
· Tables
Tables in the text must be made in the Microsoft Word editor (not scanned or in the form of a drawing). Tables must be located within the working area. Formatting the table number and its name: regular font, size 11 pt, centered. Please note that there is no period at the end of the table title! The contents of the table are normal font, size 11 pt, single spacing. If the article contains tables
· Illustrations
Drawings are placed within the working area. You can use pictures in JPEG and GIF formats. Drawings must allow movement in the text and the ability to change sizes. The scanned image used in the text must have a resolution of at least 300 dpi.
Signature under the picture. Formatting of the title and number of the figure - normal font, size - 11 pt, center alignment, single spacing. Please note that there is no period at the end of the name of the picture!
· Page numbering and footers
Don't use headers and footers. Page numbering is at the bottom right, starting from page 1.
Article text...article text... . Text of the article... etc.
· Bibliography
The list of references is located at the end of the article. Font size 12 pt., formatting aligned to the width of the page.
Examples of a list of references:
For books:
Tooth A.T. Organizational crisis management. M.: University Humanitarian Lyceum, 2003.
Petrunin Yu.Yu., Borisov V.K. Business ethics. M.: Delo, 2000.
For articles in journals, collections of works and other collective publications:
Marinko G.I. Organizational culture and knowledge management // Philosophy of science and scientific and technical civilization: Anniversary collection / Responsible. ed. S.L. Katrechko. M.: Polygraph-Inform, 2005. pp. 322-338.
Voronina T.P., Molchanova O.P. Features of managing an innovative organization // Bulletin of Moscow University. Ser. 21. Management (state and society). No. 2. 2004. P. 66-82.
For materials from INTERNET:
Surin A.V. 10 years of management training at Moscow University: experience and problems. - http://e-journal..pdf (the date the material was viewed on the Internet is indicated in brackets).
TERMS OF PUBLICATION
The collection is assigned the international index ISBN, BBK and UDC indices.
All articles are subject to editing (scientific and technical).
The editorial committee of the collection of conference materials reserves the right to refuse publication to authors of articles that do not correspond to the level of the conference.
Distribution is carried out (in accordance with the Federal Law of November 23, 1994 “On Legal Deposit of Documents”) to the main libraries of the Russian Federation and member countries of the Commonwealth of Independent States, to the Russian Book Chamber. The planned circulation is at least 500 copies.
on the publication of open data by state bodies and local governments and technical requirements for the publication of open data
(version 2.2)
I. General provisions | |
II. Determination of lists of open data sets and priority of their publication | |
III. Technological infrastructure | |
IV. Technical requirements for publishing datasets | |
V. Terms of use of open data | |
VI. How to publish datasets | |
Appendix 1. Description of characteristics that should be included in the data set passport | |
Appendix 2. Example of describing the structure of a data set | |
Appendix 3. Requirements for submitting passports of data sets using the RDFa format |
I. General provisions
1. This document was prepared in pursuance of the Decree of the President of the Russian Federation of May 7, 2012 No. 601 “On the main directions for improving the public administration system.” In accordance with subparagraph d) of paragraph 2 of the Decree, the Government of the Russian Federation was instructed, until July 15, 2013, to provide access on the Internet to open data contained in the information systems of state bodies and local governments of the Russian Federation.
II.Determination of lists of open data sets and priority of their publication
4. Information containing information on the activities of state bodies and local self-government bodies posted on the Internet in accordance with the Federal Law of January 1, 2001 “On ensuring access to information on the activities of state bodies and bodies” is subject to publication in the form of open data. local self-government", as well as information containing information collected, stored, processed or published by state bodies or local government bodies in the exercise of their powers.
a) the demand for relevant sets of open data by potential consumers of information, assessed in accordance with methodological recommendations for determining the demand and priority of disclosed data;
b) the degree of readiness, characterized by the availability of the necessary data in structured formats in electronic form, as well as the readiness of organizational, technical, technological and other means necessary for the publication of open data sets;
c) publication costs (financial, time, labor) necessary to publish open data sets and keep them up to date.
Information that is in high demand and degree of readiness, while requiring minimal costs, should be published in the form of open data by state bodies and municipal authorities as a matter of priority.
To increase the degree of readiness of information for publication in the form of open data, state bodies and municipal self-government bodies are recommended, when carrying out work on the design, creation or development of automated systems, to establish appropriate requirements for such work, providing for the use of machine-readable open formats when collecting, processing, storing and publishing information .
When creating a registry and open data sets, it should be taken into account that:
b) for each data set, a person responsible for the content of a specific data set, its correctness, completeness and relevance must be identified;
c) for each data set, the update frequency must be established taking into account the needs of information users;
The generated register of open data is approved by a state body or local government body and is subject to publication on the official website of the body on the Internet.
III. Technological infrastructure
5. Open data sets to be published or links to these data sets must be posted on the official websites of state bodies or local governments that are the owners of these data sets. To do this, websites must be prepared as follows:
a) a specialized page must be created on the website for the publication of open data in machine-readable formats (hereinafter referred to as the open data page);
b) on the main page of the website there should be a visually visible hyperlink to the open data page with the inscription “Open Data”;
c) the open data page must contain a register of open data;
e) in order to make open data pages accessible to search robots, a link to the metadata directory must be placed - permission in robots. txt, indication in sitemap. xml.
IV. Technical requirements for publishing datasets
Requirements for the name and identification number of the data set
6. The name of the data set used in registers, passports and open data pages is selected as follows:
a) the name of the data set should reflect its content;
b) the name of the data set should not repeat the information contained in the identification number (code) of the data set (see below).
7. is formed as follows:
a) identification number format:<код организации>.<порядковый номер набора данных>.<номер версии набора данных>
b) the organization code is the taxpayer identification number (TIN) corresponding to the government agency, local government agency or organization that published the data set.
c) the serial number of the set is unique and is assigned by the state body, local government body or organization that published it, in accordance with the numbering in the open data register, starting from 1;
d) the set version number is assigned by the state body, local government body or organization that published it, starting from 1. The set version is considered new if the data in the set has changed, or the characteristics of the data set (passport) have changed.
Open Data Page Requirements
8. The address of the open data page on the Internet (URL) should be formed according to the following template: “<адрес веб-сайта>/opendata/" or "<адрес веб-сайта>/open data/”, if addresses in Cyrillic are used for addressing within the website.
The Open Data page should have the title "Open Data" and provide website users with:
2) statistical information about data sets opened by a state body or local government (their number, formats, etc.).
3) feedback (on-screen forms for feedback or links to on-screen forms for feedback), allowing website users to leave suggestions and feedback on issues of opening government data, including errors identified in data sets and their passports;
4) means of searching for data opened by a state body or local government body. If no more than 20 data sets are open by a state body or local government body, it is not necessary to create such search tools;
5) descriptions of the conditions for using data opened by a state body or local government (if such a description is not provided on the pages of the data sets);
6) file representation of the list (register) of data sets opened by a state body or local government body.
Requirements for publishing a registry of open data sets
9. The registry of open data sets must be presented in HTML or RDFa format (Resource Description Framework in attributes metadata description model in accordance with W3C recommendations (http://www. w3.org/TR/xhtml-rdfa-primer/)). When visually presented in HTML format, a file representation in CSV format must be provided (text format for presenting tabular data comma-separated values, in accordance with the specification http://www.rfc-editor.org/rfc/rfc4180.txt, hereinafter format CSV) or XML (Extensible Markup Language, in accordance with the W3C specification (http://www. w3.org/TR/xml11/), hereinafter XML format)
1) Representation of a registry of data sets in RDFa or HTML format on a page<адрес веб-сайта>/opendata/ for each data set should include:
Serial number of the data set;
2) When using a file representation of the registry in CSV format, the file should be located at "<адрес веб-сайта>/opendata/opendatalist. csv" or "<адрес веб-сайта>/open data/registry of open data. csv". The registry must contain an up-to-date list of all open data sets (names and links to pages of these sets). Records about each of the data sets must be separated by a newline character. Data within a data set record must be separated by ";" (semicolon). Inside each data field there are symbols ";" (semicolon) and "line feed" are not allowed.
3) When using the XML file representation of the registry, the XML format file should be located at "<адрес веб-сайта>/opendata/opendatalist. xml" or "<адрес веб-сайта>/open data/registry of open data. xml" .
Requirements for the open data set page and open data set passport
10. The title of the dataset page must match the title of the dataset. The dataset page must provide website users with:
1) information about the data set, necessary and sufficient for its use (data set passport) - in a visual interface and in the form of a file for downloading;
2) descriptions of the conditions for using the dataset (if such a description is not provided on the open data page);
3) the ability to immediately download data from a published set without requiring additional authorization, entering a Captcha code or other restrictions;;
4) feedback (on-screen forms for feedback in the form of comments, or links to on-screen forms for feedback), allowing website users to leave suggestions and feedback on issues of opening government data, including errors identified in data sets and their passports. The feedback implemented on the dataset page must link user input to the appropriate dataset.
The address of the open data set page should be formed according to the following template: “<адрес веб-сайта>/opendata/<код организации>.<порядковый номер набора данных>.<номер версии набора данных>" or "<адрес веб-сайта>/open data/<код организации>.<порядковый номер набора данных>.<номер версии набора данных>", if addresses in Cyrillic are used for addressing within the website.
Each version of the dataset has its own separate page.
The open data set page should contain information describing the open data in the form of a data set passport.
The open data set passport must include the data listed in Appendix 1.
The data set passport must be presented in HTML or RDFa format.
When visually presented in HTML format, a file representation in CSV or XML format must be provided. The name and location of the file representation of the passport must correspond to one of the following templates:
1) <адрес страницы набора данных>/opendatameta. xml
2) <адрес страницы набора данных>/opendatameta. csv
The open data set passport displayed in the visual interface is recommended to be presented using the RDFa format in accordance with the requirements given in Appendix 3.
Requirements for the presentation of open data sets
11. Requirements for published open data sets:
a) open data should be published in CSV or XML formats. It is recommended to publish data in CSV format in a flat tabular form, and the use of a newline character in the content of the record is not allowed. It is recommended to publish complex hierarchical data in XML formats;
b) in case of significant volumes, frequent updates or the need to form specific samples, open data can be provided through a software interface that has a published specification; the software interface must provide the ability to fully automatically (without human intervention) access to all information in the data set;
c) the file of each version of the data set must have a permanent hyperlink formed according to the template: “<адрес веб-сайта>/opendata/<код организации>.<порядковый номер набора данных>.<номер версии набора данных>/<код организации>.<порядковый номер набора данных>.<номер версии набора данных>.csv" or "<адрес веб-сайта>/opendata/<код организации>.<порядковый номер набора данных>.<номер версии набора данных>/<код организации>.<порядковый номер набора данных>.<номер версии набора данных>.xml";
d) the number of stored versions of the data set is determined based on resource capabilities for storage, taking into account the needs of users of the data set;
e) if the size of the data set exceeds 10 megabytes, it is recommended to archive it using an archiving algorithm that has a specification in the form of an open standard;
e) together with data published in XML format, files of a structural description of the format should be published in the form of an XSD schema (a language for describing the structure of the XML document XML Schema, in accordance with W3C recommendations http://www.w3.org/TR/xmlschema-0 /, hereinafter the XSD scheme);
g) in the case of providing access to a data set through a software interface, the data set page must contain a complete description of the software interface (specifications of protocols, data formats, primary parameters for accessing the service, etc.), sufficient to implement fully automatic access to the data set for a specialist qualified as a programmer;
h) to represent open data sets containing information from various subject areas, existing standard data markup formats (schema.org, YMapsML, XAL, etc.) that have a published specification should be used;
i) it is necessary to avoid changing the format for presenting open data, as this complicates the automatic processing of data. In case of a format change, it is necessary to notify users, for example, by setting the value of the “Last change content” parameter to “Data structure change” in the data set passport.
V. Terms of use of open data
12. When publishing open data sets, the list of sets page must contain a description of the conditions for using the data or a link to it.
13. The terms of use should not require users to enter into an agreement with a government or local government agency.
14. The terms of use should not restrict users of data from using it for non-commercial and commercial purposes.
15. The terms of use must provide for the free provision of open data.
16. The terms of use must include a requirement for a mandatory link to the data set in projects using data from this set.
18. The terms of use should not require registration and authorization on the site to be able to use open data.
VI. How to publish datasets
19. Disclosed data must be published in the following order:
a) a state body or local government body translates a data set into a format in which this data set is to be published;
b) a state body or local government body publishes a data set, adds the necessary information to the open data page of its website (including the registry of open data sets published by a state body) and the page of the corresponding data set;
c) a state or local government body verifies the availability of the published data set for website users;
d) a state body or local government body transmits in the form of a file in CSV format a record of a published data set, downloaded from the register of data sets opened by a state body or local government body, to a federal-level working group maintaining a unified register of open data;
e) the federal-level working group updates the unified register of open data, as well as other information about published sets of government data, which it maintains on a web page on the Internet to publish summary information about data opened by state bodies or local governments in machine-readable formats formats.
Annex 1.
Description of the characteristics that should be included in the data set passport.
Characteristic | Description | Description example |
|
Identification number (code) of the data set | A code that uniquely identifies a data set, including its version | ||
Data set name | Short name of the data set | List of MFCs |
|
Description of the dataset | An expanded description of the dataset, reflecting its contents and features that may be important to potential users | List of multifunctional centers for the provision of public services indicating address information and a list of services provided |
|
Dataset owner | The organization that owns the data set, publishes it, and is responsible for maintaining it | Ministry of Economic Development of Russia |
|
Responsible person | The official responsible for opening this set (The last name, first name and report are indicated sequentially, separated by a space; the position of the person is indicated, separated by a comma), | deputy head of department |
|
Responsible person's phone number | Responsible person's phone number | ||
His email address | |||
Hyperlink (URL) to the set | Address of the data set on the Internet | http://www. *****/opendata/.1.1/.1.1.xml |
|
Data Format | |||
Description of the data set structure | Description of each information field of the data set structure. For data sets presented in XML format, an XSD schema is an XML file. For data sets in CSV format – a text file containing the name and description of each field. In this case, the description of the structure of the data set must also contain a description (including in the form of links) of all reference books and classifiers used to generate the data set. If access to a data set is provided through a software interface, a hyperlink to a page containing a description of such an interface is provided. | http://www. *****/opendata/.1.1/.1.1.xsd |
|
Date of first publication of an open dataset (in DD.MM.YYYY format) | |||
Date of last modification to the data set (in DD.MM.YYYY format) | |||
Information about what exactly has changed in the dataset compared to its previous version. Selected from a limited list of values: Changing the data structure Eliminating the identified error Updating a Dataset Making changes to the kit passport. | Changing the data structure |
||
The frequency with which the data set must be updated in order to keep it up to date. Select from a limited list of values: Periodic update (annually, quarterly, monthly, daily); By calendar date; As changes occur (indicating the event and the deadline for entering data). | Daily |
||
Keywords that reflect the content and features of the data set by which users will be able to find it on the website and in the registry | multifunctional center, address, contact person, work schedule |
Application2.
An example of describing the structure of an open data set
Table name | Fields |
||||||||
Name | Description | Field type | Unique | Mandatory | Length | Quantity decimal places | Link to another table |
||
MFC addresses | MFC name | Official name of the MFC | text | 150 characters | |||||
Address of the MFC point according to the specified format | Rich text field | 300 characters | |||||||
Phone number according to the specified format | Formatted numeric field | 10 characters | |||||||
List of MFC services | MFC name | Official name of the MFC | text | 150 characters | MFC addresses/MFC name |
||||
List of services provided | List of all services provided in this MFC | List of text strings | 30 lines of 40 characters |
Application3.
Requirements for the submission of data set passports
using RDFa format
General information
RDFa (Resource Description Framework in attributes) is a model developed by the World Wide Web Consortium (W3C) for representing data, especially metadata, through attributes of HTML, XHTML and XML software environments.
These requirements for the presentation of data set passports are based on the following standards:
b) RFC2413 - Generally recognized Internet standard "Encoding Dublin Core Metadata in HTML";
c) GOST R 7.0.10-2010 - Russian standard “Set of metadata elements “Dublin Core”.
The following RDFa dictionaries are used to represent open data passports:
a) foaf (Friend of a Friend) - "http:///foaf/0.1/" - to provide an object class;
b) dc (Dublin Core) - "http://purl. org/dc/terms/" - to provide object properties (the "Qualified Dublin Core" edition is used, as it contains an extended list of properties).
Requirements
Each open data set passport (in the visual interface) must be represented by an RDFa object with a mandatory indication of the class and type of the object and properties, each of which strictly corresponds to a specific value from the open data passport.
An object representing an open data set passport must have a “Document” class from the “foaf” dictionary (used as the “typeof” attribute, denotes the essence of the object, that this object is a document) and a “dc:type” property with the value “OpendataMeta” − a special value identifying a document as an open data passport.
The correspondence between data from the passport of the open data set and properties from the Dublin Core dictionary is shown in the table:
Data from the data set passport | Properties from the dictionary "Dublin Core» |
Identification number (code) of the data set | |
Data set name | |
Description of the dataset | |
Dataset owner | |
Responsible person | |
Responsible person's phone number | |
Responsible person's email address | |
Data Format | |
Description of the data structure | |
Date of first publication of the dataset | |
Last modified date | |
Frequency of updating the data set | |
Keywords that match the content of the dataset |
The HTML markup of the Open Data Passport page must meet the following requirements:
a) the open data passport must have the HTML class “opendata-meta”;
b) each information must include a serial number, name and value and must be marked with the “opendata-meta-field” class;
c) the serial number of each information must be marked with the class “opendata-meta-field-id”;
d) the name of each information must be marked with the class “opendata-meta-field-title”;
e) the value of each information must be marked with the class "opendata-meta-field-value".
· Igor Zhuravlev
· Igor Zhuravlev, Andrey Kurosh, Alexey Chumachenko, Polina Vafina
· Igor Zhuravlev, Polina Vafina
You have received an email with multiple recipients in the copy. What happens if you click the Reply All button?
· A letter will be created, where the address from which you received the original letter will be indicated in the “To” field
· A letter will be created, where in the “To” and “Copy” fields all addressees listed in the original letter will be respectively indicated.
· An email will be created with an empty “To” field.
· A letter will be created, where the recipients listed in the original letter will be indicated in the “Copy” field
You received an email from a specific address. There are several more addresses in the “Copy” field. You want to reply only to the person from whose address the letter came. Which button should you press?
· Answer
· Reply All
· Create a message
· Forward
What is the “To Execute” button used for?
· To set a calendar reminder
· To prepare a response on behalf of the manager
· So that the message is always marked as unread
· To forward a letter to a subordinate
Which concept is defined below?
· Open data
Open Data Passport
666. The definition of which concept is given below:
· Open data
· Open government data
· Open Data Passport
In what format is data not prepared for the open data set for the purpose of their publication on the Open Data Portal of the Russian Federation?
· XML format
· DOC format
· CSV format
Which icon will launch a software application to create a set of open data in CSV format?
Table 1
table 2
· Table 1
· Table 2
Which table meets the requirements for publishing an open data set?
Table 1
table 2
· Table 1
· table 2
6. Procedure for publishing open data sets
General rules for publication in the form of open data, applicable to a state body or local government:
a) a state body or local government body translates the data set into a machine-readable format in which this open data set is subject to publication;
b) a state body or local government body publishes a data set, adds the necessary information to the page of the open data section (portal) and provides a link to the page of the corresponding set (file representation of the set) of open data. The open data set page must include a link to download the selected open data version or to a programming interface (API);
c) a state body or local government body checks the availability of a published set of open data for users of the official website on the Internet;
d) a state body or local government body transmits in the form of a file in a machine-readable format a record of a published set of open data, downloaded from the register of data sets opened by a state body or local government body, to the authorized government body;
e) the authorized government body updates the consolidated register of open data, as well as other information about published sets of open government data, which they maintain on a page on the Internet for the publication of summary information about data opened by state bodies or local government in machine-readable formats , thereby keeping the consolidated registry of open data sets up to date.
The interaction diagram for publishing open data (Figure 1) reflects the role-based approach to the process under consideration, representing a description of the functional and technological components. Thus, icons indicate functional roles (one employee can have several roles).
Figure 1 - Scheme of interaction when publishing a set
open data (not provided)
a) an industry division of a state body or local government body prepares material for presentation in the form of open data. This preparation is carried out by the role “Information Provider” (the role responsible for the content of the material);
b) after preparing the material, the “Information Provider” transfers the material to the “Technical Specialist” of its department for its conversion into machine-readable data. Upon receipt of the material, the “Technician” checks the material for errors and the possibility of correct representation into machine-readable data;
c) after translating the data into a machine-readable representation, the “Technical Specialist” transfers the data to the “Content Manager” (the role responsible for publishing open data sets in one of the mandatory ways, as well as alternative publishing methods) or uses automated tools for self-publishing an open data set;
In order to ensure access of citizens and organizations to publicly available information about the activities of the Federal Tax Service in the form of open data, in pursuance of Decree of the President of the Russian Federation dated 05/07/2012 No. 601 “On the main directions for improving the public administration system”, implementation of the provisions of the Federal Law dated 02/09/2009 No. 8-FZ “On ensuring access to information about the activities of state bodies and local governments”, Federal Law dated July 27, 2006 No. 149 “On information, information technologies and information protection”, Resolution of the Government of the Russian Federation dated July 10, 2013 No. 583 “On ensuring access to publicly available information about the activities of state bodies and local governments in the information and telecommunications network “Internet” in the form of open data”, Order of the Government of the Russian Federation dated July 10, 2013 No. 1187-r, minutes of the meeting of the Government Commission for Coordination of Open Activities Government dated May 29, 2014 No. 4, I order:
1. Approve the Regulations for the preparation and disclosure of publicly available information in the open data format in accordance with the principles of openness in accordance with this order.
2. The order of the Federal Tax Service of Russia dated March 23, 2015 No. ММВ-7-6/118@ “On publicly available information of the Federal Tax Service of Russia posted on the Internet in the form of open data” shall be declared invalid.
3. The heads (acting heads) of structural divisions of the central apparatus of the Federal Tax Service of Russia must ensure control over the timely submission of publicly available information to the structural division of the central apparatus of the Federal Tax Service, coordinating the work on the generation of open data, and to the structural division of the central apparatus of the Federal Tax Service, coordinating organizational issues providing access to open data and publicly available information from the Federal Tax Service of Russia.
4. Entrust control over the implementation of this order to the deputy head of the Federal Tax Service, who coordinates methodological and organizational support for the activities of the Federal Tax Service of Russia in implementing the Open Government project.
Regulations for the preparation and disclosure of publicly available information in open data format in accordance with the principles of openness
I. General provisions
1. These Regulations for the preparation and disclosure of publicly available information in open data format in accordance with the principles of openness (hereinafter referred to as the Regulations) determine the procedure for the preparation and disclosure of priority socially significant sets of open data on the official website of the Federal Tax Service (https://www.nalog. ru) in the information and telecommunications network “Internet” (hereinafter referred to as the Internet site).
2. The following basic concepts, terms and abbreviations are used in these Regulations:
a) Open data - publicly available information in open data format, as well as information containing information about the activities of the Federal Tax Service of Russia and posted on the Internet in accordance with Federal Law No. 8-FZ dated 02/09/2009 “On ensuring access to information about activities state bodies and local government bodies" in a format that allows automated processing without preliminary changes by humans (machine-readable format), for the purpose of repeated, free and free use;
b) Schedule - the schedule for disclosing priority socially significant data sets of the Federal Tax Service of Russia for the implementation of measures in the field of open data for 2017-2018 was approved by Order of the Federal Tax Service of Russia dated July 13, 2017 No. ММВ-7-17/549@ “On the organization of work on the implementation of measures in the field of open data in 2017 - 2018";
c) A set of open data - a set of homogeneous elements of machine-readable data and meta-information describing them;
d) Passport of an open data set - a set of information about a set of open data published on the Internet. The open data set passport format is given in the Methodological Recommendations for the publication of open data by state bodies and local governments, as well as the technical requirements for the publication of open data, approved by the minutes of the meeting of the Government Commission for the Coordination of Open Government Activities dated May 29, 2014 No. 4 (hereinafter referred to as the Methodological Recommendations ). Requirements for filling out the Open Data Set Passport are given in these Regulations;
e) Structure of the data set - description of the fields of the data set, as well as the type of information that is indicated in these fields;
f) External consumers - individuals, legal entities, foreign organizations, foreign structures without the formation of a legal entity, state extra-budgetary funds, the Central Bank of the Russian Federation, state bodies, local governments, foreign tax administrations, defined in the Policy of the Federal Tax Service of Russia in the field of quality of provision public services and implementation of government functions for 2015-2018, approved by order of the Federal Tax Service of Russia dated August 31, 2015 No. ММВ-7-17/371@.
3. Participants in the interaction in the preparation and placement of publicly available information in open data format are:
a) employees of structural divisions of the central office of the Federal Tax Service of Russia (hereinafter - the Central Office of the Federal Tax Service of Russia), responsible for providing publicly available information (hereinafter - the Information Provider);
b) employees of the structural unit of the Central Election Commission of the Federal Tax Service of Russia, coordinating the work on the generation of open data (hereinafter referred to as the Coordinator);
c) employees of the structural unit that organizes the provision of access to open data (hereinafter referred to as the Content Manager);
d) executor of the State contract (hereinafter referred to as the Technical Specialist).
II. Preparation and publication of publicly available information in open data format
4. Preparation of publicly available information in open data format is carried out according to the Schedule.
5. The information provider prepares the material to be provided in the form of open data and sends the Open Data Set Passport and the Data Set Structure to the Coordinator and Content Manager for approval.
6. The Coordinator and Content Manager check the Data Set Structure for errors and the ability to correctly convert the material into machine-readable Open Data Sets.
7. In case of incorrect preparation of the material, the Content Manager, within seven working days, sends a memo to the Information Provider with recommendations for improvement.
8. After agreeing on the Structure of the data set, the Information Provider sends the Technical Specialist materials for conversion into machine-readable data.
9. After converting the material into machine-readable data, the Technical Specialist transfers it to the Content Manager or uses automated tools to independently publish the Open Data Set.
11. In case of transfer of material to the Content Manager for publication, the Content Manager checks the submitted materials for correctness of input and within seven working days ensures publication on the Internet site in accordance with the Methodological Recommendations.
12. In the case of using automated tools for self-publication of an Open Data Set, the Technical Specialist controls such publication.
13. The information provider monitors the relevance of the open data set of the Russian Federation (https://www.data.gov.ru) published on the Internet site, on the Portal (hereinafter referred to as the Open Data Portal) in the area of its activities in accordance with periodicity determined by the Schedule for a given Open Data Set.
14. The Coordinator, in case of detection of an outdated Open Data Set posted on the Internet site or Open Data Portal, sends a memo to the Information Provider about the need to update the Open Data Set. In this case, the Information Provider is obliged to update the Open Data Set within two days from the date of receipt of the memo.
III. Features of publishing publicly available information in open data format and creating new Open Data Sets
15. Open data sets must be published on the Internet site, taking into account the requirements of the Open Data Portal for further automatic export.
16. Technical requirements for the presentation of Open Data Sets in electronic form are approved by the Methodological Recommendations.
18. The frequency of updates of Open Data Sets should not be less than once a year.
19. When creating new Open Data Sets, the Information Provider must provide a function for automatically uploading publicly available information in open data formats in the information systems of the Federal Tax Service of Russia, and also take this function into account when expanding the functionality of the information systems of the Federal Tax Service of Russia in accordance with the Temporary Recommendations for the formation, direction and consideration of requirements for AIS “Tax-3” software, approved on December 1, 2016 by Deputy Head of the Federal Tax Service of Russia A.S. Petrushin, mandatory for use from 01/01/2017 (sent by letter from the Information Technology Department dated 12/02/2016 No. 6-8-04/0454@).
20. Requests and proposals for the formation of new Open Data Sets are sent by external consumers to the Coordinator in any way that allows identifying the sender of the request and containing contact information of the external consumer for feedback purposes.
21. When receiving requests and proposals from external consumers for the formation of new Open Data Sets, the Coordinator redirects the requests and proposals to the Information Provider in the area of activity to provide a conclusion on the possibility of forming the specified Open Data Sets.
22. The information provider, within a week from the date of receipt of the request or proposal from the Coordinator, sends a conclusion to the Coordinator and Content Manager on the request submitted by the Coordinator and, if such Open Data Sets are ready to be formed, the information provider initiates the introduction of additions to the Schedule and is guided by these Regulations. Next, the actions described in the Regulations are performed.
Application
to preparation and disclosure
publicly available information in format
open data in accordance with
principles of openness,
approved by the Federal Tax Service of Russia
dated March 6, 2018 No. ММВ-7-17/125@
Open Data Set Passport
| № | Characteristic | Characteristic value |
|---|---|---|
| 1 | An identification number | The identification number is indicated in the format provided for by the Methodological Recommendations |
| 2 | Data set name | The name of the data set is indicated in the form in which the set is to be published, allowing one to determine the type of data contained in the set |
| 3 | Description of the dataset | A brief description of the data set is indicated, which should not repeat the name of the data set. The description of the data set should be simple, understandable and as informative as possible about the content of the information in the data set. |
| 4 | Dataset owner | Federal Tax Service of Russia |
| 5 | Responsible person | Indicate the full name and position of the person responsible for sending the application for posting the data set on the Internet site |
| 6 | Responsible person's phone number | The contact telephone number of the (full) responsible person indicated in the Passport is indicated. |
| 7 | Responsible person's email address | [email protected] mailbox address in Outlook, or another mail program intended for use by employees of the Federal Tax Service of Russia for the exchange of external data. |
| 8 | Hyperlink (URL) to the set | |
| 9 | Data Format | Specify the data format (csv, xml, etc.) |
| 10 | Description of the data set structure | For example, http://data.nalog.ru/opendata/7707329152-job/structure-20170614.csv |
| 11 | Date of first publication of the dataset | |
| 12 | Last modified date | The date is indicated in the format DD.MM.YYYY |
| 13 | Contents of last change | Indicates all changes that were made to the data set during a scheduled or unscheduled update of data, related or not related to a change in the structure of the data set |
| 14 | Relevance date | The date is indicated in the format DD.MM.YYYY |
| 15 | Keywords that match the content of the dataset | Several keywords are indicated that can help search for a data set on the Internet, as well as on the Internet site |
| 16 | Hyperlinks (URLs) to previous releases of the dataset | |
| 17 | Hyperlinks (URLs) to previous versions of the dataset structure | |
| 18 | Version of methodological recommendations | The version of the guidelines is indicated in X.0 format, where X is the serial number indicated in Arabic numerals |
Document overview
The procedure for preparing and disclosing publicly available information on the activities of the Federal Tax Service of Russia in the open data format has been improved.
Open data refers to publicly available information and information about the activities of the Federal Tax Service of Russia, posted on the official website of the Service (https://www.nalog.ru) in a format that allows automated processing without preliminary changes by humans (machine-readable format), for repeated, free and free use. use.
The features of publishing publicly available information in open data format and creating new sets of open data are determined. The frequency of updating open data sets is at least once a year.
