W3C home > Mailing lists > Public > public-digipub-ig@w3.org > February 2014

Re: An aside: Some of the TR documents in epub3 (a.k.a. eating our own dog-food:-)

From: Ivan Herman <ivan@w3.org>
Date: Thu, 27 Feb 2014 18:12:52 +0100
Cc: W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-Id: <4B591EDB-3522-4110-A23A-FC1EF78DA758@w3.org>
To: "<Frederick.Hirsch@nokia.com>" <Frederick.Hirsch@nokia.com>

On 27 Feb 2014, at 17:01 , <Frederick.Hirsch@nokia.com> <Frederick.Hirsch@nokia.com> wrote:

> Ivan
> 
> This is a great idea, and even better that you did an implementation. It should be very useful to read a number of specs offline while traveling for example.
> 
> Id like to try this on a set of  specifications for another group Im chairing. It looks like youve written good documentation. If I see any issue I'll do a pull request.

Thanks.

The issue is respec. I actually tried to do some with xmlproc (SPARQL uses that) but, the output of xmlproc is suprisingly 'flat'. And that manifests itself in extracting the TOC. What the tool does is to try to extract the top level TOC for each constituting spec, and compile a merged TOC for the whole book; but if the TOC structure in the spec is messy then, well, this becomes difficult. respec is great for this; I do not know what tools your groups use.

And, of course, all this is still beta release at best:-)

Thanks

ivan

> 
> Thanks
> 
> regards, Frederick
> 
> Frederick Hirsch
> Nokia
> 
> 
> 
> On Feb 27, 2014, at 10:54 AM, ext Ivan Herman <ivan@w3.org> wrote:
> 
>> I had a private project the past few weeks (actually I started a few months ago but I was on and off) to convert official W3C documents to EPUB3 automatically. For an individual document that is not all that interesting (although it does allow off-line usage), but it is great if one has a set of recommendations that belong together, so to say. In such a case a book is actually a collection of specs but can be considered as one.
>> 
>> The tool is pretty mature by now; it does all kinds of nice things like changing possible cross references to references within the book, including all the necessary css files, images, etc, in the book rather than referring to the Web address, etc. We just had a major publication of a new version of RDF a few days ago, and that prompted me to put up a number of such ebooks:
>> 
>> http://www.w3.org/dpub/ebooks/
>> 
>> I think we should definitely use this when we publish WG Notes, eg, latireq or annotation. Many groups have/had alternative formats for their specs and tese are referred to from the document header. In the past, hm, well, ehem, the alternative format was often a PDF file:-( I guess we ought to publish epub3 when the time comes; eating our own dog food...
>> 
>> Ivan
>> 
>> P.S. Needless to say: if you find some issues with those books, please tell me. This is the first time a seriously produce eBooks, looking at the spec and other ebooks...
>> 
>> Disclaimer: Of course, these are _not_ official documents, just a reproduction thereof!
>> 
>> 
>> ----
>> Ivan Herman, W3C 
>> Digital Publishing Activity Lead
>> Home: http://www.w3.org/People/Ivan/
>> mobile: +31-641044153
>> GPG: 0x343F1A3D
>> FOAF: http://www.ivan-herman.net/foaf
>> 
>> 
>> 
>> 
>> 
> 
> 


----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
FOAF: http://www.ivan-herman.net/foaf






Received on Thursday, 27 February 2014 17:13:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:35:48 UTC