Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2B Skokan.ppt


Published on

  • Be the first to comment

  • Be the first to like this

2B Skokan.ppt

  1. 1. Technologies employed in the Access-eGov system Marek Skokan Technical University of Kosice, Slovakia
  2. 2. Project Access-eGov <ul><li>Number: FP6-2004-27020 </li></ul><ul><li>Funded by EC under under Sixth framework programme </li></ul><ul><li>Coordinated by Technical University of Kosice </li></ul><ul><li>Started in January 2006 </li></ul><ul><li>Duration 36 months </li></ul><ul><li>Effort is 410 person-months </li></ul><ul><li>Aims at development of component-based enhancements of existing e-Government infrastructure based on Semantic Web technologies and distributed architectures (G2C, G2B relations) </li></ul><ul><li>More on project at </li></ul>
  3. 3. Current situation - Basic facts <ul><li>There are considerable high number of electronic services provided by PA institutions </li></ul><ul><ul><li>Services provided by PA institution in all governmental levels </li></ul></ul><ul><ul><li>Heterogeneous environment - service discovery process might be a challenging task </li></ul></ul><ul><li>The service discovery itself is not enough (for users) </li></ul><ul><ul><li>In case of more complicated life events we should somehow compose them (services) </li></ul></ul><ul><ul><li>We need more services performed in a (not necessary linear) sequence </li></ul></ul><ul><li>A ‘helping’ user oriented system (Access-eGov) has to: </li></ul><ul><ul><li>Deal with integration, in the environment of PA institutions with possibly heterogeneous service descriptions </li></ul></ul><ul><ul><li>Enable interoperability of services </li></ul></ul><ul><ul><li>Support traditional services </li></ul></ul><ul><ul><li>Enable discovery, composition and execution of services </li></ul></ul>
  4. 4. Key technologies for such ‘helping’ system <ul><li>P2P networks </li></ul><ul><ul><li>Enable connection among levels of local, regional, national and European PA institutions </li></ul></ul><ul><ul><li>Enable delegation of responsibilities for registering and updating of e-services into decentralised (Access-eGov) system to local providers (manageable by PA institutions) </li></ul></ul><ul><li>Semantic technologies </li></ul><ul><ul><li>Enable a precise semantic discovery process of services, service composition and execution </li></ul></ul><ul><ul><li>Enable to cover interoperability issue </li></ul></ul><ul><li>SOA (Service Oriented Architecture ) and Web services </li></ul><ul><ul><li>Enable to provide relevant functionalities of e-services to client (service consumer) </li></ul></ul><ul><ul><li>Flexibility in case some processes are changed </li></ul></ul>
  5. 5. Peer-to-peer <ul><li>P2P systems – distributed systems without any centralized control or hierarchical organization </li></ul><ul><li>Each node runs software with equivalent functionality </li></ul><ul><li>Implementations usually means creation of virtual networks with a structure/topology which does not depend on the physical internet </li></ul><ul><li>A lot of positive features </li></ul><ul><ul><li>fault tolerance, scalability, ease of deployment </li></ul></ul><ul><ul><li>no need for specialized equipment => building of P2P systems is quite cheap </li></ul></ul>
  6. 6. SOA – Web Services <ul><li>SOA – architecture where component are modular services that can be discovered and used by clients </li></ul><ul><li>Web services can be seen as a corresponding implementation technology </li></ul><ul><li>Services (e.g. governmental) can participate in a workflow, where the order of their invocation affects the operation </li></ul><ul><li>Enable to create composed services relevant to real life situations </li></ul>
  7. 7. Semantic technologies <ul><li>WSM* </li></ul><ul><ul><li>WSMO (Web Service Modelling Ontology) serves as conceptual model for describing semantic Web Services </li></ul></ul><ul><ul><ul><li>Goals, Web services, Ontologies, Mediators </li></ul></ul></ul><ul><ul><li>WSML (Web Service Modelling Language) formalizes WSMO </li></ul></ul><ul><ul><li>WSMX (Web Service Execution Environment) is implementation which enables discovery, selection, mediation, and invocation of Semantic Web Services </li></ul></ul>
  8. 8. Advantages for Access-eGov - Peer-to-peer <ul><li>Easy deployment </li></ul><ul><ul><li>Un-attended joining of new resources/nodes </li></ul></ul><ul><ul><li>Install the Access-eGov software on some ‘online’ computer (e.g. PC) and register this node into infrastructure </li></ul></ul><ul><li>Stability (fault tolerance) of the overall infrastructure </li></ul><ul><ul><li>Failure or unavailability of a single node does not necessary disable the system – thanks to replicated data (redundantly stored in more nodes) </li></ul></ul><ul><li>=> The Access-eGov system can be very reliable and instead of that its building should be cheaper than the building centralistic system </li></ul>
  9. 9. Advantages for Access-eGov – SOA/Web services <ul><li>The code needed to expose existing legacy application by using SOA is relatively small </li></ul><ul><ul><li>Once the service is created it can be easily re-used </li></ul></ul><ul><ul><li>The use of services doesn't depend on a specific platform </li></ul></ul><ul><ul><li>SOA allows easy process transformations </li></ul></ul><ul><li>=> The Access-eGov system can be really flexible technological solution supporting e-Government </li></ul>
  10. 10. Advantages for Access-eGov - Semantic technologies <ul><li>Sophisticated goal-oriented discovery </li></ul><ul><ul><li>goal is matched against description of Web service </li></ul></ul><ul><li>Definition of relatively small amount of pre-defined goals </li></ul><ul><li>Creation and maintenance of services (high amount) – up to the PA institutions </li></ul><ul><li>Mediation - Interoperability and Multilanguage support </li></ul><ul><li>Non-functional properties – user preferences </li></ul><ul><li>=> The Access-eGov system enable interoperability and can serve really accurate service relevant to the current situation </li></ul>
  11. 11. Conclusions <ul><li>The combination of described technologies appears to be promising </li></ul><ul><li>WSMO enables to compose atomic services into composed services </li></ul><ul><li>WSMO together with SOA (Web services) and distributed (P2P) infrastructure containing service descriptions make possible interoperability between different types of legacy systems used within public service backend </li></ul>
  12. 12. Thank you for attention! If you have further questions you can contact me at [email_address] Project web Site:
  13. 13. Physical architecture <ul><li>Knowledge formalisms </li></ul><ul><ul><li>OWL-S </li></ul></ul><ul><ul><li>WSMO </li></ul></ul><ul><ul><li>WSDL-S </li></ul></ul><ul><ul><li>BPEL4WS </li></ul></ul><ul><li>Framework candidates </li></ul><ul><ul><li>METEOR-S </li></ul></ul><ul><ul><li>WSMX </li></ul></ul><ul><ul><li>IRS III </li></ul></ul>Access-eGov selection Access-eGov selection
  14. 14. Conceptual Architecture - Glossary <ul><li>Life event </li></ul><ul><ul><li>Denotes a specific situation in the life of citizen or a life of organization that requires a series of public services to be performed. </li></ul></ul><ul><li>Generic scenario </li></ul><ul><ul><li>Decomposes life events to sub-goals. It is customizable for the specific user needs. </li></ul></ul><ul><li>Goal </li></ul><ul><ul><li>Specifies those objectives that client might have when consulting a service, including functionalities that the service should provide from the user’s perspective. </li></ul></ul>
  15. 15. Services provided by the Access-eGov system <ul><li>Information provider view </li></ul><ul><ul><li>Annotate service </li></ul></ul><ul><ul><li>Register service </li></ul></ul><ul><ul><li>Create generic scenario </li></ul></ul><ul><li>Information consumer view </li></ul><ul><ul><li>Specify goal </li></ul></ul><ul><ul><li>Execute goal / scenario </li></ul></ul><ul><ul><li>Update scenario for offline activities </li></ul></ul><ul><ul><li>Tune privacy settings </li></ul></ul>
  16. 16. Modules and Components (1) <ul><li>Architecture breakdown </li></ul><ul><ul><li>6 modules </li></ul></ul><ul><ul><li>21 components </li></ul></ul><ul><li>Service annotation module </li></ul><ul><ul><li>Service annotation component </li></ul></ul><ul><ul><li>Life events and goals management component </li></ul></ul><ul><ul><li>Ontology management component </li></ul></ul><ul><li>Service Discovery module </li></ul><ul><ul><li>Full-text search component </li></ul></ul><ul><ul><li>Matching component </li></ul></ul><ul><ul><li>Filtering component </li></ul></ul><ul><ul><li>Reasoning component </li></ul></ul><ul><ul><li>Mediation component </li></ul></ul>
  17. 17. Modules and Components (2) <ul><li>Service composition module </li></ul><ul><ul><li>Resolving component </li></ul></ul><ul><ul><li>Chaining component </li></ul></ul><ul><li>Scenario execution module </li></ul><ul><ul><li>Goal/scenario execution component </li></ul></ul><ul><ul><li>Web Services invocation component </li></ul></ul><ul><li>Personal assistant module </li></ul><ul><ul><li>User and profile management component </li></ul></ul><ul><ul><li>Goal selection component </li></ul></ul><ul><ul><li>Visualisation and data entry component </li></ul></ul>
  18. 18. Mapping to the wsmx components <ul><li>WSMX </li></ul><ul><li>discovery </li></ul><ul><li>selector </li></ul><ul><li>data mediator </li></ul><ul><li>process mediator </li></ul><ul><li>orchestration </li></ul><ul><li>choreography </li></ul><ul><li>comm manager </li></ul><ul><li>resource manager </li></ul><ul><li>AeG </li></ul><ul><li>matching </li></ul><ul><li>filtering </li></ul><ul><li>mediation </li></ul><ul><li>mediation </li></ul><ul><li>[replaced by execution] </li></ul><ul><li>[replaced by execution] </li></ul><ul><li>ws connection </li></ul><ul><li>data repository </li></ul>
  19. 19. Logical Architecture – Structural View AeG P2P Node AeG P2P SNode Core components Composition Execution Discovery Mediation Core components Discovery Mediation AeG Personal Assistant client AeG Annotation services (optional) AeG Annotation services (optional) E-service B P2P network service protocols (SOAP/ XML e-forms) SOAP/HTTP(S) SOAP/HTTP(S) Data repositories Data repositories &quot;Traditional&quot; service B Organization C Organization B Organization A AeG Annotation services (optional) SOAP/HTTP(S) &quot;Traditional&quot; service C