Building and Integrating Competitive IntelligenceReports Using the Topic Map Technology<br />Vojtěch Svátek, Tomáš Kliegr,...
CI and Business Clusters<br />CI – Competitive Intelligence is a sub-field of business intelligence that supports decision...
TheTopic Map<br />1] Ontology: putting concepts into context<br />Instances<br />Associations<br />TopicTypes<br />2] Anno...
Testbed<br />A case study assignment at an introductory knowledge engineering course, attended by 150- 200 students each s...
S1: Individual ontologies, merge<br />Each team wrote the CI report (in  a text editor)<br />Consequently, they obtained a...
Topic Maps Merging<br />Merging of: Business cluster topic map, All unstructured documents, Linking files<br />Linking fil...
Issues<br />Annotated text fragmented, since each fragment is stored as internal occurrence<br />Laborious<br />Duplicate ...
S2: Collaborative Ontology Population <br />Goal: remove duplicate topic types<br />Startup ontology was placed on a Postg...
Issues<br />Separation of ontology enrichment and document annotation is not natural and requires an experienced annotator...
S3: Annotation by linking<br />Goal: move annotation fully to the web<br />All students used one instance of OKS server<br...
Issues … and finally advantages<br />Issues:<br />OKS Ontopoly was not stable enough in concurrent setting<br />X-Pointer ...
Summary& Plans<br />On the competitive intelligence use case, we tested several approaches for collaborative ontology desi...
Upcoming SlideShare
Loading in …5
×

Building and Integrating Competitive Intelligence Reports Using the Topic Map Technology

756 views
718 views

Published on

Competitive intelligence (CI) supports the decision makers in understanding the competitive environment by means of textual reports prepared based on public resources. CI is particularly demanding in the context of larger business
clusters. We report on a long-term project featuring large-scale manual semantic annotation of CI reports wrt. business clusters in several industries. The underlying ontologies are the result of collaborative editing by multiple student teams. The results of annotation are finally merged into CI maps that allow easy access to both the original documents and the knowledge structures.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
756
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Building and Integrating Competitive Intelligence Reports Using the Topic Map Technology

  1. 1. Building and Integrating Competitive IntelligenceReports Using the Topic Map Technology<br />Vojtěch Svátek, Tomáš Kliegr, Jan Nemrava, Martin Ralbovsý,<br /> Vojtěch Roček ,Jan Rauch<br />University of Economics, Winston Churchill Sq. 4, Prague, Czech Republic<br />Jiří Šplíchal, Tomáš Vejlupek<br />Tovek s.r.o., Chrudimská 1418, Prague, Czech Republic<br />
  2. 2. CI and Business Clusters<br />CI – Competitive Intelligence is a sub-field of business intelligence that supports decision makers in understanding the competitive environment by means of reports prepared based on (public) resources.<br />Cluster is a set of companies in related fields operating in the same geographical area<br />How to link and search<br />multiple CI reports?<br />Envisaged Solution: Create a complementary topic map <br />that would put the important facts into context<br />
  3. 3. TheTopic Map<br />1] Ontology: putting concepts into context<br />Instances<br />Associations<br />TopicTypes<br />2] Annotate important bits of text with ontology concepts<br />
  4. 4. Testbed<br />A case study assignment at an introductory knowledge engineering course, attended by 150- 200 students each semester<br />The goal is to get a picture of the whole industry<br />Students work in groups of 5<br /><ul><li>Each group covers one company and its environment</li></ul>Two assignments:<br />Students write CI reports of about 25 pages based on publicly available sources of information. <br />2) Important pieces of information are expressed in a machine-readable way with topic maps.<br />Each semester we tested a slightly different setting (S1-S3) of tools and techniques… now running for the fourth semester<br />
  5. 5. S1: Individual ontologies, merge<br />Each team wrote the CI report (in a text editor)<br />Consequently, they obtained a copy of a startup ontology<br />Students extended the ontology with new topic types using Tovek Topic Mapper (TTM): an ontology editor and annotating tool (desktop application)<br />Students used TTM to annotate bits of text with a topic type. <br />Annotated text became an internal occurrence in the topic map<br />The ontologies enriched with new topic types and annotations were collected from all teams<br />We used OKS to merge the topic maps<br />Extend ontology<br />Annotate<br />DOC<br />HTML<br />The result is a linking file between the document and the shared topic map<br />XTM<br />Startup Ontology<br />Result is a linking file conneting document with the topic map<br />
  6. 6. Topic Maps Merging<br />Merging of: Business cluster topic map, All unstructured documents, Linking files<br />Linking files<br />CI reports<br />HTML<br />XTM<br />DOC<br />Shared industry topic map<br />
  7. 7. Issues<br />Annotated text fragmented, since each fragment is stored as internal occurrence<br />Laborious<br />Duplicate topic types<br />Effective merging requires unique identifiers, which was achieved only for companies (registration numbers used in subject indicators)<br />
  8. 8. S2: Collaborative Ontology Population <br />Goal: remove duplicate topic types<br />Startup ontology was placed on a PostgreSQL server<br />Student teams collaboratively enriched the ontology with topic types, association types and occurrence types they assumed to use during the annotation in Topic Mapper<br />The ontology was then frozen: each team got its copy. <br />TTM was used only for annotation, and then OKS for merging<br />Collaborative Ontology Creation<br />remote repository<br />Topic Maps<br />for<br />Merging<br />Import<br />ontology<br />Shared topic map<br />students<br />Annotate only<br />
  9. 9. Issues<br />Separation of ontology enrichment and document annotation is not natural and requires an experienced annotator<br />Annotations still kept as internal occurrences<br />Multiple concurrent instances of OKS servers resulted in corruption in the topic map, probably due to caching in OKS<br />Two topic map tools used, original documents not easily accessible<br />
  10. 10. S3: Annotation by linking<br />Goal: move annotation fully to the web<br />All students used one instance of OKS server<br />CI reports were placed into a CMS (Joomla!)<br />Each structural unit was assigned an id (via HTML’s &lt;a name&gt;)<br />Annotation was done via external occurrences<br />External occurrences point at a specific bookmark at the document, where the annotated fragment starts. The annotated fragment is assumed to span up to the nearest following bookmark.<br />
  11. 11. Issues … and finally advantages<br />Issues:<br />OKS Ontopoly was not stable enough in concurrent setting<br />X-Pointer technology, which could be used to mark spans in the document, is not supported by current browsers<br />Advantages:<br />The text with full content (including even figures or links) in the CMS is more intelligible than fragments in internal occurrences<br />Further editing of an article is possible in the CMS without invalidating the annotation<br />Full-text search feature of the CMS can be exploited<br />Bringing the best from the CMS world and OKS<br />
  12. 12. Summary& Plans<br />On the competitive intelligence use case, we tested several approaches for collaborative ontology design and document annotation with some 500 users altogether.<br />OKS is a great tool, which gets additional edge by being web-based<br />We deem the last approach taken: documents stored in a CMS linked through external occurrences with OKS as usable - contingent on improvements in Ontopoly and Joomla!<br />Ontopoly wishes<br />Greater stability in case of concurrent user access<br />We missed user management and versioning in Ontopoly<br />Joomla! wishes<br />Support for „tagging“ arbitrary bits of text<br />A tool for creating XPointer URLs based on user selection<br />A functionality that would highlight part of the document based on a URL containing XPointer span<br />

×