Add :embargoDateRange to BIBO (or DCTerms)

[kcoyle]

No suitable property was found for this.

The embargo date range should be used by repositories to avoid issuing a work that is under embargo.
Recommendation:

• Add embargoDateRange to BIBO, unless this is determined to be suitable for DCTerms. (value is EDTF)

[aisaac]

For the record, in Europeana we have reused cc:deprecatedOn from the Creative Commons CCrel vocabulary, for an analogous use case: https://europeana.atlassian.net/wiki/spaces/EF/pages/2291138591/cc+License
I'm ready to accept that this may not address exactly the need of SRAP, of course.
In this case a new property should indeed be added.

If it has to be as simple as stating embargoDateRange directly on a scholarly resource, then adding it in BIBO may be more appropriate. Indeed this feels quite specific a need for DCTerms. More specifically, if a property to meet the use case was to be added to DCTerms, I would rather expect it to be added as a general attribute for setting a validity range of a dcterms:Policy resource (which would be attached to the scholarly resource). But that is probably too convoluted for SRAP at the moment, right?

I hope I'm making sense here.

[kcoyle]

There's also dct:dateAvailable. I'm not sure why the embargo "range" is needed - presumably the resource is not available before the start date, so the end date is what will matter to people. "Embargo" is pretty specific, as @aisaac says.

[philbarker]

Does embargo here relate to the period before which open access to the publication is not allowed [1]. That is, the publication may be available, from the publisher, at a price, but after the embargo period it is available at no cost. If so it would change the discussion around the use of dct:dateAvailble, which does cover the terms under which the resource is available.

1. https://en.wikipedia.org/wiki/Embargo_(academic_publishing)