Claudia; RDF/XML (.rdf) and Turtle (.ttl) are equivalent text
serializations of RDF - i.e. they are interpreted by TopBraid as the
same data structures and hence the problem cannot be at there.
(However, if you want to try, just convert your RDF/XML file to
Turtle using Export... > TopBraid Composer >
Export/Merge/Convert RDF Graphs.
As Holger has stated, try using the Preferences for SPIN to generate
sp:text representations of SPARQL queries.
-- Scott
On 2/12/2015 2:26 AM, Claudia Grieco
wrote:
Thanks for your reply.
My rule file is in RDF (not *.ttl). May this be part of the
problem?
Claudia
Il giorno giovedì 12 febbraio 2015 00:49:48 UTC+1, Holger
Knublauch ha scritto:
Yes, this has been reported before. Switch to the
sp:text syntax to avoid inferences that may garble up the
SPIN RDF syntax.
Holger
On 2/11/2015 21:47, Claudia Grieco wrote:
Hi everyone,
Now the problem appears whenever I try to run any
inferences on the rules. Parameters are added in EVERY
function call and the added parameters are even in the
inference list
example
spin:contains(?area, ?spThing1)
becomes spin:contains(?area, ?area, ?spThing1) with
inferences:
-spin:contains(?area, ?area, ?spThing1) sp:arg
?area
-spin:contains(?area, ?area, ?spThing1) sp:arg
?spThing
Do you have any idea why?
thanks
Claudia
Il giorno mercoledì 4 febbraio 2015 14:28:47 UTC+1,
Claudia Grieco ha scritto:
Hi ,
Thanks for your reply, I'll try to follow
your advices
Bye
Claudia
Il giorno sabato 24 gennaio 2015 00:57:31 UTC+1,
Holger Knublauch ha scritto:
Hi
Claudia,
such effects may happen when (OWL RL)
inferences are executed over a graph
containing SPIN RDF syntax triples. When you
interrupt the inferencing process, it will
not have cleaned up the "trivial" inferences
and thus you may end up with triples that
mess up the SPIN RDF syntax. Resetting the
inferences should fix this, but better:
don't interrupt the process.
If you want to 100% avoid complications due
to the SPIN RDF syntax, switch to SPIN text
syntax using sp:text. The Model menu has
items to convert to the text-only format (in
which SPIN queries are not represented as
triples), and there is a TopBraid Composer
preference under "SPIN" to always use
sp:text.
HTH
Holger
On 1/24/15, 2:31 AM, Claudia Grieco
wrote:
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]
---
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
topbraid-user...@googlegroups.com.
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 topbrai...@googlegroups.com
---
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 topbraid-user...@googlegroups.com.
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.
--
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.
|
