KR20130064226A - Query processing apparatus and method to use relational database as owl ontology on semantic web - Google Patents

Query processing apparatus and method to use relational database as owl ontology on semantic web Download PDF

Info

Publication number
KR20130064226A
KR20130064226A KR1020110130734A KR20110130734A KR20130064226A KR 20130064226 A KR20130064226 A KR 20130064226A KR 1020110130734 A KR1020110130734 A KR 1020110130734A KR 20110130734 A KR20110130734 A KR 20110130734A KR 20130064226 A KR20130064226 A KR 20130064226A
Authority
KR
South Korea
Prior art keywords
query
tbox
abox
query processing
rbox
Prior art date
Application number
KR1020110130734A
Other languages
Korean (ko)
Other versions
KR101280058B1 (en
Inventor
김명호
최지웅
Original Assignee
숭실대학교산학협력단
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 숭실대학교산학협력단 filed Critical 숭실대학교산학협력단
Priority to KR20110130734A priority Critical patent/KR101280058B1/en
Publication of KR20130064226A publication Critical patent/KR20130064226A/en
Application granted granted Critical
Publication of KR101280058B1 publication Critical patent/KR101280058B1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2452—Query translation
    • G06F16/24522—Translation of natural language queries to structured queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/36—Creation of semantic tools, e.g. ontology or thesauri
    • G06F16/367—Ontology

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Artificial Intelligence (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Animal Behavior & Ethology (AREA)

Abstract

PURPOSE: A query processing device using a relational database in a semantic web as OWL(Ontology Web Language) ontology and a method thereof are provided to use the relational database in the semantic web as the OWL ontology without a data movement process and a schema structure change for the relational database. CONSTITUTION: A query analyzing unit(110) classifies a query received from a semantic web application into an ABox query processing part and a TBox/RBox query processing part. A TBox/RBox processing unit(120) infers TBox OWL ontology generated from a schema of a relational database to transmit the TBox/RBox query processing part and requests query processing. An ABox processing unit(130) processes the ABox query processing part based on schema metadata collected from the relational database and metadata about the TBox ontology. [Reference numerals] (110) Query analyzing unit; (120) TBox/RBox processing unit; (130) ABox processing unit; (140) Query result transmitting unit

Description

Query Processing Apparatus and Method to use relational database as OWL ontology on semantic web}

The present invention relates to a query processing apparatus and method for using a relational database (RDB) as an OWL ontology in a semantic web, and more particularly, a relational database that is already built and serviced. Relates to an apparatus and a method for use in query processing in the semantic web.

The Semantic Web is a framework that allows computers to process information and relationships between resources in the distributed environment such as the Internet.

In relation to the Semantic Web, the ontology describes concretely the concepts that are the smallest unit of information so that computers can understand the information. Can be. Or simply as a database for the Semantic Web.

In addition, the Resource Description Framework (RDF) and Ontology Web Language (OWL) are the "ontology description language" recommendations (standards) for the semantic web published by the World Wide Web Consortium (W3C). OWL, unlike RDF, is a language designed to expand knowledge in ontology by reasoning.

SPARQL, on the other hand, is a standard query language for RDF. That is, applications on the Semantic Web request a SPARQL query to obtain data from the RDF ontology, and the RDF ontology responds with a result set for the query.

The standard query language for the OWL ontology is currently unpublished. However, OWL ontology is designed to be downgraded to RDF ontology and analyzed (OWL ontology can be interpreted as RDF ontology), so OWL ontology can also extract data using SPARQL. However, in this case, since SPARQL extracts knowledge based on pattern matching, there is a limitation that it is impossible to extract knowledge based on logic from OWL ontology. Therefore, W3C is currently developing SPARQL 1.1 to provide OWL-level queries by extending the semantics of SPARQL.

As the semantic web is attracting attention as the next generation web, a study is performed to automatically convert data of various formats (RDB, XML, EXCEL) that supply data to the current web (WWW) into the ontology of the RDF or OWL format required by the semantic web. Is actively underway.

The relational database (RDB), which is one of the current web data, is a collection of data items composed of a series of structured tables. The structure of the database and the location of the data to be constructed are predetermined.

Since RDB is responsible for supplying data for composing most of the dynamic web contents in the current web, research to convert the semantic relation between RDB data and data into RDF or OWL is very important in the field of semantic web research. In position.

Korean Patent Registration No. 0919845 discloses a metamodeling-based ontology system. According to the disclosed system, an ontology relational database structure can be constructed using an ontology language semantic tag model based on the syntax structure and semantic structure of the ontology language.

However, the prior art is an invention for extracting data from ontology documents expressed in ontology languages such as XML, RDF, and OWL, storing them in a database, and serving them, and having a specific type of database schema for storing ontology.

The technical problem to be solved by the present invention is to process a relational database that is already built and serviced without considering the semantic web, and to use it as an OWL ontology in the semantic web without any special changes. An apparatus and method are provided.

Another technical problem to be solved by the present invention is to query a relational database that is already built and serviced without using the semantic web as an OWL ontology in the semantic web without any change. The present invention provides a computer-readable recording medium having recorded thereon a program for executing a processing method on a computer.

In order to achieve the above technical problem, the query processing apparatus for using the relational database as the OWL ontology in the semantic web according to the present invention, the ABox query processing portion and the TBox / RBox query processing portion of the query received through the semantic web application A query analysis unit classified into; A TBox / RBox processing unit for requesting query processing by transmitting the TBox / RBox query processing unit to a native inference unit that infers a TBox OWL ontology generated from a schema of a relational database previously constructed to perform TBox / RBox query processing; An ABox processor configured to process the ABox query processing part based on schema metadata collected from the relational database and metadata about the TBox ontology received from the native inference machine; And a query result transmission unit which transmits the result data extracted from the relational database based on the result of processing the ABox query processing unit and the processing result of the TBox / RBox query processing unit by the native inference device to the semantic web application. Equipped.

In order to achieve the above technical problem, a query processing method for using the relational database as an OWL ontology in the semantic web according to the present invention, (a) the ABox query processing portion and the TBox / RBox queries received through the semantic web application Classifying the query processing portion; (b) The TBox / RBox query processing portion infers a TBox OWL ontology generated from a schema of a pre-established relational database and sends it to a native inference that performs TBox / RBox query processing to request query processing, and the ABox query Processing the processing based on the schema metadata collected from the relational database and metadata on the TBox ontology received from the native inference machine; And (c) transmitting the result data extracted from the relational database based on the processing result of the ABox query processing part and the processing result of the TBox / RBox query processing part by the native inference machine to the semantic web application. Have

According to a query processing apparatus and method for using a relational database as an OWL ontology in the semantic web according to the present invention, the relational database is OWL in a semantic web environment without a separate schema structure change and data movement process for a previously constructed relational database. It can be used like an ontology. It can also save time costs and solve data inconsistencies caused by data movement.

1 is a diagram illustrating a structure in which an RDF ontology generated from an RDB is serviced to a semantic web application.
2 is a diagram illustrating a structure in which an OWL ontology generated from an RDB is serviced to a semantic web application.
3 is a diagram showing the configuration of an entire system including a query processing apparatus for using a relational database as an OWL ontology in the semantic web according to the present invention;
4 is a block diagram showing the configuration of a preferred embodiment of a query processing apparatus for using a relational database as an OWL ontology in the semantic web according to the present invention;
5 is a block diagram showing a specific configuration of a mapping unit;
6 is a view showing a role of a query processing apparatus for using a relational database as an OWL ontology in the semantic web according to the present invention in terms of a relational database and a semantic web;
7 is a flowchart illustrating a preprocessing process of a query processing apparatus according to the present invention;
8 is a flowchart illustrating a process of executing a query processing apparatus according to the present invention after the preprocessing process of FIG. 7.

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the apparatus and method for using the relational database according to the present invention as the OWL ontology.

1 is a diagram illustrating a structure in which an RDF ontology generated from an RDB is served to a semantic web application.

Referring to FIG. 1, an RDF ontology generated from an RDB can serve a semantic web application in two ways: (a) structure and (b) structure. Techniques that support (a) structures appeared earlier than those that support (b) structures.

The structure (a) of FIG. 1 is a structure for converting entire RDB data into RDF, loading the RDF repository suitable for servicing an RDF ontology, and then performing a SPARQL query service. (a) Using the structure incurs a separate RDF store purchase, build cost, and time costs. In addition, there is a problem that an inevitable data inconsistency occurs between data in the original RDB and RDF ontology.

Structure (b) of Figure 1 is a structure that has been recently proposed to overcome the disadvantages of the structure (a). Unlike structure (a), (b) does not generate RDF from RDB in advance. However, after generating only the data corresponding to the query result in RDF format at the time of SPARQL query, RDF data is transmitted to the client requesting the query.

(b) At the heart of the structure is the SPARQL query engine. This query engine translates internally entered SPARQL queries into SQL queries and also translates SQL query results into RDF format.

In addition, the structure of (b) enables the existing RDB to be simultaneously serviced as an ontology without any additional modification process, thereby facilitating the construction of the semantic web-based ontology infrastructure at a lower cost.

However, the service shown in FIG. 1 has a problem due to the limitations of the RDF itself. RDF ontology is a collection of edge-labeled directed graphs, and SPARQL, a query language for RDF, is also based on graph pattern matching. Therefore, RDF-based ontology cannot satisfy the needs of semantic web applications that want logic-based knowledge extraction.

2 is a diagram illustrating a structure in which an OWL ontology generated from an RDB is serviced to a semantic web application.

The research on converting RDB to RDF and serving it is at a commercially available level, but the research on converting RDB to OWL and serving it is at an early stage. At the current level, the only way to use the reasoning machine called KAON2 is to service the RDB as an OWL ontology.

Referring to FIG. 2, the hybrid reasoner may mean KAON 2. Hybrid reasoners also play the role of a query engine.

In general, OWL ontology derived from RDB includes a large amount of data due to the nature of RDB, because KAON2 can infer large-scale OWL ontology. However, KAON2 inference machine performs inference in DB, and for inference using KAON2, it must comply with DB schema required by KAON2.

That is, the RDB to be converted to OWL should be converted to the structure required by KAON2. This means that the data migration process must be carried out by moving the entire original RDB to a separate DB defined by the structure required by KAON2.

This process has the problem of additional DB purchase and construction cost and time and effort cost for data migration. In addition, there is an unavoidable data discrepancy with the original data.

This is similar to the disadvantage of the structure (a) of FIG. 1 described above. Meanwhile, since the ontology converted in the RDB has to undergo an inference process before performing the query service, the initial construction time is longer than that of the structure of FIG.

On the other hand, the limitation of RDF based on the graph pattern matching as described above can be overcome by the ontology of the OWL level. However, there is a problem related to the support of the inference system in order to service the OWL level ontology for RDB.

The ontology derived from the RDB has large OWL Individuals created from the RDB instance. In other words, in such an environment, the inference system must be able to infer a large ABox that can handle a large number of objects.

However, most OWL-supported inference systems focus on TBox (Terminological) inference based on Tableaux algorithm, and have the problem of ABox inference that occurs due to the characteristics of Tableaux algorithm. The problem with ABox inference is that since all of the ontology is loaded into memory and then inferred operations are performed, the amount of memory required is equal to the capacity of the RDB instance.

As an alternative to the large-capacity ABox inference of the Tableaux algorithm-based inference, there is a disk-based inference for performing ABox inference on disk. The disk-based inference machine must perform the inference while storing the data for inference in the RDB, or conform to the specific DB schema designed by the inference machine for the purpose of inference.

Therefore, if you want to service the ontology derived from RDB using disk-based inference, you have to go through the data migration process. This means that the on-site physical generation of ontology from RDB is required, and the same problem occurs in the data migration process described above.

In conclusion, the present invention has a structure for enabling the service to be OWL ontology at the same time without requiring a separate structure change and data movement process in the relational database that is already built and serviced to solve this problem.

3 is a diagram showing the configuration of an entire system including a query processing apparatus for using a relational database as an OWL ontology in the semantic web according to the present invention.

Referring to FIG. 3, the entire system is composed of a query engine 100, a mapping unit 200, a native reasoner 300, and a relational database 400. In FIG. 3, the query engine 100 corresponds to the query processing apparatus according to the present invention. Hereinafter, the query processing apparatus according to the present invention will be described by defining the query engine 100.

The query engine 100 classifies the OWL level query statement input from the semantic web application into an ABox query processing portion and a TBox / RBox query processing portion. The native inference unit 300 receives the query processing request from the query engine 100, processes the TBox / RBox query processing portion, and transmits the result back to the query engine 100.

The query engine 100 collects necessary metadata from the native reasoner 300 and the mapping unit 200 to process the ABox query processing part. Thereafter, the mapping unit 200 generates the SQL format based on the data structure generated by the query engine 100 from the processing result of the ABox query processing unit, and generates mapping data necessary for generating the SQL query set. 100).

