Method and apparatus for providing safeguarding against malicious ontologies

Abstract

A method for providing a mechanism for safeguarding against malicious ontologies may include causing examination of a received file associated with an ontology to determine a namespace marking for subjects, predicates and objects of each triple of the file that are to be stored in a database, utilizing relationship data corresponding to the namespace marking to identify triples whose subjects or objects do not correspond to the ontology, and determining whether the relationship data enables the triples whose subjects or objects do not correspond to the ontology to be considered as a valid data set for storage in the database. A corresponding apparatus and computer program product are also provided.

1 . A method comprising:
 causing examination of a received file associated with an ontology to determine a namespace marking for subjects, predicates and objects of triples of the file that are to be stored in a database;   utilizing relationship data corresponding to the namespace marking to identify triples whose subjects or objects do not correspond to the ontology; and   determining whether the relationship data enables the triples whose subjects or objects do not correspond to the ontology to be considered as a valid data set for storage in the database.   
     
     
         2 . The method of  claim 1 , wherein causing examination of the received file comprises determining the namespace marking for subjects, predicates and objects of triples to be stored in a triple data store database. 
     
     
         3 . The method of  claim 1 , wherein utilizing the relationship data comprises determining a presence of positive relationship data indicating that ontology files associated with a different namespace determined for a subject or object of a triple are allowed to change definitions of the received ontology file. 
     
     
         4 . The method of  claim 1 , wherein utilizing the relationship data comprises determining a presence of negative relationship data indicating that ontology files associated with a different namespace determined for a subject or object of a triple are not allowed to change definitions of the received ontology file. 
     
     
         5 . The method of  claim 1 , further comprising allowing the triples that do not correspond to the ontology to be added to the database in response determining that the relationship data enables the subjects, predicates and objects that do not correspond to the ontology to be considered as a valid data set for storage in the database. 
     
     
         6 . The method of  claim 1 , further comprising preventing the triples that do not correspond to the ontology from being added to the database in response determining that the relationship data does not enable the triples that do not correspond to the ontology to be considered as a valid data set for storage in the database. 
     
     
         7 . The method of  claim 1 , further comprising removing the triples that do not correspond to the ontology from the database in response determining that the relationship data does not enable the triples that do not correspond to the ontology to be considered as a valid data set for storage in the database. 
     
     
         8 . An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:
 cause examination of a received file associated with an ontology to determine a namespace marking for subjects, predicates and objects of triples of the file that are to be stored in a database;   utilize relationship data corresponding to the namespace marking to identify triples whose subjects or objects that do not correspond to the ontology; and   determine whether the relationship data enables the triples whose subjects or objects do not correspond to the ontology to be considered as a valid data set for storage in the database.   
     
     
         9 . The apparatus of  claim 8  wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to cause examination of the received file by determining the namespace marking for subjects, predicates and objects of triples to be stored in a triple data store database. 
     
     
         10 . The apparatus of  claim 8  wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to utilize the relationship data by determining a presence of positive relationship data indicating that ontology files associated with a different namespace are allowed to change definitions of the received ontology file. 
     
     
         11 . The apparatus of  claim 8  wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to utilize the relationship data by determining a presence of negative relationship data indicating that ontology files associated with a different namespace are not allowed to change definitions of the received ontology file. 
     
     
         12 . The apparatus of  claim 8  wherein the at least one memory and computer program code are further configured to, with the at least one processor, cause the apparatus to allow the triples that do not correspond to the ontology to be added to the database in response determining that the relationship data enables the triples that do not correspond to the ontology to be considered as a valid data set for storage in the database. 
     
     
         13 . The apparatus of  claim 8  wherein the at least one memory and computer program code are further configured to, with the at least one processor, cause the apparatus to prevent the triples that do not correspond to the ontology from being added to the database in response determining that the relationship data does not enable the triples that do not correspond to the ontology to be considered as a valid data set for storage in the database. 
     
     
         14 . The apparatus of  claim 8  wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to remove the triples that do not correspond to the ontology from the database in response determining that the relationship data does not enable the subjects, predicates and objects that do not correspond to the ontology to be considered as a valid data set for storage in the database. 
     
     
         15 . The apparatus of  claim 8 , wherein the apparatus is a mobile terminal and further comprises user interface circuitry configured to facilitate user control of at least some functions of the mobile terminal. 
     
     
         16 . A computer program product comprising at least one computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions including program code instructions that when executed at least cause an apparatus to:
 cause examination of a received file associated with an ontology to determine a namespace marking for subjects, predicates and objects of triples of the file that are to be stored in a database;   utilize relationship data corresponding to the namespace marking to identify triples whose subjects or objects do not correspond to the ontology; and   determine whether the relationship data enables the triples whose subjects or objects do not correspond to the ontology to be considered as a valid data set for storage in the database.   
     
     
         17 . The computer program product of  claim 16 , wherein program code instructions for causing examination of the received file include instructions for determining the namespace marking for subjects, predicates and objects of triples to be stored in a triple data store database. 
     
     
         18 . The computer program product of  claim 16 , wherein program code instructions for utilizing the relationship data include instructions for determining a presence of positive relationship data indicating that ontology files associated with a different namespace are allowed to change definitions of the received ontology file. 
     
     
         19 . The computer program product of  claim 16 , wherein program code instructions for utilizing the relationship data include instructions for determining a presence of negative relationship data indicating that ontology files associated with a different namespace are not allowed to change definitions of the received ontology file. 
     
     
         20 . The computer program product of  claim 16 , further comprising program code instructions for allowing the triples that do not correspond to the ontology to be added to the database in response determining that the relationship data enables the triples that do not correspond to the ontology to be considered as a valid data set for storage in the database, preventing the triples that do not correspond to the ontology from being added to the database in response determining that the relationship data does not enable the triples that do not correspond to the ontology to be considered as a valid data set for storage in the database, or removing the triples that do not correspond to the ontology from the database in response determining that the relationship data does not enable the triples that do not correspond to the ontology to be considered as a valid data set for storage in the database.