Include titanium-rdfc in report

[vorburger]

Prompted by filip26/ld-cli#71,

and vaguely related to enola-dev/enola#1103,

perhaps someone would like to add https://github.com/filip26/titanium-rdfc,

to https://w3c.github.io/rdf-canon/reports/ ?

@filip26

[filip26]

Pasting an explanation from here: eclipse-rdf4j/rdf4j#5255 (comment)

Thank you for mentioning Titanium RDFC. The library was originally a fork of RDF-URDNA but diverged to align with W3C RDF-CANON, to quickly adapt to requirements such as exposing the blank node label map, and incorporating the latest Titanium JSON-LD updates. Over time, it has evolved into a standalone library.

The latest version, 2.0, which I’m currently working on, introduces RdfConsumer, a new interface designed to minimize the need for transport object creation (which is expensive in Java) and enable stream-like processing.

The next version, should depend on an artifact like titanium-rdf-api (or something similar), which will be extracted from titanium-json-ld, making it possible to depend only on this library instead of the entire titanium-json-ld.

The test suite and much of the codebase still originate from the RDF-URDNA fork. Given that there are already Java libraries for this in the report, I hesitate to add another one -perhaps when version 2.0 is released.

FYI: Planned improvements - feedback is very welcome!
See JSON-LD to RDF example
RDFConsumer interface proposal

[gkellogg]

We can add Titanium RDFC to the implementation report, it just requires someone to submit an EARL report showing the conformance. Instructions for doing this are detailed in the report.