Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Formats > Other formats

Notices

Reply
 
Thread Tools Search this Thread
Old 05-21-2009, 11:30 AM   #31
pepak
Guru
pepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura about
 
Posts: 610
Karma: 4150
Join Date: Mar 2008
Device: Sony Reader PRS-T3, Kobo Libra H2O
Quote:
Originally Posted by rogue_ronin View Post
if I do this properly, with meta and structure strictly controlled, CSS can do things like change layout such that you reorder the book (at least I think so; wizards please chime in.)
Tim the Enchanter quoth, 'Yes'.
pepak is offline   Reply With Quote
Old 05-21-2009, 11:43 AM   #32
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
I would add: Language and rights to the meta tags. language=en and rights="public domain" (this is the ePUB name for license). There should also be a unique identifier, ISBN or equivalent. id="xxxxx". A personal favorite of mine is the description. This is a short description of the eBook. It is often used by dealer to describe the book and can be viewed in some reader programs before opening the book. The metadata wiki article has some ideas. DublinCore has the official name for terms. You may want to conform.

You might want to make the latest revision machine readable by pulling it out of the comment.

Dale
DaleDe is offline   Reply With Quote
Old 05-21-2009, 11:52 AM   #33
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Quote:
Originally Posted by pepak View Post
A few comments:
- I think you will have trouble with authorfirst/authorlast/illustratorfirst/illustratorlast if a book has multiple authors/illustrators.
I think so too, re: "should they have numbers?" I think I'm trying to predict incompatibilities -- I mean, in my head I'm assuming that a <meta> like "Author" is so common that I need to use it in a "traditional" way. But your idea below--

Quote:
I would combine all info about one author into one meta, then used multiple instances of said meta to describe multiple authors:
Code:
<meta name="author" content="Raymond E. Feist|Feist|Raymond E.|feist@midkemia.com" />
<meta name="author" content="Janny Wurts|Wurts|Janny|" />
--made me think of this:
Code:
<meta name="author" content="Raymond|E.|Feist|" />
<meta name="author" content="Janny||Wurts|" />
<meta name="author" content="T.|K. F.|Weisskopf|" />
Which is stupid-easy to parse for separate values, and if it got read by some meta-utility as a single value, it would still be readable. What do you think? Similar for Illustrator, too, of course.

Twice now you've suggested email addresses. Given what I've suggested above, perhaps a different solution occurs to you? I don't want to put the email in the author slot, although I think it works in the proofer slot because it's so much less important, and not likely to be used for organizing...

Quote:
The classes seem superfluous: Personally, I prefer to use classes only to modify the default structural information. E.g. <h1>, as the "top header", is always used for title, unless class specifies something else. Similarly, <p> is always a common paragraph; I will only add class if I want to specify that it is not a normal paragraph after all.
Yeah, I think you're right -- any class names, or element names above are really just placeholders for now. Just using them to nail down the meta-section pattern. I've laid out some structural elements in a post above -- I'm open to your suggestions.

