[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Bookmap implementation
Refer to "bookmap.mod" for the element declaration of chapter and entity declaration for % chapter-atts, I won't bother duplicating that information here, but folks can look at the bookmap.mod themselves to see the definitions.
Chapter does not contain special chapter-level metadata or markup which forces the specialization of <topicref> to <chapter>.
From: France Baril [mailto:France.Baril@ixiasoft.com]
Sent: Friday, February 09, 2007 2:00 PM
To: dita@lists.oasis-open.org
Subject: Bookmap implementationHi, I had looked at the bookmap implementation earlier and had found it pretty nice, but lately I started looking at it from an implementation point of view.Bang, I was slapped in the face. I know it's late in the process, but I thought I should say something anyway.In order to allow embedding maps in maps and to ease manipulation of a single map. I would suggest that we drop the structure:BookmapprefacechapterchapterchapterappendiceappendiceAnd get something that is more like:BookmapPrefaceChapters (specialized from topicgroup?)topicreftopicreftopicreftopicrefAppendices (specialized from topicgroup?)topicreftopicrefWith the current structure, if I want to add a level around the first 10 chapters, I have to change the element name for all 10 topicrefs that were previously identified as chapters. Moreover, it becomes hard to implement maps in maps because you get multiple chapter levels.France, who just woke up...P.S. Feel free to slap me in the face again for bringing this up now!!!!
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.441 / Virus Database: 268.17.32/677 - Release Date: 2/8/2007 9:04 PM
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]