- From: Henry Story <henry.story@bblfish.net>
- Date: Fri, 4 May 2018 19:10:00 +0200
- To: Stian Soiland-Reyes <soiland-reyes@manchester.ac.uk>
- Cc: Semantic Web IG <semantic-web@w3.org>, Ivan Herman <ivan@w3.org>
I found a project called WebPub which links to W3C activity that started recently https://w3c.github.io/dpub-pwp-ucr/ it has an implementation which is just the right thing for moving between ePub and the web. https://github.com/HadrienGardeur/webpub-manifest which seems to be a json-ld file. It also has code to try it out. I have not yet built the manifest to try it out. Is this on the right track? I'd be happy to try it out, for my paper "Epistemology in the Cloud" http://bblfish.net/blog/2018/04/21/ Henry > On 4 May 2018, at 16:14, Stian Soiland-Reyes <soiland-reyes@manchester.ac.uk> wrote: > > On Tue, 1 May 2018 17:52:53 +0100, Henry Story <henry.story@bblfish.net> wrote: >>> I can't annotate or share inner URIs like >>> file:///run/user/1000/gvfs/archive:host=file%25253A%25252F%25252F%25252Ftmp%25252Fmozilla_stain0%25252FEpistemology%25252520In%25252520The%25252520Cloud.epub/OPS/chapter-1.xhtml >>> (puh) >> Does it help if I unzip it? >> http://bblfish.net/blog/2018/04/21/epub/ >> At least that makes for dereferenceable URLs (and allows people here to inspect that epub >> online to better follow your points below. > > > Yay! > > So just one extra step, and then the inner ePub document is on the web, > linkable, archievable and everything. > > This is why re-use of standards is > generally a good thing - ePub didn't have to use HTML, they could have > used XML (JATS?) or their own thing. > > >> So perhaps to get started all one would need is is little epub js viewer that could fetch >> the unzipped files and show them? > > Yes, the only tricky bit after unzipping is to find the "index" (the > base-names could vary based on and embed some links for navigation > between chapters. > > (users should not have to navigate Apache folders or inspect > container.xml manually) > > But that is out of scope for this list :) -- the previously mentioned > W3C web publishing efforts might have more on that. > > >> It seems like one could immediately then use the web annotation model. > > Yes, as long as the js is run from the individual chapter HTML files, > not as easy for annotators to find the right identifiers if it's a > single epubview.html that loads dynamically the other HTML files into > the DOM. > > > -- > Stian Soiland-Reyes > The University of Manchester > http://www.esciencelab.org.uk/ > http://orcid.org/0000-0001-9842-9718 >
Received on Friday, 4 May 2018 17:10:29 UTC