VocBench Validation doensn't seem to work
16 views
Skip to first unread message
Karen Goes
Jul 9, 2026, 9:35:36 AM (5 days ago) Jul 9
to vocbench-user
Good afternoon,
We have the new version of VocBench (v15.1.1) running with the history and validation turned on (after some struggles), but now it appears that the validation doesn't 'work'. In VocBench it shows the colors and a newly added concept turns green, but it is also immediately present in the main repository of our GraphDB. With a previous version I know I tested that it wouldn't be visible until after the validation process was complete in the, back then core, repository.
The way it works now kinda defeats the purpose of having validation in the first place. Is this a (known) bug in the new version or am I missing something?
Kind regards,
Karen
Karen
Manuel Fiorelli
Jul 9, 2026, 10:27:11 AM (5 days ago) Jul 9
to Karen Goes, vocbench-user
Hi Karen,
I tested the History & Validation feature with version 15.1.1 on GraphDB 11.2.1, and I found it to work as expected. Looking at the SPARQL query you provided, I think there might be a slight misunderstanding regarding how validation is implemented. Let me explain.
When you add a triple, the proposed change is recorded in the support repository in a reified form, along with metadata about the activity that generated it. However, it is also written into the main repository within a dedicated staging "add" graph. This latter step is necessary so that the triple can be retrieved while still being distinguished from approved data (which, for example, makes it possible to display a proposed addition in green).
Your SPARQL query gave the impression that the data is simply written into the main repository because, without a GRAPH clause, it matches against the union of all graphs. You can wrap the triple pattern inside a GRAPH clause instead, as shown in the following query:
Snippet di codice
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
SELECT * WHERE {
GRAPH ?g {
?s skos:prefLabel 'test3'@en .
}
} LIMIT 100
By doing this, you should get a result where ?g is set to a graph whose name is derived from your project's main graph, but altered slightly to distinguish it as the corresponding staging addition graph.
Best regards,
Manuel
I tested the History & Validation feature with version 15.1.1 on GraphDB 11.2.1, and I found it to work as expected. Looking at the SPARQL query you provided, I think there might be a slight misunderstanding regarding how validation is implemented. Let me explain.
When you add a triple, the proposed change is recorded in the support repository in a reified form, along with metadata about the activity that generated it. However, it is also written into the main repository within a dedicated staging "add" graph. This latter step is necessary so that the triple can be retrieved while still being distinguished from approved data (which, for example, makes it possible to display a proposed addition in green).
Your SPARQL query gave the impression that the data is simply written into the main repository because, without a GRAPH clause, it matches against the union of all graphs. You can wrap the triple pattern inside a GRAPH clause instead, as shown in the following query:
Snippet di codice
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
SELECT * WHERE {
GRAPH ?g {
?s skos:prefLabel 'test3'@en .
}
} LIMIT 100
By doing this, you should get a result where ?g is set to a graph whose name is derived from your project's main graph, but altered slightly to distinguish it as the corresponding staging addition graph.
Best regards,
Manuel
--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/c421d1cf-98ff-434e-b479-194d457668d0n%40googlegroups.com.
--
Manuel Fiorelli
Reply all
Reply to author
Forward
0 new messages