update validation to current state

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: ce8e63ee9e6c39d7f4a9cfe2c75a83836832cbb6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Rdataflow]

@giacomociti would it make sense to update and simplify the validation steps - WDYT? - I like two step validation as you mention it in the docs (and the rest is done by the magic of profiles) ... so I wonder: might it be worth to mention them here?

[giacomociti]

I approved the PR, your changes make sense to me @Rdataflow. But I'm not sure I get what you mean with updating the validation steps

[Rdataflow]

@giacomociti the validation steps currently in this spec

• The cube structure and contents
• The structure of the observations
• The integrity of the constraints

... while in the barnard59 cube docs there occur only two (because recently validation was simplified using the newly established code:imports functionality)

• check-metadata
• check-observations

therefore my question is whether it makes sense to you to adapt the validation steps validation of this spec to match those two from barnard59 documentation?

ps: this might be by summarizing point 1 and 3