The query engine 100 requests the relational database 400 for query processing in the generated SQL format, processes the result data extracted from the relational database 400 into a URI format, and then queries the TBox / RBox by the native inference unit 300. Send to the semantic web application with the processing result of the processing part.

On the other hand, if the query input from the semantic web application does not include the TBox / RBox query processing portion, the query engine 100 does not request the query processing to the native inference 300.

However, the query engine 100 generates a new TBox / RBox query and transmits it to the native reasoner 300 to collect metadata necessary to process the ABox query processing portion, and uses the processing result to transmit the ABox query processing portion. Can be processed.

As described above, the query processing apparatus according to the present invention, that is, the query engine 100 is a relational database (requiring a process such as a separate structure change and data movement) to the relational database 400 that is already built and serviced ( 400 can be used as an OWL ontology to process queries from semantic web applications.

4 is a block diagram showing a configuration of a preferred embodiment of the query engine 100, that is, a query processing apparatus for using the relational database as an OWL ontology in the semantic web according to the present invention, and FIG. It is a block diagram showing the specific configuration of.

4 and 5, the query engine 100 of the present invention is composed of a query analyzer 110, TBox / RBox processing unit 120, ABox processing unit 130 and the query result transmission unit 140 The mapping unit 200 includes a query mapping unit 210, a data mapping unit 220, and a schema mapping unit 230.

The query analyzer 110 classifies the query received through the semantic web application into an ABox query processing part and a TBox / RBox query processing part.

The TBox / RBox processing unit 120 uses the TBox / RBox query processing unit as a native inference unit 300 that infers the TBox OWL ontology generated from the schema of the relational database 400 previously constructed to perform TBox / RBox query processing. Request for query processing by sending. Native reasoner 300 represents a conventional reasoner based on the Tableaux algorithm.

In this case, as described above, if the input query does not include the TBox / RBox query processing part, the TBox / RBox processing unit 120 does not request a query processing for the native reasoner 300.

The ABox processing unit 130 processes the ABox query processing part based on the metadata collected from the relational database 400 and the metadata received from the native inference unit 300.

If the received query does not include the TBox / RBox query processing part, the TBox / RBox processing unit 120 generates a new TBox / RBox query for collecting data necessary for processing the ABox query processing part, thereby inducing the native inference machine 300. To transmit.

The ABox processing unit 130 receives the processing result of the native inference unit 300 for the newly generated TBox / RBox query and processes the ABox query processing part.

The query result transmission unit 140 extracts the result data extracted from the relational database 400 based on the processing result of the ABox query processing part and the processing result of the TBox / RBox query processing part by the native inference machine 300. To send.

Specifically, the ABox processing unit 130 converts the query processing result of the ABox query processing unit into the SQL format and queries the relational database 400, and the query result transmission unit 140 converts the result data into a URI format to TBox. / RBox Sends the result of the query processing part to the semantic web application.

Since the processing result of the TBox / RBox query processing part by the native inference unit 300 is provided in a URI format, it can be transmitted to the semantic web application without a separate format conversion.

In this case, the query mapping unit 210 provides the ABox processing unit 130 with data required for the ABox processing unit 130 to generate an SQL format based on the data structure generated from the query processing result for the ABox query processing unit. The data mapping unit 220 provides the query result transmission unit 140 with data required for the query result transmission unit 140 to convert the result data extracted from the relational database 400 into a URI format.

In addition, in connection with the query processing process, the data mapping unit 220 provides the ABox processing unit 130 with metadata about elements of the relational database 400 mapped to each element of the ABox query processing unit. In addition, the schema mapping unit 230 provides the TBox OWL ontology to the native inference unit 300, and provides metadata about the elements of the relational database 400 mapped to each element of the TBox / RBox query processing unit. 130).

