You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But when specifying a set of bnode IRIs as a VALUES block such as VALUES ?s { <bnode://foo> <bnode://bar> } then filter conditions are not updated and/or injected appropriately.
One solution using our custom bnode function would be to rename VALUE block variables which may be become bound to bnode IRIs and then add a subsequent BIND statement afterwards:
ExprTransformVirtualBnodeUris correctly transforms
into
But when specifying a set of bnode IRIs as a VALUES block such as
VALUES ?s { <bnode://foo> <bnode://bar> }
then filter conditions are not updated and/or injected appropriately.One solution using our custom bnode function would be to rename VALUE block variables which may be become bound to bnode IRIs and then add a subsequent BIND statement afterwards:
VALUES ?s { <bnode://foo> <bnode://bar> }
becomes
The portable approach would be to still rename the variables of the VALUES blocks but then add appropriate FILTER statements to the graph patterns:
The text was updated successfully, but these errors were encountered: