Hello all -
I am looking for help evaluating Virtuoso and RDF(S) more generally for data
integration purposes in the life sciences and pharmaceutical space. We are out
of bandwidth to do evaluation this internally, and I haven't been able to find
a Virtuoso consultants directory or anything of
Hi,
Just a small remark about this subject. When I use the method [1], I
have to specify the full path, not just the relative path as shown in
the example.
Thanks for your help,
Pierre
[1]: http://docs.openlinksw.com/virtuoso/fn_rdf_load_rdfxml_mt.html
On Wed, 2010-12-15 at 08:42 +0100,
Hi Pierre,
Relative paths work for me:
$ /opt/virtuoso/bin/isql 1162
Connected to OpenLink Virtuoso
Driver: 06.01.3127 OpenLink Virtuoso ODBC Driver
OpenLink Interactive SQL (Virtuoso), version 0.9849b.
Type HELP; for help and EXIT; to exit.
SQL DB.DBA.RDF_LOAD_RDFXML_MT (file_to_string_output
* Mark James
The commercial version of virtuoso has a 'virtual database' capability. You
can create tables within virtuoso that are links to tables within other
rdbms. It's then possible to create rdf views and either materialize the
triples or query the rdbms data directly.
Thank you
Hi Pierre,
The relative path base is the server working directory i.e. in the place where
virtuoso.ini file is, and since your file is on desktop server can't find it
unless full path is given.
Best Regards,
Mitko
On Dec 16, 2010, at 2:38 PM, Pierre-Yves wrote:
Hi Hugh,
This is what I
On 12/16/10 7:38 AM, Pierre-Yves wrote:
Hi Hugh,
This is what I do:
$ /usr/libexec/virtuoso/isql virtuoso
Connected to OpenLink Virtuoso
Driver: 06.01.3127 OpenLink Virtuoso ODBC Driver
OpenLink Interactive SQL (ODBC), version 0.9849b.
Type HELP; for help and EXIT; to exit.
SQL
Hi Lars,
What are the remote database(s) you are seeking to virtualize data into
Virtuoso from ?
The docs page you found below details whats happening at the lower level, but
the materialization of the views can also be performed using the Virtuoso
conductor with the following steps :
* Kingsley Idehen
I am sure you understand that as a fundamental principle, OpenLink
implements standards whenever such exist. If standards don't exist and a
problem persists, we innovate. If standards emerge later, we support
immediately.
What I wrote was not meant as criticism of
On 12/16/10 3:59 PM, Lars Marius Garshol wrote:
* Kingsley Idehen
I am sure you understand that as a fundamental principle, OpenLink
implements standards whenever such exist. If standards don't exist and a
problem persists, we innovate. If standards emerge later, we support
immediately.
What I
