KR101554576B1 - System and method for managing cooperation based ontology - Google Patents

Abstract

A collaborative ontology management system according to the present invention includes a project manager, an access authority setting unit for setting access rights of a plurality of editors and general users, a project management unit for creating and managing a project, an ontology based on the generated project, An ontology schema management unit for generating an ontology schema and generating an ontology schema by performing at least one of addition, modification and deletion of the generated ontology and a plurality of schemas; an ontology schema management unit for creating a plurality of ontology instances based on the ontology schema; And a storage unit for storing the generated ontology schema and the ontology instance, wherein the access right setting unit grants the project management authority to the project manager, and the ontology schema and the ontology instance Management authority to the plurality of editors, and grants the right to manage the ontology instance to the general user.

Description

[0001] SYSTEM AND METHOD FOR MANAGING COOPERATION BASED ONTOLOGY [0002]

The present invention relates to a collaborative ontology management system and method.

Many ontology generation methods, generation systems, and generation tools have been developed and existed. However, there is a problem that users can not understand each other on the generated ontology. Therefore, it is often impossible to reuse the ontology. To solve this problem, a collaborative ontology generation technology is being studied.

There is Wikipedia (Wikipedia), an encyclopedia based on a typical collaboration, and DBpedia, which contains contents converted from Wikipedia into ontologies. The schema / instance concept is a type of item / content rather than a feature / value type, and there is a problem that one item can not be filled with a plurality of various contents. In addition, divipedia is a system that converts Wikipedia generated content into an ontology and is not a system that generates a specific ontology.

In addition, there is a plug-in technology that enables Ontology to be developed simultaneously with different people using Protege, an ontology development tool developed by Stanford University. In this way, the collaborative ontology generation technology, in which people develop ontologies at the same time, can generate more common ontologies as many people can see and generate ontologies, and can be reusable because they are developed with the consent of many people .

However, in the case of the related art, only members that are specifically selected can share, create, and manage the ontology, which limits sharing and reuse. There is also a lack of functionality to provide and publish the generated ontology.

Korean Patent Publication No. 2011-0041894 (entitled " Instance Update Method on Ontology ") relates to a method for updating changed information of an instance constituting an ontology, A technique capable of managing a plurality of objects is disclosed.

Korean Patent Application No. 2011-0138487 entitled " Web-based Ontology Editing & Operating System " describes a method of extracting and analyzing ontologies using a structural characteristic of an ontology, Based ontology editing and operating system that can be easily used by related persons.

However, the above prior arts disclose general contents that can create, delete and edit the ontology, but it is difficult to share and reuse the ontology. Therefore, it is necessary to develop technology that can manage the ontology by classifying the performers in each stage and classifying the authority and role for each performer.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems of the prior art, and it is an object of the present invention to provide an ontology which is generated by members having rights as a project manager, an editor and a general user, The present invention provides a collaborative ontology management system and method capable of adding an instance to a generated ontology by users having general authority.

According to a first aspect of the present invention, there is provided a collaborative ontology management system including a project manager, an access authority setting unit for setting access rights of a plurality of editors and general users, An ontology schema management unit for generating an ontology and a plurality of schemas based on the generated project and generating an ontology schema by performing at least one of addition, modification and deletion of the generated ontology and a plurality of schemas, An ontology instance management unit for generating a plurality of ontology instances based on the ontology schema and a storage unit for storing the generated ontology schema and the ontology instance, Assigns the ontology schema and the ontology instance management authority to the plurality of editors, and grants the ontology instance management authority to the general user.

According to a second aspect of the present invention, there is provided an ontology management method using a collaboration-based ontology management system, comprising: setting access rights of a project manager, a plurality of editors, and a general user; creating a project; Generating an ontology schema and a plurality of ontologies based on the plurality of schemas; generating an ontology schema and a plurality of ontologies based on the plurality of schemas; Wherein the step of creating the ontology schema and the ontology instance includes the step of assigning the project management authority to the project manager and storing the ontology schema and the ontology instance management authority in a plurality of Project Editors And I give it, and give it the ontology instance administrative privileges to regular users.

