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
With the mechanism of link assets, KorAP can also enable the use of URI templates in Kalamar. Similar to values that iframe-plugins can receive to get information about a query, a VC or a match, document URI templates should be filled with values for a certain document and/or match.
Example
A URI template stored per document is data:application/x.korap-link-template;title=OWID-Suche,https://www.owid.de/suche/wort?wort={match/orth:0}. When the link is embedded in the metadata view, the field can be filled by the match information, where {match:orth:0} is replaced by the first orth token of the match. Similar values could be {field:title} where the variable is replaced by the metadata field "title". Annotations may need to be retrieved additionally to fill the templates to make variables like {match:tt/l:0} possible.
The variable names should be accessible in the same way with match-based iframe-plugins. Actually it would be good to have an identical mechanism.
Goal
Simple connection between between KorAP and other linguistic ressources, like DGD, where linkage to passages would require access to token identifier.
The text was updated successfully, but these errors were encountered:
Idea
With the mechanism of link assets, KorAP can also enable the use of URI templates in Kalamar. Similar to values that iframe-plugins can receive to get information about a query, a VC or a match, document URI templates should be filled with values for a certain document and/or match.
Example
A URI template stored per document is
data:application/x.korap-link-template;title=OWID-Suche,https://www.owid.de/suche/wort?wort={match/orth:0}
. When the link is embedded in the metadata view, the field can be filled by the match information, where{match:orth:0}
is replaced by the first orth token of the match. Similar values could be{field:title}
where the variable is replaced by the metadata field "title". Annotations may need to be retrieved additionally to fill the templates to make variables like{match:tt/l:0}
possible.The variable names should be accessible in the same way with match-based iframe-plugins. Actually it would be good to have an identical mechanism.
Goal
Simple connection between between KorAP and other linguistic ressources, like DGD, where linkage to passages would require access to token identifier.
The text was updated successfully, but these errors were encountered: