Closed gwcox66 closed 8 years ago
@pulquero are you available to take a look at this?
I'll see if I can take a look this week, I expect the spin parser may have overwritten the minus with the filter.
On Monday, 29 August 2016, 23:30, Jeen Broekstra <notifications@github.com> wrote:
@pulquero are you available to take a look at this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I believe the same also occurs with OPTIONAL and other like constructs.
Thanks @pulquero! I modified my constructors as follows and performed the same test otherwise:
However, both messages were asserted in the resulting sxxicci:TestPub7Proposal
individual, seeming to indicate that both OPTIONAL clauses had run:
Thank you @jeenbroekstra and @pulquero!
I'm working with RDF4J Workbench, and I'm hoping this is a bug and not "pilot error":
I'm writing SPIN constructors using a custom subproperty
sxxicc:activeSxxiPub7ComplianceCheckPolicy
(see enclosed ontology RDF file). MinusClauseProblem.zipThe sxxicc:Pub7FakeProposal class has two constructors (see TopBraid Composer FE screen capture above) which differ only by a
FILTER
statement. Given the 2 SPARQL Update queries I use to instantiate this class, NEITHER should assert theirCONSTRUCT
because of theMINUS
clause. The?dataItem
does have thesxxicc:TopSecretPub7DataItem
class. However, the first constuctor does assert the CONSTRUCT triple. It seems that the addition of theFILTER
statement negated theMINUS
clause. How can that be?First setup SPARQL update query (sets up the DataItem005 individual and invokes parsing constructors):
Second setup SPARQL update query:
Resulting
sxxicc:Pub7FakeProposal
individual (shows that only first compliance check asserted triple when neither should have):Resulting
sxxicc:Pub7DataItem005
individual (shows that this is a member of thesxxicc:TopSecretPub7DataItem
class and therefore should satisfy theMINUS
clause, preventing both constructors from asserting triples)