KR20140104544A - System and method for building of semantic data - Google Patents

Abstract

Disclosed are a system and a method for constructing semantic data. The system for constructing the semantic data according to an embodiment of the present invention includes a first database which constructs first data from a first schema; a semantic data generating unit which generates the semantic data constructed with a second schema which is different from the first schema by collecting the first data from the first database in response to a request of a user; a semantic data storage unit which stores the semantic data; and a semantic data request processing unit which processes the request of a user, transmits the processed result to the semantic data generating unit or the semantic data storage unit, and supplies the processed result of the request of the user to the user.

Description

System and method for constructing semantic data [0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system and a method for constructing semantic data, and more particularly, to a system and a method for constructing semantic data capable of efficiently providing semantic data corresponding to information requested by a user.

With the development of computing technology and the Internet, a wide range of data is being constructed and provided in various fields. However, in order to efficiently link or utilize the provided data, there is a limit to the data to be provided in order to understand the format and meaning of the provided data.

The present disclosure provides a system and method for constructing semantic data that can efficiently provide semantic data corresponding to information requested by a user.

A semantic data construction system according to an embodiment includes a first database for constructing first data with a first schema; A semantic data generation unit for collecting the first data from the first database and generating semantic data constructed with a second schema different from the first schema, in response to a user's request; A semantic data storage unit for storing the semantic data; And a semantic data request processing unit for processing the request of the user and transmitting the processed result to the semantic data generating unit or the semantic data storing unit and providing the processing result of the user's request to the user, A data collecting unit for collecting the first data corresponding to the request from the first database; A schema processor for analyzing the first schema and selecting an attribute corresponding to the request of the user among attributes of the first schema to form the second schema into the second schema; And a semantic data determination unit for forming the semantic data using the first data collected from the data collection unit and the second schema formed from the schema processing unit.

The data collecting unit may collect only a part of the first data corresponding to the request of the user.

The semantic data may be RDF (Resource Description Framework) data, and the second schema may be a schema that defines RDF data.

The semantic data generating unit may further include a repertoire storing unit storing information on the first schema and the second schema processed by the schema processing unit.

Wherein the semantic data request processing unit analyzes the request of the user and if the request of the user is a request for semantic data related to the generated semantic data, And generate semantic data corresponding to the request of the user by referring to the information about the second schema.

Wherein the semantic data request processing unit includes a data comparing unit for comparing the semantic data corresponding to the request of the user with the semantic data previously stored in the semantic data storing unit and the semantic data comparing unit includes semantic data corresponding to the request of the user The semantic data storage unit transmits the semantic data corresponding to the request of the user to the semantic data storage unit in response to the user's request to the semantic data storage unit .

Wherein the semantic data request processing unit includes a request type determination unit for determining whether the request of the user is related to generation of new semantic data or update of previously generated semantic data, According to the result, the semantic data can be generated or the previously generated semantic data can be updated.

The semantic data request processing unit may include an authority checking unit for determining whether the request of the user is permitted.

Wherein the semantic data construction system further comprises a second database for constructing second data with a schema identical to or different from the first schema, Any attribute and any attribute included in the schema for the second data may be reflected in the formation of the second schema.

Wherein the semantic data generation unit collects second data from an external network in response to the request of the user and stores an arbitrary attribute included in the first schema and an arbitrary attribute included in the schema for the second data, 2 can be reflected in the formation of the schema.

According to the system and method for constructing semantic data according to the present disclosure, there is an advantage that data can be efficiently linked or utilized in different meanings. In addition, according to the system and method for constructing semantic data according to the present disclosure, it is possible to provide semantic data optimized for a user's request.

1 is a block diagram illustrating a healthcare system in accordance with one embodiment of the present disclosure.
2 is a diagram showing an example of the first data and the second data of FIG.
3 is a block diagram illustrating a healthcare system in accordance with another embodiment of the present disclosure.
Fig. 4 is a block diagram showing the semantic data request processing unit of Fig. 1 or Fig. 3 in more detail.
FIG. 5 is a diagram showing an example in which a user associates or utilizes the semantic data of FIG. 1 or FIG. 3;
Figures 6 and 7 are block diagrams, respectively, illustrating a healthcare system in accordance with another embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The embodiments of the disclosure are provided to more fully describe the present disclosure to those skilled in the art. The present disclosure is capable of various modifications and may take various forms, and specific embodiments are illustrated and described in the drawings. It is to be understood, however, that the intention is not to limit the present disclosure to the particular forms disclosed, but to include all modifications, equivalents, and alternatives falling within the spirit and scope of the appended claims. Like reference numerals are used for similar elements in describing each drawing. In the accompanying drawings, the dimensions of the structures are shown enlarged or reduced from the actual size for the sake of clarity of the present disclosure.

The terminology used in this disclosure is used only to describe a specific embodiment and is not intended to limit the disclosure. The singular expressions include plural expressions unless the context clearly dictates otherwise. In this disclosure, the terms "comprises" or "having" and the like are used to specify that a feature, a number, a step, an operation, an element, a part, or a combination thereof, But do not preclude the presence or addition of one or more other features, integers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are not to be construed as an ideal or overly formal sense as clearly defined in this disclosure .

1 is a block diagram conceptually showing a semantic data construction system according to an embodiment. 1, the semantic data construction system SBSYS includes a first database DB1, a semantic data generation unit SDGU, a semantic data storage unit SST, and a semantic data request processing unit RPU. .

The first data base DB1 generates and stores the first data DTA1 in the first form. For example, the first data DTA1 may represent information about an arbitrary mantissa. For example, the first data DTA1 may include information about a song called by a certain artist and a composer of the song. In this example, as shown in FIG. 2A, the first database DB1 can construct information on the mantissa A as table 1 with the first data DTA1. In Table 1, Each index corresponds to each piece of music called A by the artist A, and the attributes included in each index may include information about a song name and a composer of the corresponding song.

As shown in FIG. 2B, the first data DTA1 can further include information on a composer of each song of an arbitrary number in Table 2, wherein Table 1 and Table 2 are table 3 The relationship can be formed by For example, an arbitrary index of Table 3 may include information on the relationship between the second attribute of Table 1 and each index of Table 2. [

In the case of forming the first data DTA1 with the structure as shown in FIG. 2A or FIG. 2B, restrictions may be imposed on the user to associate or utilize the first data DTA1. For example, the user may request data of a different form or meaning from the schema defining the first database DB1. In the example described above, each attribute of each index of the table 1 is fixed in the first database DB1. The user uses the semantic data SDTA that associates other attributes with some attributes included in the first data DTA1 To this end, efforts and costs such as directly reconstructing the first data DTA1 and extracting the corresponding attributes may be caused. For reference, the first database DB1 may adopt one or more schemas defining a database.

In this way, heterogeneity of data can lead to waste of resources such as diversification of computer system and diversification of related services on the web, which makes it difficult to make meaningful use of existing data. Therefore, there is a need for a way to efficiently link and utilize data that have been individually constructed for correct decision-making and convergence service development. The approach presented in this disclosure will be described.

1, the semantic data generation unit SDGU according to the present invention collects first data DTA1 from a first database DB1 in response to a user request Req, (SDTA) corresponding to Req. To this end, the semantic data generation unit SDUU may include a data collection unit (DCU), a schema processing unit (SPU), and a semantic data determination unit (SDU).

The data collection unit DCU may collect the first data DTA1 from the first database DB1 in response to the user's request Req. For example, the data collection unit (DCU) may collect all or part of the first data (DTA1). 2 (b), the data collection unit DCU collects the first data DTA1 including only the information corresponding to the table 1 in response to the user's request Req, The first data DTA1 including information corresponding to the first data DTA1 can be collected. The user's request (Req) may be a request for semantic data (SDTA) required by the user. Alternatively, the data collecting unit (DCU) may collect the first data (DTA1) in a specific table, a specific index unit, or a specific attribute unit of FIG. 2 (a) or (b) It is possible.

However, the data acquisition unit (DCU) can perform the above operation only when the semantic data SDTA corresponding to the user's request (Req) is not present in the semantic data storage unit (SST). The same applies to the schema processing unit (SPU) and the semantic data determination unit (SDU) described later. The operation of determining whether the semantic data SDTA corresponding to the user's request Req exists in the semantic data storage unit SST will be described later.

1, the schema processing unit SPU automatically analyzes the schema for the first data DTA1 from the collected first data DTA1 and stores the semantic data corresponding to the user's request Req SDTA) can be selected. Hereinafter, the schema for the first data DTA1 is referred to as a first schema (SCH1), and the schema for the semantic data (SDTA) is referred to as a second schema (SCH2). In order to perform the above operation, the schema processing unit SPU may include a schema analysis unit SHA and a schema selection unit SHS.

The schema analysis unit (SHA) can analyze the first schema (SCH1). For example, when the first data DTA1 includes information on the first schema SCH1, the schema analysis unit SHA analyzes the schema from the first data DTA1 transmitted from the data collection unit DCU can do. Alternatively, the schema analysis unit (SHA) may analyze the first schema (SCH1) based on the information on the previously stored first schema (SCH1). The information on the first schema (SCH1) may be provided to the schema analysis unit (SHA) as a separate document from the first data (DTA1).

The schema analysis unit (SHA) may analyze the first schema (SCH1) and transmit the result to the schema selection unit (SHS). For example, the analysis result of the first schema (SCH1) shows that the first data (DTA1) is formed by each table for each mantissa, and each index of the corresponding table includes information about the song of the corresponding mantissa, And a title and a composer for the song as attributes.

The schema selection unit SHS can receive the analysis result of the first schema SCH1 and select the second schema SCH2 corresponding to the request Req of the user. For example, if the request of the user (Req) is for a composer of each song of a certain mantissa, the schema selector SHS selects a second schema (SCH2) containing the attribute from the analysis result of the first schema ) Can be formed. For example, when the semantic data (SDTA) is formed from RDF (Resource Description Framework) data, the second schema (SCH2) includes a <Subject, a Predicate, Object)> type, and can be determined as an arbitrary attribute of at least one of a subject, a predicate, and an object selected from an analysis result of the first schema (SCH1). RDF data is data defined to exchange resources on the World Wide Web Consortium (W3C) standard that defines the Semantic Web.

