E-TRANSACTIONS ENABLER: INTEROPERABILITY

Transcription

1 E-TRANSACTIONS ENABLER: INTEROPERABILITY Electronic Transactions by Markaki O., Askounis D.

2 What is Interoperability (Io)? IEEE glossary: the ability of two or more systems or components to exchange information and to use the information that has been exchanged ISO/IEC , Information Technology Vocabulary: the capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units European Commission / EIF v2.0: Interoperability is the ability of disparate and diverse organizations to interact towards mutually beneficial and agreed common goals, involving the sharing of information and knowledge between the organizations via the business processes they support, by means of the exchange of data between their respective information and communication technology (ICT) systems European Commission / Enterprise Interoperability Research Roadmap: Interoperability is a utility-like capability that enterprises can invoke on the fly in support of their business activities

3 Where is it a necessity? Systems ebusiness Systems (between different organisations) egovernment Systems Inter-Enterprise Systems Sub-Systems (Modules) of an Enterprise System Between enterprises or organisations regardless of IT infrastructures Data Between Data or Documents People Between.. People

4 Interoperability Levels (EIF)

5 Enterprise Interoperability Areas

6 EI Areas Mapping to IoP Layers

7 EI Areas: Data Interoperability ID SA.1 Title Data Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags The ability of data (including documents, multimedia content and digital resources) to be universally accessible, reusable and comprehensible by all transaction parties (in a human-to-machine and machine-to-machine basis), by addressing the lack of common understanding caused by the use of different representations, different purposes, different contexts, and different syntaxdependent approaches Backlinks - Outbound Links Social Networks Interoperability Services Interoperability Knowledge Interoperability Semantic Data Representation Data Standardization Schema Matching Data Mediation Semantic Information Exchange, Data Sharing, Data Integration, Schema Matching, Data Mash-ups

8 EI Areas: Process Interoperability ID SA.2 Title Process Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags The ability to align processes of different entities (enterprises), in order for them to exchange data and to conduct business in a seamless way Backlinks - Outbound Links Knowledge Interoperability Services Interoperability Process Modelling Process Reengineering Process Standardisation Process Alignment Automated Process Execution Process, Process Modelling, Process, Reengineering, Tasks, Patterns

9 EI Areas: Rules Interoperability ID SA.3 Title Rules Interoperability Description Hierarchical Links Indicative Scientific Areas Tags The ability of entities to align and match their business and legal rules for conducting legitimate automated transactions that are also compatible with the internal business operation rules of each other. Backlinks - Outbound Links Services Interoperability Knowledge Interoperability Electronic Identity Interoperability Rules Modelling Legislation Homogenisation/Alignment Rules Execution Rules, Legislation, Business Rules, Legal Rules

10 EI Areas: Objects Interoperability ID SA.4 Title Objects Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags Objects interoperability refers to the networked interconnection of everyday objects. Devices or hardware components interoperability can be seen as a particular case of the object interoperability domain. Backlinks - Outbound Links Knowledge Interoperability Electronic Identity Interoperability RFID interoperability Internet-connected objects Networked media Factory-of-Things Smart Objects / Devices Interoperability in Internet of Things, RFID interoperability, Smart Objects / Devices / Controllers, Internet-connected objects, Networked media

11 EI Areas: Software Systems Interoperability ID SA.5 Title Software Systems Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags Software Systems Interoperability refers to the ability of an enterprise system or a product to work with other enterprise systems or products Backlinks - Outbound Links Services Interoperability Electronic Identity Interoperability Component-based software engineering Service- oriented Architecture (SOA) and Web Services Software Interoperability Monitoring and Evaluation Requirements engineering for interoperable enterprises Application Interoperability, Application Middleware, SOA, B2B gateways, Software Agents, Software Adapters, SOA, ESB, RMI

12 EI Areas: Cultural Interoperability ID SA.6 Title Cultural Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags The degree to which knowledge and information is anchored to a unified model of meaning across cultures Backlinks - Outbound Links Knowledge Interoperability Social Networks Interoperability Language interoperability Regional aspects compatibility Policy Interoperability Alignment in traditions, religions and ethics Culture, Context, Language, Linguistics

13 EI Areas: Knowledge Interoperability ID SA.7 Title Knowledge Interoperability Description Hierarchical Links Indicative Scientific Areas Tags The ability of two or more different entities to share their intellectual assets, take immediate advantage of the mutual knowledge and utilise it, and to further extend them through cooperation Backlinks Data Interoperability Process Interoperability Rules Interoperability Objects Interoperability Cultural Interoperability Outbound Links Cloud Interoperability Knowledge Sharing & Knowledge Repositories Transportation of Knowledge Business Units Alignment Smart Infrastructures Knowledge embedded systems Context-aware systems Ontology Matching Knowledge, Intellectual Assets, IPR, Business Units, Intelligence, Knowledge Management, Ontologies