6 is a view showing the role of a query processing apparatus for using a relational database as an OWL ontology in the semantic web according to the present invention in terms of a relational database and a semantic web.

Referring to FIG. 6, since the query processing apparatus according to the present invention uses an existing RDB as it is, the query processing apparatus may operate in the same manner as a general SQL query tool based on the RDB. In other words, from the standpoint of RDB, the apparatus of the present invention is regarded as the same as general SQL query tool.

On the other hand, in view of the semantic web using the OWL ontology, the apparatus of the present invention serves to make the RDB appear as an OWL ontology. That is, the apparatus of the present invention serves as an OWL view for the RDB from the semantic web point of view.

7 is a flowchart illustrating a preprocessing process of the query processing apparatus according to the present invention, and FIG. 8 is a flowchart illustrating a process of performing the query processing apparatus according to the present invention after the preprocessing process of FIG. 7.

In the preprocessing process, the schema mapping unit 230 collects schema metadata from the relational database 400 that is built in advance (S710).

Next, the schema mapping unit 230 generates a TBox of the OWL ontology by applying a schema mapping algorithm based on the collected metadata, and transmits the TBox of the OWL ontology to the native inference unit 300 (S720).

After inferring the TBox OWL ontology and expanding the ontology (S730), the native inference unit 300 waits for a query processing request of the TBox / RBox query processing unit from the TBox / RBox processing unit 120 (S740).

