distributed aggregator cache with ipfs

the aggregator could store rendered html/pdf/epub in ipfs. it would be nice if this renderings are referenced in rdf. so create an own rdf index, and keep track of already done renderings:

<ipfs:bafybeia...>
  tg:renderingOf <textgrid:kv2q.0>
  tg:renderedBy aggregator#githash
  tg:styleSheet <textgrid:...> # if used. if internal do not mention, the githash has it
  xsd:date 2025-11-23:19:24

so we may look up in the triplestore, if there is an existing rendering and take this from ipfs. also we have track if renderings change, as the CID changes.

as a frontend we may have /resolve/render or just /render as aggregator frontend which shall take care of this, so e.g.

• /render/html/textgrid:kv2q.0
• /render/text/textgrid:kv2q.0

etc

possibly also

• /render/html/textgrid:kv2q.0/info or
• /render/html/textgrid:kv2q.0?info

to get hold of the above mentioned rdf metadata set about this rendering