session 1. e-documents

8
e-SENS Electronic Simple European Networked Services e-Document roadmap - from architecture to solution Making e-services a reality in Europe, 6-7 November 2014, Luxembourg Radu Boncea <[email protected]> IT architect and e-Document Task Force leader http://wiki.ds.unipi.gr/display/ESENS/SAT-+eDocument

Upload: e-sens-project

Post on 13-Jul-2015

67 views

Category:

Government & Nonprofit


0 download

TRANSCRIPT

e-SENS Electronic Simple European Networked Services

e-Document roadmap - from architecture to solution

Making e-services a reality in Europe, 6-7 November 2014, Luxembourg

Radu Boncea <[email protected]>

IT architect and e-Document Task Force leader

http://wiki.ds.unipi.gr/display/ESENS/SAT-+eDocument

An e-Document is any electronic document, structured or unstructured, which supports various formats and it is supporting functionality that fulfils a set of generic, domain or use case specific requirements.

Thus an e-Document carries information as payload and supports functions to be used in processing and presenting the information to the end-user, functions exposed as e-Document services. Therefor we may refer to e-Document as ‘e-Document as information’ or ‘e-Document as a service’.

e-Document mind-map

Profiling and implementing

EIRA Solution Architecture Template Solution Architecture

Application Component

Profiling

Implementing

From architecture to solution - workflow

Basic generic use case

Producer workflow 1. Providing the document:

• structure and describe the document using semantic tools; • tranform to agreed exchange format; • add annotations or free text to data level in the document; • add processing rules;

2. Secure the document: • attach timestamps and signatures; • encrypt the document;

3. Send the document: • validate the document and resulted metadata files; • package the document and the metadata files into an e-

Container format; • send the document to the document consumer using an

electronic delivery solution;

Consumer workflow 1. Receive the document:

• unpack the document; • validate the document and the metadata files; • acknowledge the reception of the document;

2. Process the document: • process metadata and rules; • process data and information;

e-Document with e-Delivery

Questions to the panel

To panel:

• What do you need e-Document for?

• What functionality from e-Document you see as valuable for your domain activity?

• Where it can fail?

To audience:

• Do you see potential for e-Documents in your domain?

11/11/2014 e-SENS General Assembly, Country x 8