repoze.annotea README
repoze.annotea implements the server side of the W3C Annotea specification for RDF-based annotations on content, using repoze.bfg as the underlying framework for the application.
Please see docs/index.rst for the documentation.
repoze.annotea Changelog
0.1 (2008-11-30)
Initial release.
1 maintainer
Metadata
1 maintainer
Release files for repoze.annotea 0.1
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 | |
|---|---|---|---|---|
| repoze.annotea-0.1.tar.gz | 26.8 kB | Without provenance | Details |
Release files / repoze.annotea-0.1.tar.gz
| Download URL | repoze.annotea-0.1.tar.gz |
|---|---|
| Size | 26.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9cfa0b11729429ee748eccd3702effccccc94f82fb134ba12545e9afc1d3b8c
|
|
BLAKE2b-256 checksum How to use checksums |
d4a4963eb0bd38242dc0d99bdeb3b0f61dfef57dfa9d2a49c6b68fa017f26ad5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for repoze.annotea 0.1
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.