According to the above-described embodiments of the present invention, it is possible to improve the reusability of various types of ontologies.

In addition, the ontology can be managed continuously and the instance can be added, which can increase the quality of the ontology.

In addition, since various instances can be added through participation of general users, it is easy to collect and manage a wide variety of data.

1 is a block diagram of a collaboration-based ontology management system according to an embodiment of the present invention.
2 is a view showing an access authority set by the access authority setting unit.
3 is a flowchart illustrating a method of managing a collaboration-based ontology according to an exemplary embodiment of the present invention.
FIG. 4 is a diagram illustrating each step performed according to the access right of the project manager, the editor, and the general user in the collaboration-based ontology management method according to the embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when an element is referred to as "comprising ", it means that it can include other elements as well, without departing from the other elements unless specifically stated otherwise.

1 is a block diagram of a collaboration-based ontology management system 100 according to an embodiment of the present invention.

The collaboration-based ontology management system 100 includes an access authority setting unit 110, a project management unit 120, an ontology schema management unit 130, an ontology instance management unit 140, and a storage unit 150.

1 refers to a hardware component such as software or an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and performs predetermined roles .

However, 'components' are not meant to be limited to software or hardware, and each component may be configured to reside on an addressable storage medium and configured to play one or more processors.

Thus, by way of example, an element may comprise components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, Routines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

The components and functions provided within those components may be combined into a smaller number of components or further separated into additional components.

The access authority setting unit 110 sets the access authority of the project manager, a plurality of editors, and a general user. At this time, the access authority setting unit 110 grants the project management authority to the project manager, grants the ontology schema and the ontology instance management authority to a plurality of editors, and grants the ontology instance management authority to the general user. The access authority setting unit 110 will now be described with reference to FIG.

2 is a view showing the access authority set by the access authority setting unit 110. As shown in FIG.

The access authority setting unit 110 can set access rights of the project manager, a plurality of editors, and general users. Specifically, the project manager is allowed to have access to the project management unit 120. Accordingly, the project manager can set the project creation, the purpose setting of the project, and the disclosure of the project. The editor is given an authority to access the ontology schema management unit 130, and the editor can create an ontology and a plurality of schemas, and add, modify, and delete the schema. Lastly, the general user is granted the right to access the ontology instance management unit 140. Accordingly, the general user can create the ontology instance and add, modify, and delete the instance.

On the other hand, the project manager may have authority to access the ontology schema management unit 130 and the ontology instance management unit 140 as well as the authority to access the project management unit 120. The editor may have the authority to access the ontology schema management unit 130 and have the authority to access the ontology instance management unit 140. However, the general user can only have access to the ontology instance management unit 140 and can not have access to the project management unit 120 and the ontology schema management unit 130. In addition, a plurality of editors can not have the authority to access the project management unit 120 as well.

Referring again to FIG. 1, the project management unit 120 creates and manages a project. As described above, the project management unit 120 is given access authority only to the project manager, and creates a project. The project management unit 120 may set not only the project but also the purpose of the project, the disclosure of the project, and the addition or deletion of a plurality of editors.

The ontology schema management unit 130 generates an ontology and a plurality of schemas based on the project generated by the project management unit 120 and performs at least one of addition, modification, and deletion of the generated ontology and a plurality of schemas, Create a schema. On the other hand, the ontology schema can be mainly composed of class, property, and relation, and can be expressed in an ontology language such as OWL, RDFS, and the like.

The ontology instance management unit 140 creates a plurality of ontology instances based on the ontology schema. At this time, the ontology instance management unit 140 can perform at least one of addition, modification, and deletion of the ontology instance to the generated ontology instance. The ontology instance management unit 140 can access the ontology instance management unit 140 through a user interface and can be accessed by a general user. At this time, general users having access rights to the ontology instance management unit 140 can be an unspecified number of users. On the other hand, the ontology instance may be a web resource such as an ID or a URI, or a literal value, and may be represented by RDFS or the like.