Information on the schema analyzed and determined by the schema processing unit (SPU) may be included in the repertoire storage unit (RST) shown in FIG. If the request (Req) of the user is related to the requested semantic data (SDTA), the schema processing unit (SPU) refers to the schema stored in the repertoire storage unit (RST) (SCH2) can be formed. For example, when the newly requested user's request (Req) corresponds to a subclass for an attribute of the first schema (SCH1) selected by any of the attributes forming the predetermined second schema (SCH2) The schema processing unit (SPU) can refer to the schema of the repertoire storage unit (RST). For example, if the arbitrary attribute of the predetermined second schema (SCH2) is for the automobile and the newly requested user's request (Req) is for the grandrer, the schema processing unit (SPU) The attribute for the lower class may be selected from the attribute of the first selected schema (SCH1) by referring to the information, and the hierarchy may be formed so as to be reflected in the second schema (SCH2). The determination operation as to whether the user's request (Req) is related to the requested semantic data is described below.

1, the semantic data determination unit SDU uses the information of the first data DTA1 corresponding to the attributes included in the selected second schema SCH2 and the second schema SCH2 to generate semantic data SDTA). &Lt; / RTI &gt; The generated semantic data SDTA can be stored in the semantic data storage unit SST.

4 is a diagram showing an example of the semantic data request processing unit of Fig.

