1 / 43

Telework Ontology – needs and solutions

Telework Ontology – needs and solutions. Zigmas Bigelis Project “TELEBALT” consultant, zigmasb@is.lt ECMConsulting, zigmas.bigelis@ecmconsulting.com Saulius Maskeliūnas Institute of Mathematics and Informatics, -------------. Content. 1. Telework terms 2. Ontology definition

rianna
Download Presentation

Telework Ontology – needs and solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Telework Ontology – needs and solutions Zigmas Bigelis Project “TELEBALT” consultant, zigmasb@is.lt ECMConsulting, zigmas.bigelis@ecmconsulting.com Saulius Maskeliūnas Institute of Mathematics and Informatics, ------------- TELEBALT conference "Teleworking Business, Education, Research and e-Commerce” , Vilnius, Lithuania, October 21-22, 2002

  2. Content 1. Telework terms 2. Ontology definition 3. Semantic Web 4. Web Ontology Language 5. Taxonomy and ontology software 6. Knowledge Management 7. Telework ontology needs 8. Domain Knowledge Centre, as part of IDC 9. Information Demonstration Centre (IDC) 10. Ontology-based Web Applications for IDC – Proposals for Partnership TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  3. Telework Telecommuting Flexible work eWork Remote work Agile work Teleworker Mobile worker Home-based worker Virtual team Virtual office Hoteling Telecottage Telecentre Compressed work schedule Flexible work program Work-life balance and much more 1. Telework terms TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  4. 7. Telework ontology needs • Ontology of telework domain itself • Ontology of teleworker domain • Main telework problems and barriers • Management • Communication • Both management and communication need for better understanding both each other and information to be collected, processed and shared • Less time for search and retrieval of the relevant information • 2 modes: one knows what knows and don’t knows TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  5. 2. What is an Ontologywww.cs.ma.ac.uk/~stevensr/onto/node3.html • Ontology is the specification of conceptualization , Gruber • The conceptualization is the couching of knowledge about the world in terms of entities (things, the relationships they hold and the constraints between them) • The specification is the representation of this conceptualization in a concrete form. • The main components of an ontology are concepts, relations, instances and axioms TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  6. Ontology-bases applicationsMain areas • Knowledge management systems • E-commerce • Intelligent search systems TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  7. http://sem.ucalgary.ca/KSI/KAW/KAW99/papers/Uschold2/final-ont-apn-fmk.pdfhttp://sem.ucalgary.ca/KSI/KAW/KAW99/papers/Uschold2/final-ont-apn-fmk.pdf Ontology-bases applicationsMain types • Neutral authoring • Ontology as specification • Common access to information • Ontology-based search TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  8. 3. Semantic Webhttp://www.w3.org/2001/sw/Activity • Semantic comes from the Greek words for sign, signify, and significant, and today means of or relating to meaning, often in language. • The Semantic Web is an extension of the current Web in which information is given well-defined meaning, better enabling computers and people to work in cooperation. • It is the idea of having data on the Web defined and linked in a way that it can be used for more effective discovery, automation, integration, and reuse across various applications. TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  9. Semantic Web (cnt’d 1)http://www.w3.org/2001/sw/Activity • For the Web to reach its full potential, it must evolve into a Semantic Web, providing a universally accessible platform that allows data to be shared and processed by automated tools as well as by people. • The Semantic Web is an initiative of the World Wide Web Consortium (W3C), with the goal of extending the current Web to facilitate Web automation, universally accessible content, and the 'Web of Trust'. TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  10. Semantic Web (cnt’d 2)http://www.w3.org/2001/sw/Activity • Tim Berners-Lee wrote the Road map for the Semantic Web in 1998, and it continues to be a good place to start for those who enjoy theory • The Semantic Web lends itself to collaboration, teamwork, and cooperation. In addition to the RDF Interest Group which serves as W3C's primary focal point for Semantic Web community discussion, there are a variety of domain specific communities who are using RDF/XML to publish their data on the Web. TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  11. 4. Web Ontology (WebONT) Working Group Charterwww.w3.org/2001/sw/WebOnt/charter • The WG, part of the Semantic Web Activity, will focus on the development of a language to extend the semantic reach of current XML and RDF meta-data efforts. • Tim Berners-Lee outlined the necessary layers for developing of applications that depend on an understanding of logical content, not just human-readable presentation • This WG will focus on building the ontological layer and the formal underpinnings thereof. TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  12. Web Ontology Working Grouphttp://www.w3.org/TR/owl-features/ • The OWL (Web Ontology Language) is being designed by the W3C Web Ontology Working Group in order to provide a language that can be used for applications that need to understand the content of information instead of just understanding the human-readable presentation of content. • OWL facilitates greater machine readability of web content than XML, RDF, and RDF-S support by providing a additional vocabulary for term descriptions. TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  13. OWL –ontology definition Ontology –a machine readable set of definitions that create • a taxonomy of • classes and • subclasses, and • relationships between them TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  14. OWL (cnt’d) • Web Ontology language OWL is a semantic markup language for publishing and sharing ontologies on the World Wide Web. • OWL is derived from the DAML+OIL Web Ontology Language and builds upon the Resource Description Framework [RDF/XML Syntax] • OWL Recommendations to be approved on 2002. TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  15. 5. Ontology and taxonomy • A taxonomy is a hierarchical system of classification representing structural differences http://www.epsltd.com/Database/Reports/Taxonomy/TaxonomyExec.htm • Hierarchical taxonomy expressing IS A (hypernymy hyponymy) relation . • By definition, a taxonomy is simply a classification scheme, whereas an ontology serves to provide semantics and associations/relationships. http://www.brint.com/wwwboard/messages/128417.html TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  16. Need for Taxonomy • More than 80% of unstructured information on the Web • Cataloguing unstructured information is a chronic problem • Taxonomy software correlates and groups unstructured information from myriad of sources • Search when you know what are you looking for • Search when you don’t know • www.entopia.com/pdfs/delphi_taxonomy_white_paper.pdf TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  17. Survey on categorization and taxonomy management • Survey, February 2002, Delphi Group • 450 organizations, half of them revenue over %100 million • More than 60% - finding information was difficult process • Over 50% - spending 2 or more hours each day searching for information • Search time is one of the fundamental symptoms of infoglut and how to measure taxonomy management • Process of search is “waste of time” • www.entopia.com/pdfs/delphi_taxonomy_white_paper.pdf TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  18. Ontology and taxonomy software • Entopya http://www.entopia.com • Applied Semantics http://www.aplliedsemantics.com • Semio http://www.semio.com • Stanford University project Protégé-2000 • EU projects • On-to-knowledge http://www.ontoknowledge.com • OntoWeb http://www.ontoweb.com • and more TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  19. EC project OntoWebhttp://www.ontoweb.org/download/deliverables • Ontologies provide a common vocabulary of an area and define-with different levels of formality – the meaning of the term and the relations between them • Knowledge in ontology is mainly formalized using 5 kinds of components: • Classes • Relations • Functions • Axioms • Instances • Classes in the ontology are usually organized in taxonomies TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  20. 6. Knowledge Management stageswww.kmworld.com/publications v11, issue 3 • Stage 1 – “by the internet out of intellectual capital”. KEY PHRASES : “best practices” and later “lessons learned” • Stage 2 – “human and cultural dimensions, the human relations stage”. KEY PHRASE: “communities of practice” • Stage 3 – “content and retrievability”.KEY PHRASES : “CONTENT MANAGEMENT” and “TAXONOMIES” • Dr. Michael Koenig of Long Island University TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  21. Creating Knowledge from Datahttp://www.darwinmag.com/reada/whitepepaers/070101_data.html • Transforming data and info into knowledge is not a passive activity such as going to a library and doing some research. • KM is fundamentally active – people need to have access to the right info at the right time. • KM needs to be proactive, tightly integrated with business processes and integrally related to day-to-day operational activities. TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  22. 7. Telework ontology needs • Ontology of telework domain itself • Ontology of teleworker domain • Main telework problems and barriers • Management • Communication • Both management and communication need for better understanding both each other and information to be collected, processed and shared • Less time for search and retrieval of the relevant information • 2 modes: one knows what knows and don’t knows TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  23. Telework ontology needs (cnt’d) • New Telework Consortium www.telcoa.org has been created • Killer application that will drive the growth of ultra-high-bandwidth services to the home won’t be entertainment as is generally assumed, but “telework”, or more specifically what Schaer call “interpersonal communications” • http://www.nwfusion.com.cgi-bin/mailto/x.cgi TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  24. 8. IDC’s Domain Knowledge CentreGoal and main feature • Our goal has been not developing only ontology but ontology-based Web application and approach (background of methodology) for ontology building • Main feature – from information collected and enriched by individual during each day work to collaborative development of shared knowledge • Domain Ontology is a core module of knowledge TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  25. Domain Knowledge • The domain knowledge describes the main static information and knowledge objects in an application domain. • The main kind of components used to describe domain knowledge is ontologies. • http://babage.dia.fi.upm.es/ontoweb/wp1/OntoRoadMap/index.html TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  26. Domain Knowledge CentreUssage purposes • collecting information • distributed semi-automatic transforming information to knowledge and • shared using of this knowledge and collected information • intelligent search of collected information and knowledge • serving as an information and knowledge background for ontology-based applications development TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  27. Domain Knowledge CentreStructure • The core modules: I. Information sources DB, i.e. Domain Knowledge Centre enriched by metadata and metatags (concepts, attributes and values) II. Domain ontology module TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  28. I. Information sources DB Features • Enriched info – metatags – are one of knowledge types in DKC • Knowledge should be created as each day procedure • On the next version adding of knowledge should be carried on in shared collaboration mode TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  29. Information sources DB – Enter & Edit Form TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  30. 1st option Concept Property (attribute) Value Value note 3rd option Class Concept Individual (instance) 2nd option Concept Property (attribute) Value Value note 4th option Instance name Property Value Information sources DB Information representation structure TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  31. 5th option Class Term - Definition of term 6th option Term Relationship TYPE Other term Comment Information sources DB Information representation structure (cnt’d) TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  32. Domain – Concept – Attribute – Value TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  33. An example of report TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  34. II. Domain ontology module • Ontology core module is in process of development • Network model to be used instead of typically used hierarchical model • Ontology module prototype is developed on relational DB (Microsoft Access) TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  35. Domain ontology moduleOntology development procedures • Enriched manually structured information (concepts, attributes, values) serves as a background for developing and continuous enhancement of domain ontology • Telework ontology contains more than 100 terms (concepts and attributes) TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  36. Domain ontology module Information representation structure • Class • Type of relation • Concept • Type of relation • Property (attribute) • Value • Value constraints description TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  37. Enter & Edit Form of Ontology module TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  38. Domain Knowledge Centre of Project Activities (telework, teamwork, collaboration) E-library on EC projects, products related to TELEBALT project using intelligent ontology-based search E-library on 6th Framework Program main issues Intelligent Search system of TELEBALT websites system (LT, LV, EE) Other Ontology-based Web applications of TELEBALT project (to be discussed) 9. Information Demonstration Centreof TELEBALT Project TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  39. 10. Ontology-based Web apps for IDCProposals for Partnership • Documents (e.g. legal acts) storehouse with ontology-based search • Information collecting and semi-automatic generating of surveys and reports • Website structure ontology – support of website enhancement and search • Management of project group TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  40. Ontology-based Web applicationsProposals for Partnership (cnt’d 1) • Personal and company e-Library • Partnership supporting intelligent system • Contracts and project proposals support system • Intelligent interactive consulting system • Product and services catalogue development system TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  41. Ontology-based Web applicationsProposals for Partnership (cnt’d 2) • Information transforming to Knowledge system • Information and Knowledge Quality Checking system • Integration of Business Intelligence products and Domain ontology • Ontology-based CRM application • Document annotation self-automated generation TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  42. Ontology-based Web applicationsProposals for Partnership (cnt’d 3) • Research and Development information analysis system • Situation evaluation, problem identification, alternative generation and decision making system • Training information systems building tool TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

  43. Thanks for attention !? Zigmas Bigelis, UAB “ECMC” zigmas.bigelis@ecmconsulting.com Saulius Maskeliūnas, Institute of Mathematics and Informatics, Vilnius TELEBALT conference, Vilnius, Lithuania, October 21-22, 2002

More Related