Conversation
docs pipeline standardization with other SDK repos and minor fixes
…annotation-level first)
`clams-vocabulary` and `pyproject.toml` migration
deprecating fnum-based operations in VDH
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
2 participants
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.
Overview
mmif.vocabularywith fully-fledged pydantic classes inclams-vocabularypackage 2) deprecating framenum-based image extraction functions in VDH (frame numbers are no longer considered as proper timestamps)Additions
pyavandclams-vocabularyas new dependenciesChanges
mmif.vocabularypackage is now a thin wrapper aroundclams-vocabularypackage (clams-vocabularyandpyproject.tomlmigration #381 )AnnotationTypesandDocumentTypesclasses are no longer simple string enums, but pydantic-based validation-supported python classesRemoval
durationTimeUnitis no longer written to video documents'Annotationproperty. This is non-API change hence not triggering major version bump. (based on clamsproject/mmif@a74dc46, all time notations without explicit unit specification are considered as milliseconds)