Quote:
- Not sure what would the navigation buttons be used for.
Look at the my response to pdurrant above -- navigating from place to place in the book. (You can't create links via CSS can you?)

Quote:
You can't [put <div>s in the head.] Even if you could, that would make the metainformation visible, which is not a good thing, IMO.
Right. 'nuff said, no <div>s in the head.

m a r

Last edited by rogue_ronin; 05-21-2009 at 12:24 PM.
rogue_ronin is offline   Reply With Quote
Old 05-21-2009, 12:14 PM   #34
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Quote:
Originally Posted by DaleDe View Post
I would add: Language and rights to the meta tags. language=en and rights="public domain" (this is the ePUB name for license).
Like the language idea. I'll add it. The rights idea -- I have a "copyrightholder" tag already, I could simply use "public domain" as its value.

Quote:
There should also be a unique identifier, ISBN or equivalent. id="xxxxx".
Both "ISBN" and "fileid" are already in the proposal.

Quote:
A personal favorite of mine is the description. This is a short description of the eBook. It is often used by dealer to describe the book and can be viewed in some reader programs before opening the book.
Another good idea. It's in!

Quote:
The metadata wiki article has some ideas. DublinCore has the official name for terms. You may want to conform.
I may. If you know the terms, you could save me some research.

Quote:
You might want to make the latest revision machine readable by pulling it out of the comment.
It's in both places. The commented version is for easy human readable access. Look farther down and you'll see both version number and revision date in the <meta> file section.

m a r
rogue_ronin is offline   Reply With Quote
Old 05-21-2009, 12:51 PM   #35
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Okay, after input from both DaleDe and pepak, here is an updated and rearranged example of a meta-head:

Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>A Princess of Mars</title>

<!-- BEGIN: DOCUMENT HISTORY -->

<!-- Created on 20/May/2004 -->
<!-- Revision # 0.10 on 30/Jun/2004 -->
<!-- Revision # 0.20 on 28/Dec/2004 -->
<!-- Revision # 0.40 on 13/Apr/2005 -->
<!-- Revision # 0.70 on 30/Sep/2006 -->
<!-- Current Revision # 0.80 on 18/May/2009 -->

<!-- END: DOCUMENT HISTORY -->

<!-- BEGIN: REVISION GUIDELINE -->

<!--
   0.10 :: Initial Conversion
   0.20 :: Cover and Frontispiece
   0.30 :: Sections, Chapters and TOC
   0.40 :: Endnotes and/or Blockquotes
   0.50 :: Initial Spellcheck
   0.60 :: M-dashes and Hyphens and Ellipses
   0.70 :: Italics, Bold, and Pre-Formatted Text
   0.80 :: Reading Proof
   0.90 :: Checked Against Canonical Source
   1.00 :: Final Version -- Optimal
 1.00+ :: Minor Error Corrections
-->

<!-- END: REVISION GUIDELINE -->

<!-- BEGIN: EBOOK META INFORMATION -->

<meta name="filename" content="APrincessOfMars" />
<meta name="fileid" content="FoundText0085" />
<meta name="filecreationdate" content="20/May/2004" />
<meta name="fileversion" content="0.80" />
<meta name="filerevisiondate" content="18/May/2009" />
<meta name="filesource" content="University of Virginia Electronic Text Center" />
<meta name="filescanner" content="Judy Boss" />
<meta name="fileproofer" content="Kelly Tetterton" />
<meta name="fileproofer" content="Peter-John Byrnes" />
<meta name="fileproofer" content="Found Text (foundtext@gmail.com)" />

<meta name="title" content="A Princess of Mars" />
<meta name="subtitle" content="Barsoom #01" />
<meta name="series" content="Barsoom" />
<meta name="seriesnumber" content="01" />

<meta name="author" content="Edgar|Rice|Burroughs|" />
<meta name="illustrator" content="Frank||Frazetta|" />

<meta name="genre" content="Science Fiction::General" />
<meta name="isbn" content="" />
<meta name="language" content="en" />
<meta name="description" content="" />

<meta name="publisher" content="Found Text" />
<meta name="publicationdate" content="08/July/2010" />
<meta name="publicationcity" content="Honolulu" />
<meta name="publicationcity" content="Bangkok" />

<meta name="copyrightholder" content="Public Domain" />
<meta name="copyrightdate" content="" />

<!-- END: EBOOK META INFORMATION -->

<!-- BEGIN: STRUCTURE HINTS -->

<!--
<h1> :: Title of book
<h2 class="subtitle"> :: Subtitle of book
<h3 class="chapter"> :: Chapter headings
<p> :: regular paragraph
<p class="epigram"> :: quotation that opens chapters
<em class="psionic"> :: telepathic communication
etc. etc.
-->

<!-- END: STRUCTURE HINTS -->

<!-- BEGIN: MANIFEST -->

<!--
APrincessOfMars.html :: main document, this file
images\cover.png :: cover image, 1-bit, 314x480px
images\arrow_down.png :: chapter navigation down button, 1-bit, 30x30px
images\arrow_up.png :: chapter navigation up button, 1-bit, 30x30px
images\bar.png :: decoration, 1-bit, 150x9px
images\book_plate.png :: series logo, or frontispiece image, 1-bit, 314x224px
images\end_of_book.png :: colophon image, closes book, 1-bit, 250x170px
images\logo.png :: publisher logo, 1-bit, 70x70px
images\return.png :: endnote return button, 1-bit, 40x13px
images\toc.png :: navigation button, links to Table of Contents, 1-bit, 30x30px
sounds\logo.wav :: publisher logo sound, 8 bit, unsigned single channel (mono), 16khz sample rate, 16KB/s
-->

<!-- END: MANIFEST -->

</head>
rogue_ronin is offline   Reply With Quote
Old 05-21-2009, 02:36 PM   #36
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
copyright holder is slightly different I think especially for creative commons licenses. Here is the location of the dublin core specifications. This is currently used in ePUB and earlier forms of this documentation. http://dublincore.org/
As I mentioned there is also metadata as a topic in our wiki.

Dale
DaleDe is offline   Reply With Quote
Old 05-22-2009, 03:53 AM   #37
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Quote:
Originally Posted by DaleDe View Post
copyright holder is slightly different I think especially for creative commons licenses. Here is the location of the dublin core specifications. This is currently used in ePUB and earlier forms of this documentation. http://dublincore.org/
As I mentioned there is also metadata as a topic in our wiki.

Dale
I looked a the metadata page on the wiki. But the DublinCore stuff is way to involved to scan: and it's focused on XML. I'm trying to keep it simple...

And I want to be careful not to try and re-create ePub here.

Still, there are a few things from the wiki that are worth discussing:

keywords: effectively tags. Worth adding?

comments: Not sure that I need to do this, but I'm open to argument.

identifier: the main issue is, should I rename "fileid" to "identifier"? Can't think of a good reason -- identifier seems too abstract.

editor: might add this -- it's not from the wiki, exactly, but is mentioned in the "creator/contributor" section. Creator and contributor seem too general to me, but I'm open to arguments.

subject: isn't genre enough? Also, I should maybe show y'all the genre list I found and use. It's really more like a subject list.

date: I'm thinking maybe it should be yyyy/mmm/dd, but not yyyy/mm/dd -- the numbers are confusing, but 3-letter code for months is optimal.

rights: I'm not sure about this. Open Source, Public Domain, Creative Commons -- and what do you put for something under copyright? Is there anything else?

m a r
rogue_ronin is offline   Reply With Quote
Old 05-22-2009, 04:29 AM   #38
gwynevans
Wizzard
gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.
 
gwynevans's Avatar
 
Posts: 1,402
Karma: 2000000
Join Date: Nov 2007
Location: UK
Device: iPad 2, iPhone 6s, Kindle Voyage & Kindle PaperWhite
Quote:
Originally Posted by rogue_ronin View Post
date: I'm thinking maybe it should be yyyy/mmm/dd, but not yyyy/mm/dd -- the numbers are confusing, but 3-letter code for months is optimal.
[FX: Raises eyebrow] Optimal? [/FX]

I think you'd be better off going with the yyyy-mm-dd format of the ISO 8601 standard.

One of the problems you'll have with mmm is Locale - for example, in French, the first three letters of June and July are both 'jui' (juin and juillet)!
gwynevans is offline   Reply With Quote
Old 05-22-2009, 04:44 AM   #39
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Quote:
Originally Posted by gwynevans View Post
[FX: Raises eyebrow] Optimal? [/FX]
[FX: shrugs, hangs head in shame][SFX: plaintive flute]Bad use of word. "Preferable to my limited sensibilities" is more accurate.[/SFX][/FX]

Quote:
I think you'd be better off going with the yyyy-mm-dd format of the ISO 8601 standard.

One of the problems you'll have with mmm is Locale - for example, in French, the first three letters of June and July are both 'jui' (juin and juillet)!
I surrender to you, to pepak, to the wiki, to ePub, to wikipedia, to ISO 8601 etc. I'll switch it to yyyy/mm/dd.

[SFX: Thrilling Horns signal a Flourish!][/SFX]



m a r
rogue_ronin is offline   Reply With Quote
Old 05-22-2009, 06:49 AM   #40
pepak
Guru
pepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura about
 
Posts: 610
Karma: 4150
Join Date: Mar 2008
Device: Sony Reader PRS-T3, Kobo Libra H2O
We won! Yahooo!!!! :-)
pepak is offline   Reply With Quote
Old 05-22-2009, 11:23 PM   #41
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
And I thought I was done with meta!

Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>A Princess of Mars</title>

