INTEROPERABILITY

Marko Ambrož, MPA www.mju.gov.si

Ohrid 2007

From the year 2001

• eGov Interoperability model v1.0 2001 (arhitektura in infrastruktura e-Uprave)

– Based on service definition for access reference registers,

– Used by eGov applications ,– Platform independent (MS Win servers, Linux, Unix),– Open standards (http, https, JDBC, XML),– J2EE infrastructure (Oracle IAS 10g, IBM Websphere

v6.1),– Infrastructure for relational database (Oracle 10g)- Backup center (database replications, test environment)

“tipical service model”

Model tipičnega baznega modula

Vhodni podatki:Ključ - poizvedbenipodatki,Kdo,Od kod,Zakaj.

Izhodni podatki:Atributni podatki

Vmesnik

Servis Servis

Dnevnik ZBIRKA

Vpis Vpis

Tabele zbirke

Varnostna shema

zahteva

odgovor

App. Interface Database and stored procedure

jdbc

eGov Interoperability Model v1.0 2001

- All present eGov app based on InterOp v1.0,

- No formal aproval by gov.,

- De facto standard,

- Used as Tech. Specs. in tenders and are obligatory for developers,

- Today the only way to access reference registers,

- Used as basic principle for access app. own databases,

- 6 years of experience, - Mature design, - Mature and proven services,

SJU – eGOV services – formular generator

SJU – eGOV services – formular generator -2

Metaregister

MediaWiki

MediaWiki – NIONational Interoperability Framework

• Uvod NIO Namen in cilji NIO • Načela delovanja Opis in objava načel delovanja • Pravna podlaga Objava pravne podlage za dostop do evidenc • Katalog storitev NIO Priprava kataloga storitev NIO • Dogovori Objava dogovorov, ki urejajo razmerja med organi • Postopki Objava postopka in pravil za vključitev novega organa • Avtentikacija Opis in objava podprtih načinov avtenikacije • Avtorizacija Objava pravil za določitev dostopnih pravic • Varnostne zahteve Opis varnostnih zahtev • Katalog javnih evidenc Objava postopka upravljanja s katalogom • XML sheme Določitev postopka za objavo XML shem • Standardi Objava tehničnih, semantičnih in organizacijskih standardov • Semantična orodja Določitev potrebnih semantičnih orodij • Integracije Opis povezovalnih mehanizmov za integracijo • Poizvedbe v evidencah Določitev postopka poizvedb • Posredovanje sprememb Določitev postopka za izvajanje posredovanja sprememb • Revizijske sledi Določitev revizijskih sledi • Centralni nadzor Določitev postopkov in nivoja nadzora • Osnovni gradniki CIS Določitev osnovnih funkcionalnih gradnikov • Povezava z EU Objava postopka za integracijo Pan-evropskih storitev • Certificiranje Določitev postopka za preverjanje skladnosti uporabnika z NIO

MediaWiki – IVPInformation Security Policy

1. Uvod in krovna politika upravljanja z informacijsko varnostjo

2. Politika fizičnega varovanja, varovanja v zvezi z osebjem, zaščite delovnega mesta, varovanja opreme

3. Politika zaščite osebnih podatkov in zagotavljanja zaupnosti

4. Politika primerne rabe informacijskih sistemov 5. Politika upravljanja z dokumenti, procesi in arhivi

6. Politika naročanja storitev pri zunanjih izvajalcih

7. Politika upravljanja s produkcijo, politika upravljanja neprekinjenega poslovanja in politika izdelovanja, preverjanja in hranjenja varnostnih kopij 8. Politika upravljanja in nadzora omrežja

9. Politika razvoja in vzdrževanja aplikacijskih sistemov, obvladovanja sprememb in dodeljevanja in nadzora dostopov 10. Politika zagotavljanja skladnosti delovanja z IVP

11. Politika zagotavljanja neprekinjenega poslovanja, vzpostavitev po nesreči

Future developements

• Public tenders:– National Interoperability Framework (Portal)– Pilot for CIS – Full CIS implementation

http://www.mju.gov.si/si/javna_narocila/

"Common Assessment Method for Standards and Specifications"

• Please could you send me your own relevant documents on this topic:– Assessment methods, – list of Criteria, – Standards,– Specifications,– Classification, …)

coming from national or even regional and local level.

NAŠ ODGOVOR

–Assessment methods,

(NE POSTOJI)

–list of Criteria,

(NE POSTOJI)

–Standards,

(SAMO ZA RAZMJENU DOKUMENATA)

