It should be noted that dct:references, defined as "A related resource that is referenced, cited, or otherwise pointed to by the described resource", is a subproperty of dct:relation, defined as "A related resource". Given that the issue is formulated very generally as " link to related resources", it seems that dct:relation would be the better solution.

+1 

this is also how this information requirement is modelled in ADMS. 

https://joinup.ec.europa.eu/asset/adms/home 

ADMS has several ways of expressing relations:

Relevant for this issue:

1. dct:relation for (unspecified) relationships between Assets (which are by defeinion Datasets)

2. wdrs:describedBy for a reference to the "main documentation or specification of the Asset"

3. foaf:page for a reference to "documentation that contains information related to the Asset"

We could use the same approach: dct:relation for a link to related Datasets, foaf:page for related documentation.

[] foaf:page void:DatasetDescription is discussed at MO2, so more details from my side there. 

DCAT, in contrast to VOID, keeps the Dataset/Distribution description details at the dcat:Dataset and dcat:Distribution classes level, instead of having a specialized class as void:DatasetDescription.

In order not to variate from what DCAT recommends, we could stick to inline descriptions and add dct:relation directly to the dcat:Dataset and/or dcat:Distribution?