Use case: linksets to non-RDF targets

[GoogleCodeExporter]

A use case mentioned on the list by Alasdair Gray.

They have linksets that don't link to another RDF dataset, but to a set of web 
pages. Example: Each gene might have an associated web page on some biomedical 
database site (which is exposed only as HTML).

Linksets currently assume that both "ends" of the link are RDF datasets. The 
assumption would have to be relaxed for void:Linkset to be appropriate here.

Original issue reported on code.google.com by richard....@gmail.com on 23 Mar 2013 at 8:15

[rob-metalinkage]

Another angle on this - let us imagine a world where content-negotiation may be used to get the RDF, or HTML, or other representation of a resource. Would it be valid to use a Linkset in these cases whre RDF may be available at some point in the future? If not, then you'd need to develop a best practice for migrating or reconciling an alternative (lets call it a CrossRefSet for arguments sake) with a Linkset in the future when a RDF encoding is available for the given URIs.

Maybe this can be done using polymorphism - simply declare it a void:Linkset in addition to document that RDF is now available. Or, maybe you simply get explicit using TechnicalFeature and dcterms:hasFormat from the outset, and let the user decide how a Linkset can be exploited based on its technical features.