Hydra-RDF
hydra-rdf is the translingual RDF support package for Hydra. It is generated into
Haskell, Java, Python, and TypeScript from a common set of DSL sources, and depends only on hydra-kernel.
For background on how Hydra relates to RDF and SHACL, see the RDF wiki page.
What it provides
- RDF 1.1 syntax model — IRIs, literals, blank nodes, triples, graphs, datasets.
- SHACL syntax model and coder — maps Hydra types to SHACL shapes and Hydra terms to RDF descriptions (the data triples that conform to those shapes).
- OWL 2 syntax model — full coverage of OWL 2 classes, properties, individuals, and axioms. Syntax only; there is no OWL coder yet.
- ShEx syntax model.
- XML Schema syntax model.
- N-Triples serializer (
rdfGraphToNtriples) — the only output format currently supported. Reading (parsing) of any RDF format is not yet supported. - Eclipse RDF4j overlay (
hydra.rdf.overlay.java.SerdeNative) — a host-native Java integration that serializes Hydra RDF graphs (hydra.rdf.syntax.*) via RDF4j's Rio writers (and supports the reverse). Hand-written, host-specific code: it lives underoverlay/java/hydra-rdf/and is copied onto the generated distribution at assembly time (#511; formerly the separatebindings/java/hydra-rdf4jartifact). Its third-party dependency (org.eclipse.rdf4j:rdf4j-rio-ntriples) is declared inoverlay/java/hydra-rdf/build.json.
Demos
Three demos exercise this package end-to-end:
- demos/shacl — generates SHACL shapes from the Hydra kernel types, encodes kernel modules as N-Triples, and validates the data against the shapes.
- demos/avro — bidirectional Avro coder; the included AvroWorkflows tool transforms Avro-schema'd JSON data into SHACL RDF.
- demos/genpg — generates a property graph from relational CSV data and emits it as either GraphSON or RDF/SHACL N-Triples.
N-Triples output
The serializer follows the N-Triples 1.1 specification.
Literals preserve all Unicode verbatim and escape only ", \, LF, and CR. IRIs emit any
of the spec-disallowed characters (controls and <>"{}|^\) as \uXXXXUCHAR escapes; all other code points pass through. Earlier versions replaced any non-ASCII character with?`; that bug was fixed in #363.
Metadata
Release files for hydra-rdf 0.18.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 |
|---|---|---|---|---|
| hydra_rdf-0.18.0.tar.gz | 56.8 kB | Without provenance | Details for hydra_rdf-0.18.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hydra_rdf-0.18.0-py3-none-any.whl | Python 3 | none | any | Details for hydra_rdf-0.18.0-py3-none-any.whl |
Total release size: 114.0 kB
Release files / hydra_rdf-0.18.0.tar.gz
| Download URL | hydra_rdf-0.18.0.tar.gz |
|---|---|
| Size | 56.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a64eaa26f3f4a36ae9407e27e6f151afa5d2276a20c05d2c6c94d75008d2617
|
|
BLAKE2b-256 checksum How to use checksums |
e3c847d08ea5959e73ed27ec5404dfa0367a489447f88dd2fb2fd8838bf8b557
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.8
|
Release files / hydra_rdf-0.18.0-py3-none-any.whl
| Download URL | hydra_rdf-0.18.0-py3-none-any.whl |
|---|---|
| Size | 57.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec8e2dedd244f548f54f0eb5a0c3af7e47aa9a2e407191821054e4bcb08193f1
|
|
BLAKE2b-256 checksum How to use checksums |
1158e7c21fab8b4f486225573de8b804d3932be24d3e002135fedfb3a740d29d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.8
|
Security for hydra-rdf 0.18.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.