Do we need the inverse of dcat:prev - i.e., dcat:next?

[andrea-perego]

Issue originally raised in #1308 (comment) by @agreiner :

[...] it just occurred to me that next/previous has the same issue for developers as we encountered with membership in a series, that developers won't know in advance which one is being used to hold the chain together and so would have to test for both in code. Also, assigning next when a dataset is first published seems like a stretch, so we again run into the problem of updating the metadata after the fact. Yet, having next when it's available would certainly be useful. I sort of want to make previous required but both encouraged, or say you can't use next without also using previous.

[andrea-perego]

This issue has been addressed via PR #1391 by moving inverse properties to a dedicated section, and by requiring that they are all used in addition to the "default" ones (e.g., dcat:next can only be used in addition to dcat:prev).

Closing.