OK, try this instead. Add a property, let's name it
:doNotProcessRule. For the classes you do not want to be processed,
add (one ore more) rule name, such as "rule1". The use the
following graph pattern.
WHERE {
?this ...
OPTIONAL {
This feels very close to what I was thinking, because it fits very well
with my use case.
However, the question remains (because one can start imagining a lot of use
cases):
Wouldn't it be more powerful/beautiful if it could be something like
:myClass spin:ignore :rule1 (eg. just for :myClass,
Nikolaos; One approach would be to FILTER out the class instances. I.e.:
{ ?this :prop ?value .
...
?undesiredInstance a :SubClass1 .
FILTER (?this != ?undesiredInstance)
}
-- Scott
Sent from my iPhone
On Apr 3, 2015, at 7:05 AM, Nikolaos Beredimas bere...@gmail.com wrote:
Quoting
Quoting from http://www.w3.org/Submission/spin-modeling/ :
In other words, SPIN class descriptors can only narrow down and further
restrict what has been defined further up in the class hierarchy. In this
spirit, *global* class descriptions are those that are attached to the
root class
Just a followup on this issue. I searched for and removed all the resources
that started with a numeric character and reloaded a fresh Sesame
repository. But I got the same type of error (below) as when trying to
establish the TBC connector before. This leads me to wonder whether the
leading
Hi Rich,
sorry if this had been clarified already, but can you confirm that you
are using a matching Sesame server version: TopBraid expects Sesame 2.6,
as they may have changed their communication protocol between versions.
Thanks,
Holger
On 4/4/15 2:02 AM, Rich Keller wrote:
Just a
Hi Nikolaos,
this is certainly an interesting question, yet I don't see how to solve
this. As soon as inferencing is activated, and you have a class
hierarchy such as
rdfs:Resource
ex:RootClass rule1
ex:ChildClass rule2 overrides rule1
and ex:Instance a ex:ChildClass, then
