The bkbook element is the top-level element of a DITA book application, or "delivery context." The structures within it represent the setup and organization for a conventional book (at least regarding the general type used by the members of the community that provided requirements for this DTD).
None--this is the root element of the bkbook vocabulary.
bkprolog then bknotices (optional) then bkfrontm (optional) then bkbody then bkappendixes (optional) then bkbackm (optional)
Name Description Data type Default value Required? spec Provides a formal lookup table to enable this element for DITA specialization processing CDATA ' bkbook.bkbook ' no
The minimal context for a titled cover for a single chapter is:<bkbook> <bkprolog> <bktitle>How to unfriz a gromlof</bktitle> </bkprolog> <bkbody> <bkchapter> <topicref href="task32.xml"/> </bkchapter> </bkbody> </bkbook>
The bkprolog element sets up the printing context for a DITA book application. This includes the elements used to create the covers and title pages, and the metadata used to produce, track, describe, and register the book for delivery.
bkbook
bktitle then bksubtitle (optional) then bkauthor (0 or more) then bkabstract (optional) then bkcontrolinfo (optional) then prodinfo (optional) then bkpubdate (optional) then bkprintloc then bkcopyr (optional) then ( bibdesc or ldesc ) (0 or more)
No author-defined attributes.
asdf
The bknotices element organizes the two main components of information used on a formal Notices page: the conventional edition notice (bkednotices) and an annotative link to extended, special notices (bkspecialnotices).
bkbook
No author-defined attributes.
asdf
The bkfrontm (front matter) element provides a location for prefatory topics that introduce the main chapters or parts of a book. By implication, a table of contents and lists of exhibits are considered front matter, however they are usually automatically generated and therefore their inclusion can also be style-controlled rather than indicated explicitly by an author.We may need to introduce a different element than bkchapter for the structuring content of the front matter.
bkbook
Any number of bkchapter elements:
No author-defined attributes.
<bkfrontm> <bkchapter> <topicref href="task32.xml"/> </bkchapter> </bkfrontm>
bkbook
No author-defined attributes.
<bkbody> <bkchapter> <topicref href="task32.xml"/> </bkchapter> </bkbody>
The bkappendixes element...
bkbook
No author-defined attributes.
<bkappendixes> <bkappendix> <topicref href="apndx01.xml"/> </bkappendix> </bkappendixes>
The bkbackm (back matter) element provides a location for non-mainstream content of a book. By implication, an index is considered back matter, however an index is usually automatically generated and therefore its inclusion can also be style-controlled rather than indicated explicitly by an author. Therefore the only element presently defined as content for the back matter is bkglossary.
bkbook
No author-defined attributes.
<bkbackm> <bkglossary> <topicref href="task32.xml"/> </bkglossary> </bkbackm>
The bktitle element holds the main title for the book.
bkprolog
text data or basic.ph.nolink
No author-defined attributes.
<bktitle>The Making of "Plan 9 from Outer Space"
The bksubtitle element holds the subtitle for the book.
bkprolog
text data or basic.ph.nolink
No author-defined attributes.
<bksubtitle>or, Making something out of almost nothing</bksubtitle>
The bkauthor element is used to indicate the authors of a book.Perhaps we should consider also introducing the bio element which is in the metadata portion of topic dtd, as a peer in this dtd with bibdesc, ldesc, and other definitional elements. This would provide additional associative data about the author, useful for cover liner notes, etc..
bkprolog
text data or author
No author-defined attributes.
<bkauthor>John Doe</bkauthor>
The bkabstract element permits a brief description of the book, useful for indexing services such as IBM's book serving repositories.
bkprolog
text data or full.phandblock or txt.incl
No author-defined attributes.
<bkabstract> <p><q>It leaps, it creeps, it glides and slides across the floor.</q></p> <p>These words introduce the world's most chilling lyrics, the subject of this novel you won't want to put down until you have read every last word!</p> </bkabstract>
The bkcontrolinfo element provides document tracking information for the book.The copyright portion may be considered as either document tracking info or as a top level property in itself (possible a direct child of <prolog>).
bkprolog
critdates (0 or more) then permissions (optional) then status (0 or more) then copyright (0 or more)
No author-defined attributes.
No example presently.
The bkpubdate element represents the expected publication date of a book; it is reused in constructing the title of an edition notice, and in other cover locations.It might also contain thedate element from topic dtd as a form of typed data. For now, a purely string value happens to match usual practice.
bkprolog
text data
No author-defined attributes.
<bkbpubdate>March 2000</bkpubdate>
The bkprintloc element defines the printing location for a particular hardcopy production of a book. This value must be printed on the back cover of books that conform to the guidelines of many companies.The value in it should be a grammatically proper continuation of the lead-in prompt, "Printed in"... (closing punctuation will be style-controlled depending on localization rules).
bkprolog
text data
No author-defined attributes.
<bkprintloc>the United Stated of America</printloc>
The bkcopyr element allows logging of the copyright year or years for the content.This information is mapped into the copyright portion of the edition notices page.
bkprolog
text data
No author-defined attributes.
<bkcopyr>2001</bkcopyr>
The bkspecialnotices element allows the introduction to more extensive special notices that will be located elsewhere in the book (typically in the back matter), such as safety notices, RF emission notices, fair use advisories, etc..
bknotices
text data or full.phandblock or title or txt.incl
No author-defined attributes.
<bkspecialnotices> <title>Please note!</title> <p>Information that could save your life probably can't be found in this book.</p> </bkspecialnotices>
The bkednotices element provides a formal location for edition notice information, including publication dates, contact information, disclaimers, and additional copyright notices.
bknotices
text data or full.phandblock or title or txt.incl
No author-defined attributes.
Not defined yet...
Parameter Entity defining element content.The includetypes parameter entity defines the content model for the elements that directly contain topics.For authoring a "book shell," only the topicref element should be defined in this parameter entity. For validating an intermediate file comprise of the replacement content of the topicref elements, this value should include the topic types that are expected in the result document. Also, any DTDs representing those topics types should also be included into the bkbook dtd in the same manner as the compulsory topic dtd (which defines some of the prolog elements used within bkbook).
any element that can containtopicref .
Declarations for content model: ( topicref or topic ) (0 or more)
NA
NA
The bkpart element...
bkbody
title (optional) then bkpre (optional) then topicref (optional) then bkpost (optional) then bkchapter (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bkchapter element provides a formal nesting structure for topics within the body of a book.
bkfrontm , bkbody , bkpart
title (optional) then bkpre (optional) then includetypes then bkpost (optional) then bksection (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bkappendix element provides a formal nesting structure for topics within the body of a book.
bkappendixes
title (optional) then bkpre (optional) then includetypes then bkpost (optional) then bksection (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bkglossary element provides a formal nesting structure for topics within the body of a book.
bkbackm
title (optional) then bkpre (optional) then includetypes then bkpost (optional) then bksection (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bksection element provides a formal nesting structure for topics within the body of a book.
bkchapter , bkappendix , bkglossary
title (optional) then bkpre (optional) then includetypes then bkpost (optional) then bksubsection (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bksubsection element provides a formal nesting structure for topics within the body of a book.
bksection
title (optional) then bkpre (optional) then topicref (optional) then bkpost (optional) then bksubsect1 (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bksubsect1 element provides a formal nesting structure for topics within the body of a book.
bksubsection
title (optional) then bkpre (optional) then topicref (optional) then bkpost (optional) then bksubsect2 (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bksubsect2 element provides a formal nesting structure for topics within the body of a book.
bksubsect1
title (optional) then bkpre (optional) then topicref (optional) then bkpost (optional) then bksubsect3 (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bksubsect3 element provides a formal nesting structure for topics within the body of a book.
bksubsect2
title (optional) then bkpre (optional) then topicref (optional) then bkpost (optional) then bksubsect4 (0 or more)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bksubsect4 element is the deepest of the allowed nesting within the book delivery context. This limit enforces a general guideline for authors and prevents arbitrarily deep nesting.
bksubsect3
title (optional) then bkpre (optional) then topicref (optional) then bkpost (optional)
Name Description Data type Default value Required? id Description for element id ID #IMPLIED no
asdf
The bkpre element provides a location for initial discourse leading up to the first instance of a topic reference.
bkpart , bkchapter , bkappendix , bkglossary , bksection , bksubsection , bksubsect1 , bksubsect2 , bksubsect3 , bksubsect4
text data or full.phandblock or txt.incl
No author-defined attributes.
asdf
The bkpost element provides a location for closing discourse following a topic reference.
bkpart , bkchapter , bkappendix , bkglossary , bksection , bksubsection , bksubsect1 , bksubsect2 , bksubsect3 , bksubsect4
text data or full.phandblock or txt.incl
No author-defined attributes.
asdf
The topicref element provides a way to name a topic that is intended to be referenced as content in place of this element. The effect is equivalent to an "external entity reference."Topicref must always refer to a valid DITA topic or specialization thereof.
bkpart , bksubsection , bksubsect1 , bksubsect2 , bksubsect3 , bksubsect4
no content
Name Description Data type Default value Required? href Description for element href CDATA #REQUIRED yes parse Description for element parse (xml | parse | cdata) xml yes %univ-atts; A set of related attributes, described at %univ-atts; parameter entity See the extended discussion in the Topic DTD Reference. NA
Given the need to imbed the local topic file, task32.xml:<topicref href="task32.xml"/>This example refers to a file nested within a parent topic. The reference is to the nested file's id, which in this case might be the id of the same topic as referenced literally in the previous example.<topicref href="mastertasks.xml#task32"/>