Another asymmetry between editor and viewers is the lack of editor
counterpart to "dash:DetailsViewer".
In a case of a nested object I would propose something like
"dash:ShapeEditor" or "dash:DetailsEditor" which would indicate that the
given node should be edited as a SHAPE form.
I could be rendered in various ways:
- directly, as a nested form
- as a link to open an editor separately:
- in a dialog
- by replacing the current form
- in a master-details interface
I expect that a highest score would be given a PropertyShape which
explicitly calls out a suitable "sh:node".
Otherwise, the shape could be chosen by finding appropriate shapes by their
targets:
- "sh:class" matched to "sh:targetClass"
- identifier matched to "sh:targetNode"
- others (I don't know SHACL enough yet)
What do you think?
Tom
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/13ca1bf4-7f08-4dbe-8ee6-d3f5b1d6cedeo%40googlegroups.com.