14 EI Areas: Services Interoperability ID SA.8 Title Services Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags The ability of an entity to seamlessly and automatically discover, aggregate and utilise a service that belongs to another entity. Backlinks Data interoperability Services Interoperability Rules Interoperability Software Systems Interoperability Outbound Links Cloud Interoperability Automatic service discovery, description, composition, negotiation Service Deployment Service Engineering Service Mediation Enterprise Mashups Service-oriented Architectures (SOA) and Web Services Services discovery, composition, provision, QoS

15 EI Areas: Social Networks Interoperability ID SA.9 Title Social Networks Interoperability Description Hierarchical Links Indicative Scientific Areas The ability of enterprises to utilise social networks for collaborations and interconnection purposes, by aligning their internal structure to the fundamental aspects of the social networks Backlinks Data Interoperability Cultural Interoperability Outbound Links Ecosystems Interoperability Social Network Integration Social Analytics & Social Cross-Networks Analysis Social Business Models Tags Social Networks, Social Media, Web 2.0, Social Computing, Enterprise 2.0

16 EI Areas: eid Interoperability ID 10 Title eid Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags The ability of different eid systems to collaborate in order to automatically authenticate entities and to pass on security roles and permissions to eid holders, regardless the system that they originate from Backlinks Rules Interoperability Objects Interoperability Software Systems Interoperability Outbound Links Cloud Interoperability Digital Signatures Interoperability Federated Identity Management Systems Interoperability Electronic Identity Security Electronics ID Cards Infrastructures & Services Single Sign On Architectures Electronic Identity, eid, Authentication, Authorisation, Permissions, Security, Access

17 EI Areas: Cloud Interoperability ID SA.11 Title Cloud Interoperability Description Hierarchical Links Indicative Scientific Sub-areas Tags The ability of cloud services to be able to work together with both different cloud services and providers, and other applications or platforms that are not cloud dependant. Backlinks Services Interoperability Knowledge Interoperability eid Interoperability Outbound Links Ecosystems Interoperability Cloud Application Interoperability Cloud Orchestration Unified Cloud Interfaces Cloud Federation Cloud Computing, InterCloud, Cross-cloud Federation, Cloud Interconnection

18 EI Areas: Ecosystems Interoperability ID SA.12 Title Ecosystems Interoperability Description Hierarchical Links Indicative Scientific Sub-Areas Tags The ability of instant and seamless collaboration between different ecosystems, ecosystems and independent entities, entities within the ecosystems and the ability of different independent entities to formulate virtual structures for specific purposes. Backlinks Social Networks Interoperability Cloud Interoperability Outbound Links - Distributed Systems and Agents Business Ecosystems Interoperation Virtual Enterprise Integration Business Ecosystems, Digital Ecosystems, Virtual Enterprises, Digital Enterprises, Virtual Factories, Factories of the Future, Business Sectors Interconnection, Business Domain Interconnection

19 Technical Interoperability Web Services

20 Service-oriented Architecture Supports the design of applications based on services Web services; representation of software programs, DBs or processes: Defined on their functionality Defined on the exchanged messages Accessible via a network

21 Example of Service-oriented Architecture A compact-disc (CD) with Data, and a CD Player that provides the playback service of reading the CD If CD player breaks down: SOA can replace the CD player with any device of different specifications, e.g. a portable CD player. Still the service will be the same. In a different architecture, e.g. object-oriented, each CD needs its own CD player Object-orientation says: "keep data and methods that manipulate data (business processes) together"; Service-orientation says: "keep the business process in the service, and pass data to it".

22 Web Service A web service is a software system designed to support interoperable machine-to-machine interaction over a network. W3C, Web Services Glossary

23 Web Service A Web Service is a software application identified by a URI (Uniform Resource Identifier), whose interfaces and binding are capable of being defined, described and discovered by XML artifacts, and which supports direct interactions with other software applications using XML-based messages via Internet-based protocols. W3C, Web Services Glossary

24 Rules of Web Service How one system can request data from another system. Which specific parameters are needed in the data request. What would be the structure of the data produced. (Normally, data is exchanged in XML files, and the structure of the XML file is validated against an.xsd file.) What error messages to display when a certain rule for communication is not observed, to make troubleshooting easier. Image:

25 Web Service by example Questions Is every online service a web service? e.g. Is a web site that allows you to book a hotel room a web service? Ταξιδιωτικό Γραφείο Ξενοδοχείο Internet Web Site

