Would be useful to have that optionally have that info as columns in the grouping tables, to check for integrity of the links. THe idea is that these create a unique ID for each HDU.
In CTAO we also define a DATA_ID header that is a UUID generated by the data preparer when the data product is created that we can use that to ensure the file is the one we expect, even if it's path changed or the file was renamed. But maybe that is beyond what is needed for VODF.
Would be useful to have that optionally have that info as columns in the grouping tables, to check for integrity of the links. THe idea is that these create a unique ID for each HDU.
In CTAO we also define a
DATA_IDheader that is a UUID generated by the data preparer when the data product is created that we can use that to ensure the file is the one we expect, even if it's path changed or the file was renamed. But maybe that is beyond what is needed for VODF.