Context eGSB/ISSS

Each agenda is defined by the relevant legislation. Within the agenda, the data necessary and specific for its execution are kept on subjects and objects. These data can also only be recorded on the basis of the relevant legal provisions. Subjects and objects are dealt with within an agenda in a certain context (given by legislation), i.e. subjects and objects are understood in a certain 'context' within the performance of that agenda. These contexts differ in the execution of different agendas, which is reflected, inter alia, by the fact that different objects are dealt with in relation to subjects in different agendas and different data are recorded and, where appropriate, exchanged on subjects and objects. We can therefore say that the context:

determines the legal status of the entity (subject or object) within the agendas and

the specific data (attributes) of the entity defined in the agenda are associated with it.

Methodologies for creating contexts address the detailed process

Methodology for context creation

Methodology for implementing a new context for a subject or object of a right transmitted via eGSB/ISSS

The context creation methodology introduces two levels of context - technical and conceptual. The technical level of context consists of an XSD schema that defines the syntax of the XML messages in which the shared data is expressed. In particular, to use eGSB/ISSS services for a linked data pool, it is necessary to know:

The agency from which the reader wants to use the data,

The agenda that the reader is executing and in which the data is read,

The context for querying the data from the publishing AIS.

Before using eGSB/ISSS, the reader must first determine the context and its XSD schema according to which it will receive query responses in the eGSB/ISSS services. Therefore, he must first call a special eGSB/ISSS service to read the Context Catalog, in which he then finds out which context he must call to get the data from the providing agenda.

Conceptual Context Models

The conceptual level of a context consists of a conceptual model that defines the semantics (meaning) of a context by describing its semantic (meaning) links to other contexts maintained within the same agenda, as well as in other agendas, and by describing its semantic links to the public administration ontology. The ontology of public administration defines the basic concepts of public administration that exist across the legal order of the Czech Republic and the semantic links between them. Examples of such concepts are subject of law, object of law, natural person, legal person, etc.

The ambition of the conceptual model of the context is not to model the real world, but its abstraction describing the subjects and objects of data, data about them and the relationships between them as they are defined in the legislation and as they are understood in the given agenda. The conceptual model is derived from the general meanings defined in the ontology of public administration, it takes over, specialises and extends these and redefines them if necessary. The elements of the conceptual model are linked to the corresponding legislative provisions from which they derive. As the conceptual model of context is linked to the conceptual models of related contexts and to the ontology of public administration, it is itself an ontology. The set of conceptual models of all contexts then forms an ontology describing

the subjects and objects of law,

the contexts in which they exist,

the data held about them in the contexts

the semantic relationships between them

This forms a conceptual semantic map of the data held by the public administration.

List of contexts

A detailed list of contexts is available at https://egsbkatalog.cms2.cz/. This list is only available from the CMS/KIVS network, not from the public internet.

Order	Code	Name
1	A1029.1	Insured
2	A1029.2	Self-employed
3	A1029.3	Employer
4	A1029.4	Territorial organizational unit
5	A1046.1	Driver's licence holder - documents for applying for a driving licence
6	A1046.2	Driver - application for driving licence
7	A1046.RidicRozsirene	Driver - extended data
8	A1046.RidicBasic	Driver - basic data
9	A1046.RidicBasic	Driver - basic data
10	A1061.1	NBU Avizace
11	A121.1	Authenticated Person Data Overview
12	A121.2	List of business entity data
13	A124.1	ISKN - Record of rights for a person
14	A124.2	ISKN - Certificate of Ownership
15	A1341.1	Insurer's Certificate of Insurance
16	A1341.2	OSVC PP notice
17	A1341.3	OsVC PP ZP notification
18	A1341.4	List of OSVC PP
19	A344.1	Notification via Citizen Portal
20	A3726.1	Patient
21	A385.1	Notification of OSVC PP
22	A385.2	List of OSVC PP
23	A392.1	Debtor
24	A392.2	ODU
25	A4003.1	Health Service Providers
26	A4003.2	Patient medical records
27	A418.1	Person under investigation
28	A418.2	Vehicle under investigation
29	A418.3	NBU Lustration
30	A483.1	Criminal Records Bureau