solution to respecting dash:hidden of skos elements in tagger panel

[Simon Opper]

Hi all

In a tagset I want to hide certain skos resources , primarily conceptschemes, but it appears that the code that renders the tagger panel does not respect dash:hidden in all cases.

It looks there are two behaviours occurring:

1. if the scheme is declared as hidden in the included source taxonomy -> it is hidden in the tagger panel

2. if the scheme is declared hidden in the tagset graph -> the panel does not respect this and still shows the scheme.

Is this intended ?

behaviour 1. does not give me the desired solution as I wish to hide certain schemes only in the tagset and I do not want to declare it as hidden in the source taxonomy.

is there a workaround ? 

Many thanks in advance

Cheers

Simon

[Holger Knublauch]

Hi Simon,

I think the behavior that you describe works as-designed. The tag set graph is only supposed to contain the mappings, while the display of the tags queries the taxonomy only and therefore won't see any dash:hidden triples that you may have "smuggled" into the tag set graph. (Pro tip: you can actually see which graph the Add Tags panel queries if you look at the Network monitor of Chrome's dev tools - that's not the union of all graphs).

The only solution that I see is to create another intermediate Taxonomy that includes/owl:imports the original Taxonomy but adds the dash:hidden triples that you need here. Such an intermediate/proxy taxonomy could potentially be auto-generated.

Holger

--
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/ea405382-79ec-4ccc-95bd-336d362d8346n%40googlegroups.com.

[Simon Opper]

Thanks Holger

All good Re the design of the tagger. Makes sense.

Regarding the auto-generated proxy taxonomy you mentioned, we utilise proxying graph loading methods now too. In our process, I would configure a new "managed graph" via our manifest loader that proxies the global taxonomy in a new taxonomy that stores the dash hidden triples as you also suggest. This would require the additional graph management setup in our method which is fine but I wonder if you mean there is another in-built or sparql/dash/swp EDG method?

If you're envisaged process uses a different mechanism it would be good to know more.  

Cheers mate

Simon 

[Holger Knublauch]

On 2021-11-18 9:54 am, Simon Opper wrote:

Thanks Holger

All good Re the design of the tagger. Makes sense.

Regarding the auto-generated proxy taxonomy you mentioned, we utilise proxying graph loading methods now too. In our process, I would configure a new "managed graph" via our manifest loader that proxies the global taxonomy in a new taxonomy that stores the dash hidden triples as you also suggest. This would require the additional graph management setup in our method which is fine but I wonder if you mean there is another in-built or sparql/dash/swp EDG method?

No, we don't have anything automated for that.

Cheers
Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/b942ac7f-754d-4880-9519-aa9df0d3a5f1n%40googlegroups.com.