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
There is this problem that there are columns in the input file which are bound to one specific column which is a key of the dataset. In UBD66 this is the SitePlot one. Currently this is simply shown as the unique key for this column.
After talking to BAFU I had to add the remaining columns in a way that we can query them as well. For that I did two things:
SitePlot is now a skos:Concept and it points to additional "pseudo-dimensions" via skos:narrower. Each of this dimensions is again a skos:Concept and contains a skos:prefLabel.
Each pseudo-dimension is also its own skos:Concept and to this definition I attached a qb:order so we can figure out which one should be shown first.
There is this problem that there are columns in the input file which are bound to one specific column which is a
key
of the dataset. In UBD66 this is theSitePlot
one. Currently this is simply shown as the unique key for this column.After talking to BAFU I had to add the remaining columns in a way that we can query them as well. For that I did two things:
skos:Concept
and it points to additional "pseudo-dimensions" viaskos:narrower
. Each of this dimensions is again askos:Concept
and contains askos:prefLabel
.skos:Concept
and to this definition I attached aqb:order
so we can figure out which one should be shown first.Example:
skos:narrower
Altitude
qb:order
I hope the idea is clear, if not please let me know.
The text was updated successfully, but these errors were encountered: