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
This does not work if there are multiple references beneath a <B1> tag, because the equal condition executed in the background will look like the following (snippet). It checks for equality of [C11] and [C12] with [C11, C12], which of course does not work.
Line 1075: 15:26:04.741 [main] DEBUG b.u.i.k.functions.agent.AgentImpl .execute(34) - Executing function 'http://example.com/idlab/function/equal' with arguments '('http://users.ugent.be/~bjdmeest/function/grel.ttl#valueParameter' -> '[C11]')('http://users.ugent.be/~bjdmeest/function/grel.ttl#valueParameter2' -> '[C11, C12]')'
Line 1084: 15:26:04.741 [main] DEBUG b.u.i.k.functions.agent.AgentImpl .execute(34) - Executing function 'http://example.com/idlab/function/equal' with arguments '('http://users.ugent.be/~bjdmeest/function/grel.ttl#valueParameter' -> '[C12]')('http://users.ugent.be/~bjdmeest/function/grel.ttl#valueParameter2' -> '[C11, C12]')'
Line 1087: 15:26:04.741 [main] DEBUG b.u.i.k.functions.agent.AgentImpl .execute(34) - Executing function 'http://example.com/idlab/function/equal' with arguments '('http://users.ugent.be/~bjdmeest/function/grel.ttl#valueParameter' -> '[C11]')('http://users.ugent.be/~bjdmeest/function/grel.ttl#valueParameter2' -> '[C12]')'
Is this a bug? How can I go around this behavior if this is not a bug?
The text was updated successfully, but these errors were encountered:
In my XML shown below there are references from /A1/B2/C1REF/@pid to /A1/B1/C1/@id
In my mapping the references are added with a join condition (last paragraph) :
This does not work if there are multiple references beneath a
<B1>
tag, because the equal condition executed in the background will look like the following (snippet). It checks for equality of[C11]
and[C12]
with[C11, C12]
, which of course does not work.Is this a bug? How can I go around this behavior if this is not a bug?
The text was updated successfully, but these errors were encountered: