Ok, I changed some rules and my problem was solved
Thank you guys for your help
bye
Claudia
Il giorno domenica 15 febbraio 2015 23:48:20 UTC+1, Holger Knublauch ha
scritto:
>
> Hi Claudia,
>
> it is possible that fewer rules fire because the triples of the SPIN RDF
> syntax probably lead to some more inferences, and then further iterations
> of the rule engine. Some of them may have been unwanted inferences from the
> start. Do you have specific (wanted) inferences that are now missing? If
> yes, can you provide details such as the rules file?
>
> TopBraid should not add prefixes to the individual rules, but may add
> prefixes to the surrounding file. It may basically lift up all prefixes
> from imported files, so that the SPIN rules can be parsed independently.
>
> HTH
> Holger
>
>
> On 2/13/2015 22:45, Claudia Grieco wrote:
>
> Also I see that topbraid is automatically adding prefixes to rules (spra,
> sparqlmotion ecc. ) is it normal?
>
> Il giorno venerdì 13 febbraio 2015 12:38:50 UTC+1, Claudia Grieco ha
> scritto:
>>
>> Thanks everyone for the help.
>> I tried 1)converting rules in rdf file to sp:text 2)converting the entire
>> file in ttl
>> In both cases the problem I wrote about doesn't appear anymore, but in
>> both cases some rules seem to not fire anymore (the inference process seems
>> also a bit quicker) because I don't get all the results I was getting prior
>> the problem
>> some suggestions?
>>
>> Il giorno venerdì 23 gennaio 2015 17:31:55 UTC+1, Claudia Grieco ha
>> scritto:
>>>
>>> Hi to all,
>>> I'm currently using TopBraid Composer Free Edition
>>> Version: 4.5.0
>>>
>>> I have noticed a strange behaviour: wherever I launch an inference on
>>> a file, and then I interrupt (Cancel) the inference process for some
>>> reason, Top Braid rewrites my rule file adding variables at random to
>>> function called in rules.
>>> For example the following spin:rule:
>>> *INSERT {*
>>> * ?previousPerson tracking:blobMatch ?this .*
>>>
>>> *}*
>>> *WHERE {*
>>> * ?previousPerson a foaf:Person .*
>>> * ?previousPerson tracking:blobMatch ?b2 .*
>>> *[....]*
>>> * FILTER (((spin:myfunction(?b2, ?this) && spin:hasHumanSize(?this))
>>> && (?dist <= 45)) && (?dist = spin:getMinHumanDistance(?b2, ?this))) .*
>>> * .*
>>> *}*
>>>
>>> becomes:
>>> *INSERT {*
>>> * ?previousPerson tracking:blobMatch ?this .*
>>>
>>> *}*
>>> *WHERE {*
>>> * ?previousPerson a foaf:Person .*
>>> * ?previousPerson tracking:blobMatch ?b2 .*
>>> *[....]*
>>> * FILTER (((spin:myfunction(?b2, ?this) && spin:hasHumanSize(?this,
>>> ?this)) && (?dist <= 45)) && (?dist = spin:getMinHumanDistance(?b2, ?this,
>>> ?b2))) .*
>>> * .*
>>> *}*
>>>
>>> Sometimes it also changes the order of variables in my fuction
>>> declaration...
>>> What could be the problem?
>>> Note: I'm currently storing rules in rdf format instead of ttl, is it an
>>> issue?
>>> Thanks a lot
>>> Claudia
>>>
>> --
> You received this message because you are subscribed to the Google Group
> "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
> Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid
> Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
> To post to this group, send email to [email protected]
> <javascript:>
> ---
> You received this message because you are subscribed to the Google Groups
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
--
You received this message because you are subscribed to the Google Group
"TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live,
TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
---
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