Referring to FIG. 1 and FIG. 4, the semantic data request processing unit RPU receives a request (Req) from a user and provides the corresponding semantic data SDTA to the user. The semantic data request processing unit (RPU) may include a request analysis unit (RAU) and semantic data calling and providing unit (CPU).

The Request Analysis Unit (RAU) can receive and analyze the user's request (Req). For example, the request analysis unit RAU includes a semantic data comparison unit CMU to check whether the semantic data SDTA corresponding to the request Req of the user is stored in the semantic data storage unit SST can do. For example, the request analysis unit (RAU) may store information on the semantic data (SDTA) stored in the semantic data storage unit (SST). The result of the determination as to whether or not the semantic data SDTA corresponding to the user's request Req is stored in the semantic data storage unit SST is transmitted to the semantic data calling and providing unit CPU.

When the semantic data SDTA requested by the user is stored in the semantic data storage SST, the semantic data calling and providing CPU calls the semantic data SDTA directly to the semantic data storage SST. On the other hand, if the semantic data SDTA is not stored in the semantic data storage unit SST, the semantic data calling and providing unit CPU generates semantic data SDTA in the semantic data generating unit SDGU described above (Req) to the semantic data generation unit (SDGU). The semantic data SDTA generated by the semantic data generation unit SDGU may be stored in the semantic data storage SST and transmitted to the semantic data calling and providing unit CPU as described above.