At this time, the schema mapping unit 230 stores the collected metadata locally. This is because when the ABox processing unit 130 requires metadata for query processing, the overall query processing time can be shortened by minimizing the connection to the DB using the stored metadata.

After the preprocessing process described above, the query analysis unit 110 classifies the OWL level query received through the semantic web application into an ABox query processing part and a TBox / RBox query processing part (S810), and processes the ABox query on the received query. It is determined whether the part exists (S820).

If the ABox query processing part does not exist in the received query (when only the TBox / RBox query processing part exists), the TBox / RBox processing unit 120 performs processing of the TBox / RBox query processing part in the native inference unit 300. Request and receives the processing result of the TBox / RBox query processing part from the native inference unit 300 again (S900).

Thereafter, the query result transmitter 140 transmits the processing result of the TBox / RBox query processing part to the semantic web application (S890). At this time, since the processing result of the TBox / RBox query processing part is URI format, there is no format conversion separately.

Meanwhile, when the ABox query processing part exists in the received query, the query analyzing unit 110 determines whether the TBox / RBox query processing part exists (S830).

If there is an ABox query processing part but no TBox / RBox query processing part exists in the inputted query (when only the ABox query processing part exists), the ABox processing unit 130 provides information necessary for processing the ABox processing part. In order to obtain a new TBox / RBox query is generated to request a query processing to the native inference 300 (S850).

