KR100661243B1 - Topic map editor, method of processing topic map in the topic map editor and recording medium - Google Patents

Abstract

A topic map editor, and a topic map processing method and a recording medium thereof are provided to efficiently process generation and edition of correlation between distributed knowledge information resources and a related topic map. A user interface(100) receives/transmits an operation command and data related to construction/modification of the topic map to a controller, and individually displays a topic map structure, a topic list, a correlation list, and a resource list to one screen while displaying a result received from the controller. A controller(300) generates the topic map structure, the topic list, the correlation list, and the resource list according to the operation command/data inputted through the user interface, and transmits generated data to the user interface. The user interface includes a control frame(10) interpreting/transferring the inputted operation, data generation, and data storing command to the controller, and a menu frame(12) displaying the topic map structure, the topic list, the correlation list, and the resource list to each area of a display area.

Description

Topic map editor, method of processing topic map in the topic map editor and recording medium}

1 is a view for schematically explaining the TAO (Topic, Association, Occurrence) of the toppack map,

2 is a block diagram of a topic map editor according to an embodiment of the present invention;

3 is a DTD structure diagram of XTM 1.0 applied to an embodiment of the present invention,

4 is a view for explaining a topic relationship extraction pattern employed in the data management unit of FIG.

5A to 5E are views illustrating a GoF design pattern used in the topic relationship extraction pattern of FIG. 4;

6 is a flowchart illustrating a topic map processing method in a topic map editor according to an embodiment of the present invention;

7A to 7E are screen examples employed in describing the flowchart of FIG. 6.

<Description of Symbols for Major Parts of Drawings>

10: control frame portion 12: menu frame portion

30: project management unit 32: topic class management unit

34: data management unit 36: topic model unit

38: relationship management unit 40: resource management unit

42: topic management unit 44: topic map file management unit

46: topic map database management unit 100: user interface unit

200: system management unit 300: control unit

The present invention relates to a topic map editor, a topic map processing method and a recording medium in the topic map editor, and more particularly, a topic map editor and a topic map editor for facilitating inputting, editing, and verifying data related to a topic map. The present invention relates to a topic map processing method and a recording medium.

As information resources connected to the Internet increase rapidly, the search and use of information becomes more difficult. Current networks do not provide high accuracy in retrieving the desired information, nor do they present relevant information among a large number of information.

Finding and searching for relevant information by users is not only very inefficient, but also sometimes impossible. In addition, it is very difficult to organize and reuse such information because a lot of information exists on the Internet in various forms.

As one of various efforts to solve this problem, the concept of semantic web has emerged. The semantic web is a kind of conceptual network that gives meaning to data existing on the web and allows the machine to know these meanings. Each concept has a group of resources associated with it and can be associated with other concepts so that this conceptual network can be used to navigate between information resources or Web resources.

Recently, various tools for searching web sites or resources based on ontology such as RDF, RDFS, OWL, and Topic Map have been developed.

Topic maps are a kind of virtual map that expresses knowledge about the complex structure of information resources and organizes them into topics and their relationships.

Existing ontology languages are represented by attributes and values, so existing information needs to be transformed to construct an ontology, but a topic map can integrate information resources without using a location to convert forms. In addition, topic maps can be easily merged between different topic maps, which is very useful when a large amount of heterogeneous information resources needs to be integrated.

The standard for topic maps was first proposed in January 2000, ISO / IEC 13250 Topic Maps, expressed in HyTM. In February 2001, XML Topic Maps (XTM) 1.0 using the XML syntax was proposed by Topicmaps.org, and ten months later, ISO / IEC 13250 (HyTM) and XTM 1.0 were integrated and jointly developed in ISO / IEC 13250: 2002. (HyTM, XYM 1.0).

The basis of a standardized topic map is composed of topics, associations, and resources.

For example, referring to the opera topic map of FIG. 1, a topic expresses a theme such as "Tosca", "Madame Butterfly", "Rome", "Italy", "Puccini", or "Lucca". Puccini was born in Lucca and composed Tosca, so there is a "born-in" association between "Puccini" and "Lucca" topics, and a "Compose" association between "Puccini" and "Tosca" topics. do. Resources for this topic can be in the form of addresses such as /snl/puccini.htm, file: ///C/topicmaps/opera/occurs/puccini-gallery.htm, or text such as 1924/11/29, 1858/12/22 It has a data type.

