Re: [Virtuoso-users] Semantic search

2010-01-05 Thread Alexander Sidorov
Hi Hugh, Sorry, I have read it innattentively first time. It is really what I searched. Thank you :) Regards, Alexander 2010/1/3 Hugh Williams > Hi Alexander, > > Given that RDF-stores use SPARQL as their query mechanism, any form of > semantic search is going to use SPARQL ultimately to acce

Re: [Virtuoso-users] EF4 support

2010-01-05 Thread Hugh Williams
Hi Alexander, We do plan to support EF4 which is already being looked into. Note that as detailed on the Microsoft ADO.Net Blog Team site "Providers for Entity Framework 3.5 will work unmodified against Entity Framework 4.0. Also, most of the features and improvements introduced in Entity Frame

Re: [Virtuoso-users] EF-provider

2010-01-05 Thread Kingsley Idehen
Alexander Sidorov wrote: Hello! OpenLink EF provider is great in that it can be used with almost any relational database. But unfortunately it doesn't work without Virtuoso. It would be great to move the database independence mechanism from Virtuoso to the provider itself. I have no idea how d

Re: [Virtuoso-users] Entity Framework provider

2010-01-05 Thread Kingsley Idehen
Alexander Sidorov wrote: Hi Hugh, At the moment I'm especially interested in working with Virtuoso using .NET. Are there some other frameworks excepting dotnetRDF and LINQTORDF? I'm also interested in EF, but not in this context. Documentation says your EF-provider can be used to access non-

[Virtuoso-users] EF-provider

2010-01-05 Thread Alexander Sidorov
Hello! OpenLink EF provider is great in that it can be used with almost any relational database. But unfortunately it doesn't work without Virtuoso. It would be great to move the database independence mechanism from Virtuoso to the provider itself. I have no idea how difficult it is to implement..

[Virtuoso-users] EF4 support

2010-01-05 Thread Alexander Sidorov
Hello! What are your plans about EF4 support? Regards, Alexander

Re: [Virtuoso-users] Entity Framework provider

2010-01-05 Thread Alexander Sidorov
Hi Hugh, At the moment I'm especially interested in working with Virtuoso using .NET. Are there some other frameworks excepting dotnetRDF and LINQTORDF? I'm also interested in EF, but not in this context. Documentation says your EF-provider can be used to access non-relation data stores. I expect

Re: [Virtuoso-users] Entity Framework provider

2010-01-05 Thread Hugh Williams
Hi Alexander, Yes, we did perform some work to provide LiNQ2RDF support for Virtuoso which was committed to the project in 2008, see: http://virtuoso.openlinksw.com/Whitepapers/html/linqtordf/linqtordf1.htm I thought you were more interested in EF support which I why I did not include

Re: [Virtuoso-users] Set upper limit for matches from bif:containswildcard

2010-01-05 Thread Magnus Haraldsen Amundsen
t.com __ Information from ESET NOD32 Antivirus, version of virus signature database 4704 (20091220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 4744 (20100105) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

Re: [Virtuoso-users] Entity Framework provider

2010-01-05 Thread Alexander Sidorov
Hi High, Thank you for dotnetRDF link: I didn't know about this framework before. I have also found one more .NET framework with Virtuoso support - LINQ2RDF. Now I'm choosing which of them to use. Regards, Alexander 2010/1/3 Hugh Williams > Hi Alexander, > > The walk-throughs provide sample ap

Re: [Virtuoso-users] international characters in vsp pages

2010-01-05 Thread Eddy Vanderlinden
Hi Mitko, I did as requested: set http_charset='utf-8'; -- not only at the top of the page but also in the procedure adapted the rest of the code but the result remained the same. Then I commented the 'else' condition to find out which values felt into the condition 'isstring'. See file

Re: [Virtuoso-users] international characters in vsp pages

2010-01-05 Thread Mitko Iliev
Hi Eddy, You should not cast the result to varchar before to re-code to wide , the cast to varchar would try to recode utf-8 to default server narrow charset , thus : Also you need to set the http charset to utf-8 : >> sets the http charset to utf-8 foreach (any row in data) do { htt