The storage unit 150 may store the generated ontology schema and the ontology instance. Based on the stored ontology schema and ontology instance, the ontology visualization unit 160 and the document output unit 170 to be described below can visualize or output the ontology schema and the instance.

The storage unit 150 may be a nonvolatile memory such as a cache, a read only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) A memory device, a volatile memory device such as a RAM (Random Access Memory), or a storage medium such as a hard disk drive (HDD), a CD-ROM, or the like.

The collaboration-based ontology management system 100 according to the present invention may further include an ontology visualization unit 160 and a document output unit 170. [

The ontology visualization unit 160 can visualize the ontology schema and the ontology instance based on the visualization type and condition. In other words, when the project manager and multiple editors create or derive an ontology schema or an ontology instance, or when an ordinary user creates an ontology instance or wants to obtain desired information from the ontology schema or ontology instance, can do. At this time, the ontology visualization unit 160 can preferentially arrange or remove the schema based on the project manager and the plurality of editor information among the plurality of schemas, or visualize the filtered ontology instance.

On the other hand, the visualization type may be a form such as RDF or OWL, or may be a table form of an ontology graph or database consisting of circles and lines. The project manager, multiple editors and general users can place the desired ontology schema first, or exclude the undesired ontology schema, and can visualize the ontology instance by filtering based on the optimized ontology schema optimized for the user information.

The document output unit 170 may output the visualized ontology schema and the ontology instance in a documented format. At this time, the document output unit 170 may document the ontology schema and the ontology instance by selecting the type and condition of the document. Through the document output unit 170, a project manager, a plurality of editors, and general users can document and output the results of the visualized ontologies in the form of a web page, RDF, OWL, graph, or picture file.

In this way, the collaboration-based ontology management system 100 according to the present invention can easily visualize the ontology and display it to the users, thereby allowing users who do not have accurate knowledge about the ontology to easily participate and document the ontology.

3 is a flowchart illustrating a method of managing a collaboration-based ontology according to an exemplary embodiment of the present invention.

The collaborative ontology management method according to the present invention first sets the access rights of the project manager, the plurality of editors, and the general users (S110). At this time, the project management authority is assigned to the project manager in relation to the access authority, the right to manage the ontology schema and the ontology instance is given to the plurality of project editors, and the authority to manage the ontology instance is granted to the general user.

Specifically, the project manager is given the right to manage the project, and multiple editors are allowed to manage the ontology schema. Also, the general user is allowed to manage the ontology instance. At this time, the project manager can have the authority to be managed by the editor and the general user, and the editor can have the right to manage the ontology instance by the general user. However, ordinary users can not have administrative privileges for project managers and editors, and editors can not have administrative privileges for project administrators.

Next, the project is created by the project manager (S120). At this time, the project manager can not only create the project but also set the purpose of the project, set whether the project is disclosed or not, It is possible.

Next, an ontology and a plurality of schemas are generated based on the generated project, and an ontology schema is generated by performing at least one of addition, modification, and deletion for the generated ontology and a plurality of schemas (S130).

Next, a plurality of instances are created based on a plurality of schemas, and an ontology instance is created (S140). At this time, it is possible to perform at least one of addition, modification, and deletion of the ontology instance to the generated ontology instance. The ontology instance management right is granted to the general user, and the ontology instance can be managed through the user interface.

Next, the created ontology schema and the ontology instance are stored (S150). Based on the stored ontology schema and the ontology instance, the ontology schema and instance can be visualized or documented and output as described below.

The collaboration-based ontology management method according to the present invention may further include visualizing an ontology schema and an ontology instance based on a visualization type and a condition. The step of visualizing the ontology schema and the ontology instance may first arrange or exclude the schema based on the project manager and the plurality of editors among the plurality of schemas, or visualize the filtered ontology instance.

In this case, the visualization type can be a form such as RDF or OWL, and it can be a table form of an ontology graph or database composed of circles and lines,

In addition, the collaboration-based ontology management method according to the present invention may further include documenting and outputting a visualized ontology schema and an ontology instance. Through the document output, the project manager, multiple editors, and general users can document and output the results of the visualized ontologies in the form of a web page, RDF, OWL, graph or picture file.

Thus, the collaborative ontology management method according to the present invention can easily visualize the ontology and display it to the users, so that users who do not have accurate knowledge about the ontology can easily participate and document the ontology.

FIG. 4 is a diagram illustrating each step performed according to the access right of the project manager, the editor, and the general user in the collaboration-based ontology management method according to the embodiment of the present invention.

The collaboration-based ontology management method according to the present invention distinguishes access authority for each project manager, editor, and general user. First, the project manager sets the access authority of the project manager, the editor, and the general user (S110). Then, a project is created (S120), the purpose of the generated project is set, the disclosure status is set, and a plurality of editors can be added or deleted.

A plurality of editors selects a project, checks whether the project has access right, and generates an ontology schema of the project to which the access right is granted (S130). At this time, a step of visualizing an ontology schema may be additionally performed.

General users first select a project, check whether the project has access permission, and create an ontology instance of the project to which the access right is granted (S140). At this time, a step of visualizing an ontology instance may be additionally performed. In addition, the visualized ontology instance can be documented and output.

One embodiment of the present invention may also be embodied in the form of a recording medium including instructions executable by a computer, such as program modules, being executed by a computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes any information delivery media, including computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism.

While the methods and systems of the present invention have been described in connection with specific embodiments, some or all of those elements or operations may be implemented using a computer system having a general purpose hardware architecture.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

100: Collaboration-based ontology management system 110: Access right setting unit
120: project management unit 130: ontology schema management unit
140: ontology instance management unit 150:
160: Ontology visualization unit 170: Document output unit

Claims (10)

In a collaborative ontology management system,
A project manager, a plurality of editors, and an access authority setting section for setting access authority for general users,
A project management unit for creating and managing a project,
An ontology schema management unit for generating an ontology and a plurality of schemas based on a project generated by the project management unit and generating an ontology schema by performing at least one of addition, modification and deletion of the generated ontology and a plurality of schemas;
An ontology instance management unit for generating a plurality of ontology instances based on the ontology schema;
And a storage unit for storing the generated ontology schema and the ontology instance,
Wherein the access authority setting unit grants the management authority for the project to the project manager, the management authority for the ontology schema to the plurality of editors, and the management authority for the ontology instance is managed by the plurality of editors, A collaborative ontology management system for general users. The method according to claim 1,
Wherein the ontology instance management unit performs at least one of adding, modifying, and deleting an ontology instance to the generated ontology instance. The method according to claim 1,
And an ontology visualization unit for visualizing the ontology schema and the ontology instance based on the visualization type. The method of claim 3,
Wherein the ontology visualization unit preferentially arranges or removes a schema based on information of the project manager and a plurality of editors among the plurality of schemas, or visualizes a filtered ontology instance. The method of claim 3,
Based ontology schema and a document output unit for documenting and outputting the ontology instance. A method for managing an ontology using a collaborative ontology management system,
Setting the access rights of the project manager, the plurality of editors, and the general users respectively,
Creating a project,
Generating an ontology and a plurality of schemas based on the generated project,
Generating an ontology schema by performing at least one of adding, modifying, and deleting the generated ontology and a plurality of schemas;
Generating a plurality of ontology instances based on the plurality of schemas; and
Storing the created ontology schema and ontology instance,
Wherein the setting of the access authority comprises:
Based ontology management that is given to a plurality of project editors and the general user, a management right of the project is assigned to a project manager, management rights of the ontology schema are given to the plurality of editors, Way. The method according to claim 6,
Further comprising performing at least one of adding, modifying, and deleting the ontology instance to the collaboration-based ontology management method. The method according to claim 6,
Further comprising: visualizing the ontology schema and the ontology instance based on the visualization type. 9. The method of claim 8,
Wherein the step of visualizing the ontology schema and the ontology instance comprises:
Wherein a schema is first arranged or removed based on information of the project manager and a plurality of editors among the plurality of schemas, or a filtered ontology instance is visualized. 9. The method of claim 8,
Further comprising documenting and outputting the visualized ontology schema and the ontology instance, and outputting the collaborative ontology schema.

Images