https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=SfsheathMicroformats Wiki - User contributions [en]2026-04-30T02:50:17ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=irc-people&diff=43125irc-people2010-09-21T12:52:22Z<p>Sfsheath: </p>
<hr />
<div>A list of [[irc|IRC]] regulars, sorted by nick, and their normal timezones (winter/summer).<br />
<br />
* {{irc user|Amodal1| amodal1|-0500/-0600}}<br />
* {{irc user|Adam Ballai|AdamBallai|-700/-700}}<br />
* {{irc user|Adam Craven|AdamCraven|+0000}}<br />
* {{irc user|Alenonimo|Alenonimo|-0300}}<br />
* {{irc user|Alexander Graf|AlexanderGraf|+0100}}<br />
* {{irc user|Axelator|ax|-0700}}<br />
* {{irc user|Tomasino|aloneone|-0500}}<br />
* {{irc user|AmanuelTewolde|Amanuel|-0500/-0400}}<br />
* {{irc user|Amette|amette|+1000}}<br />
* {{irc user|Amir Guindehi|AmirGuindehi|+1000}}<br />
* {{irc user|Andr3|andr3|+0000}}<br />
* {{irc user|Ajaswa|Andrew Jaswa|-0500}}<br />
* {{irc user|AndrewDisley|AndrewDisley|+0000}}<br />
* {{irc user|Andrii Ponomarov|Andrii|+0300}}<br />
* {{irc user|AngeloGladding|angelogladding|-0800/-0700}}<br />
* {{irc user|AnselHalliburton|anselxyz|-0800/-0700}}<br />
* {{irc user|Ashe Dryden|Ashe|-600}}<br />
* {{irc user|Atamido|Atamido|-0600/-0500}}<br />
* {{irc user|Barce|Barce|-0800/-0700}}<br />
* {{irc user|Azathoth|Florian Beer|+1000}}<br />
* {{irc user|Tyler Roehmholdt|Baristo|-0800/-0700}}<br />
* {{irc user|Belling|Belling|-0800/-0700}}<br />
* {{irc user|BenjaminCarlyle|BenjaminCarlyle|+1000}}<br />
* {{irc user|HenriBergius|bergie|+0200/+0300}}<br />
* {{irc user|Ben Ward|BenWard|-0800/-0700}}<br />
* {{irc user|BenWest|bewest|-0800/-0700}}<br />
* {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}<br />
* {{irc user|Robert|blueace|+0100}}<br />
* {{irc user|Robert|blueace|+0100}}<br />
* {{irc user|BluesMoon|bluesmoon|+0530}}<br />
* {{irc user|BobChao|BobChao|+0800}}<br />
* {{irc user|Bob Jonkman|BobJonkman|-0500/-0400}}<br />
* {{irc user|Oli|boblet|+0900}}<br />
* {{irc user|Boneill|boneill|+0000}}<br />
* {{irc user|Brian|briansuda|+0000}}<br />
* {{irc user|TimT|bringo|-0800/-0700}}<br />
* {{irc user|Briski|Briski|+0000}}<br />
* {{irc user|BryanL|BryanL|-0500/-0400}}<br />
* {{irc user|BryanRieger|Bryan Rieger|+0000}}<br />
* {{irc user|Bug-E|Bug-E|+0200}}<br />
* {{irc user|CarlaHufstedler|carlamagpie|-0500/-0400}}<br />
* {{irc user|Colin_Barrett|cbarrett|-1000}}<br />
* {{irc user|Cognizance|Cognizance|-0800/-0700}}<br />
* {{irc user|ColinDDevroe|cdevroe|-0500/-0600}}<br />
* {{irc user|CoryGwin|corygwin|-0500/-0600}}<br />
* {{irc user|Cgriego|cgriego|-0600/-0500}}<br />
* {{irc user|Charlvn|Charl|+0200/+0200}}<br />
* {{irc user|CharlesRoper|charles_r|0000/+0100}}<br />
* {{irc user|Chris_Cressman|Chris Cressman|-0500/-0400}}<br />
* {{irc user|ChristopherStJohn|cks|-0600/-0500}}<br />
* {{irc user|JeremyBoggs|clioweb|-5000/-4000}}<br />
* {{irc user|Cloud|Cloud|+0000}}<br />
* {{irc user|Cruster|cruster|+0200}}<br />
* {{irc user|Csarven|csarven|-0500/-0400}}<br />
* {{irc user|ChrisBrentano|ctb|-0800/-0700}}<br />
* {{irc user|DanC|DanC|-0600/-0500}}<br />
* {{irc user|DanielBurka|DanielBurka|-0400}}<br />
* {{irc user|DanielJohnLewis|danieljohnlewis|0000}}<br />
* {{irc user|DannyAyers|danja|+0100/+0200}}<br />
* {{irc user|Dave Cardwell|davecardwell|+0000}}<br />
* {{irc user|DavidMead|DavidMead|-0400}}<br />
* {{irc user|DavidRussell|davidrussell|-0600/-0500}}<br />
* {{irc user|DBounds|Darren Bounds|-0500}}<br />
* {{irc user|Ddonat|David Gratton|-0800/-700}}<br />
* {{irc user|DenisDefreyne|ddfreyne|+0100/+0200}}<br />
* {{irc user|DeanEro|deanero|-0800/-0700}}<br />
* {{irc user|DeepText|Deep Text|-0800/-0700}}<br />
* {{irc user|DerrickPallas|DerrickPallas|-0800/-0700}}<br />
* {{irc user|DimitriGlazkov|dglazkov|-0600/-0500}}<br />
* {{irc user|DiegoBudny|DiegoBudny|<small>-unspecified-</small>}}<br />
* {{irc user|DKerzman|DKerzman|-0600}}<br />
* {{irc user|Dan Kubb|dkubb|-0800/-0700}}<br />
* {{irc user|Dreamisle|dreamisle|-0500}}<br />
* {{irc user|DrErnie|DrErnie|-0800/-0700}}<br />
* {{irc user|DrewMcLellan|drewinthehead|+0000/+0100}}<br />
* {{irc user|DrewBell|droob|-0600/-0500}}<br />
* {{irc user|DimitriosZachariadis|dzach|+0200/+0300}}<br />
* {{irc user|Ed Summers|edsu|-0500/-0400}}<br />
* {{irc user|Enric|Enric|-0800/-0700}} (alt sp "enric")<br />
* {{irc user|Evan|evanpro|-0500}}<br />
* {{irc user|Evan|e_s_p|-0500}}<br />
* {{irc user|Ket Majmudar|ethicaljunction|+0100}}<br />
* {{irc user|EdwardWelker|ewelker|-0500}}<br />
* {{irc user|ChrisMessina|factoryjoe|-0800/-0700}}<br />
* {{irc user|Fil|Fil|+0200}}<br />
* {{irc user|CFinke|Finke|-0700/-0600}}<br />
* {{irc user|MarkoMrdjenovic|friedcell|+0100/+0200}}<br />
* {{irc user|GarethR|garethr|+0000/+0100}}<br />
* {{irc user|GeorgeBrock|georgebrock|+0000/+0100}}<br />
* {{irc user|Grantbow|Grantbow|-0800/-0700}}<br />
* {{irc user|Griffin|Griffin|-0600/-0500}}<br />
* {{irc user|Guillaume Lebleu|glebleu|-0800}}<br />
* {{irc user|Aubergine10|Guy Fraser|+0100/+0000}}<br />
* {{irc user|HenrichPoehls|HenrichP|+0100}}<br />
* {{irc user|IanHickson|Hixie|-0800/-0700}}<br />
* {{irc user|Hlb|hlb|+0800-0700}}<br />
* {{irc user|EdwardOConnor|hober|-0800/-0700}}<br />
* {{irc user|Ichigo|ichigo|+1000}}<br />
* {{irc user|Alper|illustir|+0100}}<br />
* {{irc user|Inkbase|inkbase|-0800/-0700}}<br />
* {{irc user|IwaiMasaharu|iwaim|+0900}}<br />
* {{irc user|Izo|IZO|<small>-unspecified-</small>}}<br />
* {{irc user|Jabz|Jabz|+0000}}<br />
* {{irc user|JamieKnight|JamieKnight|+1000/0000}}<br />
* {{irc user|JayMyers|jaymyers|-0600/-0500}}<br />
* {{irc user|JoeGregorio|jcgregorio|<small>-unspecified-</small>}}<br />
* {{irc user|WizardIsHungry|jcw9|-0500/-0400}}<br />
* {{irc user|Adactio|Jeremy Keith|+0000}}<br />
* {{irc user|jrodgers|JesseRodgers|-0500}}<br />
* {{irc user|JasonK|jkridner|-0600/-0500}}<br />
* {{irc user|JeffMcNeill|jeffmcneill|-1000}}<br />
* {{irc user|JimboJW|jimbojw|-0600/-0500}}<br />
* {{irc user|Jonathan_Arkell|jonnay|-0700/0600}}<br />
* {{irc user|JonathanMalek|JonathanMalek|-0800/-0700}}<br />
* {{irc user|JosephHolsten|josephholsten|-0600/-0500}}<br />
* {{irc user|JulianStahnke|julianstahnke|+0000}}<br />
* {{irc user|Kapowaz|kapowaz|+0000/+0100}}<br />
* {{irc user|Keri Henare|kerihenare|+1200}}<br />
* {{irc user|KevBurnsJr|kevburnsjr|-0800}}<br />
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)<br />
* {{irc user|RyanKing|kingryan|-0800/-0700}}<br />
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC<br />
* {{irc user|Lachlan Hunt|Lachy|+1000/+1100}}<br />
* {{irc user|Levitation|levitation[A]|+0200/+0300}}<br />
* {{irc user|Linmic|linmic|+0800-0700}}<br />
* {{irc user|MarkNg|madness|+0000/+0100}}<br />
* {{irc user|Mark Mansour|Mark Mansour|+1100}}<br />
* {{irc user|MarkNormanFrancis|Mark Norman Francis|+0000/+0100}}<br />
* {{irc user|Maddiin|Martin Czura|+0100}}<br />
* {{irc user|MattBowen|Matt Bowen|-0500/-0400}}<br />
* {{irc user|Groningen|Matthias Kluth|+0100}}<br />
* {{irc user|MattisManzel|Mattis Manzel|+0100/+0200}}<br />
* {{irc user|CiaranMc|McNulty|+0000/+0100}}<br />
* <span class="vcard"><span class="fn org">[[mfbot]]</span> - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.</span><br />
* {{irc user|MicroAngelo|MicroAngelo|+0000/+0100}}<br />
* {{irc user|Mike|Michael McCracken(mmc)|-0800/-0700}}<br />
* {{irc user|MikeKaply|mkaply|-0600/-0500}}<br />
* {{irc user|SteveIvy|monkinetic/redmonk|-0700}}<br />
* {{irc user|MWTE|mwte|+0000/+0100}}<br />
* {{irc user|RobManson|nambor|+1000}}<br />
* {{irc user|Naterkane|Nater Kane|-0500}}<br />
* {{irc user|Nelix|nelix|+1000}}<br />
* {{irc user|neuro|neuro|<small>-unspecified-</small>}}<br />
* {{irc user|Niekie|niekie|+0100/+0200}}<br />
* {{irc user|NTollervey|ntoll|+0000/+0100}}<br />
* {{irc user|Pawlik|pawlik|+0100/+0200}}<br />
* {{irc user|Andy Pemberton|pembertona|-0500/-0400}}<br />
* {{irc user|Phae|Phae|+0000/+0100}}<br />
* {{irc user|pius|Pius Uzamere|+0500}}<br />
* {{irc user|PriitLaes|plaes|+0200/+0300}}<br />
* {{irc user|ChrisCasciano|pnhChris|-0500/-0400}}<br />
* {{irc user|Hugopeixoto|Politoed|+0000/+0100}}<br />
* {{irc user|PetarPopov|popov|-0800/-0700}}<br />
* {{irc user|Pfefferle|pfefferle|+0100/+0200}}<br />
* {{irc user|Lauren Scime|pseudowish|-0800/-700}}<br />
* {{irc user|DavidOsolkowski|qid|-0500}}<br />
* {{irc user|RCanine|RCanine|-0500/-0400}}<br />
* {{irc user|Remi|Remi|-0500/-0400}}<br />
* {{irc user|ZachCarter|riah|-0500/-0400}}<br />
* {{irc user|RobertBachmann|RobertBachmann|+0100/+0200}}<br />
** Office hours: <s>Wednesday, 18:00-20:00 UTC</s> (Currently no office hours}}<br />
* {{irc user|RobLinton|RobLinton|-0800/-0700}}<br />
* {{irc user|Ronnos|Ron Kok|+0000}}<br />
* {{irc user|SamJohnston|samj|+0100/+0200}}<br />
* {{irc user|SarahWorsham|sazbean|-0500/-0400}}<br />
* {{irc user|sebheath|sebheath|-0500/-0400}}<br />
* {{irc user|ScottNelle|snelle|-0500/-0400}}<br />
* {{irc user|ScottRozic|gravitas|-0500/+0100}}<br />
* {{irc user|Dana Benson|Snowden|-0800/-0700}}<br />
* {{irc user|SinDoc|SinDoc|+0100/+0200}}<br />
* {{irc user|Savell Martin|Savell|+0000/+0000}}<br />
* {{irc user|Smackman|Steve Farrell|-0800/-0700}}<br />
* {{irc user|SpikeUK|SpikeUK|+0000/+0100}}<br />
* {{irc user|Steve Ganz|SteveGanz|-0800/-0700}}<br />
* {{irc user|Stii|Stii|+0200 GMT}}<br />
* {{irc user|ReinierZ|surial|+0100 GMT}}<br />
* {{irc user|SuperPhly|SuperPhly|-600/-500}}<br />
* {{irc user|SyedSRahman|syedsrahman|+0530}}<br />
* <span class="vcard"><span class="fn">sym[[User:LynX|lynX]]</span></span> or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100}}<br />
* {{irc user|DavidLehn|taaz|-0500/-0400}}<br />
* {{irc user|Tantek|Tantek|-0800/-0700}}<br />
* {{irc user|tbmartin|tbmartin|-0800/-0700}}<br />
* {{irc user|themattharris|themattharris|-0800/-0700}}<br />
* {{irc user|Wojciech|theanxy|+0100/+0200}}<br />
* {{irc user|TheJbf|thejbf|+0100/+0200}}<br />
* {{irc user|Thomasknoll|thomasknoll|-0800}}<br />
* {{irc user|thuddwhirr|thuddwhirr|-0800/-0700}}<br />
* {{irc user|TobyInk|tobyink|+0000/+0100}}<br />
* {{irc user|Trovster|trovster|-0800/-0700}}<br />
* {{irc user|Vadania|vadania|-0600/-0700}}<br />
* {{irc user|Vant|vant|+0900}}<br />
* {{irc user|venkateswaran|vensilver|+5.30 GMT}}<br />
* {{irc user|Victor|victor|+0100/+0200}}<br />
* {{irc user|V-I-P|V-I-P|+0100/+0200}}<br />
* {{irc user|KrissWatt|VoodooChild|+0000/+0100}}<br />
* {{irc user|WebOrganics|weborganics|+0100}}<br />
* {{irc user|JacksonWilkinson|whafro|-0500/-0400}}<br />
* {{irc user|Richard Conyard|WhiskeyM|+0000}}<br />
* {{irc user|Veeliam|William Lawrence|-0800/-0700}}<br />
* {{irc user|StevenWoods|woodss|+0000 GMT}}<br />
* {{irc user|Ianloic|yakk|-0800/-0700}}<br />
* {{irc user|LarsStrojny|mastaYoda|+0100}}<br />
* {{irc user|ZimbaTm|zimbatm|+0100}}<br />
* {{irc user|FoundAtion|Foundation|-0800}}<br />
* {{irc user|PJKix|pjkix|-0800/-700}}<br />
* {{irc user| ChrisBroadfoot|broady|+1000}}<br />
* {{irc user|Natalie Downe|NatBat|+0000}}<br />
* {{irc user|Dotjay|dotjay|+0000}}<br />
* {{irc user|PeterHellberg|zil|+0100}}<br />
* {{irc user|Kiryl Zhybul|zkv|+0400}}<br />
* {{irc user|ScottThorpe|Salve|-0800/-0700}}<br />
* {{irc user|Dane|imdane|-0600/-0500}}<br />
* {{irc user|ThomasLoertsch|tl|+0100/+0200}}<br />
* {{irc user|Francisco Bernardo|frantic0|+0100/+0200}}<br />
* {{irc user|Steven Osborn|steve918|-0700/-0800}}<br />
* {{irc user|Trodrigues|trodrigues|+0000}}<br />
* {{irc user|Epicurious|epicurious|+0000/+0100}}</div>Sfsheathhttps://microformats.org/wiki/index.php?title=book-brainstorming&diff=43111book-brainstorming2010-09-17T16:31:41Z<p>Sfsheath: /* Parts of a book */ typo: "has" should have been "have"</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.<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>Sfsheathhttps://microformats.org/wiki/index.php?title=book-brainstorming&diff=43110book-brainstorming2010-09-17T16:25:41Z<p>Sfsheath: added a 'catalog' class.</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.<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 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>Sfsheathhttps://microformats.org/wiki/index.php?title=book-brainstorming&diff=43108book-brainstorming2010-09-16T17:14:48Z<p>Sfsheath: /* Parts of a book */ type</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.<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>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>Sfsheathhttps://microformats.org/wiki/index.php?title=book-brainstorming&diff=43104book-brainstorming2010-09-16T15:51:07Z<p>Sfsheath: /* Background */ more language extending the scope of the mf.</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. 'tableofcontent' is more clear.<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>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>Sfsheathhttps://microformats.org/wiki/index.php?title=book-brainstorming&diff=43103book-brainstorming2010-09-16T15:44:46Z<p>Sfsheath: /* Introduction */ extending the scope of the microformat to forms of extended prose beyond books.</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 />
[[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.<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. 'tableofcontent' is more clear.<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>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>Sfsheathhttps://microformats.org/wiki/index.php?title=Main_Page&diff=43096Main Page2010-09-15T17:17:39Z<p>Sfsheath: Undo revision 43094 by Spanishproperty01 (Talk)</p>
<hr />
<div><entry-title>Welcome to the microformats wiki!</entry-title><br />
__TOC__<br />
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.<br />
<br />
==Introduction==<br />
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.<br />
<br />
== Get Started==<br />
To get started with microformats:<br />
<br />
* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definition==<br />
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.<br />
<br />
Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.<br />
<br />
* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].<br />
<br />
== How to contribute ==<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
* [[get-started|Get started]] by adding microformats to your website, services, and products.<br />
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.<br />
* Write a [[testimonial]].<br />
* Do something on the [[to-do|to do list]].<br />
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).<br />
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.<br />
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].<br />
<br />
This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.<br />
<br />
== Specifications ==<br />
The list of current, stable [[microformats|Microformats]] open standard specifications.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''<br />
<br />
== Drafts ==<br />
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.<br />
<br />
* [[adr|adr]] - for marking up address information<br />
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)<br />
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)<br />
* [[haudio|hAudio]]<br />
* [[hlisting|hListing]] - open, distributed listings<br />
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio. <br />
* [[hnews|hNews]]<br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - for cooking+baking recipes<br />
* [[hresume|hResume]] - for publishing resumes and CVs<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache<br />
* [[rel-home]] - indicate a hyperlink to the homepage of the site<br />
* [[rel-payment]] - indicate a payment mechanism<br />
* [[robots-exclusion|robots exclusion]]<br />
<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].<br />
<br />
== Examples ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Resources ==<br />
See [[resources]].<br />
<br />
== User centric development ==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
== Shared work areas ==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
== Tools, test cases, additional research ==<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.<br />
<br />
== Microformats wiki translations ==<br />
<span id="microformats_wiki_translations_in_other_languages">You may read and edit microformats articles in many other languages:</span><br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* languages just started<br />
** [[Main_Page-fa|<span lang="fa">پارسی</span> (Farsi)]] {{NewMarker}}<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
* elsewhere<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.<br />
<br />
See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].</div>Sfsheathhttps://microformats.org/wiki/index.php?title=book-formats&diff=43092book-formats2010-09-14T14:15:17Z<p>Sfsheath: typo, alphabetized list of formats, added epub.</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 formats 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.idpf.org/specs.htm Epub] - 'ePub' is the generic name for a set of specifications published by the International Digital Publishing Forum.<br />
* [http://www.bl.uk/news/2007/pressrelease20071022.html RDA: Resource Description and Access]<br />
* [http://www.tei-c.org/ TEI]<br />
<br />
== See Also ==<br />
<br />
* [[book-examples]]<br />
* [[book-brainstorming]]</div>Sfsheathhttps://microformats.org/wiki/index.php?title=book-brainstorming&diff=43088book-brainstorming2010-09-13T20:33:29Z<p>Sfsheath: /* 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.<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 />
[[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.<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. 'tableofcontent' is more clear.<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>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>Sfsheathhttps://microformats.org/wiki/index.php?title=book-brainstorming&diff=43087book-brainstorming2010-09-13T20:32:08Z<p>Sfsheath: /* Background */</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.<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 />
[[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.<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>Sfsheathhttps://microformats.org/wiki/index.php?title=User:Sfsheath&diff=43016User:Sfsheath2010-08-31T19:00:32Z<p>Sfsheath: public domain template</p>
<hr />
<div>{{Template:cc-public-domain-release}}</div>Sfsheath