The request analysis unit RAU includes the request type determination unit TAU to determine whether the request Req of the user requests the provision of the semantic data SDTA or the semantic data SDTA stored in the semantic data storage unit SST, (Addition, deletion, or modification) of the SDTA. This can be determined by analyzing the query term contained in the user's request (Req).

If the request (Req) of the user is a request for the semantic data (SDTA), the semantic data calling and delivering (CPU) is the semantic data (SDTA) previously stored in the semantic data storage (SST) The semantic data generated by the data generation unit SDGU and stored in the semantic data storage unit SST can be provided to the user. Or the request (Req) of the user is a request to the updater of the semantic data (SDTA) stored in the semantic data storage (SST), the semantic data calling and providing unit (CPU) (SDTA) stored in the storage unit (SST).

The updating of the semantic data SDTA can be performed by referring to the information on the second schema (SCH2) stored in the repertoire storage unit RST of the SDU in FIG. 3. Alternatively, although not shown, the update of semantic data (SDTA) may be performed by separate update logic.

The request analysis unit (RAU) may further include an authorization checking unit (AIU) for determining whether the request (Req) of the user is allowed.

The semantic data (SDTA) sent to the semantic data calling and providing unit (CPU) can be provided to the user. Also, although not shown, the processing result of the request (Req) of the user (for example, an update result of the semantic data) may be provided to the user.

As shown in FIG. 5, the user who acquires the semantic data SDTA may include or modify the semantic data SDTA to store or use the semantic data SDTA as user semantic data, or may use the semantic data SDTA as an application such as a smartphone application have.

In the above description, the semantic data construction system collects the first data from one database to generate semantic data. However, it is not limited thereto. 6, the system for constructing a semantic data according to the present disclosure includes first data DTA1 and second data DTA2 from a first database DB1 and a second database DB2, respectively, (SDTA) from at least one or more data.

For example, any attribute contained in the schema for the first data (DTA1) and any attribute included in the schema for the second data (DTA2) may be included in the schema (SCH2) for the semantic data (SDTA) And can be formed with arbitrary attributes. For example, if any attribute included in the schema for the first data DTA1 is for the fruit and any attribute included in the schema for the second data DTA2 is for the color, then the semantic data SDTA ) Can be formed of RDF data in which the banana and yellow are formed as subjects and objects, respectively, and the color of the banana is colored yellow as the predicate.

The first database DB1 and the second database DB2 in FIG. 6 may be defined by the same or different schemas, respectively. The second database DB2 in FIG. 6 may exist outside the semantic data construction system SBSYS of the present disclosure.

Further, as shown in Fig. 7, the collected data is not limited to that provided from the database, but may also be provided by the network NT. The network NT of FIG. 7 may include the Internet and social media.

