http://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=HOWCOMEMicroformats Wiki - User contributions [en]2026-04-30T01:44:04ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=book-brainstorming&diff=66682book-brainstorming2018-02-21T08:57:14Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat. Many of the class names proposes are suitable for other forms of extended prose, such as articles and longer notes.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
The scope of the term "book" has no clear limits when applied to texts made public on the Internet. It is therefore the case that many of the class names here can be used for any presentation of extended prose, including those which will never appear in print. In particular, articles can have tables of contents, lists of figures, appendices, glossaries, references, bibliographies among other shared parts. It is likely that the continued shift in publishing to online forms will blur the distinctions re-enforced by physical manifestations so this microformat encourages reuse in all suitable situations.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents [[User:Sfsheath|Sfsheath]] 20:33, 13 September 2010 (UTC) why is this abbreviated. 'tableofcontents' is more clear. [[User:HOWCOME|HOWCOME]] 08:57, 21 February 2018 (UTC) 'TOC' in an established, if cryptic, term in the publishing world<br />
<tr><td>lot <td>List of Tables [[User:Sfsheath|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoftables' is more clear.<br />
<tr><td>lof <td>List of Figures [[User:Sfsheath|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoffigures' is more clear.<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>catalog <td>The section of a book listing discrete, similarly structured descriptive entries.<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books have all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following baseline markup is proposed:<br />
<br />
:<code><nowiki><div class="figure">...<p class="caption">...</div></nowiki></code><br />
<br />
In addition, figures can be given additional class names:<br />
<br />
<table border><br />
<tr><th>Class name<th>Description<br />
<br />
<tr><td>wide<td>The figure is wide and that it may need to intrude into margins<br />
<tr><td>flex<td>The figure is anchored at a certain position, but the presentation of the figure may occur in a nearby place. For example, the figure may be floated to the top of the page. Using this class can make typesetting easier and is recommended unless the figure needs to be placed exactly where it appears in the markup.<br />
</table><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</nowiki></div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=31682book-brainstorming2007-07-03T18:04:03Z<p>HOWCOME: /* Figures */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following baseline markup is proposed:<br />
<br />
:<code><nowiki><div class="figure">...<p class="caption">...</div></nowiki></code><br />
<br />
In addition, figures can be given additional class names:<br />
<br />
<table border><br />
<tr><th>Class name<th>Description<br />
<br />
<tr><td>wide<td>The figure is wide and that it may need to intrude into margins<br />
<tr><td>flex<td>The figure is anchored at a certain position, but the presentation of the figure may occur in a nearby place. For example, the figure may be floated to the top of the page. Using this class can make typesetting easier and is recommended unless the figure needs to be placed exactly where it appears in the markup.<br />
</table><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</nowiki></div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=18114book-brainstorming2007-07-03T18:03:24Z<p>HOWCOME: /* Figures */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following baseline markup is proposed:<br />
<br />
:<code><nowiki><div class="figure">...<p class="caption">...</div></nowiki></code><br />
<br />
In addition, figures can be given additional class names:<br />
<br />
<table border><br />
<tr><th>Name<th>Meaning<br />
<br />
<tr><td>wide<td>The figure is wide and that it may need to intrude into margins<br />
<tr><td>flex<td>The figure is anchored at a certain position, but the presentation of the figure may occur in a nearby place. For example, the figure may be floated to the top of the page. Using this class can make typesetting easier and is recommended unless the figure needs to be placed exactly where it appears in the markup.<br />
</table><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</nowiki></div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=18113book-brainstorming2007-07-03T17:54:53Z<p>HOWCOME: /* Figures */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following baseline markup is proposed:<br />
<br />
:<code><nowiki><div class="figure">...<p class="caption">...</div></nowiki></code><br />
<br />
In addition, figures can be given additional class names:<br />
<br />
<table border><br />
<tr><th>Name<th>Meaning<br />
<br />
<tr><td>wide<td>The figure is wide and that it may need to intrude into margins<br />
<tr><td>anchored<td>The figure is anchored at a certain positino, but the presentation of the figure may occur in a nearby place. For example, the figure may be floated to the top of the page.<br />
</table><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</nowiki></div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=18112book-brainstorming2007-07-03T17:47:23Z<p>HOWCOME: /* Figures */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following categories are proposed<br />
<br />
<br />
<br />
:<code><nowiki><div class="figure">...<p class="caption">...</div></nowiki></code><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</nowiki></div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=18111book-brainstorming2007-07-03T17:46:23Z<p>HOWCOME: /* Figures */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following categories are proposed<br />
<br />
<br />
<br />
:<code><nowiki><div class="figure">...<p class="caption">...</div><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</nowiki></div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=18110book-brainstorming2007-07-03T17:44:27Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following categories are proposed<br />
<br />
<br />
<div class="figure wide narrow anchored"><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=18109book-brainstorming2007-07-03T17:43:50Z<p>HOWCOME: /* Figures */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form blobs that cannot be split over several pages. By classifying figures into different categories, typesetting can be made easier. The following categories are proposed<br />
<br />
<br />
<div class="figure wide narrow anchored"><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=18108book-brainstorming2007-07-03T17:41:24Z<p>HOWCOME: Adding initial section on figures</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal of HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In boom, the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Figures ==<br />
<br />
Figures are often used in book. From a typesetting persepctive, figures are troublesome as they form big blobs that cannot easily be split over several pages. By classifying figures into different categories, typeseeting can be made easier. The following categories are proposed<br />
<br />
<div class="figure wide narrow anchored"><br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vocabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in practice. The boom microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=journal-formats&diff=32765journal-formats2007-02-07T23:22:15Z<p>HOWCOME: added link to NLM</p>
<hr />
<div>= Journal Formats =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
<br />
<br />
== Introduction ==<br />
<br />
This page lists and discusses formats for journal publishing.<br />
<br />
== Formats ==<br />
<br />
* [http://docbook.org/ DocBook]<br />
* [http://dtd.nlm.nih.gov/ NLM]<br />
<br />
== NLM ==<br />
<br />
[http://xml.coverpages.org/nlmXML.html NLM]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=journal-formats&diff=13381journal-formats2007-02-07T23:20:57Z<p>HOWCOME: added list of formats</p>
<hr />
<div>= Journal Formats =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
<br />
<br />
== Introduction ==<br />
<br />
This page lists and discusses formats for journal publishing.<br />
<br />
== Formats ==<br />
<br />
* [http://docbook.org/ DocBook]<br />
* [http://dtd.nlm.nih.gov/ NLM]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=journal-formats&diff=13380journal-formats2007-02-07T23:18:23Z<p>HOWCOME: created page on journal formats</p>
<hr />
<div>= Journal Formats =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
<br />
<br />
== Introduction ==<br />
<br />
This page lists and discusses formats for journal publishing.</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=journal-brainstorming&diff=32764journal-brainstorming2007-02-07T23:16:51Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Journal Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
<br />
<br />
== Introduction ==<br />
<br />
This page discusses various thoughts and strawman proposals for a journal microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML was developed in a scientific community to help researchers exchange information. However, HTML does not provide any special support for publishing scientific papers. Several [[journal-formats | XML-based formats]] offer a vocabulary of elements to publishers of scholarly journals.</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=journal-brainstorming&diff=13378journal-brainstorming2007-02-07T23:16:38Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Journal Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
<br />
<br />
== Introduction ==<br />
<br />
This page discusses various thoughts and strawman proposals for a journal microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML was developed in a scientific community to help researchers exchange information. However, HTML does not provide any special support for publishing scientific papers. Several [[journal-formats XML-based formats]] offer a vocabulary of elements to publishers of scholarly journals.</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=journal-brainstorming&diff=13377journal-brainstorming2007-02-07T23:15:02Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Journal Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
<br />
<br />
== Introduction ==<br />
<br />
This page discusses various thoughts and strawman proposals for a journal microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML was developed in a scientific community to help researchers exchange information. However, HTML does not provide any special support for publishing scientific papers. Several XML-based formats offer a vocabulary of elements to publishers of scholarly journals.</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=journal-brainstorming&diff=13376journal-brainstorming2007-02-07T23:13:45Z<p>HOWCOME: started page on journal publishing</p>
<hr />
<div>= Journal Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
<br />
<br />
== Introduction ==<br />
<br />
This page discusses various thoughts and strawman proposals for a journal microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML was developed in a scientific community to help researchers exchange information. However, HTML does not provide any special support for publishing scientific papers. Should a microformat be developed for this purpose?</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=13436book-brainstorming2007-02-07T09:25:16Z<p>HOWCOME: /* Comparison with DocBook */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vovabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in pracice. The [[boom]] microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table border><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-formats&diff=23811book-formats2007-02-06T22:07:21Z<p>HOWCOME: adding link to home page</p>
<hr />
<div>= Book Formats =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/ Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Examples of data foramts used for electronic books, with a preference to formats used for publishing books on the Web.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Formats ==<br />
<br />
* [http://docbook.org/ DocBook]<br />
* [http://www.tei-c.org/ TEI]<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-brainstorming]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=13365book-brainstorming2007-02-06T22:05:27Z<p>HOWCOME: added introduction, corrected some text</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/articles/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors.<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>introduction <td>An introductory chapter<br />
<tr><td>chapter <td>The content itself is typically organized in numbered chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vovabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in pracice. The [[boom]] microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>introduction <td>not defined<br />
<tr><td>chapter <td>chapter<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resulting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]<br />
* [http://ocoins.info/ OCoins]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-examples&diff=6344book-examples2006-02-05T20:15:11Z<p>HOWCOME: added link to home page</p>
<hr />
<div>= Book Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Examples of books that people actually publish on the Web. This is focused predominantly on the books themselves rather than references to books. For references to books, see the [[cite-examples]] page and related pages.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
* Books by MarkPilgrim: [http://diveintopython.org/toc/index.html Dive Into Python], [http://diveintogreasemonkey.org/toc/ Dive Into Greasemonkey], and arguably [http://feedparser.org/docs/ Feed Parser Documentation]. All of these are produced with a similar toolchain (DocBook XML to HTML via XSLT).<br />
* [http://www.gutenberg.org/dirs/1/3/132/132.txt Art of War from Project Gutenberg]<br />
<br />
== See Also ==<br />
<br />
* [[book-formats]]<br />
* [[book-brainstorming]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=8678book-brainstorming2006-02-05T20:14:18Z<p>HOWCOME: expanded on the uchapter</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters (e.g., an introduction or an overview of the chapters) thar are formatted similar to chapters, except for the numbering<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vovabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in pracice. The [[boom]] microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>chapter <td>chapter<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction, that are formatted similar to chapters.<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resuliting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing having a series of subclassed "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4770book-brainstorming2006-01-30T18:04:27Z<p>HOWCOME: /* Are there enough sections? */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters (e.g., an introduction) thar are formatted similar to chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Other features of a book ==<br />
<br />
Sections types provide a vovabulary for classifying different parts, pages, of a book. Book authors will also need to classify smaller elements, e.g.:<br />
<br />
* sidenotes<br />
* footnotes<br />
* different kinds of tables: small, multi-page ...<br />
* table captions<br />
<br />
HTML has defined the semantics of table captions through the "caption" element. Alas, the quality of deployed browsers is variable and this makes it hard to use the "caption" element in pracice. The [[boom]] microformat proposes class names for this to go around widely deployed bugs.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>chapter <td>chapter<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction, that are formatted similar to chapters.<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resuliting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing having a series of subclassed "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4547book-brainstorming2006-01-30T17:59:08Z<p>HOWCOME: /* Comparison with DocBook */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters (e.g., an introduction) thar are formatted similar to chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>chapter <td>chapter<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction, that are formatted similar to chapters.<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resuliting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
This underlines a difference between HTML and some other SGML/XML formats: in HTML, content is presented roughly in the same order as it appears in the structure. Other formats, e.g. DocBook, often require a transformation stage where content is moved from abstract elements (e.g., "info") to more concrete elements (e.g., the front and back covers).<br />
<br />
HTML does not have the more abstract elements (although "meta" could possibly be used) and subclassing having a series of subclassed "div" elements in the order of presentation is therefore a pragmatic approach.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4546book-brainstorming2006-01-30T17:53:42Z<p>HOWCOME: /* Comparison with DocBook */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters (e.g., an introduction) thar are formatted similar to chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>DocBook element<br />
<tr><td>frontcover <td>not defined, <br />
<tr><td>halftitlepage<td>not defined<br />
<tr><td>titlepage <td>not defined<br />
<tr><td>imprint <td>not defined<br />
<tr><td>dedication <td>dedication<br />
<tr><td>inspiration <td>not defined<br />
<tr><td>foreword <td>not defined, "preface" is recommended<br />
<tr><td>preface <td>preface<br />
<tr><td>toc <td>toc<br />
<tr><td>lot <td>lot<br />
<tr><td>lof <td>not defined, "lot" is recommended<br />
<tr><td>chapter <td>chapter<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction, that are formatted similar to chapters.<br />
<tr><td>part <td>part<br />
<tr><td>afterword <td>not defined<br />
<tr><td>references <td>reference (not the singular form)<br />
<tr><td>appendix <td>appendix<br />
<tr><td>bibliography <td>bibliography<br />
<tr><td>glossary <td>glossary<br />
<tr><td>index <td>index<br />
<tr><td>colophon <td>colophon<br />
<tr><td>promotion <td>not defined<br />
<tr><td>backcover <td>not defined<br />
</table><br />
<br />
Although DocBook doesn't have elements for all section types, it is still possible for these sections to appear in the resuliting publication. For example, an XSLT processor can add a title page in the printed output based on information in DocBook's "author" element.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4545book-brainstorming2006-01-30T17:49:10Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters (e.g., an introduction) thar are formatted similar to chapters<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>bibliography <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4544book-brainstorming2006-01-30T17:40:08Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have a separate "acknowledgements" section instead of using the "preface" section for this. Also, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. <br />
<br />
However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4543book-brainstorming2006-01-30T17:37:19Z<p>HOWCOME: /* Comparison with DocBook */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Comparison with DocBook ==<br />
<br />
DocBook [http://www.docbook.org/ docbook] is an SGML/XML vocabulary which is been developed for "books and papers about computer hardware and software", but it can also be used for other kinds of books. DocBook is a complex specification; it contains around [http://www.docbook.org/tdg5/en/html/pt02.html 400 different elements]. Some of DocBook's elements are similar to the section types in the table above:<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4542book-brainstorming2006-01-30T17:20:14Z<p>HOWCOME: /* Comparison with DocBook */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Comparison with DocBook ==<br />
<br />
[http://www.docbook.org/ docbook]<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4540book-brainstorming2006-01-30T16:53:03Z<p>HOWCOME: /* Are there enough sections? */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Comparison with DocBook ==<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4538book-brainstorming2006-01-30T16:51:52Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
The main motivation for developing a microformat for book is to encourage reuse of content for different media types. By offering people a sample HTML file and an associated style sheet, HTML can become a compelling format to use for book production. As such, the class names described in a book microformat are primarily hooks for style sheets to use, and secondarily machine-readable semantics.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4537book-brainstorming2006-01-30T16:46:25Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many section types? ===<br />
<br />
It may be argued that the list of possible section types is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microformat is a judgement call.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4536book-brainstorming2006-01-30T16:41:26Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used section types.<br />
<br />
<table><br />
<tr><th>Section&nbsp;type<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Are there too many sections? ===<br />
<br />
It may be argued that the list of possible section names is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind:<br />
<br />
* the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
* publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists. <br />
<br />
Nontheless, some of the proposed sections could be combined. for example, the forewords and the preface are often formatted in the same manner and there is no need to distinguish between the two in the style sheet. Another similar example is the list of tables and the list of figures. And having a colophon isn't that common, is it? However, all the proposed section types are in common use and the cost of listing one more type is small compared to the extra cost of differentiating between sections through other means than standardized class names. <br />
<br />
<br />
=== Are there enough sections? ===<br />
<br />
The list of possible section types is seemingly endless. For example, one could have different types of sections for different types of promotional material. The postcard, which is often included in books, is formatted very differently from the list of other books in the same series. Thus, having several promotional elements would make sense. However, in the interest of simplicity it is important to keep the number of section types at a manageable level. <br />
<br />
In the end, determining the list of section types for a microforman is a judgement call.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4535book-brainstorming2006-01-30T16:27:22Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section&nbsp;name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Complexity ===<br />
<br />
It may be argued that the list of possible section names is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind<br />
<br />
- the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
- publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4534book-brainstorming2006-01-30T16:27:04Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section&nbsp;name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
::<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code><br />
<br />
:Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Complexity ===<br />
<br />
It may be argued that the list of possible section names is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind<br />
<br />
- the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
- publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4533book-brainstorming2006-01-30T16:26:35Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section&nbsp;name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
::<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
=== Complexity ===<br />
<br />
It may be argued that the list of possible section names is too long for a "microformat". While one should always strive for simplicity, a few things should be kept in mind<br />
<br />
- the section names only affect on attribute on one element (namely, the class attribute on the div element)<br />
<br />
- publishing is an established industry and paper-based books are not likely to change. As such, the format describes something that already exists.<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4532book-brainstorming2006-01-30T16:22:10Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section&nbsp;name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
In [[boom]], the section names are used as class names on the <code><nowiki><div></nowiki></code> element:<br />
<br />
::<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4531book-brainstorming2006-01-30T16:15:23Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section&nbsp;name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
In [[boom]], the section names are used as class names on the <br />
<nowiki><div class="halftitlepage"><br />
</div></nowiki><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4530book-brainstorming2006-01-30T16:14:54Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section&nbsp;name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
In [[boom]], the section names are used as class names on the :d<br />
<nowiki><div class="halftitlepage"><br />
</div></nowiki><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4529book-brainstorming2006-01-30T16:13:05Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section&nbsp;name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
In [[boom]], the section names are used as class names on the :d<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4528book-brainstorming2006-01-30T16:12:50Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><th>Section name<th>Description<br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction.<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, afterword.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
In [[boom]], the section names are used as class names on the :d<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4527book-brainstorming2006-01-30T16:09:00Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction or a postscript<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>promotion <td>Promotional material from the publisher, e.g., a list of other titles in the same series<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
Not all books has all sections. A typical novel will have instances of around 10 sections. (My copy of Robert M. Pirsig's "Zen and the art of Motorcycle maintenance" uses these sections: frontcover, inspiration, praise, promotion, titlepage, imprint, preface, inspiration, part, chapter, uchapter.) Non-fiction books often use more sections. (My randomly chosen title from O'Reilly uses 16 sections: frontcover, halftitlepage, titlepage, imprint, toc, lof, foreword, preface, part, chapter, appendix, index, bio, colophon, promotion, backcover.)<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4526book-brainstorming2006-01-30T15:04:47Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><td>frontcover <td>The front cover<br />
<tr><td>halftitlepage<td>The halftitle page is simple with only the title of the book, and perhaps the name of the authors<br />
<tr><td>titlepage <td>The title page contains (at least) the book title, the name of the author and the name of the publisher<br />
<tr><td>imprint <td>The imprint page typically starts with a copyright statement and also contains information about where the book is printed, its ISBN number etc. <br />
<tr><td>dedication <td>The dedication page is where you find "for mom"<br />
<tr><td>inspiration <td>Many books contain inspirational quotes by other authors<br />
<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors<br />
<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors<br />
<tr><td>toc <td>Table of Contents<br />
<tr><td>lot <td>List of Tables<br />
<tr><td>lof <td>List of Figures<br />
<tr><td>chapter <td>The content itself content is typically organized in numbered chapters.<br />
<tr><td>uchapter <td>Many books contain unnumbered chapters, e.g., an introduction or a postscript<br />
<tr><td>part <td>Some books organize sets of chapters into parts<br />
<tr><td>references <td>References from the text of the book are often listed in a separate section<br />
<tr><td>appendix <td>Additional information can be organized into appendices<br />
<tr><td>biblio <td>The bibliography lists other books and sources for further reading<br />
<tr><td>glossary <td>The glossary defines terms used in the book<br />
<tr><td>index <td>The index is a list of keyword with page references<br />
<tr><td>colophon <td>The colophon page contains information about the production of the book<br />
<tr><td>backcover <td>The back cover<br />
</table><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4525book-brainstorming2006-01-30T13:55:32Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<table><br />
<tr><br />
<td> 1 <td> 2<br />
<tr><br />
<td> 3 <td> 4<br />
</table><br />
<br />
<nowiki><br />
<table><br />
<tr><th>Section name</th><th>Description</th></tr><br />
<tr><td>frontcover</td></tr><br />
</table><br />
</nowiki><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4524book-brainstorming2006-01-30T13:53:59Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<nowiki><br />
<table><br />
<tr><th>Section name</th><th>Description</th></tr><br />
<tr><td>frontcover</td></tr><br />
</table><br />
</nowiki><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4523book-brainstorming2006-01-30T13:53:18Z<p>HOWCOME: /* Parts of a book */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<nowiki><br />
<table><br />
<tr><th>Section name<th>Description</tr><br />
<tr><td>frontcover<td></tr><br />
</table><br />
</nowiki><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4522book-brainstorming2006-01-30T13:52:28Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing]. In the authoring process, it was helpful to use a set of class name on HTML element to further classify content. The classes, along with their associated structural elements, mostly served as hooks for the associated style sheet. In particular, the class names helped separate the content into different sections of a book.<br />
<br />
== Parts of a book ==<br />
<br />
The user interface of books is fairly standarized. There is typically a front cover that includes the title of the book and the name of the author(s). Inside the cover, one will find a table of contents, chapters, and index and so forth. The table below lists commonly used sections.<br />
<br />
<nowiki><table><br />
<tr><th>Section name<th>Description<br />
<tr><td>frontcover<td><br />
<br />
</table></nowiki><br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4521book-brainstorming2006-01-30T13:29:28Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing] .<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4520book-brainstorming2006-01-30T13:28:09Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [http://www.alistapart.com/boom format for book publishing .<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4519book-brainstorming2006-01-30T13:27:36Z<p>HOWCOME: /* Background */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
HTML is a general-purpose markup language used for electronic documents, mostly for onscreen reading. <br />
Some content, however, is more suitable for other kinds of presentation and being able to reuse the same content for different media types has been a design goal or HTML and CSS.<br />
<br />
It has been shown possible to use HTML as a [format for book publishing http://www.alistapart.com/boom].<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOMEhttp://microformats.org/wiki/index.php?title=book-brainstorming&diff=4518book-brainstorming2006-01-30T13:15:03Z<p>HOWCOME: /* Proposals */</p>
<hr />
<div>= Book Brainstorming =<br />
<br />
== Contributors ==<br />
<br />
* [http://people.opera.com/howcome Håkon Wium Lie]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Background ==<br />
<br />
== Proposals ==<br />
<br />
* [http://www.alistapart.com/articles/boom boom] - the Book Microformat<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-formats]]</div>HOWCOME