humfrey
humfrey is a Django-based RESTful linked data interface to a SPARQL endpoint.
Features
Serialization to HTML, RDF, JSON, CSV.
Template selection based on rdf:types.
Semantic pingback
SPARQL rate-limiting
Using
humfrey provides a lot of the framework you need for producing a linked data site. You will need to produce a minimal Django project to pull it all together. Examples include data.ox.ac.uk, data.clarosnet.org, and opencitations.net. In due course we plan to provide a simple demonstration site that will run out of the box.
It requires a backing SPARQL endpoint to run queries against. The sites listed above use Fuseki, but it should work with any endpoint. If it doesn’t, raise an issue in the GitHub issue tracker.
You will also need running memcached and redis instances.
Running the test suite
In the root of the humfrey module run:
PYTHONPATH=.. python manage.py test --settings=humfrey.tests.settings
If using Jenkins, you can use tox or run the following:
PYTHONPATH=.. python manage.py jenkins --settings=humfrey.tests.settings
This will produce a bunch of reports using django_jenkins, which will turn up in a reports directory.
Requirements
memcached
redis
Metadata
Release files for humfrey 0.3.9
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 |
|---|---|---|---|---|
| humfrey-0.3.9.tar.gz | 136.8 kB | Without provenance | Details for humfrey-0.3.9.tar.gz |
Release files / humfrey-0.3.9.tar.gz
| Download URL | humfrey-0.3.9.tar.gz |
|---|---|
| Size | 136.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2c653f11af6dd08578770dc95c4995dbbd2cd6a04ce7a6481f3269b885186d7
|
|
BLAKE2b-256 checksum How to use checksums |
142bbb92164a1aac9de075b9ce341d59940f49d4015943dc0a9099bfc50667f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for humfrey 0.3.9
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.