Data Package is a standard consisting of a set of simple yet extensible specifications to describe datasets, data files and tabular data. It is a data definition language (DDL) and data API that facilitates findability, accessibility, interoperability, and reusability (FAIR) of data.
Note: semantics may vary between publishers — for some this is the datetime the data was created, for others the datetime the package was created.
In my opinion we should have a less dubious definition and have "This" should refer to Data Package. This is in line with the other definitions:
"... who contributed to this Data Package"
"The raw sources for this data package"
"A URL for the home on the web that is related to this data package."
"An image to use for this data package."
So created should be the datetime on which this Data Package was created. It can be generated by any software that creates a Data Package.
Regarding backwards compatibility, I don't think there will be many drawbacks (package will still validate), but a note vs v1 might be good.
"The datetime the data was created" is imo better expressed as a temporal scope, which also allows a start and end date. In Camtrap DP we use Dublin Core's temporal for this: https://camtrap-dp.tdwg.org/metadata/#temporal
Data package
createdis currently defined as:In my opinion we should have a less dubious definition and have "This" should refer to Data Package. This is in line with the other definitions:
So
createdshould be the datetime on which this Data Package was created. It can be generated by any software that creates a Data Package.Regarding backwards compatibility, I don't think there will be many drawbacks (package will still validate), but a note vs v1 might be good.
"The datetime the data was created" is imo better expressed as a temporal scope, which also allows a start and end date. In Camtrap DP we use Dublin Core's
temporalfor this: https://camtrap-dp.tdwg.org/metadata/#temporal