Although the ldes:versionKey predicate allows defining which properties to use as a version key, there's an implicit recommendation to use dct:isVersionOf because it's the only one mentioned in the examples.
The Prov-O ontology contains another useful predicate that could be used to link the version object to the main entity: specializationOf. Given how Prov-O is a W3C recommendation, and it might get used to describe projections as well, it may be interesting to consider this one instead of dct:isVersionOf.
We should indeed use it for another example! I don’t have an opinion about using one over the other, I think they can both be used depending on the use case.
Although the
ldes:versionKey
predicate allows defining which properties to use as a version key, there's an implicit recommendation to usedct:isVersionOf
because it's the only one mentioned in the examples.The Prov-O ontology contains another useful predicate that could be used to link the version object to the main entity: specializationOf. Given how Prov-O is a W3C recommendation, and it might get used to describe projections as well, it may be interesting to consider this one instead of
dct:isVersionOf
.