Consider extending temporal infromation

[roll]

Overview

Currently, there is only package.created while, generally speaking, more temporal information can be associated with data packages and data resources. E.g. see DataCite's date - https://datacite-metadata-schema.readthedocs.io/en/4.5/properties/date/

Also, package.created is limited to exact date-times, which does not work for all use cases (e.g. we cannot do mapping from DataCite's dates)

[peterdesmet]

I actually quite like the simplicity of Data Package's created and have not found a need for date ranges or more date types.

created maps directly with DataCite's <date dateType="Created">2022-08-01</date>.

I find that most of DataCite's dateTypes (like Submitted, Issued, Withdrawn) don't make sense for a standalone Data Package, but only when a Data Package is deposited on a platform (at which point the platform can assign those dates).

---

What I do think that Data Package could suggest is how to express the temporal scope of a dataset (i.e. borrow from Dublin Core). That suggestion was present in v1: https://specs.frictionlessdata.io/data-package/#descriptor, but not in v2.

[roll]

@peterdesmet
I think the problem with package.created currently that it requires full date-time with a timezone (I was going to create an issue/PR regarding it)

PS.
I think the Dublic Core is now in Custom Properties section - https://datapackage.org/specifications/glossary/#custom-properties

[peterdesmet]

Regarding PS, I would then reference "Custom properties" in the Data Package specs: after sources, but with a heading, so it appears in the menu.