Topics describe real-world topics, topics are "something that can be addressed by a machine", and abstract concepts such as "non-addressable" or "music" can also be topics. In other words, a topic can be any object, such as a person, entity, concept, or meaning. In general, the term "thing" in the real world refers to things, the topic map standard defines this as a subject (subject). That is, the topic of a particular document is composed of words that can express the subject that the author of the document wants to represent.

Associations describe interrelationships between sets of topics and specify "relationships" between topics or define "roles" that act between each relationship. And associations can be used to express hierarchical general concepts or to represent more complex sets of relationships such as "meetings" and "meetings." You can add information when constructing associations. In other words, associations allow expression of various semantic relationships, as well as vertical relationships between topics. Associated topics become "members" of the association, and each member has a "role" within the relationship.

A resource is a detailed information resource related to a topic. A resource can be used to specify the relationship between an information resource (or the information itself) and a topic or information resource, or can represent a person itself and have resource information that is the URL of the person's home page. In other words, a resource represents a route between a topic and an information resource. The URI may indicate the location of a resource outside the topic map or may be directly represented by text data of the resource. Information resources that a topic may refer to may take various forms, such as document files, image files, video files, specific records in a database, and text data. And all resources for a topic share all the attributes represented by the topic.

For the practical application of such topic maps, a topic map editor that can construct and modify a topic map is used.

Conventional topic map editors (eg, TMTab, Semantext, and Nexis) define a relationship on another screen after creating a topic when creating and editing a topic and an association, and verify the association by referring to a partial topic map structure. . As a result, the topic map specification may not be sufficiently reflected, and the user interface may be complicated and not intuitive, resulting in inconvenience due to repetitive work.

In addition, other conventional topic map editors (eg, Ontopoly) process topics and associations on various screens, or because the results of the topics and associations are expressed in HTML format. It is easy to generate errors that can duplicate themselves.

In other words, until now, a topic is created by the topic map editor and structured to create an association, and then physically compared with the topic map editor, in order to verify the overall connectivity of the associated relations between each created topic and topic. We searched the wrong contents by using a separate topic map navigator or a topic map browser on a web browser, and corrected the contents through the topic map editor. That is, in the related art, since a topic map browser on a topic map editor and a topic map navigator (or a web browser) has to be used, input and verification of data related to topic map generation must be repeatedly performed in a separate environment. As a result, not only the work efficiency is lowered but also the reliability of the data is reduced due to data duplication and errors.

SUMMARY OF THE INVENTION The present invention has been proposed to solve the above-mentioned problems, and is a topic map editor and a topic map editor capable of efficiently processing and creating topics and associations related to distributed knowledge information resources. The purpose of the present invention is to provide a topic map processing method and a recording medium.

In order to achieve the above object, a topic map editor according to a preferred embodiment of the present invention receives an operation command and data related to the construction and modification of a topic map, transmits it to a controller, and displays a result from the controller. A user interface unit that individually displays a topic map structure, a topic list, an association list, and a resource list on one screen; And

And a controller configured to generate a topic map structure, a topic list, an association list, and a resource list according to the operation command and data input through the user interface unit and transmit the generated topic map structure to the user interface unit.

The user interface unit interprets an input operation command, a data generation and storage command, and sends the control frame unit to the control unit, and a topic map structure, a topic list, an association list, and a resource list from the control unit. And a menu frame portion to be displayed on each display area.

The controller may include a memory for storing topic data, association data, and resource data according to a first GoF design pattern, and the relationship data and list data of the topic map according to a second GoF design pattern from the data in the memory. Extracts and generates the topic map structure, the topic list, the association list and the resource list by using the relation data and list data of the data in the memory and the extracted topic map, and generates the generated topic map structure and topic list. And a data management unit to structure the association list and the resource list through frames according to the third GoF design pattern.

