Section 5.3 Type Provenance (Record)
source: the last sentence seems to be a duplicate as lineage was mention there as well. Is the intention to have that metadata as DPS as well? If so, that should be mentioned. Also, the question arises what is at the beginning of that source chain? Is there a point where the data was created and therefore, there is no source anymore?origin: Isn't there a dependency between the source and its origin. For example, I could create a data set with the most common baby names in a specific year. Source for that would probably be the statistics departments of the individual countries I include. For the EU, I might end up with 27 sources and 27 origins. How do you then identify which one belongs to which (especially, if they are hosted at a CDN / blob storage)?
Part of CSDPR01 feedback from Thomas Schmidt ( @tschmidtb51 ) received around May 25, 2026 (no email headers available to the editors) and documented in full in issue # 152.
Section 5.3 Type Provenance (Record)
source: the last sentence seems to be a duplicate as lineage was mention there as well. Is the intention to have that metadata as DPS as well? If so, that should be mentioned. Also, the question arises what is at the beginning of that source chain? Is there a point where the data was created and therefore, there is no source anymore?origin: Isn't there a dependency between thesourceand itsorigin. For example, I could create a data set with the most common baby names in a specific year. Source for that would probably be the statistics departments of the individual countries I include. For the EU, I might end up with 27sourcesand 27origins. How do you then identify which one belongs to which (especially, if they are hosted at a CDN / blob storage)?