26 Web Service by example Answer Not necessarily! A web service will allow you, and other partners (e.g. travel agent) to book a room automatically. Ταξιδιωτικό Γραφείο Ξενοδοχείο 7/6/ , Internet 286 Web Service

27 Characteristics of Web Service Independent of the platform of implementation (transferable) Using open standards and common protocols, e.g. XML, HTTP Easier development and cost of deployment Stacking back-end services Publishing documentation, e.g. discovery and usage Reusability

28 Advantages of Web Services Easier data handling Simplicity in communication protocol Simplicity of infrastructure Interoperability and easier application development Intercommunication, no matter the programming language and platform Loose coupling among applications Customizing existing applications to constant changing business/clients needs Smaller development/usage costs

29 Technical Interoperability APIs

30 What is an API? An Application Programming Interface (API) is a particular set of rules and specifications that a software program can follow to access and make use of the services and resources provided by another particular software program that implements that API. It serves as an interface between different software programs and facilitates their interaction, similar to the way the user interface facilitates interaction between humans and computers. (Wikipedia) Or simpler an API is: an abstraction that is defined by the description of an interface and the behaviour of the interface.

31 Why provide an API? Source:

32 Example Web APIs Source: OPENi Project (2013)

33 What is good API design? Easy to learn Easy to use, even without documentation Hard to misuse Easy to read and maintain code that uses it Sufficiently powerful to satisfy requirements Easy to extend Appropriate to audience Joshua Bloch, Principal Software Engineer, Google.

34 Semantic Interoperability

35 Interoperability Levels (EIF)

36 Need for Semantic Interoperability - I Organization X Organization Y ASCII, XML, Word, PDF,... Need for common syntax!

37 Need for shared, common understanding Desicion Support Systems Laboratory, NTUA Need for Semantic Interoperability - II Address Χ Street, Number, Postal Code 1 ( ) 340 (δρχ) Χ Δημόσιος Φορέας Α Διεύθυνση Α Last Name Χ Family Name 01 - Greece Χ GR - Greece Δημόσιος Φορέας Β Τμήμα Α

38 How Semantics are attached to any concept Data Metadata VAT Number Issue Date Context Periodic VAT Declaration

39 Semantic Representation Elements & Standards ISO, UN, ΕΛΟΤ,... XML, OWL, TXT,... XML, EDI,... Codelists Thesauri Data Types CCTS,... XML Schema, DTD, UML... Dublin Core, egms,... Data Structures Data Schemas Metadata OWL, RDF,... Ontologies

40 Electronic Transactions 2018 etransactions Enabler: Interoperability XML Standards Family XML Schema XML Namespace XSL και XSLT XML Signature XML Encryption XML Query XForms XPath Xlink XPointer CSS RDF (Resource Description Framework) MathML GML (Geography Markup Language).

41 Electronic Transactions 2018 etransactions Enabler: Interoperability XML <?xml version="1.0" encoding="utf-8"?> <breakfast_menu> <food> <name>belgian Waffles</name> <price>$5.95</price> <description> Two of our famous Belgian Waffles with plenty of real maple syrup </description> <calories>650</calories> </food> <food calories= 900 > <name>strawberry Belgian Waffles</name> <price>$7.95</price> <description> Light Belgian waffles covered with strawberries and whipped cream </description> </food> <food> <name>berry-berry Belgian Waffles</name> <price>$8.95</price> <description> Belgian waffles covered with assorted fresh berries and whipped cream </description> <calories>900</calories> </food> </breakfast_menu>

42 XML Schema Example <?xml version="1.0" encoding="utf-8"?> <book xmlns:xsi=" xsi:nonamespaceschemalocation="c:\users\teti\deskto p\book.xsd"> </book> Books.xml <title>c# How to program</title> <serial_no> </serial_no> <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs=" elementformdefault="qualified" attributeformdefault="unqualified"> <xs:element name="book"> <xs:annotation> <xs:documentation>this is the first example in XSD</xs:documentation> </xs:annotation> <xs:complextype> <xs:sequence> <xs:element name="title" type="xs:string"/> <xs:element name="serial_no" type="xs:integer"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> Books.xsd

43 XML Schema Example <?xml version="1.0" encoding="utf-8"?> <book xmlns:xsi=" xsi:nonamespaceschemalocation="c:\users\teti\deskto p\book.xsd"> </book> Books.xml <title>c# How to program</title> <serial_no> </serial_no> <?xml version="1.0" encoding="utf-8"?> Books.xsd <xs:schema xmlns:xs=" elementformdefault="qualified" attributeformdefault="unqualified"> <xs:element name="book"> <xs:annotation> <xs:documentation>this is the first example in XSD</xs:documentation> </xs:annotation> <xs:complextype> <xs:sequence> <xs:element name="title" type="xs:string"/> <xs:element name="serial_no" type="xs:integer"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema>