–Specifications,

(NE ZVANIČNO – POSTOJEČA INFRASTRUKTURA )

–Classification, …)

(PO UREDBI O OFFICE AUTOMATION)

Non revisable document format

Adoption, by ISO/TC171-SC2 (Documentmanagement applications –Application issues) of ISO 19005: "Document management – Electronic document file format for long term conservation – Part 1, Use of PDF 1.4 (PDF/A1)"12. PDF/A is a non-revisable document format that can be used for documents that need no further processing or edition.

While there are plenty of products capable of displaying PDF/A products, there are only few products that can generate documents in PDF/A format on the market today.

Revisable document format

In May 2005 OASIS adopted an XML-based open document specification.OASIS offered this specification for international standardisation via the ISO"fast track" procedure in November 2005. On 30 November 2006, theISO/IEC standard for an "Open Document Format for Office Applications"(ISO/IEC 26300) has been published. A growing number of productssupporting the standard are becoming available.

Microsoft has adopted a “pure” XML format to be used with the Office product suite and submitted its OpenXML specification to ECMA9 inDecember 2005. Work in the relevant technical workgroup has finishedand the ECMA International General Assembly has approved the result of itswork. ECMA will offer the specification for international standardisation viathe ISO "fast track" procedure. This standardisation effort gives competitorsof Microsoft the possibility to include support of the OpenXML documentformat in their products.

http://ec.europa.eu/idabc/en/document/6227

Context of the revision Taking into account the progress made in this area, the rapid evolution of the technology and the wish to come to a document that will no longer be limited to the IDABC context, the process to prepare a second version of the EIF document has started. This second version will be written in close collaboration with the relevant Commission services and with the Member States. Other, indirect stakeholders will be given the opportunity to provide their input. This second version is expected to be ready in 2008. The second version of the European Interoperability Framework will take into account the national interoperability frameworks and related activities that today either already exist in the Member States or are being prepared.

IDAbc – EIF 1.0

The present document establishes the EuropeanInteroperability Framework (EIF) to support the pan-European delivery of electronic government services.In particular, it will be the reference document oninteroperability for the IDABC programme2.The documentrepresents the highest-ranking module of acomprehensive methodological tool kit for implementingpan-European eGovernment services. Itwill be further developed parallel to the progressand the emerging requirements of pan-Europeaninfrastructures and services.

AGThe Architecture Guidelines are designed to support the Interoperability Decision

goals, by providing:• architectural principles to ensure a coherent, generic services-based approach to developing

trans - European telematics networks;• guidance on how to use generic services and common tools as soon as these are made

available by the IDA and IDABC programmes to the EU user community.

The direct benefits of having a clearly defined architecture comprise:

• improved inter-operability between the IT and networks systems of business partners;• continued autonomy of the business partners to select the architecture for their IT solutions,

and to develop it, without being dependent on the architecture at the community level;• continued autonomy of business partners to select the service provider who can implement

the concepts and components that comply with the Architecture Guidelines, thus providing controlled, secured, managed, transparent and easy access to the common trans-European Services.

The Architecture Guidelines should be used as reference material whenever procuring or implementing services that access the trans-European Services, or as a technical framework for the achievement of generic services. Using IDA and IDABC generic services on a common architecture will:

• reduce costs thanks to reusability and economy of scale;• shorten the implementation time of new projects;• improve manageability of projects and of the implemented solutions;• set a clear migration path for existing, heterogeneous projects;• leave Administrations to concentrate on their core business applications.

National interoperability frameworks • Belgium• http://www.belgif.be • Denmark• http://standarder.oio.dk/English/• Estonia• http://www.riso.ee/en/information-policy/interoperability • France• http://synergies.modernisation.gouv.fr/rubrique.php?id_rubrique=1• Germany• http://www.kbst.bund.de/cln_012/nn_837392/SharedDocs/Meldungen/2006/saga__3__0.html• Ireland• http://www.reach.ie/technology/interoperability.html• Malta• http://ictpolicies.gov.mt/docs/cimu_t_0001_2002.pdf• Netherlands• http://www.e-overheid.nl/atlas/referentiearchitectuur/• http://www.e-overheid.nl/data/files/architectuur/E-government_in_the_Netherlands.pdf  • Spain• http://www.csi.map.es/csi/pg5c10.htm  • Sweden• http://www.verva.se/shs and http://www.verva.se/framework • United Kingdom• http://www.govtalk.gov.uk/schemasstandards/egif_document.asp?docnum=949 •