The first GoF design pattern is an Abstract Factory among a plurality of GoF design patterns, and the second GoF design pattern is a state, an iterator, and a mediator among the plurality of GoF design patterns, and the third GoF design pattern is an adapter in the plurality of GoF design patterns. to be.

On the other hand, the topic map processing method in the topic map editor according to an embodiment of the present invention, the first step of storing the input topic data, association data and resource data in the memory; Extracting relationship data and list data of a topic map from data in the memory; Generating a topic map structure, a topic list, an association list, and a resource list by using relationship data and list data of the data in the memory and the extracted topic map; And a fourth step of structuring and displaying the generated topic map structure, topic list, association list, and resource list on one screen.

The first process is performed using an Abstract Factory in a GoF design pattern, and the second process is performed using a state, an iterator, and a mediator in a GoF design pattern, and the fourth process is performed using an adapter in a GoF design pattern. Do it.

Hereinafter, a topic map editor and a topic map processing method in the topic map editor according to an embodiment of the present invention will be described with reference to the accompanying drawings.

2 is a block diagram of a topic map editor according to an embodiment of the present invention.

The topic map editor of the present invention includes a user interface unit 100 which receives a system operation related command from a user and makes an operation request to the system manager 200 and expresses a result thereof; A system manager 200 for processing a user's request in a corresponding topic map editor; And a controller 300 that receives the control of the user request from the system manager 200, performs a topic map related task, and returns the result to the user interface unit 100 through the system manager 200.

The user interface unit 100 receives a user's request, processes it, and displays the result. The user interface unit 100 receives a system operation, generation, storage or retrieval command from the user, interprets the command and transfers control to the system manager 200, and a system available to the user. And a menu frame portion 12 for displaying an operation menu.

The system manager 200 displays a system menu by receiving a user's command through the user interface 100 to perform a process desired by the user, or the project manager 30 or the data manager of the controller 300. 34) control to handle each role by passing control related to the command.

The controller 300 performs a topic map related process according to a user command received from the system manager 200. The control unit 300 includes a project management unit 30, a topic class management unit 32, a data management unit 34, a topic model unit 36, a relationship management unit 38, a resource management unit 40, a topic management unit 42, The topic map file manager 44 and the topic map database manager 46 are provided.

The project manager 30 manages knowledge information resources integrated into a topic map in group units. The topic class manager 32 manages topics of the knowledge information resource as a class. These types consist of user-specified names (eg supertype, subtype). The data manager 34 may control all topics related to topic, data, association, and resource (eg, creation, editing, and deleting of topic map data, definition of association, class creation, and relationship). And data list generation, topic map structure generation, etc.). The data manager 34 takes control from the system manager 200 and receives information related to topics, associations, and resources (eg, topicRef, subjectIndicatorRef, scope, instanceOf, topicMap, subjectIdentity, baseName, baseNameString, varient, varientName, parameters, member, roleSpec, resourceRef, resoureceData) are created and provided to the appropriate module. The topic model unit 36 generates a structure of data related to a topic. The relationship manager 38 receives the structures related to the topic from the topic model unit 36 and manages the related data. The resource manager 40 establishes an association with another topic related to the topic, and establishes an association with location information, which is a resource corresponding to the topic. The topic manager 42 manages topic information (eg, instanceOf, topicRef, subjectIndicatorRef, subjectIdentity, resourceRef, baseName, scope, baseNameString, varient, varientName). The topic map file manager 44 stores the topic map data of the knowledge information resource generated in the topic map editor in the XTM file format or recalls the stored topic map data. The topic map database manager 46 stores the topic map data of the knowledge information resource created or edited in the topic map editor in an internal database or recalls the topic MAC data stored in the database. The topic map data stored in the topic map file manager 44 is in the XTM file format, and the database in the topic mac database manager 46 is constructed as a relational database and the topic mac data stored in the database is in the form of a table schema. Is stored.

In FIG. 2, the system manager 200 is illustrated as a separate component that connects the user interface 100 and the controller 300, but the system manager 200 is included in the controller 300 as necessary. You may also do it.

The topic map data and related information above are standards conforming to the DTD of XTM 1.0 shown in FIG. 3.