<!-- BEGIN: FILE HISTORY -->

<!-- Created on 2004/05/20 -->
<!-- Revision # 0.10 on 2004/06/30 -->
<!-- Revision # 0.20 on 2004/12/28 -->
<!-- Revision # 0.40 on 2005/04/13 -->
<!-- Revision # 0.70 on 2006/09/30 -->
<!-- Current Revision # 0.80 on 2009/05/18 -->

<!-- END: FILE HISTORY -->

<!-- BEGIN: REVISION GUIDELINE -->

<!--
0.10 :: Initial Conversion
0.20 :: Cover and Frontispiece
0.30 :: Sections, Chapters and TOC
0.40 :: Endnotes and/or Blockquotes
0.50 :: Initial Spellcheck
0.60 :: M-dashes and Hyphens and Ellipses
0.70 :: Italics, Bold, and Pre-Formatted Text
0.80 :: Reading Proof
0.90 :: Checked Against Canonical Source
1.00 :: Final Version -- Optimal
1.++ :: Minor Error Corrections
-->

<!-- END: REVISION GUIDELINE -->

<!-- BEGIN: EBOOK META INFORMATION -->

<meta name="filename" content="APrincessOfMars" />
<meta name="fileid" content="FoundText0085" />
<meta name="filecreationdate" content="2004/05/20" />
<meta name="fileversion" content="0.80" />
<meta name="filerevisiondate" content="2009/05/18" />
<meta name="filesource" content="University of Virginia Electronic Text Center" />
<meta name="filescanner" content="Judy Boss" />
<meta name="fileproofer" content="Kelly Tetterton" />
<meta name="fileproofer" content="Peter-John Byrnes" />
<meta name="fileproofer" content="Found Text (foundtext@gmail.com)" />
<meta name="filecomment" content="This file has been proofed by reading, but not checked against a paper source.  Wikipedia has a nice article about this title. FOUND TEXT RAWX!!1!" />