44 Data Modelling Approach for Greek egov Transactions Build on existing standards! Interoperability Registry Retrieval of Standard Schemas Retrieval of Standard Schemas Organization A Data Exchange Organization B

45 Organizational Interoperability

46 Interoperability Levels (EIF v2.0)

47 What is an IF (Interoperability Framework)? set of recommendations which specify how Administrations, Businesses and Citizens communicate with each other Wikipedia Defines rules, sets specifications and standards for the development and operation of IT systems that allow: Cross-Interoperability amongst Organisations Integrated systems Secure Communication

48 European Interoperability Framework The European interoperability framework is a commonly agreed approach to the delivery of European public services in an interoperable manner. It defines basic interoperability guidelines in the form of common principles, models and recommendations. The new EIF is part of the Communication (COM(2017)13 4) from the European Commission adopted on 23 March 2017.

49 European Interoperability Framework

50 Current European Commission Initiatives EIF 3.0 European Interoperability Framework (EIF) v3.0: the new set of interoperability guidelines for European Member States ISA 2 Programme Interoperability Solutions And Common Frameworks For European Public Administrations, Businesses And Citizens ( ) EICart European Interoperability Cartography of solutions

51 CEN/UN Interoperability Standardisation Initiatives The European Committee for Standardization - Information Society Standardization System (CEN/ISSS) has several worksgroups for egov Standards on organisational and semantic issues (e.g. Metalex, egovshare) United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT), TBG19-eGov delivers standards on Core Components and harmonisation processes for governments worldwide

52 Is Standardization the key? Source: JavaScript Language Tooling Benjamin Woodruff

53 De Jure Vs De Facto Standards De jure standards, or standards according to law, are endorsed by a formal standards organization. The organization ratifies each standard through its official procedures and gives the standard its stamp of approval. De facto standards, or standards in actuality, are adopted widely by an industry and its customers. They are also known as market-driven standards. These standards arise when a critical mass simply likes them well enough to collectively use them

54 Key Findings after many attempts To truly enable interoperability across government, a bottom-up approach starting with technology must be avoided. Solving organizational and semantic interoperability issues deserves more priority and effort than the technical interoperability layer that has already mechanisms and standards in place. The adoption of a service-oriented approach is a crucial factor for implementing one-stop interoperable egovernment. The diffusion of needed basic infrastructure, such as electronic ID s, base registries and fundamental governmental web services has not reached the minimum needed threshold.

55 The 3 Interoperability Rules #1 Target organisational and semantic aspects first: technical standards exist already Follow the service: build your guidelines around the actual, most common services #2 #3 Enable all stakeholders and allow for constant evolution and change

56 Interoperability Application Areas A. Independent Services Interoperability is not an issue Their consumption by Services of B or C category (of this slide) is what matters B. Cross- Dependent Services Core Research Area for Interoperability C. Cross- Depended Services that include non electronic processes Cannot be made Interoperable without drastic change

57 Expected Impact (1/3) For Public Administrations Openness of organisation Common Visibility and Presence over the Web Less Bureaucracy Transparency Quality of Service Utilisation of High Efficiency Systems/Channels Collaboration between other organisation Economies of Scale by re-utilisation of IT resources (hardware/software)

58 Expected Impact (2/3) For Citizens/Enterprises Quality of Service Decrease Response Times -> Time Savings Information Access through multiple channels Reduction of Service Access Costs Ease of Searching and Discovering Information Improvement of Trust and Transparency feeling Improved Productivity for Enterprises

59 Expected Impact (3/3) IT Companies Products and Applications responding to a priori commonly agreed specifications Provision of ready made COTS (Components off the Shelf) for standardising processes and documents Faster response to Public Adminstration calls for implementation of systems Minimisation of Customised Solutions and multiple, parallel production lines

60 Conclusions Interoperability concerns all governmental organizations at national and international level Constitutes a thriving research domain from all aspects scientific, entrepreneurial, societal and political. Interoperability Standards for e-government is a dynamic space, with many directives, initiatives and standards evolving at the same time. Administrations and industry worldwide are trying hard to cope with the developments. Interoperability in digital public services cannot be achieved without process re-organisation, legal system re-structuring, and data re-work.

61 QUESTIONS Markaki O. - omarkaki@epu.ntua.gr