Thanks for that.

well i figured a way around it. when i create my triples i create that
predicate as well. seems to work as a short cut ...




> Hi
>
> Development indicate that the directType is a Sesame specific class type
> not supported in other RDF query engines like Virtuoso and Jena etc.
>
> 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 6 Jun 2010, at 09:37, bluestar wrote:
>
>> hi Hugh,
>>
>> it seems to work now! i was trying to execute a very simple
>> SELECT DISTINCT ?p WHERE {?s ?p ?o}
>>
>> i have since tried other things and it seems to be doing the right thing
>> now. thanks for all this.
>>
>> in the end i had to repackage sesame with all the dependant virtuoso
>> jars
>> into a war file ... and redeployed. i also restarted virtuoso - i dont
>> think this was necesary. then created another repo in sesame but this
>> time
>> i used dba user.
>>
>> also i found in my logs lots of these errors:
>> SQ033: SELECT access denied for column GI_SUPER of table
>> DB.DBA.SYS_ROLE_GRANTS, user ID 107
>> (ie when i was not using dba. my user has all permissions, ie
>> select/update/sponge. has DAV permissions as well).
>>
>>
>> last question: how do i determine the directType of a subject in a
>> triple?
>> sorry i keep mentioning sesame but anyway.. sesame generated a "x
>> directType y" triple; how can i achieve similar with vituoso? i dont see
>> it in the workbench and querying it doesnt find anything.
>>
>> at the moment it seems i am getting back the super class only which is
>> valid but sometimes i want the direct type.
>>
>> thanks.
>>
>>
>>
>>
>>
>>> Hi
>>>
>>> What is the query you are attempting to run that is resulting in this
>>> "unsupport query type" error ?
>>>
>>> Have you been able to confirm basic connectivity of the Sesame HTTP
>>> Repository to Virtuoso and its ability to run a simple query and
>>> explore
>>> the Virtuoso server as detailed in the documentation at [1] ?
>>>
>>> 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
>>>
>>> [1]
>>> http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtSesame2HttpRepository
>>>
>>> On 5 Jun 2010, at 07:20, bluestar wrote:
>>>
>>>> hi Hugh,
>>>>
>>>> thanks for this. i got somewhere at least.
>>>>
>>>> it seems sesame does not know about virtouso queries.
>>>>
>>>> i get this exception trying execute a query via sesame workbench.
>>>>
>>>> any suggestions?
>>>>
>>>> javax.servlet.ServletException:
>>>> org.openrdf.repository.http.HTTPQueryEvaluationException: Unsupported
>>>> query type: virtuoso.sesame2.driver.VirtuosoQuery
>>>>    
>>>> org.openrdf.workbench.base.TransformationServlet.service(TransformationServlet.java:80)
>>>>    org.openrdf.workbench.base.BaseServlet.service(BaseServlet.java:40)
>>>>    
>>>> org.openrdf.workbench.proxy.ProxyRepositoryServlet.service(ProxyRepositoryServlet.java:93)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:131)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:90)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchGateway.service(WorkbenchGateway.java:97)
>>>>    org.openrdf.workbench.base.BaseServlet.service(BaseServlet.java:40)
>>>>    
>>>> org.openrdf.workbench.proxy.CookieCacheControlFilter.doFilter(CookieCacheControlFilter.java:52)
>>>>
>>>> root cause
>>>>
>>>> org.openrdf.repository.http.HTTPQueryEvaluationException: Unsupported
>>>> query type: virtuoso.sesame2.driver.VirtuosoQuery
>>>>    
>>>> org.openrdf.repository.http.HTTPTupleQuery.evaluate(HTTPTupleQuery.java:48)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.evaluateTupleQuery(QueryServlet.java:208)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.service(QueryServlet.java:146)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.service(QueryServlet.java:99)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.service(QueryServlet.java:72)
>>>>    
>>>> org.openrdf.workbench.base.TransformationServlet.doPost(TransformationServlet.java:87)
>>>>    
>>>> org.openrdf.workbench.base.TransformationServlet.service(TransformationServlet.java:70)
>>>>    org.openrdf.workbench.base.BaseServlet.service(BaseServlet.java:40)
>>>>    
>>>> org.openrdf.workbench.proxy.ProxyRepositoryServlet.service(ProxyRepositoryServlet.java:93)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:131)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:90)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchGateway.service(WorkbenchGateway.java:97)
>>>>    org.openrdf.workbench.base.BaseServlet.service(BaseServlet.java:40)
>>>>    
>>>> org.openrdf.workbench.proxy.CookieCacheControlFilter.doFilter(CookieCacheControlFilter.java:52)
>>>>
>>>> root cause
>>>>
>>>> org.openrdf.repository.RepositoryException: Unsupported query type:
>>>> virtuoso.sesame2.driver.VirtuosoQuery
>>>>    
>>>> org.openrdf.http.client.HTTPClient.getTupleQueryResult(HTTPClient.java:992)
>>>>    org.openrdf.http.client.HTTPClient.sendTupleQuery(HTTPClient.java:414)
>>>>    org.openrdf.http.client.HTTPClient.sendTupleQuery(HTTPClient.java:397)
>>>>    
>>>> org.openrdf.repository.http.HTTPTupleQuery.evaluate(HTTPTupleQuery.java:41)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.evaluateTupleQuery(QueryServlet.java:208)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.service(QueryServlet.java:146)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.service(QueryServlet.java:99)
>>>>    
>>>> org.openrdf.workbench.commands.QueryServlet.service(QueryServlet.java:72)
>>>>    
>>>> org.openrdf.workbench.base.TransformationServlet.doPost(TransformationServlet.java:87)
>>>>    
>>>> org.openrdf.workbench.base.TransformationServlet.service(TransformationServlet.java:70)
>>>>    org.openrdf.workbench.base.BaseServlet.service(BaseServlet.java:40)
>>>>    
>>>> org.openrdf.workbench.proxy.ProxyRepositoryServlet.service(ProxyRepositoryServlet.java:93)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:131)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:90)
>>>>    
>>>> org.openrdf.workbench.proxy.WorkbenchGateway.service(WorkbenchGateway.java:97)
>>>>    org.openrdf.workbench.base.BaseServlet.service(BaseServlet.java:40)
>>>>    
>>>> org.openrdf.workbench.proxy.CookieCacheControlFilter.doFilter(CookieCacheControlFilter.java:52)
>>>>
>>>> note The full stack trace of the root cause is available in the Apache
>>>> Tomcat/6.0.24 logs.
>>>>
>>>>
>>>>
>>>>> Hi
>>>>>
>>>>> As indicated in the examples in the Virtuoso inferencing
>>>>> documentation
>>>>> at
>>>>> [1] you would need to load your OWL files into Virtuoso, which being
>>>>> in
>>>>> RDF/XML can be done with the Virtuoso RDF_LOAD_RDFXML() function as
>>>>> detailed at [2]. Once the data is loaded into Virtuoso you can then
>>>>> used
>>>>> the rdfs_rule_set() function to create the rule sets in Virtuoso, at
>>>>> which
>>>>> point when creating the Virtuoso Sesame HTTP Repository you can then
>>>>> set
>>>>> the "Inference RuleSet name" parameter to the name of the rule set to
>>>>> be
>>>>> used ie "upper" in your example below.  Note also when using the
>>>>> SPARQL
>>>>> query interface of the OpenRDF Workbench, you also need to check the
>>>>> "Include inferred statements" check box of the rule set to be applied
>>>>> against the query being run.
>>>>>
>>>>> I hope this answers your question, as that is how I got this to work
>>>>> in
>>>>> the OpenRDF Workbench using the first example in section 16.8.8.1 of
>>>>> the
>>>>> the documentation at [1] ...
>>>>>
>>>>> 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
>>>>>
>>>>> [1]
>>>>> http://docs.openlinksw.com/virtuoso/rdfsparqlrule.html#rdfsparqlruleexamples
>>>>> [2] http://docs.openlinksw.com/virtuoso/fn_rdf_load_rdfxml.html
>>>>>
>>>>> On 4 Jun 2010, at 04:13, bluestar wrote:
>>>>>
>>>>>> Hi Hugh,
>>>>>>
>>>>>> thanks for this. it confirms what i was thinking. and yes i am using
>>>>>> the
>>>>>> sesame provider as outlined in the link you gave me.
>>>>>>
>>>>>> however my next question is; how do i do it using this rdfs_rule_set
>>>>>> function; i am not really sure about this.
>>>>>>
>>>>>> for example my owl files are very similar to
>>>>>> http://proton.semanticweb.org/2005/04/protonu,
>>>>>> http://proton.semanticweb.org/2005/04/protont,
>>>>>> http://proton.semanticweb.org/2005/04/protons
>>>>>>
>>>>>> how would i do this using these owl files?
>>>>>>
>>>>>> like this:
>>>>>>
>>>>>> rdfs_rule_set ("upper",
>>>>>> "http://proton.semanticweb.org/2005/04/protonu";)?
>>>>>>
>>>>>> if so this seems to have no effect at all.
>>>>>>
>>>>>> Please let me know.
>>>>>>
>>>>>> cheers.
>>>>>>
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> If using the Virtuoso Sesame HTTP repository as detailed at [1],
>>>>>>> then
>>>>>>> you
>>>>>>> can create your inference rules in Virtuoso using the rdfs_rule_set
>>>>>>> function as detailed at [2], then you can use the "Inference
>>>>>>> RuleSet
>>>>>>> name"
>>>>>>> parameter of the created Virtuoso Sesame HTTP repository to specify
>>>>>>> the
>>>>>>> inference rule set name to be used.created with the rdfs_rule_set
>>>>>>> function.
>>>>>>>
>>>>>>> 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
>>>>>>>
>>>>>>> [1]
>>>>>>> http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtSesame2HttpRepository
>>>>>>> [2]
>>>>>>> http://docs.openlinksw.com/virtuoso/rdfsparqlrule.html#rdfsparqlrulemake
>>>>>>>
>>>>>>> On 3 Jun 2010, at 15:32, bluestar wrote:
>>>>>>>
>>>>>>>> hi,
>>>>>>>>
>>>>>>>> i am trying to use the  Virtuoso sesame provider. how do i achieve
>>>>>>>> inferencing through this?
>>>>>>>>
>>>>>>>> I have been using sesame in-mem with direct type hierarchy, but
>>>>>>>> now
>>>>>>>> moving
>>>>>>>> to Virtuoso. i want the same behaviour in virtuoso.
>>>>>>>>
>>>>>>>> i have 3 different owl files with the hierachy of all my classes;
>>>>>>>> plus
>>>>>>>> thousands of triples based on this.
>>>>>>>>
>>>>>>>> i can see there is a "Inference RuleSet name" field in the repo
>>>>>>>> creation
>>>>>>>> screen of Virtuoso sesame provider; what do i put in there?
>>>>>>>> will this enable inferencing?
>>>>>>>>
>>>>>>>> any suggestions will be greatly appreciated.
>>>>>>>>
>>>>>>>> thanks
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>>>>>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>>>>>>>> lucky parental unit.  See the prize list and enter to win:
>>>>>>>> http://p.sf.net/sfu/thinkgeek-promo
>>>>>>>> _______________________________________________
>>>>>>>> Virtuoso-users mailing list
>>>>>>>> Virtuoso-users@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>>>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>>>>>> lucky parental unit.  See the prize list and enter to win:
>>>>>> http://p.sf.net/sfu/thinkgeek-promo
>>>>>> _______________________________________________
>>>>>> Virtuoso-users mailing list
>>>>>> Virtuoso-users@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>



Reply via email to