I see. No, we have not yet implemented such complex requirements for
widget selection. You may need to explore your own approach, e.g.
through a SPARQL query.
Holger
On 2021-07-27 7:34 pm, Tomasz Pluskiewicz wrote:
The biggest difference will be not to use dash:viewer at all but have
a rendering component be selected only based on data.
I assume that a simple shape would only declare a property like *[
sh:node hydra:Collection ; sh:property [ sh:path hydra:member ;
sh:node ex:OrderItem ],* and when rendering this path the scoring
could take factor in additional information, such as *sh:path* the
parent shape's *sh:node*.
Which begs the question. Are your implementations often aware of a
broader rendering context? Another such example is actually rendering
the above *ex:OrderItem*, which could be different when rendered
inside a collection's graph, as opposed to being the top resource in a
graph.
Does this make sense?
Tom
poniedziałek, 26 lipca 2021 o 01:15:48 UTC+2 Holger Knublauch napisał(a):
Hi Tom,
I may misread your scenario, but couldn't you just use dash:viewer
and dash:editor to explicitly link from the property shape to the
preferred widget?
http://datashapes.org/forms.html#widgets
<http://datashapes.org/forms.html#widgets>
In that case, the scoring would be bypassed because a value is
already asserted.
Holger
On 2021-07-25 11:08 pm, Tomasz Pluskiewicz wrote:
Hello
Looking as DASH spec, scoring for viewers and editors is mostly
(only?) taking into account the actual property value.
However, I'm considering an implementation (and viewer definition
to match) where the scoring would actually depend on the property
itself. That also would be a multi editor, which make less sense
to score based on the objects.
Specifically, the case is for a `hydra:member` viewer, which
would render all collection members (a table maybe), and its
score assigned based on the `sh:path` of a specific Property Shape...
Are multi viewers implemented in any such way by Top Braid?
Best,
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 topbraid-user...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/fbea53b8-513f-4f28-86e8-d2f7318f1f8cn%40googlegroups.com
<https://groups.google.com/d/msgid/topbraid-users/fbea53b8-513f-4f28-86e8-d2f7318f1f8cn%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 topbraid-users+unsubscr...@googlegroups.com
<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/4a77a900-f4ba-41d3-b715-b25502894081n%40googlegroups.com
<https://groups.google.com/d/msgid/topbraid-users/4a77a900-f4ba-41d3-b715-b25502894081n%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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/ebc0e630-4df9-6150-1fd2-281d929958b7%40topquadrant.com.
