Begining with resources and their representations in or as files, on a variety of filesystems, on a variety of media, we want, in ascending order…
- A graph describing the files (e.g. path, location, dates, mime types) and resources (URIs) for which they provide a representation
- A static Apache HTTPD config generated from the graph to serve the files (or redirects) from resource URIs
- …
- Some webserver implementation to generate a variety (file, styled, contexted, with navigation, etc.) of resource representations
- …
- An evolving system (organic flexibility, feedback, community contributions, etc.)
Let's see, what to do for level one…
- Figure out the look of the graph model
- Find existing libraries to crawl an extract metadata from a filesystem
- First dump to a monolithic file, then think about a repository and automated consistancy (the graph is often a cache of the facts contains in the filesystem)
- Code