[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Fwd: [dita-comment] RE: noting a few limitations in my FrameMaker-to-DITA migration effort
It seems to me that the easy solution on this would be to allow multiple <appendices> elements in the bookmap. <appendices> would then be the "equivalent" to <part> as <appendix> is the "equivalent" to <chapter>. It would have the same caveat as part -- you can use part or chapter or nest chapter in part, but once you nest chapter in part, you can't have just a chapter floating. Similarly you could use appendices or appendix or nest appendix in appendices, but once you nest appendix in appendices, you can't have the chapter floating.
That said, I also agree with Eliot that allowing appendix in a part is something that I've seen need for at some clients. Doing that would essentially eliminate the need for <appendices> I think. You would just use <part> with nothing but <appendix> elements if that was what you needed.
Dawn
ïOn 5/4/19, 8:07 AM, "dita@lists.oasis-open.org on behalf of Eliot Kimber" <dita@lists.oasis-open.org on behalf of [email protected]> wrote:
I don't think I've ever seen a publication that had appendixes organized into parts. It would be more likely for each part to have its own appendixes section (which is a change I would make if I were designing BookMap today).
Allowing <part> within <appendixes> would be a pretty big change to the content model as it would effectively allow an entire publication to occur within <appendixes>. So you'd probably want to defin <appendixes-part> or something, at which point the cost becomes pretty hard to justify.
I would take this as input to the general requirements for the to-be-proposed "publication map".
Cheers,
E.
--
Eliot Kimber
http://contrext.com
On 5/3/19, 7:28 PM, "Kristen James Eberlein" <dita@lists.oasis-open.org on behalf of [email protected]> wrote:
Latest e-mail from dita-comment. Thoughts about a response?
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com <http://www.eberleinconsulting.com>
+1 919 622-1501; kriseberlein (skype)
-------- Forwarded Message --------
Subject:
[dita-comment] RE: noting a few limitations in my
FrameMaker-to-DITA migration effort
Date:
Tue, 30 Apr 2019 19:24:43 +0000
From:
Chris Papademetrious
<Christopher.Papademetrious@synopsys.com> <mailto:Christopher.Papademetrious@synopsys.com>
To:
'dita-comment@lists.oasis-open.org'
<dita-comment@lists.oasis-open.org> <mailto:dita-comment@lists.oasis-open.org>
As a follow-up to my 12/7/2018 post, it *would*
actually be nice to have the <bookmap> content model
expanded to allow <part> elements within large
<appendix> sets. I officially change my position on that
from âno action requestedâ to âI want itâ. :)
Adding the following:
*****
Item 3: Please allow <example>
elements within <section> elements.
I am specializing the <section>
element to represent a particular structure within a topic
(such as short description, syntax, arguments, return results,
and examples). For example,
<topic id=âfooâ>
<title>My Topic Title</title>
<body>
<description-section>
</description-section>
<syntax-section>
</syntax-section>
<arguments-section>
</arguments-section>
<example-section>
<example>
<title>Single-Phase
Example</title>
...figures, tables, or other
content...
</example>
<example>
<title>Multi-Phase
Example</title>
...figures, tables, or other
content...
</example>
</example-section>
<license-section>
</license-section>
</body>
<related-links>...</related-links>
</topic>
However, the <section> element
doesnât allow <example> within it, which blocks me from
using a proper structure for the examples section. Using
nested <topic>s instead of <section>s isnât an
option because then the <related-links> must be first in
the topic, then the nested-and-specialized topics which
actually contain the information.
For specialization purposes, please allow
<example> in <section>!
-----
Chris Papademetrious
Tech Writer, Implementation Group
(610) 628-9718 home office
(570) 460-6078 cell
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]