In FIG. 3, <TopicMap> includes <Topic>, <Association>, and <MergeMap> as a root element, and <Occurrence>, which is one of the remaining TAOs, is included as a child element of <Topic> because it is an attribute of <Topic>. . Here, <MergeMap> is an element that allows merging two topic maps, and can refer to topics on another topic map.

<TopicMap> represents a topic map document in XML grammar. <Topic> represents the core concept representing the subject of the thing, <Association> represents the association between topics, and <Occurrence> represents the actual resource address of the topic.

<InstanceOf> represents a type that defines a topic at the top level that represents a characteristic where the topics at the lower level have the same meaning, and <TopicRef> refers to a general reference that the topic refers to. Represents a URI to use.

<SubjectIdentity> represents a subject specified by a topic, and <ResourceRef> represents a URI of an occurrence.

<BaseName> represents the name of the topic, represented as a string, <Scope> represents the criteria by which the topic can be valid only in a specific scope, and <BaseNameString> represents the base of the topic. Represents a string representing a name, and <Varient> represents a name representing another name in addition to the topic's base name. In other words, the actual topic name in <BaseName> is represented by <BaseNameString>, and its attribute can be represented by <Scope>.

<SubjectIndicatorRef> represents a URI used to refer to a public criterion, and <ResoureceData> represents information of a resource (Occurrence) in the form of character data.

<association> has a <member> that refers to the topics that make up the association, and each member can express its role as a <roleSpec>. That is, <member> represents all subjects that play a given role in <association>, and <roleSpec> represents the role played by a member in an association.

Although not shown, <parameters> represents additional processing context in <varient>, and <varientName> represents the resource on which <varient> is based.

4 is a view for explaining a topic relationship extraction pattern employed by the data manager 34 of FIG. 2, and FIGS. 5A to 5E are views illustrating a GoF design pattern used for the topic relationship extraction pattern of FIG. 4.

The data manager 34 of the present invention uses a set of patterns (that is, a generation pattern, a behavior pattern, and a structural pattern) generated based on a GoF design pattern. Such a set of patterns is called a topic relationship extraction pattern.

The data manager 34 generates a GoF that stores and references the topic data 331, the association data 332, and the resource data 333 in one hash memory 334 according to the Gang of Four design pattern. Form class 330a. The data manager 34 then generates a GoF behavior object 330b which extracts the relation data 335 and the list data 336 based on the data in the hash memory 334. Then, the data manager 34 displays the structure of the topic map structure list, the topic list, the association list, and the resource list on the screen based on the relationship data and the list data generated in the behavior object through the frame 337. The adapter 330c of the GoF is formed. The data manager 34 expresses the adapter structure on one screen and displays the topic map structure, the topic list, the association list and the resource list, respectively, in accordance with the correlation.

That is, the data manager 34 generates topic data, association data, and resource data through the generation class 330a and stores them in the hash memory 334 or refer to the hash memory 334. The internal connection of topic data, association data, and resource data generated by the generation class 330a is related to each other by the internal algorithm of the generation class 330a. The associated information is dataized and stored in the hash memory 334 of the data manager 34. The data manager 34 extracts the relation data and the list data of the topic map for display on the screen by the action object in the hash memory 334. The extraction operation is performed by each manager (eg, the topic model). Extracted in association with the unit 36, the relationship manager 38, the resource manager 40, and the topic manager 42. Thereafter, the data manager 34 arranges the data extracted by the behavior object in the adapter structure in the frame to display the data extracted by the behavior object on the screen. That is, the data manager 34 arranges the topic map structure list data, the topic list data, the association list data, and the resource list data in the adapter structure in the frame and transforms the data into data suitable for the screen.

Here, the GoF design pattern (author: Erich Gamma, Richard Helm, Ralph Johnson, John Vissides, publisher: Pearson Education Korea, publication date: September 26, 2002) has a rich experience in object-oriented software design. It is a catalog of simple and accurate solutions to design problems common to top designers. This catalog consists of 23 patterns that help you design reusable designs.

These 23 patterns are largely divided into creation patterns, behavior patterns, and structural patterns by purpose. In the present invention, a detailed pattern of a desired type is selected and used in each pattern to solve a problem. That is, in the embodiment of the present invention, the abstract pattern is used in the generation pattern. The behavior pattern uses State, Iterator, and Mediator. In the structural pattern, an adapter is used.

5A to 5E show the structure of patterns selectively used in the GoF design pattern described above. The Abstract Factory pattern structure 410 of FIG. 5A provides an interface that can create a set of related objects without generating a specific class or a set of objects that are independent of each other. Participating objects include AbstractFactory, ConcreateFactory, AbstractProduct, ConcreateProduct, and Client. In the Abstract Factory pattern structure 410, an AbstractFactory defines an interface as an operation for creating objects for conceptual products. ConcreateFactory defines an operation that creates an object for a specific product. AbstractProduct defines an interface to a conceptual product object. ConcreateProduct specifically defines the object definition that the factory will create and the interface defined by AbstractProduct. Client uses the interfaces declared in the AbstractFactory and AbstractProduct classes.

The state pattern structure 420 of FIG. 5B allows behavior to be changed according to the internal state of the object. This makes the object appear to be changing classes. Participating objects include Context, State, and ConcreteState. In the state pattern structure 420, the Context defines the interface of interest to the client. The Context also manages an instance of ConcreteState. State is defined as an interface encapsulating necessary actions for each state of Context. ConcreteState is a child element of State, and State has a number of ConcreteStates as child elements. Each of these ConcreteStates is also called a ConcreteState subclass. Each ConcreteState defines the current state of the object (ie, Context, State, ConcreteState). And each ConcreteState implements the actual behavior to be processed according to the state of the context.

Mediator pattern structure 430 of FIG. 5C encapsulates interactions between objects into objects. The Mediator pattern separates the reference relationship between objects in an object, and can expand variously independently. Participants include Mediator, ConcreteMediator, and Colleague. In the Mediator pattern structure 430, the Mediator defines the interface needed to interact with the Colleague object. ConcreteMediator implements cooperative behavior by harmonizing with Colleague objects, knows what its colleague is, and manages it. The Colleague knows who the Mediator object is and makes it possible for it to connect with other objects through the Mediator.

The Iterator pattern structure 440 of FIG. 5D provides a method of sequentially accessing elements of the composite object without exposing an internal representation method. Participants include Iterator, ConcreteIterator, Aggregate, and ConcreteAggregate. In the Iterator pattern structure 440, Iterator provides an interface for accessing and traversing elements. ConcreteIterator is a class that implements the interface defined in Iterator. It remembers the current position in the collection object during the traversal process. Aggregate defines an interface that creates an Iterator object. ConcreteAggregate implements the Iterator creation interface to return an instance of the corresponding ConcreteIterator.

Adapter pattern structure 450 of FIG. 5E converts the interface of the class to another interface that the client expects. The Adapter pattern allows you to work with modified classes that can't be used together because of incompatible interfaces. Participants include Target, Client, Adaptee, and Adapter. In the Adapter pattern structure 450, Target is a class that defines a domain-dependent interface for the client to use. Client is the target to operate with the object that satisfies the Target interface. Adaptee is a class that defines an existing interface that requires interface modification. Adapter is a class that matches Adaptee's interface to the Target interface.

Therefore, Abstract Factory in the creation pattern provides an interface that can create a set of related objects or create a set of objects independent of each other without specifying a specific class.

In the present invention, a generation class is used to store topic data, association data, and resource data in the hash memory 334 in the data manager 34.

In addition, Stat in the behavior pattern can change the behavior according to the internal state of the object, Iterator can access the elements of the complex object sequentially without exposing the internal representation method, and Mediator can control the interaction between objects. Can be encapsulated with In the present invention, the data management unit 34 generates a behavioral object that extracts the list data having the relation data having the association of the topic, the association and the resource and the list data having the list of the data corresponding to the topic, the association and the resource. do.

In addition, the adapter in the architectural pattern converts the interface of the class into another interface that the client expects, and also complements the classes that cannot be used because of incompatible interfaces. In the present invention, the data manager 34 uses the same to form an adapter structure in a frame having screen interface data (eg, a data frame having contents shown on the screen of FIG. 7A).

