This content has been marked as final. Show 11 replies
I apologize for the delayed response to this query.
It is not customary for Oracle to provide detailed statements of direction. However, here are a few things we are planning for the future:
(1) Better integration with complementary 3rd party products
---eg, visualization of RDF graphs for mining and analysis,
ontology editors, query tools, etc.
(2) RDF views on Relational databases
(3) We are participating in the W3C OWL1.1 group
(4) Improved performance for loading, inferencing, semantic queries
Do you have any features you would like to see?
Sorry. I did not check your reply until now!! I did check for a response for a couple of weeks. Thanks for the response though. I will be doing some work using semantics web technologies in the bioinformatics area in the days ahead. I will get in touch with you and others in the forum if required. Thanks.
I'm working within the area of bioinformatics as well and need very much full SPARQL support (at least the OPTIONAL clause - as mentioned in earlier posts; can't do much without that).
Now that more that 6 months have gone since the answer from Melli - maybe we could hear a little more?
bw - Christian
With that many views (>1500) it seems like people are interested - couldn't we get some "hints"?
Regards - Christian
Full, native, SPARQL support is in the plan. And yes, we have recognized the need to provide at least OPTIONAL, and we plan to release this first. The release date is expected to be soon. I will post updates as soon as we have a concrete date.
Thank's is sounds good - and of cause full RDFS/OWL support is also very much wanted.
By the way, now there is also an "Oracle SQL Developer Statement of Direction" here: http://tinyurl.com/69s342 - so it's not that uncommon for the company to give this sort of info.
bw - Christian
Just to clarify, full RDFS support has been there since 10gR2 :)
Oracle 11g OWL inference supports a very rich subset of OWL semantics. It is
good enough for many applications.
It is also feasible to integrate, using Oracle Jena Adaptor, external complete DL reasoners, Pellet for example, with Oracle 11g OWL inference to achieve more semantics.
I might be wrong, but doesn't f.ex. rdfs:range = <date> imply that the system should ensure that the property value is actually a <date>?
The rule for rdfs:range is well defined by the RDFS semantics specification. I am not sure what exactly you mean by "system should ensure ..."
I think that when a property (f.ex. startDate) has the RDFS:range <date>, the database should give [at least] a warning if one tries to insert a not-valid date as property value (like in RDBMS tables).
Now I see what you are getting at.
Oracle inference is a separate process from data loading. In other words, there will be no inference going on to perform such a check as you want.
However, it might be straightforward to write a query that finds such rdfs:range triples
and list out non-valid date formats that associate with those triples.