Thereafter, the ABox processing unit 130 processes the ABox query processing part based on the processing result received from the native inference unit 300 (S860).

The ABox processing unit 130 converts the processing result of the ABox query processing unit into an SQL format and queries the relational database 400 (S870).

In this case, the query mapping unit 210 provides the ABox processing unit 130 with data necessary for generating the SQL format based on the data structure generated by the ABox processing unit 130 from the query processing result for the ABox query processing unit (S870). do.

Next, the query result transmitter 140 converts the result data extracted from the relational database 400 into a URI format (S880). The data mapping unit 220 provides data required by the query result transmitting unit 140 in this process.

Finally, the query result transmitter 140 transmits the query processing result of the converted URI format to the semantic web application (S890).

If both the ABox query processing part and the TBox / RBox query processing part exist in the received query, the TBox / RBox processing unit 120 requests the native inference machine 300 to process the TBox / RBox query processing part and re-natives. The processing result of the TBox / RBox query processing part is received from the reasoning unit 300 (S840).

On the other hand, the ABox processing unit 130 processes the ABox query processing portion by the processing result and metadata received from the native inference unit 300 (S860). In this case, the metadata is data about elements of the relational database 400 mapped to each element of the TBox / RBox query processing part.

The ABox processing unit 130 converts the processing result of the ABox query processing part into the SQL format and extracts the result data from the relational database 400 (S870).

