eid edocs the next possible steps Interoperability BE-AT-NL-PT

Transcription

1 edocs the next possible steps Interoperability BE-AT-NL-PT

2 building a demonstrator to experience in the cross-border reality to identify needs along with processes of the praxis including different styles of administration to contribute to the i2010 agenda

3 content of the presentation block intervention by MS proponents reflection by industry practical demonstration of the state of the play : ed

4 following the roadmap ADAPTING THE INFRASTRUCTURE Authentication Model & Levels Terminology 2008 Common Framework Definition of Equal Treatment of national s Role Management edoc Format Standard(s) EU provisions: Recognition of national s 2010 Federated Management Personal Data Ownership Model Recognitio n of edocs Permanent Document ID 2009 Long Term Archiving Model Long Term Archiving Guidelines MS rules on earchiving

5 potential contribution by demonstrators authentication model & levels definition of common framework personal data ownership model federated management edoc format standard(s) recognition of edocs

6 edocs capabilities To demonstrate technical feasibility To demonstrate practicability To demonstrate legal barriers Belgium Austria Netherlands Portugal

7 edocs capabilities To demonstrate formats and compatibility To demonstrate readiness To demonstrate legal barriers Austria Belgium Netherlands Portugal

8 A DEMONSTRATOR Belgium ANY companies and technologies liberty alliance, infocard,.. Austria

9 Description of and edoc Methods of generation Scope of applicability Methods of verification STANDARD CATEGORY limitations STANDARD CATEGORY FORMAT SIGNATURE VALIDITY limitations egovernment APPLICATION

10 HUMAN MOBILITY (moving into XXXX) Documents needed Identification needed Process compatibility Process interlinking Interoperability Model Standards and Tools

11 HUMAN MOBILITY (foreign study) Documents needed Identification needed Process compatibility Process interlinking Interoperability Model Standards and Tools

12 example BE AT ID-Token is not affected by interoperability Sign agreement Generate transformation from Belgium into Austrian with consent of the citizen HIDDEN PROCESS Application is not affected by interoperability LEGAL AGREEMENTS? TECHNICAL INTEROPERABILTY?

13 example AT BE ID-Token is not affected by interoperability Sign agreement???? Generate BE-SECTORID Generate transformation from Austrian into Belgium with consent of the citizen HIDDEN PROCESS Application is not affected by interoperability LEGAL AGREEMENTS? TECHNICAL INTEROPERABILTY?

14 Goal i2010 To identify obstacles To produce showcases To communicate interoperability To experience levels of security To elaborate and communicate todos

15 focus on very few models AT-model with sectoral PIN PROXY model for easo of implementation

16 POTENTIAL SHOWCASE interoperability at user environment USER IN CONTROL User User environment INTEROP PIN UNIQU E Token Service Service TRANSBORDER member state member state

17 POTENTIAL SHOWCASE interoperability proxy USER IN CONTROL TRANSBORDER User PI N User environme nt TRUSTWORTHY PROXY INTEROP SERVICE Token of PROX Y UNIQ UE member state member state Servic e

18 Starting Points the Microsoft Infocard concept the Liberty Alliance approach mobile phone access technology RFID crypto elements as Dataprotection and Acceptance......

19 edocs and where we srtand XML is emerging as a standard ODT, DOCX :: convergence still an issue esignatures are built in in both ODT and DOCX according to the same principle Useful abstactions are on the way (XHTML) First practical approaches with OFFICE 2007 OpenOffice 2.0

20 example Office 2007 sign a document (official signature) use BE, IT, FI,EE, AT Card

21 Demo Sign an XML Doc MS OFFICE 2007 Bürgerkarte