|Facts||Owner||Estonian Information System’s Authority|
|Target Audience||- National public administrations
- European public administrations
- Private sector
- IT practitioners
|Assets||- 10 + XML schemas and ontologies
- 600 information system descriptions
- 40.000 data objects
-650 code lists
- 2.500 Service descriptions
|Federation Benefits||Expected Benefits||- Stay in the forefront e-Government system development in Europe
- Larger visibility
- Explore and find projects in other countries
|Mapping to ADMS||Language||Estonian|
|Licence||Licence metadata not yet available.|
|Export of Metadata||Format||ADMS RDF|
|Transmission to Joinup||Transmission Protocol||- Web service (solution 1);
- or email (solution 2);
- or upload via a form (solution 4).
Interview with RIHA
Priit Parmakson (Estonian Information System’s Authority – Estonia) is responsible for the international dimension of the Estonian semantic asset repository RIHA (Riigi Infosüsteemi Haldussüsteem). As an analyst in the RIHA team he is closely involved in day-to-day operation as well as strategic developments of the repository. His scientific interests include architectures of large systems, and ecology of machine and human languages. RIHA is expected to join the ADMS-enabled federation of semantic asset repositories in June 2012.
Joinup team: Which types of assets does RIHA have and which ones will be shared with the ADMS-enabled federation on Joinup?
Priit Parmakson: RIHA contains a large number of assets of different asset types: international standards, XBRL schemas, metadata standards, web services, code lists... RIHA also has some XML schemas but there are very few of them. Initially, we will only share the description metadata of the code lists with the federation. These semantic assets are the most reusable. RIHA also has a large collection of Web Service descriptions. These are likely to be less relevant to parties that do not participate in the X-Road data exchange. Therefore we prefer not to share these asset types with the federation in a first stage.
Joinup team: Which benefits do you see from joining the federation?
Priit Parmakson: By joining the first wave of the federation we want to stay in the forefront of e-Government system development in Europe. The main benefit we hope to get from it is a larger visibility of RIHA and its semantic assets. Currently RIHA is quite isolated and used in Estonia only. However it holds many assets that we think could be of use in other EU Member States. By joining the federation and sharing the description metadata of our code lists we hope that they can be more easily found by an international audience. Similarly, we hope to be able to explore and find initiatives and semantic assets in other countries.
Joinup team: Does every code list in RIHA have a URL that is publicly accessible?
Priit Parmakson: The ADMS specification requires a permanent URI and access URL for every semantic asset. In RIHA, every code list has an individual URL that contains the asset’s short name so it is short and human readable. We will use this URL as a URI and access URL for the assets.
Joinup team: Can the ADMS-enabled federation on Joinup use machine translation techniques to translate Estonian description metadata?
Priit Parmakson: The name and description of the assets will naturally be in Estonian. We are interested to evaluate the results of a machine-translation of these descriptions to English on Joinup. This can certainly improve accessibility of the RIHA repository to EU citizens who do not speak our language.
Joinup team: Is there any provision on license information on assets on RIHA?
Priit Parmakson: For the moment there is no licensing information on the assets. In Estonia, users generally do not require this information, but we understand that this information can be relevant to the international users on Joinup. One aspect of reusability is indeed the knowledge that what is on Joinup can be reused without copyright infringements under the conditions of an explicit licence. For that reason the necessary licensing information will be provided on the code lists that we will expose to the federation. We are planning on using the Creative Commons license as a base.
Nature of documentation: Other