Pettenati_IESS_Geneva
•
1 like•274 views
Presentation of the talk given IESS 1.1 Second International Conference on Exploring Services Sciences IESS 1.1: 16-17-18 February 2011, Geneva, Switzerland http://iess.unige.ch/
![Outline ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (6)
Viewers also liked
Viewers also liked (8)
Similar to Pettenati_IESS_Geneva
Similar to Pettenati_IESS_Geneva (20)
Recently uploaded
Recently uploaded (20)
Pettenati_IESS_Geneva
- 1. e-profile Basic e-Service Maria Chiara Pettenati Electronics and Telecommunications Department University of Florence - Italy Creation & Management as a for Netizens and Service Providers
- 3. Future Service Scenario RISEPTIS Advisory Board February 2010
- 4. Theresa and Jorge
- 5. e-ID card containing health insurance profile
- 6. Smart Dentist Visit
- 8. A very modern holiday
- 11. source: RISEPTIS Report February 2010
- 12. Architecture Problem “The Internet was not designed with any way to know who you are dealing with and who you are connecting to” Kim Cameron
- 13. “ Patchwork quilt of kludges” Kim Cameron
- 14. Architectural approach to e-Profile management
- 16. Middleware providing the services needed for collaboration-oriented granular data management in a Web-wide distributed environment
- 17. Web infrastructure Manage granular Data units Structure Data Into Documents Provide collaboration oriented capabilities Trust-enabling Infrastructure Requirements
- 18. IDN main building elements
- 24. Infrastructure can ground the e-profile basic service
- 27. e-profile Basic e-Service Maria Chiara Pettenati Electronics and Telecommunications Department University of Florence - Italy Creation & Management as a for Netizens and Service Providers http://www.interdatanet.org
Editor's Notes
- The next ten minutes are organized around the four following topics: Point 1) Illustration of some future service scenario which serve to motivate Point 2) that is the emerging need to consider the e-profile as a basic e-service The architectural approach to it, which is InterDataNet at Point 3) And eventually the reason of my being here today – insipire some actions and share ideas inside the emerging Service Science community –at Point 4).
- Future Service Scenarios are drawn from those recently published in the RISEPTIS report “Trust in the Information Society”. RISEPTIS stands for Research and Innovation on Security, Privacy and Trustworthiness in the Information Society and it is an advisory board of the European Commission. The report was publicly presented one week ago by the Advisory Board in Spain
- Theresa, Jorge and Helena – Theresa’s beloved grandmother – are the three characters of the scenarios. T. & J. are a young couple of digital natives, living in London in a not-so-distant future.
- In the first scene of their story, J. goes to the online ID card governmental service to renew his e-ID card. He chooses the option to store on the card also his health insurance profile. He can thus avail of a lot of interesting services such as..
- Reserving a long overdue dentist visit. He chooses a nearby dentist from the related web service system, and makes the reservation. He decides also to disclose to the dentist his “dental records” from his health profile stored on his e-ID card in order to save time and money and not redo the whole set of x-rays.
- In the meanwhile, gentle Theresa goes for a retail-therapy in the local shopping center. As soon as she enters the Mall, she is localised and identified thanks to the set of devices and RFID readers she carries on (mobile device and chlothes’RFID). After few minutes she receives a personalized message on her phone offering reduction inside the store.
- The nice couple decides to take a quick break and books a last minute flight to Rome. Since they don’t have the time to book the accommodation in advance, the Global Hotel Service sends them a message when they are in the airport, waiting for boarding. They thus fill in their preferences as regards both hotel as well as food. When they arrive in Rome they receive a message containing a customized list of hotels, restaurants and, after having made their choice, they are informed that a courtesy car is on its way to pick them up from the airport.
- In the last scene of this story, we see old grandmother Helena feeling a bit lonely at home. Since she had health monitors installed in her home , her family members don’t call to check on her as often as they used to. Helena uses RFID scanners on her fridge and cupboard to manage her grocery shopping. She can thus benefit of a weekly home delivery service. Helena also enjoys the online health service portal to manage regular checkups, allowing the disclosure of her home-monitored health data, as well as her food items consumption data.
- So what? The moral of the story is that we will all use more and more online services and – as Kim Cameron said – we use our digital identity more and more as an input device of the digital world to obtain service in general and service personalization. E-profile as a basic transversal e-service, allowing “digital self” management in all domains, e-health, e-gov, e-comm, as seen before.
- Trust, security, privacy, trustworthiness, accountability, transparency, data policy and governance….
- If the idea of an e-profile as a basic service is not completely new, what is new is that the Internet architects are starting to recognize that there is an architectural problem grounding this issue. Again quoting Kim Cameron’s word, “The Internet was not designed to…” Kim Cameron is the Chief Architect of Identity in the Identity and Security Division at Microsoft
- This term is diversely used in fields such as computer science , A kludge (or kluge ) is a workaround , a quick-and-dirty solution, a clumsy or inelegant, yet effective, solution to a problem, typically using parts that are cobbled together.
- What we are looking for is an architectural approach to e-profile management…
- … and InterDataNet represents a possibile path for this quest
- IDN is a web architecture which seeks to adopt by design a set of trust-enabling requirements. Manage granular data units Globally address them Structure data in documents to which apply workflows -> make services Provide collaboration-oriented capabilities Trace, replicate, make history, … Responisibility, trust, security, privacy, trustworthiness, accountability, transparency, data policy and governance…. At an infrastructural level Simple API (alleggerire lato applicativo) trust-enabling at a system level
- The IDN framework is defined by three entities: IDN-IM ( IDN Information Model ): is the shared information model representing a generic document model IDN-SA ( IDN Service Architecture ): is the architecture handling documents IDN-IM. It exposes an IDN-APIs (Application Programming Interfaces) on top of which IDN-compliant Applications can be developed IDN Compliant Applications
- An IDN-document structures information units and it is recursively composed of nodes related to each other only through “ aggregation links ” (no cycles ⇒ DAG) Reference links express relations between distinct IDN-documents Notify links are used to notify changes
- The IDN-Service Architecture is layered in such a way to manage different levels of abstraction of information. The units exchanged between communication layers are the IDN-Nodes. The communication between IDN-SA layers follows the REST paradigm i.e. it is based on common HTTP messages containing a generic IDN-Node in the message body and IDN-Node identifier in the message header. Each layer has as input a specific type of IDN-Node and applies on it a transformation on the relevant metadata to obtain its own IDN-Node type. The transformation (adding, modifying, updating and deleting metadata) recalls the encapsulation process used in the TCP/IP protocol stack. IDN-Nodes are identified by HTTP-URI as identifiers.
- From the bottom to the top of the architecture, these are the layers: Storage Interface (SI) : provides the data storage service Storage systems often depend on the specific platform (hardware and software) and they can be native storage or legacy systems It provides a REST-like uniform view over distributed data through URL names. It provides create, read, update and delete functions of URL-addressed resources Replica Management (RM): Information History (IH) : manages primitive information units history Navigation into the history is consequently allowed as a result of the services provided by this layer Virtual Repository (VR) : is seen by the applications as the container-repository of all primitive information units It exposes the IDN APIs to the IDN-compliant Applications It provides the maximum abstraction of structured information to the application IDN-Compliant Applications : implement the context-dependent business logic and provide the user interface (they can be multi-tier applications)
- Let’s see now how the InterDataNet approach meets the e-profile basic service needs. To do so I come back to one of the RESEPTIS scenarios I illustrated few minutes ago. The one in which Jorge renews his e-ID card and reserves a visit to the dentist’s. Given how the IDN is conceived and built, the government e-ID web service is an IDN-compliant application. It offers to the user Jorge a template of his e-ID card with pre-filled fields and will present to Jorge the options he is entitled to chose, that is the possibility to store on the e-ID card his health insurance profile. Going on the dentist’s web service provider – realized trough an IDN-compliant application- Jorge will be prompted his dentist’s template for a visit request and he will be able to decide to disclose his dental records. The dentist, using an IDN-compliant application for managing his patients, will compile his view of Jorge’s e-health record, linking to Jorge’s dental records he was granted to access.
- Work in progress: IDN – infrastruttura – va avanti Applicazione e-health – PON-REC schede sanitarie Applicazione e-gov – tax services; tracking citizen residence EU- project ERC-St Gr – European Interoperability Framework for e-gov services 1) The infrastructural approach is concrete and realized, at a prototype level. It has requested about five years of work and 3 Ph.D. thesis – one about the design, one about its implementation and one about the design-implementation of the applications which is still underway. A fourth Ph.D thesis has just started. 2) The application scenario used to describe the impact of the infrastructure is purely speculative
- If I was given the possibility that you remember only one idea from this talk it would be the following one: InterDataNet infrastructural approach allows to consider a possibile path to the creation of an e-profile basic service allowing trust-enabling e-Services, i.e.it provides a concrete answer to the requirements emerging from the RISPTIS report.
- However, the road we have a very long way ahaed. if there is commong agreement that the e-profile as a basic e-service is more a system requirement to enable future service scenarios as those schetched before, we will agree also that this will be a complex, transdisciplinary issue. Since InterDatanet changes the architectural approach to support e-services, it would really benefit from being studied form a service science perspective wich would give the project a sounder possibility to demonstrate its validity, innovation and strategic viewpoint towards a “trustworhy information society”.