This content has been marked as final. Show 1 reply
Regarding your first question: Currently we only support security at the model level, not at the triple level that require. This is planned for future work. One approach to build an application with triple level security is to do what you have described - have an additional column in the triple table that stores the security level. When SDO_RDF_MATCH is executed, it returns a table, and this table can be joined with the triple table so that the result rows are filtered based on the value of the security level column in the triple table.
Any alternatives? I am able to select, insert, delete, and manipulate the normal >table securely, but I am unable to use many of the SDO functions due to it >bypassing that table (I think...)I am not sure I fully understand your second question. You are right that the triple table is "bypassed" by the query interface SDO_RDF_MATCH - that is, SDO_RDF_MATCH operates directly on the internal tables (though all this it transparent to the user). What other SDO functions would you like to use?
Oracle Semantic Technology Development Group