CLAMS Vocabulary
Python package providing type definitions for the CLAMS platform and MMIF (Multi-Media Interchange Format).
- Documentation: https://clams.ai/vocabulary
- Source: https://github.com/clamsproject/clams-vocabulary
- PyPI: https://pypi.org/project/clams-vocabulary/
Why 1.1.1?
Versions 1.0.0 through 1.1.0 were vocabulary-only releases (no Python package) as part of the MMIF specification. Starting with 1.1.1, the vocabulary is an independent Python package published to PyPI. See CONTRIBUTING.md for details.
License
Metadata
Release files for clams-vocabulary 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| clams_vocabulary-1.2.0.tar.gz | 79.4 kB | Without provenance | Details for clams_vocabulary-1.2.0.tar.gz |
Release files / clams_vocabulary-1.2.0.tar.gz
| Download URL | clams_vocabulary-1.2.0.tar.gz |
|---|---|
| Size | 79.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
acbebf59f17ca493f3106d803cda748ece75afb7e7844736056b895fc6653123
|
|
BLAKE2b-256 checksum How to use checksums |
595dc126b29127d19da955917aab2ebd04b3ba680b6a67d48c3806f1770e56dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.20
|
Security for clams-vocabulary 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.