<meta name="title" content="A Princess of Mars" />
<meta name="subtitle" content="Barsoom #01" />
<meta name="series" content="Barsoom" />
<meta name="seriesnumber" content="01" />

<meta name="author" content="Edgar|Rice|Burroughs|" />
<meta name="illustrator" content="Frank|E.|Schoonover" />
<meta name="editor" content="Newell|Metcalf" />

<meta name="genre" content="Science Fiction::General" />
<meta name="isbn" content="" />
<meta name="language" content="en" />
<meta name="description" content="" />
<meta name="keywords" content="Mars, classics, swords, planetary romance" />

<meta name="publisher" content="Found Text" />
<meta name="publicationdate" content="2010/07/08" />
<meta name="publicationcity" content="Honolulu" />
<meta name="publicationcity" content="Bangkok" />

<meta name="copyrightholder" content="" />
<meta name="copyrightdate" content="" />
<meta name="copyrightlicense" content="Public Domain" />

<!-- END: EBOOK META INFORMATION -->

<!-- BEGIN: STRUCTURE HINTS -->

<!--
<h1> :: Title of book
<h2 class="subtitle"> :: Subtitle of book
<h3 class="chapter"> :: Chapter headings
<p> :: regular paragraph
<p class="epigram"> :: quotation that opens chapters
<em class="psionic"> :: telepathic communication
etc. etc.
-->

<!-- END: STRUCTURE HINTS -->

<!-- BEGIN: MANIFEST -->

<!--
APrincessOfMars.html :: main document, this file
images\cover.png :: cover image, 1-bit, 314x480px
images\arrow_down.png :: chapter navigation down button, 1-bit, 30x30px
images\arrow_up.png :: chapter navigation up button, 1-bit, 30x30px
images\bar.png :: decoration, 1-bit, 150x9px
images\book_plate.png :: series logo, or frontispiece image, 1-bit, 314x224px
images\end_of_book.png :: colophon image, closes book, 1-bit, 250x170px
images\logo.png :: publisher logo, 1-bit, 70x70px
images\return.png :: endnote return button, 1-bit, 40x13px
images\toc.png :: navigation button, links to Table of Contents, 1-bit, 30x30px
sounds\logo.wav :: publisher logo sound, 8 bit, unsigned single channel (mono), 16khz sample rate, 16KB/s
-->

<!-- END: MANIFEST -->

</head>
Changes!

Renamed DOCUMENT HISTORY to FILE HISTORY for consistency.

keywords: added as "keywords" in the book-itself-info section. I imagine it would be useful for search, assuming it doesn't repeat things in the other tags.

comments: added as "filecomments". I guess there could be something important to know. Or folks could use it to brag.

identifier: staying with "fileid" -- which should be a reasonable attempt at a unique ID.

editor: added, using same format as "author" and "illustrator", so multiple editors are possible.

subject: staying with simply "genre", at least for now.

date: switched all to yyyy/mm/dd. And there was much rejoicing!

rights: Added it, as "copyrightlicense": I can see where it might be useful. "Open Source", "Public Domain", "Creative Commons", "CopyLeft" -- What do you put for something under copyright? "Closed" or "Private" or "Commercial"? Is there any other license?

If you think of anything else let me know. I'm still looking for a good idea about email addresses that doesn't "pollute" the name entries. How about a single "contact" entry?

Anyone want my assembled list of genres?

m a r
rogue_ronin is offline   Reply With Quote
Old 05-24-2009, 01:08 AM   #42
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Book Structure...

This is what I'm thinking...

It took a while, and I'm probably still missing things and making mistakes. I first over-used the "id" attribute. I think I pruned it pretty well, and only used classes where necessary, and at the highest levels I could.

Anything in ALL CAPS is a value determined by your naming convention or content needs. Hope you're not confused by the outline: I thought it best to name what I'm working on...

