I am working on serializing partial RDF graphs to JSON-LD using the Jena-Titanium bridge.
Problem: For Titanium to "see" the triples it needs to have a complete copy. See JenaTitanion.convert which copies all Jena triples into a corresponding RdfDatset. This cannot scale if the graph is backed by a database, and we only want to export certain triples (esp for Framing). Titanium's RdfGraph does not provide an incremental function similar to Graph.find() but only returns a complete Java List of all triples. Has anyone here run into the same problem and what would be a solution? I guess one solution would be an incremental algorithm that "walks" a @context and JSON-LD frame document to collect all required Jena triples, producing a sub-graph that can then be sent to Titanium. But the complexity of such an algorithm is similar to having to implement my own JSON-LD engine, which feels like an overkill. Holger
