Re: DOCBOOK: Bibliography: citing journal articles

[Terry Allen <tallen at sonic dot net>]

| > I don't blame you; it's taken a fair amount of experience for me to
| > figure out how to use it properly.  A key insight was that one wants
| > to use citetitle instead of title here (thanks to Eduardo!).
| 
| Well, thanks, but... I think this only adds to my confusion.
| Citetitle is not allowed in biblioentry. You put it inside a

Presently, it's allowed within Artheader, as shown in my example,
and also directly within Biblioentry, through %bibliocomponent.mix;.
(RFE 7 indicates that Artheader will no longer be allowed in
Biblioentry in the future.)  But as I say, you don't want to
use it, and eventually (RFE 83) you won't be able to.  here's
a version of the same example without artheader:

<!DOCTYPE biblioentry PUBLIC "-//OASIS//DTD DocBook V3.1//EN"> 
<!-- altered with journal title inserted -->
<biblioentry>                     
<authorgroup>
  <author><firstname>W.</firstname><surname>Clinton</surname></author>
  <author><firstname>B.</firstname><surname>Jeltsin</surname></author>
</authorgroup>
<citetitle pubwork="article">Ruling the World</citetitle>
<citetitle pubwork="journal">Journal of Applied Politics</citetitle>
<volumenum>42</volumenum>
<artpagenums>113-152</artpagenums>
<pubdate>1999</pubdate>
</biblioentry>      

| bibliomisc tag, which according to the DocBook reference
| is meant for "untyped information", which doesn't sound like
| the right place for a perfectly standard and important piece
| of information.

No, I used Bibliomixed, not bibliomisc.

| I am also somewhat surprised by the use of the same tag, with just a
| different attribute, for two substantially different pieces of
| information. Especially in a huge DTD like DocBook, which normally
| provides separate tags for minute differences in meaning!

Depends on how you view similarity and difference.  One reason
for using an attribute here is that the list of genres of things
referred to by citetitle is rather long (and growing).  It's
much easier to adjust or customize an attribute value list
than (many) content models containing many elements.

regards, Terry