BIG dctap2shacl Custom Parser
Code repository for the BIBFRAME InterOp Group's custom DCTap-to-SHACL parser.
Command Line Usage
After installing, convert one or more BIBFRAME DCTap files to a SHACL validation graph from the command:
- If installed with uv,
uv run dctap2shacl --dctap admin_metadata.tsv - If installed with pip,
dctap2shacl --dctap admin_metadata.tsv
This will create and save a turtle file, bf-validation.ttl in the same directory.
Options
-h,--helpDisplays help-i,--dctapOne or more DCTap files, seperated by commas-o,--shaclOptional, file name for the validation graph-fmt,--formatOptional, RDF serialization format, can be one of the following:turtle: Turtle (default)xmlorpretty-xml: XMLjson-ld: JSON Linked Data formatnt: N-triples
DCTap Column Support
Alternative properties
Two ways of saying "either of these properties satisfies the constraint", both of
which generate a sh:or list on the node shape:
- Same
valueNodeType— list the properties semi-colon separated in a singlepropertyIDcell. Every branch shares that one row's constraints. - Different
valueNodeType(e.g. one expects a literal and the other an IRI) — give each property its own row and name the alternative in ansh:orcolumn. Each branch keeps the constraints of its own row, so the literal and IRI alternatives can differ invalueNodeType,valueShape, and so on.
The sh:or column is normally filled in reciprocally, each row naming the other,
and the paired rows do not have to be adjacent. Alternatives are matched within a
single shapeID, so paired rows must agree on their shapeID. If an sh:or
names a property that has no row of its own, that alternative is emitted with
only its sh:path.
valueNodeType
valueNodeType maps to sh:nodeKind. Multiple types are semi-colon separated
(IRI ; bnode), and bnode may also be written blank node or blankNode.
valueNodeType |
sh:nodeKind |
|---|---|
literal |
sh:Literal |
IRI |
sh:IRI |
bnode |
sh:BlankNode |
IRI ; bnode |
sh:BlankNodeOrIRI |
IRI ; literal |
sh:IRIOrLiteral |
bnode ; literal |
sh:BlankNodeOrLiteral |
An empty, unrecognized, or fully unconstrained (all three types) cell produces no
sh:nodeKind.
Metadata
Release files for dctap2shacl 0.3.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 |
|---|---|---|---|---|
| dctap2shacl-0.3.0.tar.gz | 9.4 kB | Without provenance | Details for dctap2shacl-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dctap2shacl-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for dctap2shacl-0.3.0-py3-none-any.whl |
Total release size: 16.8 kB
Release files / dctap2shacl-0.3.0.tar.gz
| Download URL | dctap2shacl-0.3.0.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4e57ed96907f8ac6184279929f33d56edf06f522798c231708e8dc4d7afb762
|
|
BLAKE2b-256 checksum How to use checksums |
998d7e569ea1a25edd3928fa76259660dd86ca1cf371e363e9509e77c606e206
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / dctap2shacl-0.3.0-py3-none-any.whl
| Download URL | dctap2shacl-0.3.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ad24653480a77c74597ed37250faec73d68e3df94405fad95ce0a23b5c9260f
|
|
BLAKE2b-256 checksum How to use checksums |
381e52130b28bb718437e3e3415b39880824cea240039b54e4a38f97a17b325c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for dctap2shacl 0.3.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.