Implement an rdf command for converting into JSON-LD

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: This PR introduces a new jsonschema rdf CLI command that promotes a valid JSON/YAML instance into JSON-LD using x-jsonld-* schema annotations.

Changes:

• Added rdf command wiring (CMake + command dispatch + CLI help) and linked the JSON-LD core library
• Implemented src/command_rdf.cc to compile schemas with JSON-LD annotation collection and emit expanded JSON-LD, with optional flattening/compaction
• Refactored schema bundling/framing/compilation error handling into shared helpers in src/utils.h, and reused them from validate
• Extended error printing to include document JSON Pointer locations where available
• Updated shell completions (bash/zsh) and README/docs to expose the new command
• Added a comprehensive RDF test suite covering success cases, stdin/YAML inputs, and failure/error-reporting scenarios

Technical Notes: The rdf command enforces a 2019-09+ base dialect (annotation collection requirement) and maps JSON-LD context/compaction errors into consistent CLI exit codes and error formats.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[cubic-dev-ai]

3 issues found across 86 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="test/rdf/fail_compact_context_invalid_json.sh">

<violation number="1" location="test/rdf/fail_compact_context_invalid_json.sh:27">
P3: Each test run should capture **both** stdout and stderr so the unused stream is verified empty. In the text-variant run (line 27–29), stderr is captured but stdout is not; if an accidental log line or summary reaches stdout, the test won't catch it. In the JSON-variant run (line 39–42), stdout with `--json` is captured but stderr is not; text leaking to stderr alongside the JSON output would go undetected. Recommendation: redirect the unused stream to a separate file and assert it is empty, or use a helper that captures both.</violation>
</file>

<file name="test/rdf/pass_keyword_type.sh">

<violation number="1" location="test/rdf/pass_keyword_type.sh:33">
P1: The expected `@type` array has the IRIs in reverse order compared to the schema's `x-jsonld-type`. The schema specifies `["https://schema.org/Person", "https://schema.org/Agent"]` (Person first), but the expected output lists Agent first. The implementation in `vendor/blaze/src/output/output_jsonld.cc` preserves insertion order via `push_back` without sorting, so this test will fail on `diff`.</violation>
</file>

<file name="test/rdf/pass_keyword_container_index.sh">

<violation number="1" location="test/rdf/pass_keyword_container_index.sh:18">
P1: Expected output silently drops the object keys ("a", "b") which should be preserved as `@index` values per `@container: @index` semantics. In JSON-LD, `@container: @index` means the keys of the source object map to `@index` properties on each entry — analogous to how `@language` maps keys to `@language` in `pass_keyword_container_language.sh`. Without the `@index` field, the output loses the identity of each indexed entry.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>