Code:
   1. Cover
	<div class="Spine" id="Cover">
		<a href="#START_OF_BOOK ID">
			<img src="images/cover.png" />
		</a>
	</div>

   2. Frontispiece
	<div class="Spine" id="Frontispiece">
		<h2>TITLE/SERIES NAME</h2>
		<ul>
			<li>SERIES LIST TITLES</li>
		</ul>
		<img src="images/frontispiece.png" />
	</div>

   3. Front Matter
	<div class="Spine" id="FrontMatter">
		<h2>FRONT MATTER HEADING</h2>
		<p>FRONT MATTER CONTENT (BLURBS, JUNK, ADS, WHATEVER)</p>
	</div>

   4. Title Page
	<div class="Spine" id="TitlePage">
		<h1>TITLE</h1>
		<p id="Subtitle">SUBTITLE</p>
		<p id="Author">AUTHOR</p>
		<p id="Illustrator">ILLUSTRATOR</p>
	</div>

   5. Verso
	<div class="Spine" id="Verso">
		<h2>VERSO HEADING</h2>
		<a href="sounds/logo.wav">
			<img src="images/logo.png">
		</a>
		<p id="PublisherBlurb">PUBLISHER BLURB</p>
		<p id="VersionNumber">VERSION NUMBER</p>
		<p id="RevisionDate">REVISION DATE</p>
		<p id="OriginalSource">ORIGINAL SOURCE</p>
		<p id="Scanner">SCANNER</p>
		<p id="Proofer">PROOFER(S)</p>
	</div>

   6. Inscription
	<div class="Spine" id="Inscription">
		<h2>INSCRIPTION HEADING</h2>
		<p>INSCRIPTION CONTENT</p>
	</div>

   7. Acknowledgment
	<div class="Spine" id="Acknowledgment">
		<h2>ACKNOWLEDGMENT HEADING</h2>
		<p>ACKNOWLEDGMENT CONTENT</p>
	</div>

   8. Preface
	<div class="Spine" id="Preface">
		<h2>PREFACE HEADING</h2>
		<p>PREFACE CONTENT</p>
	</div>

   9. Table of Illustrations
	<div class="Spine" id="TableOfIllustrations">
		<h2>TABLE OF ILLUSTRATIONS HEADING</h2>
		<ul>
			<li>
				<a href="#ILLUSTRATION ID">ILLUSTRATION NAME</a>
			</li>
		</ul>
	</div>

  10. Table of Maps
	<div class="Spine" id="TableOfMaps">
		<h2>TABLE OF MAPS HEADING</h2>
		<ul>
			<li>
				<a href="#MAP ID">MAP NAME</a>
			</li>
		</ul>
	</div>

  11.  Table of Tables
	<div class="Spine" id="TableOfTables">
		<h2>TABLE OF TABLES HEADING</h2>
		<ul>
			<li>
				<a href="#TABLE ID">TABLE NAME</a>
			</li>
		</ul>
	</div>

  12. Table of Contents
	<div class="Spine" id="TableOfContents">
		<h2>TABLE OF CONTENTS HEADING</h2>
		<ul>
			<li>
				<a href="#CONTENT ID">CONTENT NAME</a>
			</li>
		</ul>
	</div>

  13. Introduction
	<div class="Spine" id="Introduction">
		<h2>INTRODUCTION HEADING</h2>
		<p>INTRODUCTION CONTENT</p>
	</div>


  14. Parts
	<div class="Spine" id="PART ID">
		<h2>PART HEADING</h2>
		<p>PART BLURB<p>
	</div>

    A. Prologue
		<div class="Body" id="Prologue">
			<h3>PROLOGUE HEADING</h3>
			<ul class="NavLinks"
				<li>
					<a href="#PREVIOUS CHAPTER ID">
						<img src="images/up.png" />
					</a>
				</li>
				<li>
					<a href="#TableOfContents">
						<img src="images/toc.png" />
					</a>
				</li>
				<li>
					<a href="#NEXT CHAPTER ID">
						<img src="images/down.png" />
					</a>
				</li>
			</ul>
			<h4>SECTION HEADING</h4>
			<h5>SUBSECTION HEADING</h5>
			<p class="Epigram">EPIGRAM</p>
			<p class="PullQuote">PULL QUOTE</p>
			<p>APPENDIX CONTENT</p>
			<p class="SceneBreak">&nbsp;</p>
			<img id="MAP ID" class="Map" src="images/MAPNAME.EXT" />
			<img id="ILLUSTRATION ID" class="Illustration" src="images/ILLUSTRATIONNAME.EXT" />
			<table id="TABLE ID">TABLE CONTENTS</table>
			<a id="LINK-TO-ENDNOTE ID" class="EndNoteLink" href="END NOTE ID">LINK-TO-ENDNOTE NAME</a>
		</div>

    B. Chapters
		<div class="Body" id="CHAPTER ID">
			<h3>CHAPTER HEADING</h3>
			<ul class="NavLinks"
				<li>
					<a href="#PREVIOUS CHAPTER ID">
						<img src="images/up.png" />
					</a>
				</li>
				<li>
					<a href="#TableOfContents">
						<img src="images/toc.png" />
					</a>
				</li>
				<li>
					<a href="#NEXT CHAPTER ID">
						<img src="images/down.png" />
					</a>
				</li>
			</ul>
			<h4>SECTION HEADING</h4>
			<h5>SUBSECTION HEADING</h5>
			<p class="Epigram">EPIGRAM</p>
			<p class="PullQuote">PULL QUOTE</p>
			<p>APPENDIX CONTENT</p>
			<p class="SceneBreak">&nbsp;</p>
			<img id="MAP ID" class="Map" src="images/MAPNAME.EXT" />
			<img id="ILLUSTRATION ID" class="Illustration" src="images/ILLUSTRATIONNAME.EXT" />
			<table id="TABLE ID">TABLE CONTENTS</table>
			<a id="LINK-TO-ENDNOTE ID" class="EndNoteLink" href="END NOTE ID">LINK-TO-ENDNOTE NAME</a>
		</div>

    C. Epilogue
		<div class="Body" id="Epilogue">
			<h3>EPILOGUE HEADING</h3>
			<ul class="NavLinks"
				<li>
					<a href="#PREVIOUS CHAPTER ID">
						<img src="images/up.png" />
					</a>
				</li>
				<li>
					<a href="#TableOfContents">
						<img src="images/toc.png" />
					</a>
				</li>
				<li>
					<a href="#NEXT CHAPTER ID">
						<img src="images/down.png" />
					</a>
				</li>
			</ul>
			<h4>SECTION HEADING</h4>
			<h5>SUBSECTION HEADING</h5>
			<p class="Epigram">EPIGRAM</p>
			<p class="PullQuote">PULL QUOTE</p>
			<p>APPENDIX CONTENT</p>
			<p class="SceneBreak">&nbsp;</p>
			<img id="MAP ID" class="Map" src="images/MAPNAME.EXT" />
			<img id="ILLUSTRATION ID" class="Illustration" src="images/ILLUSTRATIONNAME.EXT" />
			<table id="TABLE ID">TABLE CONTENTS</table>
			<a id="LINK-TO-ENDNOTE ID" class="EndNoteLink" href="END NOTE ID">LINK-TO-ENDNOTE NAME</a>
		</div>

    D. Appendices
		<div class="Body" id="APPENDIX ID">
			<h3>APPENDIX HEADING</h3>
			<ul class="NavLinks"
				<li>
					<a href="#PREVIOUS CHAPTER ID">
						<img src="images/up.png" />
					</a>
				</li>
				<li>
					<a href="#TableOfContents">
						<img src="images/toc.png" />
					</a>
				</li>
				<li>
					<a href="#NEXT CHAPTER ID">
						<img src="images/down.png" />
					</a>
				</li>
			</ul>
			<h4>SECTION HEADING</h4>
			<h5>SUBSECTION HEADING</h5>
			<p class="Epigram">EPIGRAM</p>
			<p class="PullQuote">PULL QUOTE</p>
			<p>APPENDIX CONTENT</p>
			<p class="SceneBreak">&nbsp;</p>
			<img id="MAP ID" class="Map" src="images/MAPNAME.EXT" />
			<img id="ILLUSTRATION ID" class="Illustration" src="images/ILLUSTRATIONNAME.EXT" />
			<table id="TABLE ID">TABLE CONTENTS</table>
			<a id="LINK-TO-ENDNOTE ID" class="EndNoteLink" href="END NOTE ID">LINK-TO-ENDNOTE NAME</a>
		</div>
   

  15. Afterword
	<div class="Spine" id="Afterword">
		<h2>AFTERWORD HEADING</h2>
		<p>AFTERWORD CONTENT<p>
	</div>

  16. About the Author Page
	<div class="Spine" id="AboutTheAuthor">
		<h2>ABOUT THE AUTHOR HEADING</h2>
		<p>ABOUT THE AUTHOR CONTENT<p>
		<img id="ILLUSTRATION ID" class="Illustration" src="images/author.png" />
	</div>

  17. Colophon
	<div class="Spine" id="Colophon">
		<h2>COLOPHON HEADING</h2>
		<p>COLOPHON CONTENT<p>
		<a href="Cover">
			<img src="images/colophon.png" />
		</a>
	</div>

  18. Endnotes
	<div class="Spine" id="Endnotes">
		<h2>ENDNOTES HEADING</h2>
		<p id="END NOTE ID">
			ENDNOTE CONTENT
			<a class="BackLink" href="LINK-TO-ENDNOTE ID">
				<img src="images/return.png" />
			</a>
		<p>
	</div>

  19. Glossary
	<div class="Spine" id="Glossary">
		<h2>GLOSSARY HEADING</h2>
		<p>GLOSSARY CONTENT<p>
	</div>

  20. Index
	<div class="Spine" id="Index">
		<h2>INDEX HEADING</h2>
		<p>INDEX CONTENT<p>
	</div>

  21. End Matter
	<div class="Spine" id="EndMatter">
		<h2>END MATTER HEADING</h2>
		<p>END MATTER CONTENT (BLURBS, JUNK, ADS, WHATEVER)<p>
	</div>
