Description:BACKGROUND
Field of the invention
[001] Embodiments of the present invention generally relate to a system for development of ontology and particularly to a system and method for development of a domain-based ontology.
Description of Related Art
[002] An ontology is a collection of concepts and subjects in a certain area or domain that displays their features and relationships. The features and relationships can be internally or externally linked. A person who deals in a study and development of ontologies is known as an ontologist. Ontologists frequently try to figure out what the categories or highest types are, and how they fit together to build a system of categories that encompasses all things. Substances, properties, interactions, states of affairs, and events are some of the most commonly suggested categories.
[003] Fundamental ontological ideas such as particularity and universality, abstractness and concreteness, or possibility and necessity define these categories. However, within ontology, disagreements frequently arise about whether things belonging to a certain category exist and, if so, how they are connected.
[004] There is thus a need for a system and method for development of domain-based ontology that can resolve the arisen disagreements in an efficient manner.
SUMMARY
[005] Embodiments in accordance with the present invention provide a system for development of domain-based ontology. The system includes an ontology application installed within a computing device, and configured to enable a user to provide an input of an entity and associated properties of the entity to the system. The system further includes a processor located on an application server. The system further includes a storage medium configured to store programming instructions executable by the processor. The storage medium includes an input receiving module configured to receive the input of the entity and associated properties of the entity from the computing device. The storage medium further includes an analyzing module configured to analyze existing domains for enlisting at least one of, the domains associated with the received entity such that the domains are analyzed based on the properties of the entity. The storage medium further includes a comparison module configured to compare the properties of the received entity with properties of entities of the enlisted domains to determine an optimal placement of the entity in at least one of, the enlisted domains. The storage medium further includes an insertion module configured to place and insert the entity at the determined optimal placement in the enlisted domain. The storage medium further includes a storage module configured to store a final prepared ontology along with the placed entity as an ontology data structure in a database for visualization to the user.
[006] Embodiments in accordance with the present invention further provide a method for development of domain-based ontology. The method comprising steps of: receiving an input of an entity and associated properties of the entity from a computing device; analyzing existing domains for enlisting at least one of, domains associated with a received entity such that the domains are analyzed based on properties of the entity; comparing properties of the received entity with properties of entities of the enlisted domains to determine an optimal placement of the entity in at least one of, the enlisted domains; placing and inserting the entity at the determined optimal placement in the enlisted domain; and storing a final prepared ontology along with the placed entity as an ontology data structure in a database for visualization to a user.
[007] Embodiments of the present invention may provide a number of advantages depending on their particular configuration. First, embodiments of the present application may provide a system for development of domain-based ontology.
[008] Next, embodiments of the present application may provide a system for development of domain-based ontology that provides a novel architectural strategy for building ontology from a ground up.
[009] Next, embodiments of the present application may provide a system for development of domain-based ontology that provides a possible alternative to develop ontologies from conventional methods.
[0010] Next, embodiments of the present application may provide a system for development of domain-based ontology that improves precision and recall in recommendation systems.
[0011] Next, embodiments of the present application may provide a system for development of domain-based ontology that innovates and facilitates portable, rapid, and simple ontology development.
[0012] Next, embodiments of the present application may provide a system for development of domain-based ontology that is carried out using open-source software and applications.
[0013] Next, embodiments of the present application may provide a system for development of domain-based ontology that aids in an integration of unstructured data in the domain.
[0014] Next, embodiments of the present application may provide a system for development of domain-based ontology that has a user-friendly interface design, using which flaws and mistakes can easily be remedied.
[0015] These and other advantages will be apparent from the present application of the embodiments described herein.
[0016] The preceding is a simplified summary to provide an understanding of some embodiments of the present invention. This summary is neither an extensive nor exhaustive overview of the present invention and its various embodiments. The summary presents selected concepts of the embodiments of the present invention in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the present invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The above and still further features and advantages of embodiments of the present invention will become apparent upon consideration of the following detailed description of embodiments thereof, especially when taken in conjunction with the accompanying drawings, and wherein:
[0018] FIG. 1 illustrates a block diagram depicting a system for development of domain-based ontology, according to an embodiment of the present invention;
[0019] FIG. 2 illustrates a diagram depicting an architecture of the system, according to an embodiment of the present invention;
[0020] FIG. 3 illustrates a block diagram of various stages of conceptualization of the system, according to an embodiment of the present invention;
[0021] FIG. 4A depicts a final prepared ontology using the system, according to an embodiment of the present invention;
[0022] FIG. 4B depicts another final prepared ontology using the system, according to an embodiment of the present invention;
[0023] FIG. 4C depicts yet another final prepared ontology using the system, according to an embodiment of the present invention; and
[0024] FIG. 5 depicts a flowchart of a method for development of the domain-based ontology using the system, according to another embodiment of the present invention.
[0025] The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including but not limited to. To facilitate understanding, like reference numerals have been used, where possible, to designate like elements common to the figures. Optional portions of the figures may be illustrated using dashed or dotted lines, unless the context of usage indicates otherwise.
DETAILED DESCRIPTION
[0026] The following description includes the preferred best mode of one embodiment of the present invention. It will be clear from this description of the invention that the invention is not limited to these illustrated embodiments but that the invention also includes a variety of modifications and embodiments thereto. Therefore, the present description should be seen as illustrative and not limiting. While the invention is susceptible to various modifications and alternative constructions, it should be understood, that there is no intention to limit the invention to the specific form disclosed, but, on the contrary, the invention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention as defined in the claims.
[0027] In any embodiment described herein, the open-ended terms "comprising", "comprises”, and the like (which are synonymous with "including", "having” and "characterized by") may be replaced by the respective partially closed phrases "consisting essentially of", “consists essentially of", and the like or the respective closed phrases "consisting of", "consists of”, the like.
[0028] As used herein, the singular forms “a”, “an”, and “the” designate both the singular and the plural, unless expressly stated to designate the singular only.
[0029] FIG. 1 illustrates a block diagram depicting a system 100 for development of domain-based ontology (hereinafter referred to as the system 100), according to an embodiment of the present invention. In an embodiment of the present invention, the system 100 may prepare an ontology for a domain. The ontology may be a well-mannered and structured classification of entities lying in a specific domain, in an embodiment of the present invention. According to embodiments of the present invention, the domain may be, but not limited to, a biology domain, a zoology domain, an engineering domain, a pharmaceutical domain, a physiological domain, and so forth. Embodiments of the present invention are intended to include or otherwise cover any domain for preparation of the ontology, including known, related art, and/or later developed technologies.
[0030] According to an embodiment of the present invention, the system 100 may comprise a computing device 102, an ontology application 104, a database 106, an application server 108, a processor 110, and a storage medium 112.
[0031] In an embodiment of the present invention, the computing device 102 may be a device used by a user to provide an input of an entity. The computing device 102 may further be used by the user to provide associated properties of the entity to the system 100, in an embodiment of the present invention. In an embodiment of the present invention, the entity may be a terminology relating to the domain for which the ontology may be prepared. According to embodiments of the present invention, the user may be, but not limited to, a biologist, a zoologist, an engineer, a doctor, a physiologist, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the user.
[0032] In an exemplary embodiment of the present invention, if the domain of the ontology is related to ‘automobiles’ then terms such as ‘four-wheeler vehicle’, ‘airplanes’, and so forth may be the entities in the prepared ontology. In another exemplary embodiment of the present invention, if the domain of the ontology is related to ‘biology’ then terms such as ‘fish’, ‘bear’, and so forth may be the entities in the prepared ontology. In yet another exemplary embodiment of the present invention, if the domain of the ontology is related to ‘chemistry’ then terms such as ‘acids’, ‘bases’, and so forth may be the entities in the prepared ontology.
[0033] The computing device 102 may be, but not limited to, a personal computer, a consumer device, and alike. Embodiments of the present invention are intended to include or otherwise cover any type of the computing device 102 including known, related art, and/or later developed technologies. In an embodiment of the present invention, the personal computer may be, but not limited to, a desktop, a server, a laptop, and alike. Embodiments of the present invention are intended to include or otherwise cover any type of the personal computer including known, related art, and/or later developed technologies.
[0034] Further, in an embodiment of the present invention, the consumer device may be, but not limited to, a tablet, a mobile phone, a notebook, a netbook, a smartphone, a wearable device, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the consumer device including known, related art, and/or later developed technologies. Embodiments of the present invention are intended to include or otherwise cover any type of the computing device 102 including known, related art, and/or later developed technologies.
[0035] According to an embodiment of the present invention, the computing device 102 may comprise software applications such as, but not limited to, a dictionary application, an encyclopedia application, a web browsing application, and the like. In a preferred embodiment of the present invention, the computing device 102 may comprise the ontology application 104 that may be a computer-readable program installed in the computing device 102 for executing functions associated with the system 100.
[0036] In an embodiment of the present invention, the database 106 may store the final prepared ontology. In an embodiment of the present invention, the ontology prepared by the system 100 may be stored in the database 106 in a form of a data structure. According to embodiments of the present invention, the data structure may be, but not limited to, a tree data structure, a graph data structure, a linked list data structure, an array data structure, a double array data structure, a circular linked list data structure, and so forth. Embodiments of the present invention are intended to include or otherwise cover any data structure for the preparation of the ontology, including known, related art, and/or later developed technologies. In an embodiment of the present invention, the prepared ontology stored in the database 106 may be able to read, written, and deleted by the user.
[0037] According to embodiments of the present invention, the database 106 may be for example, but not limited to, a distributed database, a personal database, an end-user database, a commercial database, a Structured Query Language (SQL) database, a non-SQL database, an operational database, a relational database, an object-oriented database, a graph database, a cloud server database, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the database 106 including known, related art, and/or later developed technologies.
[0038] Further, the database 106 may be stored in a cloud server, in an embodiment of the present invention. In an embodiment of the present invention, the cloud server may be remotely located. In an exemplary embodiment of the present invention, the cloud server may be a public cloud server. In another exemplary embodiment of the present invention, the cloud server may be a private cloud server. In yet another embodiment of the present invention, the cloud server may be hybrid-allocated and dedicated. According to embodiments of the present invention, the cloud server may be, but not limited to, a Microsoft Azure cloud server, an Amazon AWS cloud server, a Google Compute Engine (GEC) cloud server, an Amazon Elastic Compute Cloud (EC2) cloud server, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the cloud server including known, related art, and/or later developed technologies.
[0039] In an embodiment of the present invention, the application server 108 may be a hardware on which the processor 110 may be installed. According to embodiments of the present invention, the application server 108 may be, but not limited to, a motherboard, a wired board, a mainframe, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the application server 108, including known, related art, and/or later developed technologies.
[0040] In an embodiment of the present invention, the processor 110 may be located on the application server 108. The processor 110 may be configured to execute computer-executable instructions to generate an output relating to the system 100. According to embodiments of the present invention, the processor 110 may be, but not limited to, a Programmable Logic Control (PLC) unit, a microprocessor, a development board, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the processor 110 including known, related art, and/or later developed technologies.
[0041] In an embodiment of the present invention, the storage medium 112 may store computer programmable instructions in form of programming modules. The storage medium 112 may be a non-transitory storage medium, in an embodiment of the present invention. In an embodiment of the present invention, the storage medium 112 may communicate with the processor 110 and execute a computer-readable set of instructions present in the storage medium 112.
[0042] According to embodiments of the present invention, the storage medium 112 may be, but not limited to, a Random-Access Memory (RAM), a Static Random-access Memory (SRAM), a Dynamic Random-access Memory (DRAM), a Read-Only Memory (ROM), an Erasable Programmable Read-only Memory (EPROM), an Electrically Erasable Programmable Read-only Memory (EEPROM), a NAND Flash, a Secure Digital (SD) memory, a cache memory, a Hard Disk Drive (HDD), a Solid-State Drive (SSD) and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the storage medium 112, including known, related art, and/or later developed technologies. In an embodiment of the present invention, the storage medium 112 further comprises an input receiving module 114, an analyzing module 116, a comparison module 118, an insertion module 120, a storage module 122, and a formalization module 124.
[0043] In an embodiment of the present invention, the input receiving module 114 may be configured to receive the input of the entity from the computing device 102. The input receiving module 114 may further be configured to receive properties associated with the entity provided by the user using the computing device 102, in an embodiment of the present invention.
[0044] In an embodiment of the present invention, the analyzing module 116 may be configured to analyze existing domains for enlisting at least one of, the domains associated with the received entity. The associated domains may be analyzed based on the properties of the entity, in an embodiment of the present invention.
[0045] In an embodiment of the present invention, the comparison module 118 may be configured to compare the properties of the received entity with the properties of entities of the enlisted domains to determine an optimal placement of the entity in at least one of, the enlisted domains.
[0046] In an embodiment of the present invention, the insertion module 120 may be configured to place and insert the entity at the determined optimal placement in the enlisted domain. The insertion module 120 may further be configured to create a new ontology data structure for the entity when the comparison module 118 fails to find any optimal placement of the entity, in an embodiment of the present invention.
[0047] In an embodiment of the present invention, the storage module 122 may be configured to store a final prepared ontology along with the placed entity as the ontology data structure in the database 106. The ontology data structure may further be visualized to the user on the computing device 102, in an embodiment of the present invention.
[0048] In an embodiment of the present invention, the ontology data structure stored in the database 106 using the storage module 122 is created using a computing model. In a preferred embodiment of the present invention, the computing model may be a free-flow zig-zag model. Embodiments of the present invention are intended to include or otherwise cover any computing model for the creation of the ontology data structure, including known, related art, and/or later developed technologies.
[0049] According to embodiments of the present invention, the ontology data structure may be saved in a pre-defined format such as, but not limited to, a Portable Document Format (.pdf), a Microsoft Word Document (.docx), a Microsoft Excel Format (.xlsx), a Virtual Contact File Format (.vcf), and so forth. In a preferred embodiment of the present invention, the ontology data structure may be saved in a format of a Comma Separated Values format (.csv) file. Embodiments of the present invention are intended to include or otherwise cover any file format for saving the ontology data structure, including known, related art, and/or later developed technologies.
[0050] In an embodiment of the present invention, the stored ontology data structure may be extracted and populated on the computing device 102 using an environment framework application. In a preferred embodiment of the present invention, the environment framework application may be a Java framework application (J2EE). Embodiments of the present invention are intended to include or otherwise cover any environment framework application, including known, related art, and/or later developed technologies.
[0051] In an embodiment of the present invention, a search-related testing may be performed on the extracted and populated data structure to enable the user to search a pre-placed entity. According to embodiments of the present invention, the search-related testing may be performed using applications such as, but not limited to, a Sequential Protocol, a Resource Description Framework Query Language (SPARQL), Description Language Query (DLQ), and so forth. Embodiments of the present invention are intended to include or otherwise cover any search-related testing applications for the ontology data structure, including known, related art, and/or later developed technologies.
[0052] In an embodiment of the present invention, the visualization of the ontology data structure on the computing device 102 may be performed using a visualizing application. In a preferred embodiment of the present invention, the visualizing application may be an OntoGraf application and an OWL Viz application. Embodiments of the present invention are intended to include or otherwise cover any visualizing application, including known, related art, and/or later developed technologies.
[0053] In an embodiment of the present invention, the formalization module 124 may be configured to axiomatize the properties of the received entity. The formalization module 124 may further be configured to promote the received entity to a comparing entity for the next iteration of receiving of the entities, in an embodiment of the present invention. In an embodiment of the present invention, the comparing entity may be used by the comparison module 118 to compare the next receiving entity.
[0054] In an embodiment of the present invention, the system 100 may use an inference engine for checking inconsistencies in the ontology data structure. In a preferred embodiment of the present invention, the inference engine may be a FACT++ inference engine. Embodiments of the present invention are intended to include or otherwise cover any inference engine for checking the inconsistencies in the ontology data structure, including known, related art, and/or later developed technologies. According to embodiments of the present invention, the inconsistencies checked by the inference engine may be a misplacement of the received entity, redundancy of the received entity, un-hierarchal arrangement of the received entity, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the inconsistencies that may be checked by the inference engine, including known, related art, and/or later developed technologies. In an embodiment of the present invention, a reasoner may further be configured for identifying logical contradictions in the domains and a relationship between the entities of the domain in the ontology data structure.
[0055] FIG. 2 illustrates a diagram depicting an architecture 200 of the system 100, according to an embodiment of the present invention. In an embodiment of the present invention, a specification stage 202 may be targeted towards receiving the input from the user. The input may be received using the input receiving module 114 and the received input may be analyzed using the analyzing module 116, in an embodiment of the present invention.
[0056] In an embodiment of the present invention, a conceptualization stage 204 may be targeted towards conceptual modeling of the system 100. The conceptualization stage 204 may perform conceptual modeling using the comparison module 118, in an embodiment of the present invention.
[0057] In an embodiment of the present invention, a formalization stage 206 may be targeted towards a construction of a semi-computable model of the ontology data structure. The formalization stage 206 may perform semi-computation using the formalization module 124, in an embodiment of the present invention.
[0058] In an embodiment of the present invention, an implementation stage 208 may be targeted towards a construction of a computable model of the ontology data structure. The implementation stage 208 may perform computation using the insertion module 120, in an embodiment of the present invention.
[0059] In an embodiment of the present invention, a maintenance stage 210 may be targeted towards maintenance and keeping an operatable stage of the ontology data structure. The maintenance stage 210 may perform maintenance using the storage module 122, in an embodiment of the present invention.
[0060] FIG. 3 illustrates a block diagram of various stages of conceptualization 300 of the system 100, according to an embodiment of the present invention. In an embodiment of the present invention, a first level of conceptualization 302 of the system 100 may include concept trees and relationships. A second level of conceptualization 304 of the system 100 may include a data dictionary, class attributes, instance attributes, constraints, and instances, in an embodiment of the present invention. In an embodiment of the present invention, the second level of conceptualization 304 of the system 100 may further include relationships, dictionaries, and conditional tables. A third level of conceptualization 306 of the system 100 may include a table of formulas and rules, in an embodiment of the present invention.
[0061] FIG. 4A depicts a first prepared ontology 400 using the system 100, according to an embodiment of the present invention. In an embodiment of the present invention, the first prepared ontology 400 may be stored in the database 106 in form of a radially populated ontology data structure.
[0062] FIG. 4B depicts a second prepared ontology 402 using the system 100, according to an embodiment of the present invention. In an embodiment of the present invention, the second prepared ontology 402 may be stored in the database 106 in form of a tree-based ontology data structure.
[0063] FIG. 4C depicts a third prepared ontology 404 using the system 100, according to an embodiment of the present invention. In an embodiment of the present invention, the third prepared ontology 404 may be stored in the database 106 in form of a graph-based ontology data structure.
[0064] FIG. 5 depicts a flowchart of a method 500 for development of the domain-based ontology using the system 100, according to an embodiment of the present invention.
[0065] At step 502, the system 100 may receive the input of the entity and associated properties of the entity from the computing device 102.
[0066] At step 504, the system 100 may analyze the existing domains for enlisting at least one of, the domains associated with the received entity such that the domains are analyzed based on the properties of the entity.
[0067] At step 506, the system 100 may compare the properties of the received entity with the properties of entities of the enlisted domains to determine the optimal placement of the entity in at least one of, the enlisted domains.
[0068] At step 508, the system 100 may place and insert the entity at the determined optimal placement in the enlisted domain.
[0069] At step 510, the system 100 may store the final prepared ontology along with the placed entity as the ontology data structure in the database 106 for visualization to the user.
[0070] Embodiments of the invention are described above with reference to block diagrams and schematic illustrations of methods and systems according to embodiments of the invention. It will be understood that each block of the diagrams and combinations of blocks in the diagrams can be implemented by computer program instructions. These computer program instructions may be loaded onto one or more general-purpose computers, special purpose computers, or other programmable data processing apparatus to produce machines, such that the instructions which execute on the computers or other programmable data processing apparatus create means for implementing the functions specified in the block or blocks. Such computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the block or blocks.
[0071] While the invention has been described in connection with what is presently considered to be the most practical and various embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
[0072] This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined in the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements within substantial differences from the literal languages of the claims.
, Claims:I/We Claim:
1. A system (100) for development of domain-based ontology, the system (100) comprising:
an ontology application (104) installed within a computing device (102), and configured to enable a user to provide an input of an entity and associated properties of the entity to the system (100);
a processor (110) located on an application server (108); and
a storage medium (112) configured to store programming instructions executable by the processor (110), wherein the storage medium (112) comprises:
an input receiving module (114) configured to receive the input of the entity and associated properties of the entity from the computing device (102);
an analyzing module (116) configured to analyze existing domains for enlisting at least one of, the domains associated with the received entity such that the domains are analyzed based on the properties of the entity;
a comparison module (118) configured to compare the properties of the received entity with properties of entities of the enlisted domains to determine an optimal placement of the entity in at least one of, the enlisted domains;
an insertion module (120) configured to place and insert the entity at the determined optimal placement in the enlisted domain; and
a storage module (122) configured to store a final prepared ontology along with the placed entity as an ontology data structure in a database (106) for visualization to the user.
2. The system (100) as claimed in claim 1, wherein the insertion module (120) is further configured to create a new ontology data structure for the entity when the comparison module (118) fails to find any optimal placement of the entity.
3. The system (100) as claimed in claim 1, wherein the ontology data structure is created using a free-flow zig-zag model.
4. The system (100) as claimed in claim 1, wherein the visualization of the ontology data structure on the computing device (102) is done by using an OntoGraf application and an OWL Viz application.
5. The system (100) as claimed in claim 1, wherein the system (100) uses FACT++ as an inference engine for checking inconsistencies in the ontology data structure.
6. The system (100) as claimed in claim 5, wherein the inconsistencies are selected from a misplacement of the received entity, redundancy of the received entity, un-hierarchal arrangement of the received entity, or a combination thereof.
7. A method (500) for development of domain-based ontology, the method (500) comprising steps of:
receiving an input of an entity and associated properties of the entity from a computing device (102);
analyzing existing domains for enlisting at least one of, domains associated with a received entity such that the domains are analyzed based on properties of the entity;
comparing properties of the received entity with properties of entities of the enlisted domains to determine an optimal placement of the entity in at least one of, the enlisted domains;
placing and inserting the entity at the determined optimal placement in the enlisted domain; and
storing a final prepared ontology along with the placed entity as an ontology data structure in a database (106) for a visualization to a user.
8. The method (500) as claimed in claim 7, wherein the ontology data structure is created using a free-flow zig-zag model.
9. The method (500) as claimed in claim 7, wherein the visualization of the ontology data structure on the computing device (102) is done by using an OntoGraf application and an OWL Viz application.
10. The method (500) as claimed in claim 7, wherein the system (100) uses FACT++ as an inference engine for checking inconsistencies in the ontology data structure.
Date: 19th May 2022
Place: Noida

Nainsi Rastogi
Patent Agent (IN/PA-2372)
Agent for the Applicant