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
Currently, prefixes are hidden by default in the value part of the attribute-value table. The original intention was to let the user (eventually) hide/show the prefixes through some toggle.
However, now I think it might make the most sense to dynamically display prefixes in that column through a simple rule:
If the value column prefix matches the prefix of the current RDF resource -OR- if it matches the prefix of the attribute column, then it is hidden. This would essentially hide all relations that are part of the same dataset. The colour would be left to make their implicit relation more obvious.
In all other cases, the prefixes will be shown. This will make it clear that we are referencing e.g. cor:kickstarter in the owl:sameAs relation emanating from dn:kickstarter, while removing a tonne of superfluous ontolex: and dn: prefixes from view.
The text was updated successfully, but these errors were encountered:
Currently, prefixes are hidden by default in the value part of the attribute-value table. The original intention was to let the user (eventually) hide/show the prefixes through some toggle.
However, now I think it might make the most sense to dynamically display prefixes in that column through a simple rule:
In all other cases, the prefixes will be shown. This will make it clear that we are referencing e.g.
cor:kickstarter
in theowl:sameAs
relation emanating fromdn:kickstarter
, while removing a tonne of superfluousontolex:
anddn:
prefixes from view.The text was updated successfully, but these errors were encountered: