Following the Carina's advice:
shutdown()
change value of parameter "ResultSetMaxRows" in the .ini file to
1000000000000000
save
sudo virtuoso-t -f &
sudo isql-vt
Applying again the rule, I get same the wrong behavior: inference only
on the <uri> results to the correct inferred triples, but not in the
case of inference on the whole dataset.
I think and I am afraid I cannot "share" the dataset I am testing ( if
you meant that).
I changed my query to selection:
sparql define input:inference<something> select * from <g> where{?s ?p
?o} limit 20
I do not know how the inference is evaluated on the triples and how
the result is returned, but in the first 20 results I do not see any
new inferred triple.
On 27 April 2012 14:18, Kingsley Idehen <[email protected]> wrote:
> On 4/27/12 6:57 AM, Carina Haupt wrote:
>>
>>
>> On 27.04.2012 12:14, Alex wrote:
>>>
>>> Hello again,
>>> my scenario is the following: given a graph<g> with some triples
>>> apply a rule set based on a schema and insert the inferred triples to
>>> another graphs<rdfs_g>.
>>>
>>> So I use the following query to accomplish that:
>>>
>>> sparql define input:inference<something> insert into<rdfs_g> {?s ?p
>>> ?o} where{graph<g> {?s ?p ?o}} (1)
>>>
>>> I then check for a specific uri in rdfs_g and I see the same inferred
>>> triples but NOT all of them and the number of triples is the same.
>>>
>>> To further test it I apply the same rule for this specific uri:
>>>
>>> sparql define input:inference<something> insert into<rdfs_g> {<uri>
>>> ?p ?o} where{graph<g> {<uri> ?p ?o}} (2)
>>>
>>> Comparing the<rdfs_g> to<g> there is big difference on the number of
>>> triples (i.e. 15 to 8 rows respectively) and I think I see the total
>>> inferred triples.
>>>
>>> What is wrong with that?? I have test it (1) on a smaller dataset that
>>> <g> and works fine.
>>>
>>> I am begging to lose my mind on this. How could I debug this?
>>
>> There is a threshold in the ini file which defines how many triples are
>> returned at max. Perhaps this is the source of your problem?!
>>
>> Ciao Carina
>
>
> Yes re. INI.
>
> Alternatively, one diagnostic option re. assistance from us would be to
> change the INSERT into a SELECT and then share the SPARQL protocol URL.
>
> Kingsley
>
>>
>>> Thanks.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Virtuoso-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>
>
>
> --
>
> Regards,
>
> Kingsley Idehen
> Founder& CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter/Identi.ca handle: @kidehen
> Google+ Profile: https://plus.google.com/112399767740508618350/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Virtuoso-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>
