Hugh, I will install it and provide feedback ASAP. Thanks Nicolas
2010/5/26 Hugh Williams <[email protected]> > Hi Nicolas, > > The problem has been fixed in the Conductor and I can now successfully > generate Linked Data RDF Views for local tables on my Virtuoso 6.1.3127 open > source build. The updated conductor vad package containing this fix can be > downloaded from: > > > http://s3.amazonaws.com/opldownload/uda/vad-packages/6.1/virtuoso/conductor_dav.vad > > To update your system simply download the VAD and replace you current > conductor_dav.vad package in the <install_dir>/vad directory and go to the > current Conductor "System Admin -> Packages" tab and it should their > available for installation in the list of available vads. Alternatively, you > can point to the vad package location on File System or DAV using the > "Install Package" option of the same "System Admin -> Packages" tab. > > Do let us now if this resolves the issue on your system ... > > Best Regards > Hugh Williams > Professional Services > OpenLink Software > Web: http://www.openlinksw.com > Support: http://support.openlinksw.com > Forums: http://boards.openlinksw.com/support > Twitter: http://twitter.com/OpenLink > > On 26 May 2010, at 14:18, Hugh Williams wrote: > > Hi Nicolas, > > I have just tried this myself with a local table, and get the VDB error you > report, which looks like a bug in the Conductor RDFView UI which is shared > between the commercial and open source products, as it does not have to > perform any VDB operations to process local tables. We should be able to > quickly fix this is the Conductor VAD package and provide you with a update > VAD to install ... > > Best Regards > Hugh Williams > Professional Services > OpenLink Software > Web: http://www.openlinksw.com > Support: http://support.openlinksw.com > Forums: http://boards.openlinksw.com/support > Twitter: http://twitter.com/OpenLink > > On 26 May 2010, at 13:11, Nicolas Figay wrote: > > Hi Hugh (and Armin) > > Thanks a lot for responding and for the useful links, in particular the > matrix that complements the FAQ. > > My question was motivated by some difficulty using RDF views on internal > databases: > > Let's give a precise exemple: > > I tried to create a RDF view on the table thalia.demo.cmu, through > database<rdfview pan. > > For column selection, I clicked on primary key selection. > Then a message , I had the following message: > > External data sources:This Virtual Database feature is available only in > the commercial release of Virtuoso Universal Server. For more information on > the commercial release of the Virtuoso Universal Server, click on the > following links to learn more: > <http://virtuoso.openlinksw.com/>I then tried, after going back, the > generation by clicking "generate" button. > The message I had is the following: "This version do not support tables > without primary key, please remove table thalia.demo.cmu from set" > > So I was (and I'm still) a little bit perplex, as it is not obvious to me > if RDF View creation on a database is a part of virtual database functional > component (which is not a part of open solution) or if there is a limitation > of open solution (that does not exist with commercial version) when creating > a RDF view on a table without a primary key. > > It was the reason why I was desespately looking for detailed and clear > differences between open and commercial version, having difficulties to find > required information to understand the origins of encountered messages. > > So more precisely, my questions should be about the encountered issues and > messages I had: > > > - is the fact that creation of a RDF view without primary key does not > work comes from usage of the open version? > - is creation of RDF view a fearure of Virtual Database? > - or is encountered problems come from the fact thalia database is an > exemple of external datasource? > > > > knowing that what I would like to do is to understand how a database in > virtuoso can be accessed through a RDF view, hopping it is a feature of open > version. > > > Best regards. > > Nicolas > > > > > > > 2010/5/26 Hugh Williams <[email protected]> > >> Hi Nicolas, >> >> The differences between the commercial and open source products are listed >> in the following feature comparison matrix: >> >> http://virtuoso.openlinksw.com/main/featurematrix/index.htm >> >> In summary the following are commercial features only: >> >> - Virtual Database Engine >> - Replication >> - Clustering and high availability >> - Geo-Spatial Extensions >> >> Best Regards >> Hugh Williams >> Professional Services >> OpenLink Software >> Web: http://www.openlinksw.com >> Support: http://support.openlinksw.com >> Forums: http://boards.openlinksw.com/support >> Twitter: http://twitter.com/OpenLink >> >> On 26 May 2010, at 11:40, Nicolas Figay wrote: >> >> > Hi, >> > >> > investigating functional coverage of virtuoso (as I'm a teacher in the >> are of semantic web and digital collaboration field), I've some difficulties >> to clearly understand what the limitations are for open source communitary >> virtuoso openlink, compared to enterprise version. >> > >> > Some are appearing when trying to use the tool, for example creation of >> RDF views on tables of a database, but it is difficult to identify quicly >> what could be investigated for demonstration and what we should forget >> relying only on community edition. >> > >> > Is there a place or a document where differences are listed, as >> restrictions of community edition (version 6.x)? >> > >> > Thanks by advance. >> > >> > Nicolas >> > >> ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Virtuoso-users mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/virtuoso-users >> >> > > >
