How can you possibly not host the images? You csn't count on all your other sources making them available forever; or tomorrow; or at a predictable url.And something has to be canonical or people can (will) post whatever they please for content.
Seems like it's the least effort to put them where you want the and you know where they'll be.
Then it's time to consider whether to include a permalink in the distributed texts. Some readers
would appreciate it (think illustrations, diagrams, tables, ...) and it's not like we're trying to hide anything.
On Mon, Jan 30, 2012 at 7:24 PM, James Adcock
<jimad@msn.com> wrote:
>I propose that for version control purposes, each "work" will have its own
"project." Each project must contain the master file(s) and page scans of
the work. (Would a simple reference to the page scans at IA be sufficient?
Do we need to bust open IA's archive files so each page image can be viewed
individually?)
Are you not now heading in the direction of reinventing DP? If you already
have an existing say "DP"ed work then isn't referencing (or hosting) a
single Djvu or PDF page image file [such as is already hosted at IA] with
indexing sufficient for people to check their [incremental] changes to that
work? If you are going to start resourcing page images ala DP, even those
harvested from IA, then you are adding a ton more work.