2023-02-01T02:27:02Z

A unified interface for both source and sink would make either very easy to develop.

Create the file system target as a sink. Have it "request" all of the resources and their variants.

Dorian Taylor

How do we handle the existing file system target?

https://rdf-sak.ibis.makethingsmakesense.com/95bab4f0-5b0d-42b5-a39d-768d1d725234

Make the individual sources manage their own content negotiation.

Make the source tree into a "source".

Model the intervention of RDF::SAK to take representations from a source to a sink.

RDF::SAK (Old Intertwingler)

RDF::SAK is sclerotic and too tightly-coupled to its proximate function as a static website generator.

Several operations need to happen to resource representations between the instant they are retrieved from the source to when they are delivered to the sink.

There is already a word in REST parlance for "source": "origin".

What about content negotiation?

What about running RDF::SAK as a dynamic Web application?

What about the source tree on the file system?