book-brainstorming - Revision history

HOWCOME: /* Parts of a book */

2018-02-21T08:57:14Z

Parts of a book

← Older revision		Revision as of 08:57, 21 February 2018
Line 34:		Line 34:
	<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors		<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors
	<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors		<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors
	<tr><td>toc <td>Table of Contents [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) why is this abbreviated. 'tableofcontents' is more clear.		<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
	<tr><td>lot <td>List of Tables [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoftables' is more clear.		<tr><td>lot <td>List of Tables [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoftables' is more clear.
	<tr><td>lof <td>List of Figures [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoffigures' is more clear.		<tr><td>lof <td>List of Figures [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoffigures' is more clear.

Sfsheath: /* Parts of a book */ typo: "has" should have been "have"

2010-09-17T16:31:41Z

Parts of a book: typo: "has" should have been "have"

← Older revision		Revision as of 16:31, 17 September 2010
Line 56:		Line 56:
	:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code>		:<code><nowiki><div class="halftitlepage"><h1>Title</h1></div></nowiki></code>

	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.)		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.)

	=== Are there too many section types? ===		=== Are there too many section types? ===

Sfsheath: added a 'catalog' class.

2010-09-17T16:25:41Z

added a 'catalog' class.

← Older revision		Revision as of 16:25, 17 September 2010
Line 40:		Line 40:
	<tr><td>chapter <td>The content itself is typically organized in numbered chapters		<tr><td>chapter <td>The content itself is typically organized in numbered chapters
	<tr><td>part <td>Some books organize sets of chapters into parts		<tr><td>part <td>Some books organize sets of chapters into parts
			<tr><td>catalog <td>The section of a book listing discrete, similarly structured descriptive entries.
	<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book		<tr><td>afterword <td>An additional, often unnumbered chapter at the end of the book
	<tr><td>bibliography <td>The bibliography lists other books and sources for further reading		<tr><td>bibliography <td>The bibliography lists other books and sources for further reading

Sfsheath: /* Parts of a book */ type

2010-09-16T17:14:48Z

Parts of a book: type

← Older revision		Revision as of 17:14, 16 September 2010
Line 34:		Line 34:
	<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors		<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors
	<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors		<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors
	<tr><td>toc <td>Table of Contents [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) why is this abbreviated. '~~tableofcontent~~' is more clear.		<tr><td>toc <td>Table of Contents [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) why is this abbreviated. 'tableofcontents' is more clear.
	<tr><td>lot <td>List of Tables [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoftables' is more clear.		<tr><td>lot <td>List of Tables [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoftables' is more clear.
	<tr><td>lof <td>List of Figures [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoffigures' is more clear.		<tr><td>lof <td>List of Figures [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoffigures' is more clear.

Sfsheath: /* Background */ more language extending the scope of the mf.

2010-09-16T15:51:07Z

Background: more language extending the scope of the mf.

← Older revision		Revision as of 15:51, 16 September 2010
Line 18:		Line 18:
	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.		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.

	~~[[User:Sfsheath\|Sfsheath]] 20:32, 13 September 2010 (UTC) Could this microformat~~ be ~~generalized~~ for ~~works other than books? Many forms~~ of ~~relatively long~~ prose ~~(scholarly~~ articles~~) could also use some~~ of the ~~class names proposed here. Perhaps a better name "text class"~~ microformat.		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.

	== Parts of a book ==		== Parts of a book ==

Sfsheath: /* Introduction */ extending the scope of the microformat to forms of extended prose beyond books.

2010-09-16T15:44:46Z

Introduction: extending the scope of the microformat to forms of extended prose beyond books.

← Older revision		Revision as of 15:44, 16 September 2010
Line 3:		Line 3:
	== Introduction ==		== Introduction ==

	Given analysis and research done on [[book-examples]] and [[book-formats]], this page documents various thoughts and strawman proposals for a book microformat.		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.

	== Table of Contents ==		== Table of Contents ==

Sfsheath: /* Parts of a book */

2010-09-13T20:33:29Z

Parts of a book

← Older revision		Revision as of 20:33, 13 September 2010
Line 34:		Line 34:
	<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors		<tr><td>foreword <td>Many books contain a foreword written by someone other than the authors
	<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors		<tr><td>preface <td>The preface is written by the authors and often contains an acknowledgement of other contributors
	<tr><td>toc <td>Table of Contents		<tr><td>toc <td>Table of Contents [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) why is this abbreviated. 'tableofcontent' is more clear.
	<tr><td>lot <td>List of Tables		<tr><td>lot <td>List of Tables [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoftables' is more clear.
	<tr><td>lof <td>List of Figures		<tr><td>lof <td>List of Figures [[User:Sfsheath\|Sfsheath]] 20:33, 13 September 2010 (UTC) 'listoffigures' is more clear.
	<tr><td>introduction <td>An introductory chapter		<tr><td>introduction <td>An introductory chapter
	<tr><td>chapter <td>The content itself is typically organized in numbered chapters		<tr><td>chapter <td>The content itself is typically organized in numbered chapters

Sfsheath: /* Background */

2010-09-13T20:32:08Z

Background

← Older revision		Revision as of 20:32, 13 September 2010
Line 17:		Line 17:

	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.		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.

			[[User:Sfsheath\|Sfsheath]] 20:32, 13 September 2010 (UTC) Could this microformat be generalized for works other than books? Many forms of relatively long prose (scholarly articles) could also use some of the class names proposed here. Perhaps a better name "text class" microformat.

	== Parts of a book ==		== Parts of a book ==

Crnixon: /* Book Brainstorming */ Removed spam

2009-07-04T19:08:08Z

Book Brainstorming: Removed spam

← Older revision		Revision as of 19:08, 4 July 2009
Line 1:		Line 1:
	= Book Brainstorming =		= Book Brainstorming =

	~~T05xsn <a href="http://hwhargdbbotu.com/">hwhargdbbotu</a>, [url=http://azdowmkvliuh.com/]azdowmkvliuh[/url], [link=http://pqukdokzkbbi.com/]pqukdokzkbbi[/link], http://aoalhgsuhfok.com/~~

	== Introduction ==		== Introduction ==

92.66.66.131: /* Contributors */

2008-11-17T16:27:10Z

Contributors

← Older revision		Revision as of 16:27, 17 November 2008
Line 1:		Line 1:
	= Book Brainstorming =		= Book Brainstorming =

	== ~~Contributors ==~~		T05xsn <a href="http://hwhargdbbotu.com/">hwhargdbbotu</a>, [url=http://azdowmkvliuh.com/]azdowmkvliuh[/url], [link=http://pqukdokzkbbi.com/]pqukdokzkbbi[/link], http://aoalhgsuhfok.com/

	* [http://~~people.opera~~.com/~~howcome Håkon Wium Lie~~]
	* [http://~~tantek~~.com/~~log~~/ ~~Tantek Çelik~~]
	* Bert Bos

	== Introduction ==		== Introduction ==