Ok, then the answer is that this would require changes to the SPIN API - TopBraid does not come with such reflection capability. You could take the open source version and modify so that it does extra things similar to the SPINExplanations. Looking into the structure of the WHERE clause is nothing that we do out of the box.

Holger


On 3/15/2013 9:31, developer wrote:
I know the explanation function of SPIN. But I don't only need the rule which inferred a triple, but also the variable unifications from the where clause which matched for the construct rule. So the idea is to create a own explanation instance in the construct part of the rule, binding each variable unification to its variable name. The explanation instance must refer to the rule, for which it stores the unifications so I need the blank node of the rule.

Am Freitag, 15. März 2013 00:05:50 UTC+1 schrieb Holger Knublauch:

    On 3/15/2013 8:57, developer wrote:
    > Hi Holger,
    >
    > thanks for your fast reply. My question was if it is possible to
    > identify the rule, the current sparql-rule is stored to. Rules are
    > stored as blank nodes and have no URIs, so it is not possible to
    > identify a rule to access its structure from other rules. Is that
    > correct? The intention is to link a statement to the rule by
    which it
    > has been inferred.

    Ah ok, I think I understand better now. TBC already has an
    explanation
    facility - for each triple it remembers which rule added it. This
    info
    can be accessed from the explain button in the Inferences view. If
    you
    are a SPIN API user, you can access the same info using the
    SPINExplanations object passed into the SPINInferences.

    Where and how would you want to access this info? I think I could
    add a
    spif function to query this from other SPARQL queries.

    Holger

--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
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/groups/opt_out.



--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary 
Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--- 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/groups/opt_out.


Reply via email to