seeAlso overwrites link to source page

[EnnoMeijers]

If a rdfs:seeAlso link is present in the GraphQL output the 'Bekijk bij bron' button links this seeAlso link in stead of the formal landing page of the URI.

[sdevalk]

I think this is intentional. The seeAlso in GraphQL exposes URIs that point to user-friendly pages (i.e. pages that are friendlier than the formal URIs of the terms). The demonstrator uses/prefers that URI for the 'View at source' button [1].

For example: https://data.rkd.nl/artists/66219 is RKD's formal URI of Rembrandt. It exposes RDF, but not a user-friendly representation. The seeAlso, however, does link to a friendly representation: https://rkd.nl/explore/artists/66219. Similarly, http://vocab.getty.edu/aat/300387675 is AAT's formal URI of the term 'Ionische bekers'. AAT, however, has a friendlier page for human consumption. The seeAlso links to that page: https://www.getty.edu/vow/AATFullDisplay?find=&logic=AND&note=&subjectid=300387675

[1]

network-of-terms-demo/src/components/TermResult.vue

Line 42 in dc0e1fb

:href="term.seeAlso[0] ?? term.uri"

[EnnoMeijers]

I see your point but with some sources the seeAlso could be an alternative representation coming from a different source. To be concrete I am working on a show case for the KOOP TOOI linked data. For example gemeente Alblasserdam has a landing page but there is also an OWMS representation available. For my use case I modelled this as a seeAlso reference.

In the current situation the seeAlso overrules the original term.uri link. In other words currently the seeAlso is limited for use as alternative representation coming form the same source. I think this more restrictive than rdfs:seeAlso is originally intended. I will look into using skos:related for the alternative resource.