[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] RE: Overall fixes for bookmap for 2.0
I’m personally quite fond of (most of) the D4P pubmap approach as an alternative to bookmap – parts/chapters/appendices/etc. are defined in domains, then leveraged by several shells, allowing things like chapter maps and part maps and such.
Allows for considerably more flexibility than bookmap. Chris From: <dita@lists.oasis-open.org> on behalf of Éric Sirois <eric.sirois@ixiasoft.com> Specifically looking to allow Keydefs in a more natural position in the map versus the first instance were topicref is allowed in the current content model. Are there other things that we have ignored about bookmaps in DITA 1.3? Éric Sirois DITA Toolsmith IXIASOFT 825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1 tel + 1 514 279-4942 / toll free + 1 877 279-4942 mobile + 1 647 462-3620 eric.sirois@ixiasoft.com
/
www.ixiasoft.com
From: dita@lists.oasis-open.org [mailto:dita@lists.oasis-open.org]
On Behalf Of Éric Sirois Hi, We have a number of clients that have hit some limitations for keyref and ditavalref in bookmaps. I would like to work on a proposal that would address those limitations in DITA 2.0. Would it be possible to create a project entry in the
DITA 2.0 project? Kind regards, Éric Sirois DITA Toolsmith IXIASOFT 825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1 tel + 1 514 279-4942 / toll free + 1 877 279-4942 mobile + 1 647 462-3620 eric.sirois@ixiasoft.com
/
www.ixiasoft.com
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]