In this case, the query mapping unit 210 provides the ABox processing unit 130 with data necessary for generating the SQL format based on the data structure generated by the ABox processing unit 130 from the query processing result for the ABox query processing unit (S870). do.

Next, the query result transmitter 140 converts the result data extracted from the relational database 400 into a URI format (S880). The data mapping unit 220 provides data required by the query result transmitting unit 140 in this process.

Finally, the query result transmitting unit 140 transmits the result data and the processing result of the TBox / RBox query processing unit received from the native inference unit 300 to the semantic web application (S890). At this time, since the processing result of the TBox / RBox query processing part is URI format, there is no format conversion separately.

As a result, the difference between the case where only ABox query processing part exists in the query and the case where both ABox query processing part and TBox / RBox query processing part exist is present. When only ABox query processing part exists, ABox processing unit 130 newly sets TBox / It generates an RBox query and sends it to the native reasoner 300.

In addition, when both ABox query processing part and TBox / RBox query processing part exist, the ABox processing unit 130 schemas metadata about elements of the relational database 400 mapped to each element of the TBox / RBox query processing part. It is provided by the mapping unit 230.

The present invention can also be embodied as computer-readable codes on a computer-readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, and may be implemented in the form of a carrier wave (for example, transmission via the Internet) . The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is clearly understood that the same is by way of illustration and example only and is not to be taken by way of limitation in the embodiment in which said invention is directed. It will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the appended claims.

Claims (13)

