Localized multi-viewer

[Tomasz Pluskiewicz]

I would like to propose a new localized literal viewer which would be a multi viewer, always rendering only a single literal.

Something like dash:LabelViewer but for any property, and obviously not rendering a link.

Do you think it's a worthy addition to DASH vocab?

Tom

[Holger Knublauch]

Hi Tom,

I assume you mean the case where people only want to see values in a single language, e.g. English - correct me if I am wrong.

We have encountered this requirement several times and in TopBraid EDG have a global user option to only show values in the preferred language(s). Each user then can decide on this, and also revert back to seeing all values when needed. Note that some users have set their browsers to prefer multiple languages, so there it doesn't always need to be a single value. For example think about Switzerland or Canada.

Do you have use cases where you would want this "flag" to be active for individual properties only, but not all? Asking because in that case a global option is probably preferred to hard-coding this in the property shapes.

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/7c5acb70-86d0-4af8-91d1-1864f8787852n%40googlegroups.com.

[Tomek Pluskiewicz]

I think it’s slightly different, in a scenario a little unlike TopBraid.

Imagine a web page, where a resource is displayed. I might want to render an rdfs:label as a <h2>. I would never want multiple. Only one, using the preferred language. Browsers have a list of languages, and the first match would be used. Others ignored.

I think your remark is on point. In a typical web page rendered like that, most text properties would in fact be displayed this way, only selecting the one in a given language. Similarly, I will have a use case for displaying measurements and a similar multi-viewer could be defined in my project to select metric or imperial depending on user preference.

A global setting is thus a sensible thing to explore but I’m not sure how practical it might be in terms of automatically choosing those viewers. Maybe on per-predicate basis?

Tom

You received this message because you are subscribed to a topic in the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/topbraid-users/IAdThnSHfYY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/67a3f6af-dda5-21db-8d73-1fcb06b7988c%40topquadrant.com.

[Holger Knublauch]

On 2021-08-13 7:42 pm, Tomek Pluskiewicz wrote:

I think it’s slightly different, in a scenario a little unlike TopBraid.

Imagine a web page, where a resource is displayed. I might want to render an rdfs:label as a <h2>. I would never want multiple. Only one, using the preferred language. Browsers have a list of languages, and the first match would be used. Others ignored.

I think your remark is on point. In a typical web page rendered like that, most text properties would in fact be displayed this way, only selecting the one in a given language. Similarly, I will have a use case for displaying measurements and a similar multi-viewer could be defined in my project to select metric or imperial depending on user preference.

A global setting is thus a sensible thing to explore but I’m not sure how practical it might be in terms of automatically choosing those viewers. Maybe on per-predicate basis?

Maybe if one of the sh:datatypes is rdf:langString? That should clearly identify those.

Holger