Link between the primary resource and a related resource: use @included?

Hi all,

Just want to know your practice about the following use case.

When a webpage describes a scientific name, we can use the TaxonName 
type and profile.
If we want to refer to a taxon that uses this scientific name either as 
an accepted name or synonym, we need to use properties scientificName or 
alternateScientificName whose subject is the taxon:
taxon -- scientificName --> name
taxon -- alternateScientificName --> name

So, to annotate the page, we must add a new Taxon object. This can be 
done with *@graph* <https://www.w3.org/TR/json-ld/#named-graphs> or 
*@include* <https://www.w3.org/TR/json-ld/#included-nodes>?

My understanding is that they are pretty similar, yet @graph will list 
several possibly disconnected objects such that we don't know what is 
the primary object here, the one that is described in the page.
By contrast, *@included* has allows "to represent a set of resources 
which are used by some other resource. Included blocks may be also be 
used to collect such secondary node objects which can be referenced from 
a primary node object."

So in the end I'm doing this:

     "@type" : "TaxonName",
     "@id": "http://taxref.mnhn.fr/lod/name/60932",
     "name": "Delphinapterus leucas",
     "author": "(Pallas, 1776)",
     "taxonRank": [ "species"   ],
     "*@included*": [{
         "@type" : "Taxon",
"http://purl.org/dc/terms/conformsTo": {
             "@id": "https://bioschemas.org/profiles/Taxon/0.7-DRAFT"
         },
         "@id": "http://taxref.mnhn.fr/lod/taxon/60932",
         "name": "Delphinapterus leucas (Pallas, 1776)",
         "scientificName": { "@id": "http://taxref.mnhn.fr/lod/name/60932" }
     }]

so that the focus of the markup is still aboutthe TaxonName, and the 
Taxon is a secondary object.

Is that correct? Have you done differently?

Thx your your comments and advice.
     Franck.

-- 
Franck MICHEL, CNRS research engineer
Université Côte d’Azur, CNRS, Inria
I3S laboratory (UMR 7271)