A query analyzing unit classifying a query input through the semantic web application into an ABox query processing unit and a TBox / RBox query processing unit;
A TBox / RBox processing unit for requesting query processing by transmitting the TBox / RBox query processing unit to a native inference unit that infers a TBox OWL ontology generated from a schema of a relational database previously constructed to perform TBox / RBox query processing;
An ABox processor configured to process the ABox query processing part based on schema metadata collected from the relational database and metadata about the TBox ontology received from the native inference machine; And
A query result transmission unit configured to transmit the result data extracted from the relational database based on the result of processing the ABox query processing unit and the result of processing the TBox / RBox query processing unit by the native inference device to the semantic web application. Query processing apparatus in the semantic web, characterized in that. The method of claim 1,
The ABox processing unit converts a query processing result for the ABox query processing unit into a SQL format to extract the result data from the relational database,
And the query result transmitting unit converts the result data into a URI format and transmits the result data to the semantic web application together with the processing result of the TBox / RBox query processing unit. The method of claim 2,
A query mapping unit for providing, to the ABox processing unit, data required for the ABox processing unit to generate an SQL format based on a data structure generated from a query processing result for the ABox query processing unit; And
And a data mapping unit which provides the query result transmission unit with the data required for the query result transmission unit to convert the result data into the URI format. The method of claim 3, wherein
A schema mapping unit which provides the TBox OWL ontology to the native inference unit and provides metadata to elements of the relational database mapped to each element of the TBox / RBox query processing unit to the ABox processing unit; Query processing apparatus in the semantic web, characterized in that. The method according to claim 3 or 4,
And the data mapping unit provides metadata about elements of the relational database mapped to each element of the ABox query processing unit to the ABox processing unit. The method according to any one of claims 1 to 4,
And the metadata transmitted from the native inference unit by the ABox processor is a result of processing of the TBox / RBox query processing unit by the native inference unit. The method according to any one of claims 1 to 4,
If the TBox / RBox processing unit does not include the TBox / RBox query processing unit, the TBox / RBox processing unit generates and transmits a TBox / RBox query for collecting data necessary for processing the ABox query processing unit to the native inference unit.
And the ABox processing unit receives the processing result of the native inference unit for the TBox / RBox query and processes the ABox query processing unit. (a) classifying a query received through the semantic web application into an ABox query processing portion and a TBox / RBox query processing portion;
(b) The TBox / RBox query processing portion infers a TBox OWL ontology generated from a schema of a pre-established relational database and sends it to a native inference that performs TBox / RBox query processing to request query processing, and the ABox query Processing the processing based on the schema metadata collected from the relational database and metadata on the TBox ontology received from the native inference machine; And
(c) transmitting the result data extracted from the relational database based on the processing result of the ABox query processing part and the processing result of the TBox / RBox query processing part by the native inference machine to the semantic web application. Query processing method in the semantic web, characterized in that. The method of claim 8,
The step (c)
(c1) extracting the result data from the relational database by converting a result of the ABox query processing part into an SQL format; And
(c2) converting the result data into a URI format and transmitting the result data to the semantic web application together with the result of the processing of the TBox / RBox query processing part. The method of claim 9,
In the step (b), the metadata for the elements of the relational database mapped to each element of the TBox / RBox query processing portion and the elements of the relational database mapped to each element of the ABox query processing portion. Query processing method on the semantic web, characterized in that for processing the ABox query processing portion using metadata. The method according to any one of claims 8 to 10,
In the step (b), the metadata received from the native inference machine is a query processing method on the semantic web, characterized in that the processing result of the TBox / RBox query processing portion by the native inference. The method according to any one of claims 8 to 10,
In step (b), if the query does not include the TBox / RBox query processing portion, generates a TBox / RBox query for collecting data necessary for processing the ABox query processing portion, and transmits it to the native inference unit. And processing the ABox query processing part by receiving the processing result of the native inference device for the TBox / RBox query. A computer-readable recording medium having recorded thereon a program for executing a query processing method in the semantic web according to any one of claims 8 to 10 on a computer.
KR20110130734A 2011-12-08 2011-12-08 Query Processing Apparatus and Method to use relational database as OWL ontology on semantic web KR101280058B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR20110130734A KR101280058B1 (en) 2011-12-08 2011-12-08 Query Processing Apparatus and Method to use relational database as OWL ontology on semantic web

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR20110130734A KR101280058B1 (en) 2011-12-08 2011-12-08 Query Processing Apparatus and Method to use relational database as OWL ontology on semantic web

Publications (2)

Publication Number Publication Date
KR20130064226A true KR20130064226A (en) 2013-06-18
KR101280058B1 KR101280058B1 (en) 2013-06-28

Family

ID=48861235

Family Applications (1)

Application Number Title Priority Date Filing Date
KR20110130734A KR101280058B1 (en) 2011-12-08 2011-12-08 Query Processing Apparatus and Method to use relational database as OWL ontology on semantic web

Country Status (1)

Country Link
KR (1) KR101280058B1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111126660A (en) * 2019-11-20 2020-05-08 湖北大学 Building energy efficiency evaluation method and system based on mixed semantic reasoning technology
CN112860940A (en) * 2021-02-05 2021-05-28 陕西师范大学 Music resource retrieval method based on sequential concept space on description logic knowledge base

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102323188B1 (en) * 2020-01-10 2021-11-08 제주대학교 산학협력단 Decoupled IoT Application Store System for Virtual Objects Sharing and Discovery

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090022790A (en) * 2007-08-31 2009-03-04 주식회사 온토테크 Ontology system based on meta modeling

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111126660A (en) * 2019-11-20 2020-05-08 湖北大学 Building energy efficiency evaluation method and system based on mixed semantic reasoning technology
CN111126660B (en) * 2019-11-20 2023-09-19 湖北大学 Building energy efficiency evaluation method and system based on hybrid semantic reasoning technology
CN112860940A (en) * 2021-02-05 2021-05-28 陕西师范大学 Music resource retrieval method based on sequential concept space on description logic knowledge base
CN112860940B (en) * 2021-02-05 2022-11-25 陕西师范大学 Music resource retrieval method based on sequential concept space on description logic knowledge base

Also Published As

Publication number Publication date
KR101280058B1 (en) 2013-06-28

Similar Documents

Publication Publication Date Title
US20160335544A1 (en) Method and Apparatus for Generating a Knowledge Data Model
CN102722542B (en) A kind of resource description framework graphic mode matching method
Abbes et al. MongoDB-based modular ontology building for big data integration
US10901973B1 (en) Methods and apparatus for a semantic multi-database data lake
Konys Ontology-based approaches to big data analytics
CN109063114B (en) Heterogeneous data integration method and device for energy cloud platform, terminal and storage medium
KR101280058B1 (en) Query Processing Apparatus and Method to use relational database as OWL ontology on semantic web
Mami et al. The query translation landscape: a survey
Natarajan et al. Schema-Based Mapping Approach for Data Transformation to Enrich Semantic Web
Hosseini et al. Automated mapping for semantic-based conversion of transportation data formats
Kalna et al. A scalable business intelligence decision-making system in the era of big data
Ren et al. MHDP: an efficient data lake platform for medical multi-source heterogeneous data
CN114297224A (en) RDF-based heterogeneous data integration and query system and method
Abdelhedi et al. Relational Databases Ingestion into a NoSQL Data Warehouse
Iglesias-Molina et al. An ontological approach for representing declarative mapping languages
KR101684579B1 (en) System and method for generating knowledge
US9047391B2 (en) Searching apparatus, searching method, and computer program product
KR20080049428A (en) Method and apparatus for providing similarity searching services by semantic web
Soussi et al. Exploiting nosql document oriented data using semantic web tools
Li et al. RDFAdaptor: efficient ETL plugins for RDF data process
Alghobiri et al. A comprehensive framework for the semantic cache systems
Knollmeyer et al. Ontology based knowledge graph for information and knowledge management in factory planning
Maran et al. A Software Architecture to Provide Persistence and Retrieve of Context Data Based on Ontological Models
Huseini et al. Transformation From Relational Database To Nosql Database: Migration and Integration
Devi et al. Pubworld-A R2RML mapping driven approach to transform relational database data into shareable format

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant
FPAY Annual fee payment

Payment date: 20170410

Year of fee payment: 5

FPAY Annual fee payment

Payment date: 20180409

Year of fee payment: 6