As described above, the set of patterns applied in the present invention is called a topic relationship extraction pattern in the present invention. The present invention performs the creation and editing of topics and associations related to distributed knowledge information resources using the above-described topic relationship extraction pattern.

6 is a flowchart illustrating a topic map processing method in a topic map editor according to an exemplary embodiment of the present invention.

First, the user inputs data or commands to the user interface unit 10 (S10).

For example, when a user selects (clicks) a topic map editor execution command or a menu using a key input means (eg, a mouse, a keyboard, etc.) (not shown), a corresponding signal is sent to the user interface unit 100. Is entered. Accordingly, the menu frame unit 12 in the user interface unit 100 transmits a menu execution command to the system manager 200 (S10-1, S11), and the system manager 200 executes the input menu. After processing the operation corresponding to the command (S12-2), the result is returned to the menu frame unit 12. Accordingly, the menu frame unit 12 displays the processed menu and screen.

On the other hand, when a user inputs data or executes a button click command using key input means (for example, a mouse or a keyboard) (not shown), the control frame unit 10 in the user interface unit 100 analyzes the system. Transfer to the management unit 200 (S10-2, S12).

If the data input by the user is data for creating a topic, an association, or a resource, or an edit command or a delete command, the system manager 200 processes the command data and the text data to process the create, edit, or delete command. It transmits to 34 (S12-3).

If the content received from the system manager 200 is a command for opening or storing the topic map data, the system manager 200 transmits the command for opening or storing the topic map data to the project manager 30 (S12). -One). The project manager 30 stores or opens the topic map data and transmits the topic map data to the topic class manager 32 (S13). Then, the topic class manager 32 retains the topic type of the input topic map data, and transmits other data to the data manager 34 (S14).

Subsequently, the data manager 34 provides the topic data to the topic manager 42 to hold it (S15). Accordingly, the topic manager 42 holds the input topic data and then sends the held topic data to the data manager 34 (S16).

The data manager 34 provides the association and resource data to the resource manager 40 to retain the data (S17). Accordingly, the resource manager 40 retains the input correlation and resource data, and then sends the retained correlation and resource data to the data manager 34 (S18).

The data manager 34 then transfers the topic map structure generation command to the topic model unit 36 (S19). Accordingly, the topic model unit 36 sends the generated topic map structure data back to the data manager 34 after generating the topic map structure (S20).

The data manager 34 transfers the received topic map structure data to the relationship manager 38 so as to be retained (S21). Accordingly, the relationship manager 38 retains the received topic map structure data, and then transfers the retained topic map structure data to the data manager 34 (S22).

In this way, the data manager 34 controls the management of data to be performed. The data processing result by the processing sequence in the data management unit 34 is displayed as one screen as in the screens illustrated in Figs. 7A to 7E. 7A to 7E, reference numeral 410 denotes a display region showing a topic map structure in a tree structure, reference numeral 420 denotes a display region showing a topic list, reference numeral 430 denotes a display region showing an association list, and reference numerals. 440 is a display area showing a list of resources.

For example, when a user clicks on a "country" in the topic map structure display area 410 as shown in FIG. 7A, the topic list, association list, and resource list associated with (country) is "country". Shown as data associated with

On the other hand, when the user selects "Denmark" in the topic list display area 420 on the screen of FIG. 7A, the association list display area 430 and the resource list display area 440 are "Denmark" as shown in FIG. 7B. It is shown as data related to. That is, when the user clicks on "Denmark" in the topic list display area 420 with the mouse, the control frame unit 10 receives and interprets "Denmark selection of the topic list" and sends it to the system manager 200. The system manager 200 sends the data manager 34 the data necessary for performance control for showing a correlation list and a resource list related to the data transmitted from the control frame unit 10 on the screen. Accordingly, the data manager 34 generates the association list and the resource list by referring not only to the topic data held by the topic manager 42 but also the association and resource data held by the resource manager 40. Thereafter, the data management section 34 passes the generated list data to the control frame section 10 and the menu frame section 12 via the system management section 200 to display a screen whose contents have been changed.

