`update_shapes` should flow through to `shacl-tulip` #355

New issue

Open

opened 2026-06-22 10:39:18 +00:00 by jsheunis · 0 comments

jsheunis commented

2026-06-22 10:39:18 +00:00

Owner

Picked up in #351

I used update_shapes to change the notation's datatype from xsd:hexBinary to xsd:string (at first, setting it to null caused the field not to be displayed in the UI). This worked fine in the frontend, but the submission still had the xsd:hexBinary literal type included. I think this actually highlights an inconsistency in shacl-vue->shacl-tulip; shacl-tulip is possibly not receiving the changes from update_shapes and hence not taking it into account during submission. I am unsure though whether this was intentional or not: will need more investigation...

Current thinking is that the configuration changes via update_shapes should indeed flow through to shacl-tulip, which means some work is needed.

Picked up in https://hub.psychoinformatics.de/orinoco/shacl-vue/issues/351 > I used update_shapes to change the notation's datatype from xsd:hexBinary to xsd:string (at first, setting it to null caused the field not to be displayed in the UI). This worked fine in the frontend, but the submission still had the xsd:hexBinary literal type included. I think this actually highlights an inconsistency in shacl-vue->shacl-tulip; shacl-tulip is possibly not receiving the changes from update_shapes and hence not taking it into account during submission. I am unsure though whether this was intentional or not: will need more investigation... Current thinking is that the configuration changes via `update_shapes` should indeed flow through to `shacl-tulip`, which means some work is needed.