Differences

This shows you the differences between two versions of the page.

Link to this comparison view

en:znalostni_baze:ga_ppdf [2021/06/04 14:56] – created Tomáš Šedivecen:znalostni_baze:ga_ppdf [2021/07/07 15:27] (current) – Tomáš Šedivec
Line 37: Line 37:
 Figure 1: Data distribution and exchange scheme Figure 1: Data distribution and exchange scheme
  
-{{media/image1.png?480x215}}+{{ :znalostni-baze:ga_ppdf1.png?600 |Figure 1: Data distribution and exchange scheme}}
  
 Within each agenda, the following types of data are maintained about the entities in each role (context) in terms of the linked data pool: Within each agenda, the following types of data are maintained about the entities in each role (context) in terms of the linked data pool:
Line 89: Line 89:
 Figure 2: Data exchange schema Figure 2: Data exchange schema
  
-{{media/image2.jpg?480x388}}+{{ :znalostni-baze:ga_ppdf2.jpg?600 |Figure 2: Data exchange schema}}
  
 This schema, with the necessary simplification, lays down the rules for creating and sharing data and for its subsequent maintenance by means of complaints. This schema, with the necessary simplification, lays down the rules for creating and sharing data and for its subsequent maintenance by means of complaints.
Line 177: Line 177:
 Figure 3: Illustrative diagram of the use of digital eGovernment services by natural persons Figure 3: Illustrative diagram of the use of digital eGovernment services by natural persons
  
-{{media/image3.png?508x411|cid:image003.png@01D61721.B4167AA0}}+{{ :znalostni-baze:ga_ppdf3.png?600 |Figure 3: Illustrative diagram of the use of digital eGovernment services by natural persons}}
  
 ==== Subject of the law - legal entity and natural person in business ==== ==== Subject of the law - legal entity and natural person in business ====
Line 199: Line 199:
 Figure 4: Illustrative diagram of the use of Linked Data data from a clerk's perspective Figure 4: Illustrative diagram of the use of Linked Data data from a clerk's perspective
  
-{{media/image4.png?442x488|cid:image004.png@01D61721.B4167AA0}}+{{ :znalostni-baze:ga_ppdf4.png?600 |Figure 4: Illustrative diagram of the use of Linked Data data from a clerk's perspective}}
  
 ==== Technical Administrator of the Agenda Information System ==== ==== Technical Administrator of the Agenda Information System ====
Line 225: Line 225:
 Figure 5: View of the future state of PPDF in terms of its components, services, actors, HW and SW technologies and physical interconnection Figure 5: View of the future state of PPDF in terms of its components, services, actors, HW and SW technologies and physical interconnection
  
-{{media/image5.emf?604x720}}+{{ :znalostni-baze:ga_ppdf5.jpg?600 |Figure 5: View of the future state of PPDF in terms of its components, services, actors, HW and SW technologies and physical interconnection}}
  
 ==== View of the business logic and data extraction of VS agendas ==== ==== View of the business logic and data extraction of VS agendas ====
Line 233: Line 233:
 Figure 6: Viewing the future state of the PPDF from the perspective of the right holder Figure 6: Viewing the future state of the PPDF from the perspective of the right holder
  
-{{media/image6.emf?604x331}}+{{ :znalostni-baze:ga_ppdf6.jpg?600 |Figure 6: Viewing the future state of the PPDF from the perspective of the right holder}}
  
 ==== View of the business logic from the perspective of the rights holder ==== ==== View of the business logic from the perspective of the rights holder ====
Line 241: Line 241:
 Figure 7: Viewing the current state of PPDF from the perspective of the rights holder Figure 7: Viewing the current state of PPDF from the perspective of the rights holder
  
-{{media/image7.emf?604x404}}+{{ :znalostni-baze:ga_ppdf7.jpg?600 |Figure 7: Viewing the current state of PPDF from the perspective of the rights holder}}
  
 ==== Relationship between PPDF and VDF ==== ==== Relationship between PPDF and VDF ====
Line 354: Line 354:
   * Enabling context management (creation, modification, deletion)   * Enabling context management (creation, modification, deletion)
  
-{{media/image8.png?604x301|eGov ref L0 interface}}+{{ :znalostni-baze:ga_ppdf8.png?600 |}}
  
 ==== Reference interface design ==== ==== Reference interface design ====
Line 822: Line 822:
 Before using ISSS, the reader must first determine the context and its XSD schema, which will be used to receive query responses in ISSS. Therefore, he must first call a special 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 agency.  Before using ISSS, the reader must first determine the context and its XSD schema, which will be used to receive query responses in ISSS. Therefore, he must first call a special 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 agency. 
  
-Figure 8: View of the integration platform interfaces+Figure 9: View of the integration platform interfaces
  
-{{media/image9.png?600x294|C:\Users\sedivect\AppData\Local\Microsoft\Windows\INetCache\Content.MSO\42CD6D36.tmp}} +{{ :znalostni-baze:ga_ppdf9.png?600 |Figure 9: View of the integration platform interfaces}}
  
 === IS interface for batch data exchange === === IS interface for batch data exchange ===
Line 942: Line 942:
   - Assisted filing: In assisted filing at the counter, the relevant staff member will make a present identification against the document and, if acting on behalf of the subject at the counter, will use the relevant services to do so. If he/she is then acting on behalf of the OVM, again when enrolled in the AIS, this AIS will call the one-time translation service of the liaison identifier to the AIFO.    - Assisted filing: In assisted filing at the counter, the relevant staff member will make a present identification against the document and, if acting on behalf of the subject at the counter, will use the relevant services to do so. If he/she is then acting on behalf of the OVM, again when enrolled in the AIS, this AIS will call the one-time translation service of the liaison identifier to the AIFO. 
  
-Figure 9: View of identifiers in VS+Figure 10: View of identifiers in VS
  
-{{media/image10.png?649x538|C:\Users\sedivect\AppData\Local\Microsoft\Windows\INetCache\Content.MSO\AAC5E6B4.tmp}} +{{ :znalostni-baze:ga_ppdf10.png?600 |Figure 10: View of identifiers in VS}} 
  
 ====== Linked Data Pool Standardization ====== ====== Linked Data Pool Standardization ======
Line 1084: Line 1084:
 The process of updating data published on the reference interface is based on a general architectural schema describing the principle of operation of the linked data pool. The process of updating data published on the reference interface is based on a general architectural schema describing the principle of operation of the linked data pool.
  
-Figure 10: Working principle of the Linked Data Pool+Figure 11: Working principle of the Linked Data Pool
  
-{{media/image11.png?415x147}}+{{ :znalostni-baze:ga_ppdf11.png?600 |Figure 11: Working principle of the Linked Data Pool}}
  
-{{media/image12.png?419x28}}+{{ :znalostni-baze:ga_ppdf11.1.png?600 |}}
  
 Two key roles are defined in this process: Two key roles are defined in this process:
Line 1262: Line 1262:
 In line with the overview architecture, there is a technical separation of services for extracting changes to reference data held in the RoW and changes to data held in other ISVs (AIS<sub>publishers</sub>). In line with the overview architecture, there is a technical separation of services for extracting changes to reference data held in the RoW and changes to data held in other ISVs (AIS<sub>publishers</sub>).
  
-Figure 11: Illustrative use of the mechanism for data in ROB+Figure 12: Illustrative use of the mechanism for data in ROB
  
-{{media/image13.png?604x273}}+{{ :znalostni-baze:ga_ppdf12.png?600 |Figure 12: Illustrative use of the mechanism for data in ROB}}
  
 === PUSH === === PUSH ===
Line 1272: Line 1272:
 When data is changed, the change information for a specific recipient is passed to the reference interface. Endpoints are maintained within the ISSS reference interface for sending notifications to individual readers. When data is changed, the change information for a specific recipient is passed to the reference interface. Endpoints are maintained within the ISSS reference interface for sending notifications to individual readers.
  
-{{media/image14.png?604x273}}+{{ :znalostni-baze:ga_ppdf13.png?600 |}}
  
 ==== Subscribe to changes ==== ==== Subscribe to changes ====
Line 1425: Line 1425:
 The process of claiming data published on the reference interface is based on a general architectural schema describing the principle of operation of a linked data pool. The process of claiming data published on the reference interface is based on a general architectural schema describing the principle of operation of a linked data pool.
  
-Figure 12: The process of claiming data published on the reference interface+Figure 14: The process of claiming data published on the reference interface
  
-{{media/image15.png?372x104}}+{{ :znalostni-baze:ga_ppdf14.png?600 |Figure 14: The process of claiming data published on the reference interface}}
  
-{{media/image16.png?362x30}}+{{ :znalostni-baze:ga_ppdf12.1.png?600 |}}
  
 The data claim process is initiated when the "official", while executing an agenda, finds that the value of the data, which was obtained by reading it through the reference interface, does not correspond to reality. The data claim process is initiated when the "official", while executing an agenda, finds that the value of the data, which was obtained by reading it through the reference interface, does not correspond to reality.
Line 1453: Line 1453:
 The linked data pool allows a completely unambiguous definition and identification of individual data in the form of XSD regulations held in the Register of Rights and Obligations pursuant to Section 54(1)(c) of Act 111/2009 on the Basic Registers. When presenting these data, it is therefore necessary to define how they will be placed on the form, what description, limitations, etc. they will have. This task is addressed by the W3C Recommendations for XSL Transformation (XSLT) in the current version 3.0 (https://www.w3.org/TR/xslt-30/). The linked data pool allows a completely unambiguous definition and identification of individual data in the form of XSD regulations held in the Register of Rights and Obligations pursuant to Section 54(1)(c) of Act 111/2009 on the Basic Registers. When presenting these data, it is therefore necessary to define how they will be placed on the form, what description, limitations, etc. they will have. This task is addressed by the W3C Recommendations for XSL Transformation (XSLT) in the current version 3.0 (https://www.w3.org/TR/xslt-30/).
  
-{{media/image17.png?480x357}}+{{ :znalostni-baze:ga_ppdf15.png?600 |}}
  
 XSLT 3.0 is a language designed to transform XML documents into other representations. Thus, the definition of a form is the setting of rules for transforming the individual contexts (XML documents) that contain the data appearing on the corresponding form. The form thus defined is then uniformly interpreted (represented) when it is used. XSLT 3.0 is a language designed to transform XML documents into other representations. Thus, the definition of a form is the setting of rules for transforming the individual contexts (XML documents) that contain the data appearing on the corresponding form. The form thus defined is then uniformly interpreted (represented) when it is used.