You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visualizations may want to use labels for IRI values of observations. A path to the label could be stored in the property shape of the dimension. Besides the path, the available languages should be stored.
If no location for the label is given, optional fallbacks like schema:name or rdfs:label could be defined. The optional could ruin the query performance. Therefore the information about not having a label has some value. It can be described with a location pointing to cube:Undefined like in the following example:
Visualizations may want to use labels for IRI values of observations. A path to the label could be stored in the property shape of the dimension. Besides the path, the available languages should be stored.
Here is an example how it could look like:
The nested structure can be used to share the location of the label like shown in this example:
If no location for the label is given, optional fallbacks like
schema:name
orrdfs:label
could be defined. The optional could ruin the query performance. Therefore the information about not having a label has some value. It can be described with a location pointing tocube:Undefined
like in the following example:The text was updated successfully, but these errors were encountered: