This document discusses e-documents and their role in electronic services in Europe. An e-document carries information and supports functions to process and present that information to end users. It can be considered both as information and as a service. The document outlines producer and consumer workflows for basic e-document use cases. Producers structure documents, transform them to exchange formats, add metadata and rules, secure them with signatures and encryption, and send them in e-containers. Consumers receive the documents, validate and acknowledge them, and then process the metadata, rules, data and information. The document was presented at a conference to discuss potential applications of e-documents across different domains.

1. 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 <radu@rotld.ro>
IT architect and e-Document Task Force leader
http://wiki.ds.unipi.gr/display/ESENS/SAT-+eDocument

2. 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’.

3. e-Document mind-map

4. Profiling and implementing
EIRA Solution Architecture Template
Solution Architecture
Application Component
Profiling
Implementing

5. From architecture to solution - workflow

6. 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;

7. e-Document with e-Delivery

8. 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