Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TEA’s 2024 REF dictionaries include a Length heading that the strict parser previously rejected. The existing occurrence and column-record contracts now retain it separately as literal publisher_length, while preserving the old serialized shape when no length is supplied. Known length conflicts and contradictory field metadata fail validation; length does not imply a scientific unit or a CSV value-width limit.
Adds two exact public-source HTML fixtures and includes them in source distributions. Existing partial-definition, duplicate-heading, source-anchor and detached-projection contracts remain intact. Builds on #51.
Validation:
Source-family registration, scientific interpretation, data publication and app adoption remain separate work.