In the screen of FIG. 7B, when the user selects one data in the association list display area 430, the topic list and the resource list associated with the same are displayed as shown in FIG. 7C. This display operation is also performed similarly to the control operation of the data manager 34 described above.

In the screen of FIG. 7C, when a user selects one resource in the resource list display area 440, at least one topic having the resource, that is, the connected topic is displayed as shown in FIG. 7D. This display operation is also performed similarly to the control operation of the data manager 34 described above.

In the screen of FIG. 7D, when the user selects "Denmark" in the topic list display area 420, as shown in FIG. 7E, the association list and the resource list corresponding to the topic are displayed. This display operation is also performed similarly to the control operation of the data manager 34 described above.

In this way, the topic maps that are intricately connected to each other can be displayed in a single screen by displaying a topic map structure, a topic list, an association list, and a resource list, so that each data can be processed without any error in generating and editing. This allows users to process topic maps much more conveniently, quickly and efficiently.

As described in detail above, according to the present invention, by implementing a topic map editor using a topic relationship extraction pattern, it is possible to efficiently handle the creation and editing of topics and associations related to distributed knowledge information resources.

In particular, by displaying a topic map structure, a topic list, an association list, and a resource list on a single screen, it is possible to quickly and accurately create and edit a topic and association through one verification while referring to the entire structure of the topic map. Will be. As a result, it is possible to reduce the number of repetitive tasks in the process of producing a topic map and to easily remove data redundancy, thereby eliminating errors, thereby efficiently mapping the knowledge information to the user's intention.

On the other hand, the present invention is not limited only to the above-described embodiment, but can be modified and modified within the scope not departing from the gist of the present invention, the technical idea to which such modifications and variations are also applied to the claims Must see

Claims (11)

As a topic map editor, Receives operation commands and data related to the construction and modification of the topic map and sends them to the controller, and displays the results from the controller, and displays the topic map structure, the topic list, the association list, and the resource list individually on one screen. A user interface unit; And And a controller configured to generate a topic map structure, a topic list, an association list, and a resource list according to the operation command and data input through the user interface unit and transmit the generated topic map structure to the user interface unit. The method of claim 1, The user interface unit may include: a control frame unit for interpreting an input operation command, a data generation and storage command, and sending the command to the controller; A topic map editor comprising a menu frame portion to be displayed on a display area of the display. The method of claim 1, The control unit, And a memory for storing topic data, association data, and resource data according to a first GoF design pattern, and extracting relationship data and list data of the topic map according to a second GoF design pattern from the data in the memory. And generate the topic map structure, the topic list, the association list, and the resource list using the data in the memory, and generate the generated topic map structure, the topic list, the association list, and the resource list according to the third GoF design pattern. A topic map editor comprising a data management unit for structuring through frames. The method of claim 3, wherein And the first GoF design pattern is an Abstract Factory among a plurality of GoF design patterns. The method of claim 3, wherein The second GoF design pattern is a topic map editor, characterized in that among the plurality of GoF design patterns State, Iterator, Mediator. The method of claim 3, wherein The third GoF design pattern is a topic map editor, characterized in that the adapter in a plurality of GoF design patterns. As a topic map processing method in the topic map editor, A first step of storing input topic data, association data, and resource data in a memory; Extracting relationship data and list data of a topic map from data in the memory; Generating a topic map structure, a topic list, an association list, and a resource list by using relationship data and list data of the data in the memory and the extracted topic map; And And a fourth step of structuring and displaying the generated topic map structure, topic list, association list, and resource list on one screen. The method of claim 7, wherein The first process is a topic map processing method in a topic map editor, characterized in that the GoF design pattern is performed using an Abstract Factory. The method of claim 7, wherein The second process is a topic map processing method in the topic map editor, characterized in that the state, iterator, and mediator in the GoF design pattern. The method of claim 7, wherein The fourth process is a topic map processing method in the topic map editor, characterized in that the use of the adapter in the GoF design pattern. A computer-readable recording medium having recorded thereon a topic map processing program for executing the method according to any one of claims 7 to 10.

Images