Conceptualisation and Semantic Annotation of eGovernment Services in WSMO

1. Conceptualisation and Semantic Annotation of eGovernment Services in WSMO Karol Furdík1, Ján Hreňo2, Tomáš Sabol2 1 InterSoft, a.s., Florianska 19, 040 01 Kosice, Slovakia karol.furdik@intersoft.sk 2 Technical University of Kosice, Faculty of Economics, Letna 9, 042 00 Kosice, Slovakia jan.hreno@tuke.sk, tomas.sabol@tuke.sk

2. Conceptual model for egovernment services • Life event approach • Semantic annotation • Use case • Domain ontologies • Annotation • Annotation tool • Annotation tool • Multilinguality Contents

3. Interoperability • Access-eGov • WSMO as a basic conceptual framework • Other candidates RDF-S, WSDL-S, OWL-S, (BPEL4WS) • Fits proposed architecture an dfunctionality of Access-eGov system • Offers WSMX execution environment (reference implementation) • Discovery, selection, mediation and invocation of semantic web services Conceptual model for eGovernment services

4. Based on the life event approach, the WSMO conceptual model was reused and adapted for eGovernment application • Life Events were added as formal models of users’ needs, • consisting from multiple goals and services organised to the generic scenario • expressed by the orchestration construction consisting from workflow, control-flow, and data-flow sequences. • Goals were reused • They are organised in hierarchical manner • Goals contain a capability statement that is matched against a service’s capability. • Services were added as generalisations of the Web service concepts. • describe both electronic and traditional governmental services • In the case there is no executable service available for traditional service • Mediator and Ontology elements were reused from the WSMO model without changes. • The WSMX interfaces were reused in the implementation by mapping the Access-eGov system components. The semantic descriptions of particular services, goals, and life events were created in cooperation with user partners Life event approach

5. Coceptual model provides only framework • Semantic annotation has to be done in cooperation with particular Public Administrations • Service description • Functional and non functional properties • Preconditions • Inputs, outputs • Design of workflow sequences Semantic annotation

6. Semantic annotation - Use case diagram • Introduction and annotation of governmental services (both electronic and traditional ones) • Ontology browsing and management. To semantically describe a service, the • Goals management • Life events management.

7. Design of domain ontologies based on known conceptual descriptions (knowledge-driven design approach) • Several available resources analysed. Selected best candidates. • WSMO ontologies for description of date, time, and location; • vCard ontology for addresses and personal data; • DublinCore for metadata and document types; • Terregov, DIP, DAML, GEA, GOVML, AGLS metadata set, and IPSV ontologies for description of specific eGovernment concepts. Domain ontologies - selected candidates

8. Identification of information needs • specification of life events. • analysis of prior knowledge of users (citizens and businesses) in free-text • Transformation of free-text information into the list of life events, formally expressed by the WSML notation, and store it to the Life events ontology. • Identification of required information quality. • A list of proposed services together with related laws and regulations, documents needed to negotiate between users and PA • Creation of a glossary of topics and terms. • Creation of controlled vocabulary • Hierarchy of categories and subcategories created from the glossary by grouping the glossary terms • The categories from the controlled vocabulary can then serve as basis for the design of classes in the domain ontologies of the Access-eGov system. Domain ontologies – Requirement driven approach I

9. Domain ontologies – Requirement driven approach II • Grouping and relating the identified items. • set of other relations and mutual dependencies will be identified • An ontology-like structure is provided as the output of this step. • Design of ontology. • ontology-like structure created in the previous step needs to be formalised and expressed by WSML statements

10. Domain ontologies – Requirement driven approach III • Implementation of semantics. • conditional if-then-else expressions, loops, and workflow sequences using WSMO framework. • A formalised WSML representation of the ontology containing all the definitions (concepts, classes) of services, goals, and life • To use this ontology in a real eGovernment application, a tool is needed for creation and maintenance of instances of the services actually provided by PAs in particular applications. namespace {_"http://www.accessegov.org/ontologies/shg/", dc _"http://purl.org/dc/elements/1.1#", aeg _"http://www.accessegov.org/ontologies/core/"} goal MarriageLifeEvent nfpdc#titlehasValue "Marriage"endnfp interface MarriageLifeEventInterface orchestration workflow perform n1_1 receive ?x memberOf Q1. perform n1_2 achieveGoalApplyForMarriageGoal perform n1_3 achieveGoalWeddingPlaceReservationGoal perform n1_4 achieveGoalWeddingCeremonyGoal controlFlow source n1_1 target n1_2 source n1_2 target n1_3 source n1_3 target n1_4 dataFlow source n1_1{?x} target n1_2{?x}

11. For public administration employees • Limited knowledge on semantic technologies • Web based • User management based on roles • Annotators • Publishers • Vievers Annotation tool I

12. Service templates • Simplification of the process • Predefined set of the functional properties and workflow • Annotation • Specification of concrete values for non functional properties of services Annotation tool II

13. Web based • Browser capable of javascript required • User management • Localisable • Interface based on description of classes in WSML • Annotation produces instances ANNOTATION TOOL III

14. Annotation tool

15. Interface • Interface of Annotation tool and Personal assistant in English, German, Polish, Slovak • Data • Data for every national trial in dual language, English + national • Synchronization issue • What if one language data will change • User interface for data input and user management issue • Responsibility for translations Multilingual support

16. Multilingual support

17. WSML class representing non functional properties, together with predefined functional properties • Converter converts it to top entities WSML services • Other properties of the services currently not supported in user friendly way • Not frequent changes needed • Top entities WSML services stored in repository and used by Access-eGov Personal Assistant Client Result of annotation

18. Semantic annotation – vital for usability of semantic technologies • Reuse of existing ontologies • Semantic description of governmental services – Annotation tool • Repository for storing service descriptions • Combination of the services into complex workflow structures • Supportfor discovery, execution, and mediation of the services • Use different clients to access, browse, retrieve, and actively use the integrated governmental services Conclusion

19. Implementation of the first prototype finished Trial 1 in progress Evaluation of the trial Implementation of the requirements from the trial Integration Future work

20. More information www.access-egov.org