Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent encoding of DSID/DSED for Base and Update profiles #179

Open
FrankHippmann opened this issue Sep 11, 2024 · 0 comments
Open

Comments

@FrankHippmann
Copy link

FrankHippmann commented Sep 11, 2024

See S-101 Product Specification, s. B-5.1.1.

The S-101 ISO 8211 update profile contains the following guideline for DSID/DSED:

[edition number].[update number] for example 4.20

Specifically, it is mandatory to include the update number within the DSED.

The base profile, however, does not mandate the update number. The guideline is simply:

See clause 11.3.3

Apart from the fact that the encoding of the DSED is inconsistent, it is not possible to apply an update to a base dataset (it may be a reissue - we do not know) if the update number is not specified, unless an exchange set catalogue is present. But there are use cases where an exchange set catalogue may not be present, for instance, during data production and validation. In order to correctly identify a dataset (base or update), the update number needs to be present.

The recommendation is to use the same guideline (comment) for DSID/DSED for the base and update profiles, i.e.:

[edition number].[update number] for example 4.20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant