Subject: Re: [jats-list] BITS: Is there a canonical way to group multiple appendices and a glossary under a single 'Appendix' heading? From: Wendell Piez <wapiez@xxxxxxxxxxxxxxx> Date: Tue, 3 Sep 2013 18:33:18 -0400 |
Debbie, Ah! Thanks for the correction: I had indeed not kept in mind that app, index and glossary could only be in back, but not in the body of a book-part (which happens to indicate back matter). On the other hand ... I'm not sure I agree that this is as graceful as all that. (Now I'm with Gerrit. It does seem a bit like the tail wagging the dog. If any book-part can have back matter, then the back matter inside any one of them is its own, not the back matter in some larger undefined scope.) My own compromise might be to render the appendix and glossary as generic 'sec' (with @sec-type) so they could be in the body of the book-part. Oh dear ... I am already on record as saying that when we get to books, we need more generic structures (and thus to rely on ad-hoc semantics more) to accommodate the way books are so often sui generis by design. This is a nice example of why I think so. :-) Cheers, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^ On Tue, Sep 3, 2013 at 4:58 PM, Debbie Lapeyre <dalapeyre@xxxxxxxxxxxxxxxx> wrote: > Wendell-- > > I too, think Gerrit's "clumsy" model looks > quite acceptable. > > What you say SEEMS logical, that the content of > a book part should be in its body, but, in fact, > the elements <app>, <index>, and <glossary> > can only occur within back matter. > > The <book-part> model goes like this: > > book-part > book-part-meta? > front-matter? > body? > (para-level-stuff including table and figure and > stuff like that but NOT including index or > glossary or app)* > sec* > (book-part | xi:include)* > back? > label? > title*, > (ack | app | app-group | bio | dedication | > floats-group | fn-group | glossary | index | > index-group | notes | ref-list | sec | > sig-block | toc | toc-group)+ > > So the <book-part> model as given by Gerrit makes > perfect sense. If Gerrit had not wanted the "Appendix" > book part to be at the same hierarchical level as the > Index, the <title> element of the <back> could have > been used. > > It seems to me that this is the JATS model accommodating > some fairly unusual structures indeed, and doing it > acceptably. Gerrit does not have to rearrange his content, or > call any component something it is not. The thing with an > 'Appendix' title is a book part, and has inside it what > he said it does. That is JATS being flexible, not abusive. > > > --Debbie > > ================================================================ > Deborah A Lapeyre mailto:dalapeyre@xxxxxxxxxxxxxxxx > Mulberry Technologies, Inc. http://www.mulberrytech.com > 17 West Jefferson Street Phone: 301-315-9631 (USA) > Suite 207 Fax: 301-315-8385 > Rockville, MD 20850 > ---------------------------------------------------------------- > Mulberry Technologies: Consultancy for XML, XSLT, and Schematron > ================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [jats-list] BITS: Is there a ca, Debbie Lapeyre | Thread | Re: [jats-list] BITS: Is there a ca, Debbie Lapeyre |
Re: [jats-list] BITS: Is there a ca, Imsieke, Gerrit, le- | Date | Re: [jats-list] Coding non-consecut, Soichi Tokizane |
Month |