My use case is slightly different than TopBraid. I aim to build a universal form-builder focused on a specific shape. Such as that you would use on web page to create a very specific graph for a HTTP request.
I was initially unsure about the null score and sh:editor requirement but on second thought a dash:InstancesSelectEditor for example would be choses for similar properties indeed. How would you design a shape which can have both ways? * either an instances drop down for existing resources, * or a details editor to create a new one W dniu poniedziałek, 15 czerwca 2020 01:53:30 UTC+2 użytkownik Holger Knublauch napisał: > > Yes, I agree this has been left out for too long. We had nested editor > forms in earlier versions of TopBraid and they were clearly quite necessary. > > I have added them to the dash docs: > http://datashapes.org/forms.html#DetailsEditor > > They are not yet supported by TopBraid tools, but certainly should be in a > future release. So while they will be in the dash namespace (once I upload > it next, later this week), I have marked them dash:hidden in the tosh > namespace, rendering it invisible within TopBraid's Ontology editor. > > For now I gave it 'null' score, which means they would only ever show up > using the dash:editor property. It is quite likely that a policy based on > the presence of sh:node would be better, but then I would only do that for > blank nodes. So something like score=1 if the value node is a blank node > and there is a sh:node constraint? I guess we could iterate on those > details once you have implemented and experimented with them? > > Holger > > > On 12/06/2020 21:42, Tomasz Pluskiewicz wrote: > > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/13ca1bf4-7f08-4dbe-8ee6-d3f5b1d6cedeo%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/13ca1bf4-7f08-4dbe-8ee6-d3f5b1d6cedeo%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- 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/4db3e008-9c7e-4959-9e93-eb35b4e3a3afo%40googlegroups.com.