As described above, according to the system and method for constructing semantic data according to the present disclosure, heterogeneous data having various forms and meanings can be effectively linked or utilized. In particular, databases built by different organizations can be utilized in an integrated manner, enabling efficient data utilization, which can reduce costs for each organization and improve the profitability of the company. In addition, according to the system and method for constructing the semantic data, the semantic data optimized for the user's request can be provided.

As described above, an optimal embodiment has been disclosed in the drawings and specification. It is to be understood that the terminology used herein is for the purpose of describing the present disclosure only and is not used to limit the scope of the present invention.

For example, the semantic data of the present disclosure is not limited to RDF data described above, but may be data described in languages other than RDF, such as a semantic markup language (such as OWL and Topic Maps). Or the above-described user may be the designer of the semantic data building system according to the present disclosure. Therefore, those skilled in the art will appreciate that various modifications and equivalent embodiments are possible without departing from the scope of the present invention. The scope of the present invention should be determined by the technical idea of the appended claims.

Semantic data building system: SBSYS
First database: DB1
Semantic data generator: SDGU
Meaning Data storage area: SST
Semantic data request processing unit: RPU

Claims (10)

A first database for constructing first data with a first schema;
A semantic data generation unit for collecting the first data from the first database and generating semantic data constructed with a second schema different from the first schema, in response to a user's request;
A semantic data storage unit for storing the semantic data; And
And a semantic data request processing unit for processing the request of the user and transmitting the semantic data to the semantic data generating unit or the semantic data storing unit and providing the processing result of the user's request to the user,
Wherein the semantic data generating unit comprises:
A data collecting unit collecting the first data corresponding to the request of the user from the first database;
A schema processor for analyzing the first schema and selecting an attribute corresponding to the request of the user among attributes of the first schema to form the second schema into the second schema; And
And a semantic data determination unit for forming the semantic data using the first data collected from the data collection unit and the second schema formed from the schema processing unit. The method according to claim 1,
Wherein the data collection unit collects only a part of the first data corresponding to the request of the user. The method according to claim 1,
The semantic data is RDF (Resource Description Framework) data,
Wherein the second schema is a schema that defines RDF data. The method according to claim 1,
Wherein the semantic data generating unit further comprises a repertoire storing unit storing information on the first schema and the second schema processed by the schema processing unit. 5. The method of claim 4,
Wherein the semantic data request processing unit analyzes the request of the user and if the request of the user is a request for semantic data related to the generated semantic data, And generates semantic data corresponding to the request of the user by referring to the information about the second schema. The method according to claim 1,
Wherein the semantic data request processing unit includes a data comparing unit for comparing the semantic data corresponding to the user's request with the semantic data previously stored in the semantic data storing unit,
Wherein the semantic data comparison unit transmits the request of the user to the semantic data storage unit when the semantic data corresponding to the user's request is identical to the previously stored semantic data,
Wherein the semantic data storage unit transmits the semantic data corresponding to the request of the user to the semantic data request processing unit in response to the request of the user. The method according to claim 1,
Wherein the semantic data request processing unit includes a request type determination unit for determining whether the request of the user is related to generation of new semantic data or update of previously generated semantic data,
Wherein the semantic data generation unit generates the semantic data or updates the generated semantic data according to the determination result of the request type determination unit. The method according to claim 1,
Wherein the semantic data request processing unit includes an authorization checking unit for determining whether the request of the user is permitted or not. The method according to claim 1,
Wherein the semantic data construction system further comprises a second database for constructing second data with a schema identical to or different from the first schema,
Wherein the semantic data generation unit reflects any attribute included in the first schema and any attribute included in the schema for the second data in the formation of the second schema in response to the request of the user Semantic data building system. The method according to claim 1,
Wherein the semantic data generation unit collects second data from an external network in response to the request of the user and stores an arbitrary attribute included in the first schema and an arbitrary attribute included in the schema for the second data, 2 schema. &Lt; / RTI &gt;

Images