Re: Open eBook Specification

If you have a look at it you will see that it is a mixture of CSS and XHTML.

 I see no problem with using it, but for our purposes I dont see any
particualar advantages over XHTML.

A book XML can also be used for registering the semantics of a book, and
this specification really does not add to XHTML here.

Also I rather like the idea of seperating structure and style. XML can be
'read' by voice browsers and all of the different kinds of media, where as
as far as i can see eBook is chiefly for print media.

Maybe I am wrong, but that was my first take of the specification.

Frank

----- Original Message -----
From: Jonathan Blake <blakej1(at)nevada.edu>
To: <hwg-gutenberg(at)hwg.org>
Sent: Monday, February 07, 2000 4:26 PM
Subject: Open eBook Specification


> Greetings,
>
> Has anyone noticed the Open eBook Specification?
>
>   http://www.openebook.org/
>
> It seems like a well thought out specification written by publishers,
> authors, etc. I haven't had a chance to read all of it, but why should we
> try to create our own document type if there's already something that's
> somewhat mature (work started in October 1998) and crafted by the people
> that should know what structure and information a book document should
> have? If we find something lacking in the specification, we could extend
> it and possibly participate in developing further versions of the
> specification.
>
> --
> Jon
>
> "Semper ubi sub ubi!"
> Loosely translated: No unfurnished basements!
>
>

HWG: hwg-gutenberg mailing list archives, maintained by Webmasters @ IWA