Hi Tim,
At the moment, this is not supported. The logic for the LineageGram generation
is pretty complex and specific. There is no way to configure which properties
it will use.
We will take you input into account for future releases.
> On Mar 12, 2021, at 2:27 PM, Tim Smith wrote:
>
> Hi,
Hi,
When editing an instance with the NeighborGram panel open, when I change
the instance the NeighborGram panel does not reflect the
changes automatically. To see the change, I have to refresh the page or
navigate away from then back to the instance of interest.
Tim
--
You received this
Hi,
Displaying the NeighborGram as a panel vs a tab is great for small
instances (only a few nodes). Anything more complex requires more screen
real-estate than can be obtained with all the other panels open.
Is there a way to choose how NeighborGram opens?
Thanks,
Tim
--
You received this
Hi,
The Lineage view is helpful for the use cases it supports. However, it
would be more useful if I could define what properties are used to create
the path through the graph that is rendered. I find myself trying to do
this manually using the NeighborGram which doesn't work so well.
For
SHACL AF was initially published as the W3C Note. W3C RDF Shapes Working Group
(WG) completed its charter in June 2017. SHACL AF was published as a W3C Note
because the WG ran out of time to complete it and to take it all the way to
Recommendation during the chartered period which is typically
I have been taking advantage of sh:values in my work, but it was recently
pointed out to me that sh:values is not part of either the official SHACL
or SHACL AF. I'm wondering if you have any insight on whether it will be
officially part of SHACL AF any time soon?
(If not, I may need to recode
Thank you so much :) That worked
Br,
Maja
torsdag 26. november 2020 kl. 17:09:53 UTC+1 skrev pdo...@topquadrant.com:
> Maja,
>
> We don't currently allow you to set the 'Prefix separator' to an empty
> string via the UI, but it can be done behind the scenes via SPARQL, which
> will ultimately