Nothing in this is required exactly. (For instance, I cannot think of an example of an Inscription header. So just don't use it.) And CONTENT can include anything, right? But if something needs to explicitly be moved, let me know.

I moved Appendices under Parts; I just thought that it made sense -- formatting in an Appendix would likely be similar to a Chapter, and they seem to me to be of equivalent "rank".

How'd I do?

m a r
rogue_ronin is offline   Reply With Quote
Old 05-25-2009, 11:56 AM   #43
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
You may want to check the wiki on genre and add some of your favorites with explanation if they are missing.

Dale
DaleDe is offline   Reply With Quote
Old 05-25-2009, 01:36 PM   #44
gwynevans
Wizzard
gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.
 
gwynevans's Avatar
 
Posts: 1,402
Karma: 2000000
Join Date: Nov 2007
Location: UK
Device: iPad 2, iPhone 6s, Kindle Voyage & Kindle PaperWhite
Quote:
Originally Posted by rogue_ronin View Post
date: switched all to yyyy/mm/dd. And there was much rejoicing!
While it's your choice, I feel that I need to flag the fact that if you intended the date to be the ISO 8601 standard format, those date-element seperators should be hyphens (or not present)...
gwynevans is offline   Reply With Quote
Old 05-25-2009, 09:07 PM   #45
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
@gwynevans: I'll switch the format. I didn't read the spec, just relying on good advice here.

@dalede: I already have a list of genres, scavenged from the BISAC Subject Headings. I expect that they cannot be posted on the wiki.

Anyone have comments on the structure and tag choices?

m a r
rogue_ronin is offline   Reply With Quote
Reply

Tags
html, library, meta, structure, xhtml

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Any ongoing work on the epub specification? b.tarde ePub 10 03-18-2010 08:33 PM
ePub and top margin specification tompe Upload Help 6 01-02-2010 11:24 AM
Ask about specification bthoven PocketBook 35 11-13-2009 12:33 PM
BeBook 2 Specification keng2000 BeBook 6 11-02-2009 01:17 PM
PRS-500 lrf file specification Dave Berk Sony Reader Dev Corner 2 05-01-2007 02:12 AM


All times are GMT -4. The time now is 09:29 PM.


MobileRead.com is a privately owned, operated and funded community.