On 11 Jun 2015, at 09:15, Ruben Verborgh <ruben.verborgh@ugent.be> wrote:
> Another option is to have a very specific property like "has TPF interface",
> though that might be overly specific then.
Since a resource of the TPF interface needs to be dereferenced in any case in order to interact with it, should an rdfs:seeAlso not cut it? This allows links to other LDF's, like other endpoints (which, according to the 1.1 spec, can also be dereferenced to get the SPARQL Service description).
Probably you'd want to direct your client somehow, so it doesn't have to dereference all rdfs:seeAlso links possible. However, in general, an endpoint wouldn't add other link headers except for the ones that matter...