Skip to content

jsonschema: Add JSF (JSON Signature Format) support - #136

Open
JPEWdev wants to merge 7 commits into
mainfrom
jsf
Open

jsonschema: Add JSF (JSON Signature Format) support#136
JPEWdev wants to merge 7 commits into
mainfrom
jsf

Conversation

@JPEWdev

@JPEWdev JPEWdev commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Adds support for JSF signatures to the JSON schema by allowing the JSF property in the top level of the document.

@JPEWdev
JPEWdev marked this pull request as draft August 4, 2026 19:39
@JPEWdev
JPEWdev requested a review from bact August 4, 2026 19:39
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

Coverage report

Click to see where and how coverage changed

FileStatementsMissingCoverageCoverage
(new stmts)
Lines missing
  src/shacl2code
  main.py
  model.py
Project Total  

This report was generated by python-coverage-comment-action

@bact bact added the enhancement New feature or request label Aug 5, 2026
@JPEWdev
JPEWdev marked this pull request as ready for review August 12, 2026 22:12
@JPEWdev
JPEWdev force-pushed the jsf branch 2 times, most recently from 3167123 to d48ad6b Compare August 13, 2026 01:46
@bact bact added this to the 1.3.0 milestone Aug 13, 2026
Adds support for JSF signatures by allowing the provided signature
property in the top level of the document, and in all the code bindings.
Implements the context checks that are present in the other language
bindings in python as well
Implements the same class resolution logic as is present in the other
language bindings.
It is useful to have the line numbers in the jinja file line up with the
line numbers in the generated file as much as possible (at least until
the block at then end with all the generated classes). Rework the way
the version information is generated by Jinja to make sure this is the
case.
Implements tracking the path for validation errors, and also raising
custom exceptions that capture the path. This matches the other bindings
and also helps when debugging errors
Unknown properties (in extensible classes) should still be valid IRIs.
Test should be added to enforce that they are not blank nodes and that
context is correctly expanded.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants